The General Ledger journal report (PAYB236) is a crucial tool for payroll processing, ensuring that all financial transactions are accurately recorded and balanced within the general ledger.
We have compiled a list of possible causes for the PAYB236 report not balancing, along with steps to resolve each issue.
ER deduction
An employer (ER) deduction adjustment for pensions was entered through timesheets, which reduced the net pay due to the employer pension adjustment.
To resolve this, if the payroll is complete, cancel the incorrect payment and issue a manual payment for that payroll run.
As the employee has already been paid incorrectly, any adjustments will need to be made outside of the payroll run.
πNote: When an employer deduction adjustment is entered as a timesheet, there is no link between the adjustment and the pension scheme. Therefore, the system does not recognize which employer adjustment pension code to use to ensure the value is not subtracted from the employee's net pay.
All timesheets must be entered as adjustments. To do this, follow the steps in the relevant section below.
Portal
Click Employee then in the search field, search for employee.
Beside the relevant employee, click VIEW.
Click Pension.
Back Office
Click CorePay then click Employee.
Click Maintain Employee Pension.
Use the Pension Adjustment fields for ER.
If payroll is not complete, delete the ER Pension timesheet and enter the ER Pension. To do this, follow the steps below in the portal.
Click Employee then in the search field, search for employee.
Beside the relevant employee, click VIEW.
Click Employee Pension then click Employee Pension Details.
Reset indicators
You need to reset the indicators. To resolve this, follow the steps below in back office.
Click CorePay then click Update.
Click General Ledger Interface then click Generate General Ledger Interface.
Select Details then click Maintain Expense Code Details.
For the required expense codes, turn on the Balance Sheet Ind toggle.
No category code
If no category code is set at the employee level, check that the employee has a valid category code. If the category code is only set after the payroll period closes, our support team will need to run an update.
Please raise a new case online, referencing this article's title and include the following details:
Details of the employee.
Period affected
Missing link
If there is no link between the category, expense, and pay code, ensure that the employee's category code is attached to the relevant pay code, and the expense code must match the value in the `gl_link` field on the `gl_matrix` table.
To resolve this, support will need to run an update.please raise a new case online, referencing this article's title and include the following details:
GL PDF report.
Payroll period
Impacted company
Description of the discrepancy.
β
Pay code not mapped
If a pay code is not mapped to the employee's cost center, the employee is being paid with a pay code that is not associated with their cost center.
To resolve this, our support team will need to run an update. Please raise a new case online, referencing this article's title and include the following details:
GL PDF report.
Payroll period
Impacted company
Description of the discrepancy.
