Payroll is often one of an organisation’s largest recurring expenses, but a successful payroll run does not automatically mean the general ledger is complete and accurate. Differences can arise from timing, employee changes, manual journals, posting failures, cost-centre mappings, benefit deductions, and payroll interfaces. A disciplined payroll close control links the approved payroll results to the accounting records, cash disbursements, and liabilities that remain unpaid at period-end.
For US and Canadian financial controllers, the objective is not simply to make the payroll clearing account equal zero. It is to demonstrate that payroll expense and related liabilities are recorded in the correct period, supported by reliable source data, properly authorised, and reconciled to the systems that process and pay employees.
Why payroll-to-GL reconciliation deserves a formal control
The Financial Accounting Standards Board’s Conceptual Framework for Financial Reporting describes accrual accounting as recognising financial effects in the periods in which the underlying transactions and events occur. It specifically identifies wages and salaries not yet paid as examples of accruals. The framework is conceptual, not a substitute for applicable accounting standards, but it reinforces the close objective: the accounting period should reflect payroll earned during that period, not merely cash paid.
In SAP environments, payroll results can be summarised and posted into Accounting components, including Financial Accounting and General Ledger. SAP documents the process in its Posting to Accounting guidance. The exact process depends on the payroll solution, configuration, integrations, and release in use; controllers should validate their own design rather than assume every implementation behaves identically.
Nine month-end payroll controls
1. Reconcile approved payroll totals to the posted accounting document
Obtain the final payroll register or payroll summary, the posting-run output, and the corresponding GL document. Reconcile gross pay, employer taxes and contributions, benefits, deductions, net pay, and other material components at a level appropriate to the organisation’s chart of accounts. Document the expected and actual totals, differences, preparer, reviewer, and completion date.
Do not treat a successful interface message as proof that every accounting amount is correct. Confirm the document posted to the intended company code, ledger, period, and accounts, and investigate rejected, parked, duplicated, or partially processed items.
2. Test payroll cut-off and accrued compensation
Compare the pay-period calendar with the financial reporting calendar. Where employees have earned compensation by period-end that will be paid later, calculate the required accrual using a documented, consistently applied method and relevant payroll data. Consider bonuses, commissions, overtime, unused paid time off, and other earned compensation where applicable to the organisation’s policies and accounting framework.
For example, if a biweekly pay period crosses month-end, the controller should determine which days or services belong to the closing period and whether the recorded expense and liability reflect that activity. The calculation should be supported by employee or department-level data, reasonable assumptions, and a clear reversal or settlement process where used.
3. Reconcile payroll liabilities to subsequent settlements
Reconcile net-pay liabilities, payroll taxes, benefit deductions, retirement-plan contributions, garnishments, and other remittances to payroll reports and third-party statements. Trace material balances to subsequent bank payments or remittances, and investigate items that remain open beyond the expected settlement cycle.
Keep payroll expense and payroll liabilities distinct in the reconciliation. A liability balance can be valid at month-end if payment is not yet due; an unexplained old balance is different and requires follow-up.
4. Review suspense, clearing, and rejected-posting accounts
Identify payroll-related suspense or clearing accounts and inspect all open items. Assign each difference an owner, cause, target resolution date, and supporting evidence. Common causes include invalid cost centres, closed periods, mapping changes, employee transfers, interface errors, and manual adjustments.
Set escalation thresholds based on value, age, recurrence, and risk. Avoid routinely clearing balances to a generic expense account simply to make the reconciliation appear clean. Any write-off or reclassification should have a documented rationale and appropriate approval.
5. Validate account and cost-centre mapping
Compare payroll earning and deduction codes to approved GL accounts, departments, locations, projects, and other dimensions used in financial reporting. Review new or changed mappings before they are used in production. For material changes, retain evidence of testing and approval and compare the first live posting with the expected result.
Where payroll data feeds SAP S/4HANA Finance or another ERP through middleware, include interface mapping and transformation rules in the control scope. Confirm that totals are preserved across the source report, interface output, and accounting document.
6. Control manual journals and off-cycle payments
Review manual payroll journals, correction entries, off-cycle runs, termination payments, and late adjustments separately from the standard payroll run. Confirm business purpose, source support, authorisation, correct accounting period, and independent review. Pay particular attention to journals posted by users who can also administer payroll or change mapping rules.
Where staffing limits prevent full segregation of duties, establish a documented compensating review by an appropriately independent manager. Access restrictions and review evidence should reflect the actual risk, not just a policy statement.
7. Reconcile payroll headcount and changes to HR records
Use controlled reports to review new hires, terminations, salary changes, bank-detail changes, and changes to payroll status. Confirm that changes were authorised by the appropriate business or HR owner and processed in the correct effective period. Investigate payments to terminated employees, duplicate employee records, unusual payment changes, and inactive records that remain in payroll output.
Payroll and HR data contain sensitive personal information. Limit access to detailed employee-level evidence and use secure, approved channels when sharing support with reviewers or auditors.
8. Verify report completeness and data integrity
Document the source, parameters, period, entity, and extraction date for reports used in the reconciliation. Check record counts and control totals where available, and retain evidence that the report covers all relevant payroll runs and entities. If spreadsheets are used, control formulas, locked cells, versioning, and changes to key assumptions.
For ICFR purposes, the reliability of a report used as evidence matters as much as the reviewer’s sign-off. The PCAOB’s AS 2201 discusses understanding transaction flows and IT’s effect on financial reporting controls, as well as testing control design and operation. AS 2201 applies to relevant integrated audits; it is not a universal checklist for every private company, but its risk-focused approach is useful when designing controls.
9. Require evidence-based review and follow-up
A reviewer should do more than sign a reconciliation. Define what must be inspected: totals, period cut-off, unusual variances, aged items, journal support, and resolution of prior-period issues. Evidence should show what was reviewed, which exceptions were challenged, and how conclusions were reached.
Track recurring issues by root cause and business unit. If the same mapping error appears each month, fix the upstream configuration or ownership issue rather than relying indefinitely on manual adjustments.
A practical close checklist
- Final payroll registers and all in-scope payroll runs are identified.
- Payroll totals reconcile to accounting postings by entity, period, and relevant account.
- Period-end compensation accruals are calculated, reviewed, and supported.
- Payroll liabilities are reconciled to remittance records and subsequent settlements.
- Suspense and clearing items have owners, aging, explanations, and due dates.
- Mapping changes, manual journals, off-cycle runs, and rejected postings are reviewed.
- Reports have documented parameters and completeness checks.
- Reviewer evidence and unresolved exceptions are retained in the close repository.
US and Canadian considerations
Payroll tax, benefit, pension, and remittance obligations differ by jurisdiction and can change over time. A US entity and a Canadian entity may use common group close controls, but should maintain separate compliance calendars, account mappings, and local review procedures where requirements differ. Do not assume a payroll liability or employee-benefit treatment is identical under US GAAP, IFRS, and Canadian ASPE; assess the applicable reporting framework and the facts of the arrangement. Confirm current local filing and remittance obligations with authoritative guidance and qualified advisers.
Conclusion
A strong payroll close control connects payroll calculations, accounting postings, period-end accruals, liabilities, and cash settlements in one traceable process. The most useful reconciliation explains differences and drives them to resolution; it does not merely force accounts to balance. Controllers who combine clear ownership, reliable reports, controlled mappings, independent review, and documented follow-up can reduce close surprises and improve audit readiness.
Informational only: This article is a general control-design guide, not legal, tax, payroll, or accounting advice. Apply the accounting framework and payroll requirements relevant to each entity and confirm current obligations with appropriate specialists.
Sources
- SAP Help Portal — Posting to Accounting (PY-XX-DT), SAP S/4HANA HCM 2023 documentation.
- FASB — Conceptual Framework for Financial Reporting, September 2024.
- PCAOB — AS 2201, An Audit of Internal Control Over Financial Reporting That Is Integrated with an Audit of Financial Statements. The PCAOB notes that amendments to specified paragraphs become effective December 15, 2026; consult the applicable version for the audit period.
