Payroll journals without rekeying

Payroll and accounting are almost always separate systems, for good reasons: payroll has its own statutory requirements, its own calendar and its own confidentiality.

The consequence is a monthly handoff. Someone runs payroll, opens a summary, and types a journal into the ledger — gross pay, statutory contributions, deductions, net pay, employer costs, split across departments.

It takes twenty minutes. It happens twelve times a year. And it is one of the more error-prone routine tasks in finance, because it is entirely manual, done under time pressure, and rarely checked by anyone who was not the person who did it.

The five errors this handoff produces

Departmental splits. A journal that allocates payroll cost across cost centres by hand. Someone joined, someone moved, and the split reflects an earlier organisation.

Employer costs treated as deductions. Employer contributions are a cost to the business; employee deductions are amounts withheld and owed onward. Mixing them understates staff cost and misstates the liability.

Liability accounts that never clear. Statutory deductions accrue in a liability account and clear when paid. When the journal and the payment do not match exactly — different timing, a rounding difference, a late adjustment — a residue accumulates. Left alone it becomes a balance nobody can decompose.

Accruals for unpaid periods. Where the payroll period does not align to the accounting period, an accrual is needed. Manual accruals for part-periods are frequently forgotten or estimated inconsistently.

Adjustments posted twice. A backdated correction handled in payroll and separately in the ledger.

None of these break anything visibly. They produce staff costs that are slightly wrong by department and liability balances that slowly stop reconciling.

What automation should do

Post the journal from the payroll output directly. No retyping. The journal derives from the same figures the payslips derive from, so the ledger and payroll cannot diverge through transcription.

Apply the departmental split from current employee records. The allocation follows who actually works where, updated when someone moves, rather than a mapping maintained separately in finance.

Separate employer cost from employee deduction automatically. A structural distinction, applied consistently rather than reasoned about monthly.

Accrue part-periods. Where the calendar does not align, calculate and reverse the accrual mechanically.

Reconcile the liability accounts. Each statutory liability should clear when paid, and any residue should surface immediately rather than at year end.

The check that matters

One reconciliation catches most payroll journal problems: does each statutory liability account clear to zero after the payment is made?

If it does, the journal and the payment agree, month after month. If a residue accumulates — even small — something is systematically different between what you accrue and what you pay, and it will grow.

Run it monthly. It takes minutes and is the single most informative payroll control available to a small finance team.

What stays outside accounting

Worth being clear about scope. Automating the payroll journal is a finance task. It is not the same as running payroll, and it does not touch:

• Calculating pay, statutory contributions or tax
• Employment terms, leave entitlement or working time
• Anything requiring employment law judgement

Those belong in the payroll system and with whoever is responsible for it. The accounting integration concerns getting an accurate result into the ledger, correctly classified — not producing the result.

Confidentiality

One practical consideration. Payroll data is sensitive, and the ledger is visible to more people than payslips are.

The journal should carry the departmental and account-level detail finance needs, without exposing individual pay in the general ledger. That means the integration posts summarised figures by cost centre and account, with individual detail remaining in the payroll system where access is properly restricted.

It is worth confirming explicitly when setting this up, because a well-meaning integration that posts one line per employee is difficult to unwind once it is in the ledger history.

Common questions

Can payroll be posted to the ledger automatically?

Yes. The journal can derive directly from the payroll output rather than being retyped, with departmental allocation taken from current employee records, employer costs separated from employee deductions structurally, and part-period accruals calculated and reversed mechanically. This removes transcription error and keeps the ledger and payroll from diverging.

What is the most common payroll journal error?

Confusing employer costs with employee deductions, which understates the true cost of staff and misstates the liability. Close behind is a departmental allocation that has not been updated for people joining or moving, so cost-centre reporting reflects an earlier version of the organisation.

How do I check my payroll journals are right?

Confirm that each statutory liability account clears to zero after the corresponding payment is made. If a residue accumulates month after month, even a small one, something is systematically different between what is accrued and what is paid, and it will grow into a balance nobody can explain.

Should individual salaries appear in the general ledger?

Generally no. The journal should post summarised figures by cost centre and account so finance has the analysis it needs, while individual pay detail remains in the payroll system where access can be properly restricted. This is worth settling before an integration is built, because posting one line per employee is difficult to unwind once it is in the ledger history.

Related: AI in HR and payroll for small teams · closing the books with AI assistance · ai coding of general ledger transactions