Payroll (Loket, Nmbrs, Visma) does not flow cleanly into bookkeeping.
Payroll packages typically deliver a monthly journal entry or a flat file. Mismatch usually comes from wrong chart of accounts, a new wage type, or dimensions the payroll software does not know.
Try this first
- 1Pull from payroll the active ledger mapping and compare to your chart of accounts, the mismatch is almost always a missing row.
- 2Add the missing ledger accounts in your bookkeeping (social charges per type, holiday allowance accrual, year-end bonus).
- 3Test one month again with a sample journal entry in a test admin or staging.
- 4Enable cost centre or dimension passthrough, otherwise payroll costs land on one account without split.
- 5Plan that after every CLA change or new wage type the mapping is reviewed, otherwise it breaks quietly.
When to bring us in
If the payroll journal has been off for months, we can work out the mapping per wage type and test it.
See also
- Switching from Exact Online to Yuki, open items and history do not matchPackage migrations stumble on ledger mapping and open AR/AP. Without a mapping table you lose context.
- Twinfield to Exact, dimensions and cost centres go missingTwinfield uses dimensions, Exact uses cost centres and projects. The mapping is not one-to-one.
- Accountant asks for RGS mapping, your ledger does not follow RGSRGS is the Dutch standard chart that SBR filings and accountant software expect. Without mapping, every year-end is manual.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.