Articles in this section

How to reconcile payroll reports before EOFY

Payroll EOFY

Reconciling the Payment Summary Audit Report to the Accumulated Pay Detail Report

Confirm that employee payment summary values match payroll transaction totals before completing month-end or EOFY payroll tasks.

Overview

This article explains how to reconcile the Payment Summary Audit Report to the Accumulated Pay Detail Report in Jobpac.

If the reports do not reconcile, you can review the transaction code setup to check whether the correct group tax code and taxable flag have been applied.

Note: The Payment Summary Audit Report is produced when you print the PAYG Payment Summaries.

Step 1 — Run the Accumulated Pay report

Use the Accumulated Pay report to compare payroll transaction totals against the Payment Summary Audit Report.

1 Go to the Accumulated Pay report.
Payroll > Payroll Reports > Accumulated Pay
2 Run the report.
3 Compare the transaction code totals against the totals on the Payment Summary Audit Report.
If the totals match, no further reconciliation is required for this step. If the totals do not match, continue to Step 2.

Step 2 — Check transaction codes if the reports do not reconcile

Generate the Company Transaction Report to check whether transaction codes have the correct group tax code and taxable flag.

1 Go to the Company Transaction Report.
Payroll > Company Information > More Options > Company Transaction Report
2 Review the transaction codes included in the report.
3 Check that each transaction code has the correct group tax code and taxable flag.
If a transaction code is incorrect, update the transaction group tax code before completing your reconciliation.

Group tax codes — gross pay transaction types

Transaction codes with the following transaction types are included in gross pay. The group tax code should be 01. If no group tax code is nominated, these transaction types are still included in gross pay.

Code Description
NT Normal time
TH Time and half
DT Double time
DTH Double time and half
TR Triple time
QT Quadruple time
WKC Workers compensation
RDO Rostered day off
PHT Public holiday taken
PHA Public holiday accrual
RDJ RDO job
RDP Paid RDO
ADP Adjustment pre-tax
BKP Backpay
ACT Accruals taken
CAL Call out
LLD Leave loading

Group tax codes — other payment types

Payment type Rule
Annual leave, sick leave and long service leave If the amount is foreign income, use group tax code 16. Otherwise it is included in gross pay and the group tax code should be 01. If no group tax code is nominated, it is included in gross pay.
Pre-tax deductions Included in gross pay. The group tax code must be 01.
Allowances If reported under allowances on the PAYG Payment Summary, use group tax code 04. If included in gross pay, use group tax code 01.
Reportable superannuation For example, super salary sacrifice or additional employer contributions. Use group tax code 19.
Foreign income Use group tax code 16. This is not reported on the PAYG Summary — Individual Non-Business.
Workplace giving Use group tax code 17.
Lump sum payments A group tax code does not need to be nominated.

Note: If you need to correct an incorrect transaction group tax code, refer to How do I change a transaction group tax code.

Step 3 — Adjust employee gross values if required

If you need to adjust employee group values, you can do this from the STP2 Employee Gross Values screen.

1 Go to the STP2 Employee Gross Values screen.
Payroll > Employee Information > STP2 Emp Gross Values
2 Enter the employee code.
3 Enter the financial year.
If payroll has not been rolled into the new financial year, leave the financial year blank.
4 Right-click and select the employee.
5 Enter the correction value in the Adjustment column.
6 Click OK to save the adjustment.

You're done when:

✓ Payment Summary Audit Report totals match the Accumulated Pay Detail Report
✓ All transaction codes have the correct group tax code and taxable flag
✓ Any employee gross value adjustments have been saved
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.