...
Once timesheets are submitted, the payroll officer can use the EBA Interpreter to generate overtime and allowances based on the original entries. This generation populates the Payroll area of Timesheet Administration, leaving the original lines intact. With the Control Parameter "Recost Time from EBA" set to Yes, the original transaction will be updated to reflect the total cost of the payroll section for that line. The recosting of the Time transactions from PayrollTransactions , take takes the cost breakdown of the PayrollTransactions into account. e.g. Base, Overhead, Other. This is to get a more accurate allocation of costs to GL accounts. However, for EBA allowances that were given an "Activity" during setup, these lines will be added to the timesheet lines with their own cost and will not add cost to the original transaction line. After generation, it is the payroll officer's responsibility to review the outputs, making manual adjustments or additions as needed to ensure the values sent to the payroll software are accurate. See an example of the recosting of a Time transaction at the end of this section.
To decide whether to bill EBA generated Payroll transactions or not, use the attribute on the job's Charge Type called "Billing from EBA".
When this attribute is ticked:
...
| Note |
|---|
Any manual additions to timesheets will not be included in the payroll output until the EBA Interpreter is run over them, including leave. Running the interpreter multiple times will replace previously generated payroll lines with new ones. |
| Info |
|---|
|
To finalise the Workbench side of payroll, create a Payroll Batch and filter for the target week(s) timesheets.
Recosting original Time transaction from Payroll transactions:
There is an option to update the cost on the original Timesheet transactions that generated the Payroll transactions, once EBA has been generated. This is done by using the Control Parameter Recost Time from EBA = yes. Recosting of Time transactions from Payroll Transactions takes the cost breakdown of the Payroll Transactions into account. e.g. Base, Overhead, Other. This is to get a more accurate allocation of costs to GL accounts.
Example:
Suppose that an hour of time is entered as normal time (NT) on the timesheet, but is calculated and costed as time and a half (T1.5) by EBA.
The person’s employee class has this cost breakdown.
...
The LAB activity is flagged to apply all cost elements, and the NT time code apportions these equally.
...
Without EBA, the hour of time would be costed at $80, split 50, 20, 10.
But suppose the T1.5 time code has a different cost element allocation.
...
The EBA creates a Payroll Transaction costed at: 150% * $50 + 100% * $20 + 50% * $10 = $75 + $20 + $5 = $100
The original time transaction cost allocation is based on the T1.5 time code, and so the split is: 75, 20, 5.
The effect of this is only on the GL Coding of the labour journal, and hence what ends up in the financials.
In this example, the time is just changed from NT to T1.5, but we also correctly handle the scenario where say, 10 hours of NT is converted by EBA into 8 hours NT and 2 hours T1.5.