How payroll tax processing is set up in finance and ERP systems

In most organisations, payroll taxes are calculated inside the payroll engine, paid through treasury or a tax service, and recorded in the general ledger as summary journals. The ERP holds liability accounts and cash. Tax rules and employee elections usually sit with the payroll system or an outsourced provider.

Where the work sits

Payroll tax is a shared process. Payroll or HR owns the employee master data, including work location, residence and withholding elections. Finance owns the liability accounts, the bank and the reconciliation. A tax team, or sometimes the controller, owns registrations with each authority and the relationship with auditors.

The split matters because errors rarely start where they surface. A wrong work address entered during onboarding shows up months later as a notice from a tax authority, addressed to finance.

Many companies outsource the calculation and the filing to a payroll bureau. Others run an in-house payroll module bolted onto the ERP. In both cases the general ledger only sees totals. Employee-level detail stays in the payroll system.

Tax setup and planning

Before any calculation runs, someone has to decide which jurisdictions the business is registered in, which accounts receive employer and employee taxes, and how cost is allocated to departments or entities. This is the tax plan in practical terms. It covers registrations, deposit schedules, account mapping and who signs off on changes.

Managing that plan is ongoing work. Rates change. Employees move or start working remotely from a new state or country. New entities get acquired with their own registrations. Good setups keep a register of every tax account, its deposit frequency and the person responsible, and review it whenever headcount shifts into a new location.

The tax tables themselves are usually maintained by the payroll vendor. Finance should still know who checks that updates were applied before the first run under new rates.

Calculation and payment each cycle

The payroll engine computes gross pay, then withholding for each employee and the matching employer contributions. The output is a register plus a funding request.

Payment typically follows one of two patterns. In the first, the provider debits the company account for net pay and taxes together and remits to authorities on the company's behalf. In the second, treasury pays each authority directly, often through a government portal, based on a liability report from payroll. The second gives more control and more chances to miss a deadline.

Approval of the funding is a key control. Someone outside payroll should see the totals before cash leaves.

Posting and reconciling in the ledger

After each run, summary payroll payment information comes into the ERP, either through an interface file or a manual journal. It debits expense and credits liabilities for each tax type, plus net pay clearing. When the tax deposit clears the bank, the liability is relieved.

Reconciliation is where weak setups show. Each liability account should net to zero once deposits are made, or hold only amounts not yet due. Balances that drift indicate unposted adjustments, mapping errors or payments coded to the wrong account. Strong teams reconcile the payroll register to the ledger every cycle, and the ledger to authority statements at each filing point.

Adjustments and corrections

Payroll is rarely clean. Off-cycle payments, retroactive pay, voided cheques, taxable benefits and terminations all generate adjustments. These need to reach the ledger as their own entries, with references back to the original run.

The common failure is that payroll fixes the employee record but nobody posts the matching entry in finance. The ledger and the tax filings then disagree, and the gap is found at year end.

Statements and regulatory filings

Employees receive annual tax statements generated from the year-to-date payroll totals. Distribution is often electronic through an employee portal, with paper copies on request. Corrected statements follow when late adjustments land after issue.

Regulatory forms go to each authority on its own schedule. The provider usually prepares them, but the company remains liable for their accuracy. Before filing, totals on the forms should tie to the payroll register, the deposits made and the ledger balances. Any difference needs an explanation on record before submission.

Notices from authorities should route to one owner. Left in a shared inbox, they become penalties.

Questions to ask the people who run it

Documented procedures and daily practice often differ here. These questions tend to surface the gaps:

• Who actually enters or changes an employee's work location, and is anyone told when it moves to a new jurisdiction?
• When the provider updates tax tables, how does anyone confirm the change took effect?
• Is the summary journal loaded automatically, or does someone rekey it from a report?
• Which liability accounts carry balances that nobody can fully explain?
• How are off-cycle payments and reversals posted, and who checks they reached the ledger?
• Who receives notices from tax authorities, and where are they tracked?
• At year end, what is reconciled before statements are released, and what is left for corrections later?
• If the main payroll person were away during a deposit deadline, who would make the payment?
• Are there registrations still open for locations where no one works anymore?

The answers usually reveal workarounds that live in spreadsheets or in one person's memory. Those are the parts of the process most at risk when anything changes.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.