x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 115 subscribers
  • Views 1075 views
  • Users 0 members are here
Browse Forums
Announcements
269
topics
260
replies
Databases and Operating Systems
759
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
183
topics
410
replies
wheumann

Payroll Cost Center Override on Taxes

SOLVED
Posted By

Client is running Sage 300 version 2020, but apparently this problem has been haunting them for years, in prior versions.  A cost center override comes into play on employer tax expense, and we can’t figure out why.  This happens only on earnings codes where no cost center override is specified at the pay line level (because we don't want to override, or we're OK with using the default override). 

Example:  Employee has default Cost Center Override 20. 

Distribution Code MC, in use on his USMED tax line, goes to Account 7710.00.10. 

Taxes have no Cost Center  Override feature.  

And yet, you can see in this snipped from RVSPY, it is applying an override of “00”. 

 

 

UP0009: UPDIST   [16:45:14.87].Put(view=0x0AF4579C, field=1, size=6, verify=0, buffer='\55\53\4d\45\44\20' -> 'USMED ')

    0 <==[16:45:14.87;t=0;ovh=0] {}

    UP0009: UPDIST   [16:45:14.87].Put(view=0x0AF4579C, field=2, size=6, verify=0, buffer='\4d\43\20\20\20\20' -> 'MC    ')

    0 <==[16:45:14.87;t=0;ovh=0] {}

    UP0009: UPDIST   [16:45:14.87].Read(view=0x0AF4579C)

    0 <==[16:45:14.87;t=0;ovh=0] {}

    UP0009: UPDIST   [16:45:14.87].BlkGet(view=0x0AF4579C, count=9, fields/sizes=1/6$2/6$3/15$4/45$5/45$6/45$7/45$8/45$9/45$)

    0 <==[16:45:14.87;t=0;ovh=0] BlkGet return

     * field=1, size=6, buffer='\55\53\4d\45\44\20' -> 'USMED '

     * field=2, size=6, buffer='\4d\43\20\20\20\20' -> 'MC    '

     * field=3, size=15, buffer='\4d\65\64\69\63\61\72\65\2d\45\45\20\20\20\20' -> 'Medicare-EE    '

     * field=4, size=45, buffer='\37\37\31\30\2e\30\30\2e\31\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '7710.00.10                   [*note- this is the account we want]                '

     * field=5, size=45, buffer='\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '                                             '

     * field=6, size=45, buffer='\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '                                             '

     * field=7, size=45, buffer='\32\32\31\37\2e\30\30\2e\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '2217.00.00                                   '

     * field=8, size=45, buffer='\32\32\31\37\2e\30\30\2e\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '2217.00.00                                   '

     * field=9, size=45, buffer='\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '                                             '

    GL0100: GLAMF    [16:45:14.87].Put(view=0x0AF189BC, field=1, size=45, verify=0, buffer='\32\32\31\37\2e\30\30\2e\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '2217.00.00                                   ')

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GL0100: GLAMF    [16:45:14.87].Read(view=0x0AF189BC)

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GL0100: GLAMF    [16:45:14.87].Get(view=0x0AF189BC, field=6, size=2)

    0 <==[16:45:14.87;t=0;ovh=0] {buffer='\01\00'}

    GP0800: GPGLFMT  [16:45:14.87].Init(view=0x0B3E8284)

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GP0800: GPGLFMT  [16:45:14.87].Put(view=0x0B3E8284, field=1, size=45, verify=0, buffer='\37\37\31\30\2e\30\30\2e\31\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '7710.00.10                                   ')

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GP0800: GPGLFMT  [16:45:14.87].Put(view=0x0B3E8284, field=3, size=15, verify=0, buffer='\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '00             ') [*What is causing the 00 to override here?]

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GP0800: GPGLFMT  [16:45:14.87].Put(view=0x0B3E8284, field=2, size=6, verify=0, buffer='\30\30\30\30\30\33' -> '000003')

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GP0800: GPGLFMT  [16:45:14.87].Process(view=0x0B3E8284)

    0 <==[16:45:14.87;t=0;ovh=0] {}

    GP0800: GPGLFMT  [16:45:14.87].Get(view=0x0B3E8284, field=21, size=45)

    0 <==[16:45:14.87;t=0;ovh=0] {buffer='\37\37\31\30\2e\30\30\2e\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '7710.00.00                                   '}

    GL0100: GLAMF    [16:45:14.87].Put(view=0x0AF189BC, field=1, size=45, verify=0, buffer='\37\37\31\30\2e\30\30\2e\30\30\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20\20' -> '7710.00.00                                   ')  [* here we see the newly constructed account, which happens to be inactive]

 

How can we prevent this?

Parents
  • 0

    The employee probably has a value in his/her Cost Center tab. If you don't want tax to override segments, the best thing to do is to set up the tax with a natural account or just segments that do not have an override in the GL integration setup. Not sure how your specific client will be able to work around this. The preference would have been to set up the tax with 7710 or 7710.00, assuming that 2nd segment is not setup to override in the GL integration setup. 

Reply
  • 0

    The employee probably has a value in his/her Cost Center tab. If you don't want tax to override segments, the best thing to do is to set up the tax with a natural account or just segments that do not have an override in the GL integration setup. Not sure how your specific client will be able to work around this. The preference would have been to set up the tax with 7710 or 7710.00, assuming that 2nd segment is not setup to override in the GL integration setup. 

Children
  • 0 in reply to angel g

    Thanks for looking into this.  The Employee's cost center override is 20.  The tax is set to GL account 7710.00.10.  But calculation is changing the tax expense to 00.  The GL account of the earnings code ends in 00, and that appears to be the source of the tax expense override (because if I change the earnings code to end in 15, Sage changes the tax expense to 15).  Just don't understand why this would be, or how to work around it.

    I tried removing the Cost Center Override from the Employee's cost center tab, and applying 20 to individual lines instead.  But for this line, we don't want 20, and we don't want 00.  The pay line is going to the correct GL account, but the tax is still getting an override of 00.

*Community Hub is the new name for Sage City