What should my job date be on a payroll workflow?
With payroll, we recommend the job date represents the 'normal pay date'. So for example, if a client were paid on the 18th each month then you would enter the 18th.
On our templates we then have a deadline setup called 'this period pay day' (note 1). This deadline will walk backwards from the normal pay date (the job date) to the last working day, this works great for all clients that are paid on a working day. Of course, if you have clients paid in cash (including on weekends), then they may need to reside on a different route without this deadline.
Our templates then have another deadline called RTI submission which calculates the RTI submission itself. Of course, this is exactly the same date as the 'this period pay date' but is representing the RTI submission instead, so this deadline would be completed by a different stage.
All of the additional payroll functionality we have built works on the assumption that you have configured the system this way around. This includes BACS deadlines which work out the cut off for BACS submission. We also have various other job frequencies that are designed for payroll such as 'Last Working day of the month' etc.
Of course, for the above system to work, you have to have job creation set to -X days to ensure the jobs create ahead of pay date so that you can complete them in advance of the job date.
Both the 'this period pay date' and the RTI Submission use the deadline option called 'RTI Submission (Pay date)' - this calculated a deadline equal to the last working day before the job date.