The payroll journal

Posting the payroll journal to the ledger automatically

Posting the payroll journal automatically means the integration fetches the journal from AFAS, Nmbrs or YouForce after every payroll run and puts it as one entry in Exact Online, Unit4, Microsoft Dynamics 365 or Oracle NetSuite, summed per GL account and cost centre. The per-employee detail stays in payroll, and finance keeps the review before anything is posted for good.

Last updated: 9 November 2026

Discuss your integration All about Payroll to finance

What it is

After every payroll run someone exports a journal file, adjusts it in Excel and imports it into finance. AFAS no longer supports its old exports for external accounting packages, so many organisations are left with a home-made file.

Every package wants the journal differently. AFAS keeps debit and credit apart, Unit4 and Business Central want one amount with plus or minus, NetSuite debit and credit per line again. A manual conversion produces differences every month that the controller has to chase.

How the integration handles it

KoppelHet first sums the lines per account, cost centre and project where needed. No amounts per person end up in the ERP.
Debit and credit are converted to the form the ERP expects, and a journal only goes through when it balances to zero.
The journal lands in its own payroll daybook or as a draft, and finance posts after review. Direct posting is possible per ledger if finance chooses it.
Before posting KoppelHet checks whether accounts and cost centres exist and are open in the ERP. A missing code shows up before the batch is sent.
After posting KoppelHet checks the status in the ERP. A rejected journal appears on the platform with the reason, not only at month end.
KoppelHet remembers which runs have been posted, so a run never reaches the ledger twice.

Edge cases we handle

In AFAS a replacement rule can extend the account number with a cost centre code. The ERP does not know those numbers; KoppelHet reads account and cost centre separately.
A single entry in Unit4 may have at most 500 lines. A larger journal goes through batch processing.
Exact Online and Business Central limit the number of requests. That is why KoppelHet posts the journal as one entry with lines, not line by line.
Technicians already book their hours to projects in the ERP. The journal then posts to account and cost centre and not again to the project, so payroll costs are not doubled in project results.

What KoppelHet does

At the start KoppelHet agrees with finance at which level to post, in which daybook and whether finance completes the posting itself. Four-weekly payroll, several entities with their own chart of accounts and reporting a rejected posting straight away are part of the design. Plan on three to six weeks as an indication.

Common integrations

AFAS Profit → Unit4 ERP

AFAS to Unit4 integration: payroll journal posted in Unit4 ERP

AFAS Profit → 4PS Construct

AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company

Microsoft Dynamics 365 → AFAS Profit

Dynamics 365 and AFAS integration: cost centres to HR, payroll journal to the ERP

Visma Raet YouForce → Visma.net ERP

YouForce to Visma.net ERP integration: the YouForce payroll journal as a posting in Visma.net

Nmbrs → AllSolutions

Nmbrs to AllSolutions integration: the journal of every payroll run in the AllSolutions ledger

SAP S/4HANA → AFAS Profit

SAP S/4HANA and AFAS integration: SAP cost centres at the AFAS employer, payroll journal posted in SAP

Customer case

Koninklijke Bibliotheek

Public sector

The KB keeps employee records in Visma Raet YouForce and runs its financial administration in AFAS. Employees, managers, cost centres and the payroll journal entries move from YouForce to AFAS automatically.

Read the customer story

Frequently asked questions

Do you post per employee?

We can, but usually do not. Finance wants the journal by GL account and cost centre; per-employee detail stays in payroll.

Is the journal posted for good straight away?

Not by default. It lands in its own daybook, as a draft or on hold, and finance posts after review. Direct posting is possible if finance chooses it.

What if an account or cost centre is missing in the ERP?

Before posting KoppelHet checks whether accounts and cost centres exist and are open. A missing code shows up before the batch is sent. If the ERP still rejects a journal, the reason appears on the platform.