Payroll to finance
Unit4 and Nmbrs integration: cost centres to payroll, payroll journal to the ledger
With an integration between Unit4 ERP and Nmbrs, the cost centres from Unit4 reach Nmbrs automatically, and the journal of every payroll run then lands in the Unit4 ledger by itself. HR only picks cost centres finance knows, and finance gets the payroll journal without an export file that fails on an unknown code.
What the integration does
Anyone keeping the books in Unit4 ERP and running payroll in Nmbrs maintains the cost centres in Nmbrs by hand, and they fall behind. After every run the journal is downloaded, converted in Excel and imported, where it fails on an unknown cost centre.
- Finance opens a new cost centre in Unit4.
- It then appears with code and description in the right Nmbrs company, so HR can use it.
- After every completed payroll run KoppelHet fetches the journal of that run.
- The Nmbrs accounts are translated to the Unit4 ledger, with the cost centre on every line.
- The journal goes to the familiar batch processing (GL07) in Unit4, where finance reviews and posts it.
Back: Payroll journal per run · Journal lines per cost centre
What to watch for with Unit4 ERP and Nmbrs
- In Nmbrs an integration can add a cost centre or change its description, but not close it. If finance closes a cost centre in Unit4, it stays in Nmbrs and KoppelHet reports which employees are still linked to it.
- In Nmbrs cost centres belong to one company, not to the whole environment. With several Dutch entities KoppelHet only adds each cost centre to the companies that use it.
- Nmbrs ties the journal to the company's active year. Around year end KoppelHet checks whether a late run still belongs to the old year, so the posting lands in the right Unit4 period.
- Nmbrs can deliver the journal per cost centre, per department or per employee. For Unit4 we usually choose per cost centre, as that is where finance posts the split.
- If an extra payroll run takes place in the same month, it becomes a second posting in the same Unit4 period, with its own description.
- Unit4 is often the ERP of the whole group, with only the Dutch entity in Nmbrs. KoppelHet then posts the journal in the Unit4 company of that entity, in euro, and leaves consolidation to finance.
- Unit4 checks accounts, periods and cost centres itself when processing the batch. A rejected batch stays in place and appears as an alert in the KoppelHet platform.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
What happens to a cost centre that is closed in Unit4?
It remains in Nmbrs, as Nmbrs does not allow closing it through an integration. KoppelHet reports the closed code with the employees still assigned to it, so payroll can move them before the next run.
Can the journal go to Unit4 per employee?
Yes, Nmbrs provides that variant too. Finance usually chooses account and cost centre, as per-employee detail is already visible in Nmbrs.
We have three Nmbrs companies and one Unit4 environment. Does that work?
Yes. Per Nmbrs company we record which Unit4 company the journal goes to and which cost centres belong to it.
Is a correction run posted too?
Yes, as a separate posting with the run number in the description. Finance can then see which posting belongs to which run.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Unit4 ERPx is read through the Attribute Values API (attributeValue, description, companyId, status C = terminated) and written through the Financial Transaction Batch API for the GL07 import process (account, accountingDimension, currencyAmount with credit negative, period).
- Nmbrs is read and written through the SOAP API (CompanyService; add or update cost centres per company, no close; journal per run as XML, also per cost centre, department or employee). The run ID goes into the batch description.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Unit4 ERP | Field in Nmbrs | Notes |
|---|---|---|
attributeValue | Code (kostenplaats) | The code stays the same in both systems |
description | Description | |
companyId | CompanyId | Lookup table between Unit4 company and Nmbrs company |
status (C = beëindigd) | Geen equivalent | Nmbrs has no close action in the API; the integration reports it |
Grootboekrekening in het Nmbrs-journaal | account | Through a chart of accounts mapping |
Kostenplaats in het Nmbrs-journaal | accountingDimension (kostenplaats) | |
Bedrag debet/credit | currencyAmount | Credit becomes a negative amount |
Run en periode | period en externe referentie | The Nmbrs run ID goes into the description, so the posting can be traced |
Related
ADP Workforce Now → Unit4 ERP
ADP Workforce Now to Unit4 integration: workers from ADP as employees in Unit4 ERP, with cost centre and manager
AFAS Profit → Unit4 ERP
AFAS to Unit4 integration: payroll journal posted in Unit4 ERP
BambooHR → Unit4 ERP
BambooHR to Unit4 integration: employees from BambooHR in Unit4 ERP, with department, job and end date
BuddeeHR → Unit4 ERP
BuddeeHR to Unit4 integration: Buddee position periods as dated relations in Unit4