Cost centres and ledgers
Payroll journal with multiple employers and ledgers
With several employers KoppelHet links each AFAS employer, Nmbrs company or YouForce client to a fixed ledger in Exact Online, AllSolutions or 4PS, or to a subsidiary in Oracle NetSuite. Every journal thus lands in the books of its own operating company, in euro, and consolidation stays with finance.
What it is
A group with several entities runs payroll in one environment, but posts per operating company. In the ERP that is called a ledger, a company, a subsidiary or a branch. One entity's journal never belongs in another's books.
Without a fixed link someone picks the right ledger again every month. One wrong choice produces a posting finance has to reverse.
How the integration handles it
- For each employer, Nmbrs company or YouForce client we record which ledger the journal goes to. A run can never end up in another company's books.
- Each employer becomes its own journal. A journal entry in NetSuite belongs to exactly one subsidiary.
- The AllSolutions integration account always starts in one company. KoppelHet switches to the right company per employer before recording the journal.
- The journal goes to the Dutch entity in euro. Conversion to the group currency stays with consolidation.
- Cost centres are compared per pair, so one entity's cost centre is not chosen in another.
- If Visma.net uses branches within one company, each employer gets a fixed branch, so payroll costs per employer show separately in reporting.
Edge cases we handle
- A group ERP such as Dynamics 365, Unit4 or NetSuite holds every country. The integration only posts to the company or subsidiary of the Dutch entity.
- Each Visma.net company has its own access and its own API limit. KoppelHet therefore processes the Nmbrs companies one after another.
- A secondment entity next to the main entity is its own company in Nmbrs, and becomes its own journal in NetSuite on the matching subsidiary.
What KoppelHet does
KoppelHet records the employer-to-ledger pairs at the start and checks them on every run. A payroll bureau working in Nmbrs needs no access to the ERP: the integration has its own access to both systems. Multiple entities fall into our complex class; plan on three to six weeks.
Common integrations
Oracle NetSuite → AFAS Profit
Oracle NetSuite and AFAS integration: payroll journal on the Dutch subsidiary, cost centres from NetSuite
AFAS Profit → AllSolutions
AFAS to AllSolutions integration: the AFAS Profit payroll journal posted in AllSolutions
Nmbrs → 4PS Construct
Nmbrs to 4PS Construct integration: payroll journal after every run in 4PS, cost centres back to Nmbrs
Oracle NetSuite → Visma Raet YouForce
Oracle NetSuite and YouForce integration: payroll journal per run and cost centres in check
Microsoft Dynamics 365 → Visma Raet YouForce
Dynamics 365 and YouForce integration: cost centres in check, payroll journal posted
Nmbrs → Visma.net ERP
Nmbrs to Visma.net ERP integration: every payroll run as a journal in Visma.net
Microsoft Dynamics 365 → Loket
Dynamics 365 and Loket integration: dimensions as cost centres in Loket, journal results in Dynamics
Frequently asked questions
Can one journal cover two ledgers?
No. Each employer becomes its own journal in its own ledger or subsidiary.
Does our payroll bureau need access to the ERP?
No. The integration has its own access to both systems, separate from the bureau's and finance's accounts.
In which currency is the journal posted?
In euro, to the Dutch entity. Finance converts to the group currency at consolidation.
More on Payroll to finance
Payroll to finance: the overview
The payroll journal
Cost centres and ledgers
- Cost centres from the ERPFinance manages cost centres, payroll only picks valid values.
- Multiple employers and ledgersEach payroll employer to the right ledger, subsidiary or branch.