Automating Payroll Journal Entries for Multi-Entity Businesses

Each entity runs its own payroll instance. After every pay run, payroll exports CSV summaries and builds the journal by hand in NetSuite, mapping base salary, overtime, allowances, superannuation, PAYG withholding, leave accruals, workers compensation and salary sacrifice to the right GL accounts. That is one to two full days per cycle.

Staff who split time across two legal entities are the painful part. Their cost needs proportional allocation across subsidiaries, and the errors surface at year-end audit preparation, months after they happened.

A Celigo flow triggers after each pay run, by webhook or polling. It pulls the pay run summary, and an io.js transformation maps each component to a GL account using a configurable mapping table held in a NetSuite custom record, so finance can adjust the mapping without code.

The mapping covers base salary to department cost centre, overtime to its own account, superannuation and PAYG withholding to liability accounts, leave accruals to provisions, allowances to category-specific accounts and workers compensation to expense.

For each employee the script reads the entity assignment and picks the subsidiary. Where someone is split across entities, the flow writes proportional journal entries in line with their recorded time allocation.

Entries are created pending approval. The payroll manager receives a summary with totals per entity and anything flagged as anomalous. One approval posts the lot. Every entry references the source pay run identifier, so the audit trail holds up.

Posting drops from one to two days down to about 15 minutes of review and approval. Discrepancies between the payroll system and the GL go to zero. Roughly 40 to 50 hours a year come back to the payroll team, and audit preparation stops being an archaeology exercise.