A proposed approach to explore with your business. Scope, implementation and outcomes depend on the engagement.
Connect approved payroll to the general ledger
Ideal for
Any Australian multi-entity business, including retail groups and franchise operators, building payroll journals in NetSuite manually after each pay run.
The situation
A multi-entity business posting payroll journals into NetSuite by hand
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.
The approach
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.
Expected outcomes
The aim is to reduce repeated journal entry while keeping finance approval and reconciliation explicit. The time saved depends on payroll complexity, data quality and how many exceptions require review.
Baseline preparation and review time, then measure it across representative pay runs. Validate balanced journals, component mappings, reversals and duplicate protection before changing the operating process.