web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

HR Accrual Date

(0) ShareShare
ReportReport
Posted on by

A client uses GP2010 with Payroll and HR.  They set up a bi-weekly accrual schedule for sick and vacation time.  They also set up maximum hours per year in Accrual Setup. We found that in our first pay period of 2014 (which was 12/27/13-1/09/14) that sick and vacation time did not accrue as an extra accrual was transacted accidently in October and so the maximums had been reached.  If I run sql queries on table TATX1030 which is the accrual transaction table, I find that if I sum the accrued hours on the TRXDATE (which is the first day of each pay period), I see that the maximums are hit for 2013 and I can easily identify the additional accrual processing.

My question is: Are the calendar year accruals based on the TRXDATE in TATX1030 which again is the first day of each bi-weekly pay period? Logically one would think the calendar year accruals would be based off of the TRXENDDT which is the ending date of the payperiod.  My query is:

select * from tatx1030 where

year(trxdate) = 2013

and

accflg = 1

and

timecode_i in ('vac','vacsl','sic','sicsl')

Thanks,

Mike

*This post is locked for comments

I have the same question (0)
  • Melissa Brown Profile Picture
    190 on at

    I just encountered the same thing where the first payroll of 2018 did not accrue.  The only thing I can think of is that GP thought the maximums had been reached because the start date of the pay period was in 2017.  The accruals must not look to the Accrual Period setup to determine what constitutes a year because in that window we have calendar year 2018 starting on December 24, 2017.  GP correctly marked the period as being accrued, but no hours were added to employee balances. 

  • Isaac Olson Profile Picture
    Microsoft Employee on at

    Hello,

    Microsoft Dynamics GP looks at the year on the Next Accrual Date for the employees, and uses the maximums from that year.  So if you had not accrued through the whole calendar year yet, and the employee's next accrual date was still in 2017 it would look at the maximums in 2017.  Based on your description, this sounds like what you are running into.

    Thanks!

    Microsoft Support

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
talty09 Profile Picture

talty09 2

#1
Anthony Beatty Profile Picture

Anthony Beatty 2

#3
CP04-islander Profile Picture

CP04-islander 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans