Who it's for
The shape of the problem changes with how many entities you run and whose employees they are. What does not change is needing to show where a figure came from.
One entity, one payroll, and one person who is accountable when LHDN asks. They get the working behind every line, rather than a spreadsheet to defend from memory.
Employees move between companies, and a year-to-date figure has to follow the person rather than the payroll. A mid-year transfer is a statement, not a re-keying exercise.
Filing on behalf of clients means defending someone else's numbers to a regulator. The answer to a query is a citation rather than a reconstruction.
Payroll is where a compilation engagement most often goes wrong, because the figures arrive with no working. Here they arrive with it.
None of these is quite you?
Tell us how your entities and your people actually line up.
Yes. The employment record spans entities, which is what makes a mid-year transfer between two of your own companies a statement about a person rather than a termination and a new hire with a re-keyed year-to-date.
That is exactly what the year-to-date working is for. Every month has to add up whichever company paid it, and a month that does not is named rather than assumed to be zero.
No. PEOPLE works out and files payroll, and exports to the accounts you already keep. Replacing your accounting system is not on the roadmap and would not make your payroll any easier to defend.
You state an opening balance and the runs a previous provider made. PEOPLE derives year-to-date from that plus its own runs, and refuses to compute until every month in the window is accounted for.
Every line PEOPLE produces carries the instrument that sets it and the date that instrument took effect.