Payroll to finance
Dynamics 365 and Nmbrs integration: shared cost centres and a posted payroll journal
With an integration between Microsoft Dynamics 365 and Nmbrs, cost centres and cost units from Dynamics reach the right Nmbrs company automatically, and the journal of every payroll run then lands in Dynamics 365 by itself. The export file that is now converted and imported by hand after every run is no longer needed.
What the integration does
International companies that book in Microsoft Dynamics 365 Business Central and have Dutch payroll run in Nmbrs, sometimes by an external payroll firm, pass on new cost centres by email. The journal from Nmbrs reaches the accountant as a file, who converts it into a Business Central import.
- Finance creates a cost centre or cost unit in Dynamics for the Dutch branch.
- It then appears with code and description in that branch's Nmbrs company.
- After a completed payroll run KoppelHet fetches the journal of that run.
- The Nmbrs accounts are translated to the Dynamics ledger, with cost centre and cost unit on every line.
- The journal is staged in Dynamics. Finance posts it, or KoppelHet posts it directly if agreed.
Back: Journal per Nmbrs run · Amounts per cost centre and cost unit
What to watch for with Microsoft Dynamics 365 and Nmbrs
- Nmbrs lets an integration add and update cost centres, but not delete them. A cost centre no longer used in Dynamics stays in Nmbrs; KoppelHet reports which employees are still linked to it.
- Nmbrs keeps cost centres and cost units separately, Dynamics only has free dimensions. At the start we record which Dynamics dimension is the cost centre and which the cost unit.
- The Nmbrs journal can be requested per run for the whole company, per cost centre, per department or per employee. We pick the level at which finance wants to post in Dynamics.
- Business Central can also post a journal directly through the integration. KoppelHet only does so if finance chooses to; otherwise the journal stays as a draft.
- Nmbrs uses the company's active year for the journal. If a December run is still processed in January, KoppelHet checks the period before anything is posted in Dynamics.
- If an external payroll bureau works in Nmbrs, that bureau does not get access to Dynamics. The integration has its own, separate access to both systems.
- If you use Dynamics 365 Finance instead of Business Central, the journal lands in Finance's standard journal tables. It must then be set once how account and cost centre are supplied together.
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
Can closed cost centres disappear from Nmbrs automatically?
No, Nmbrs does not allow that through an integration. KoppelHet does report them, with the employees still on them, so payroll can move them.
Our payroll bureau runs payroll. Does it notice the integration?
It sees new cost centres appear in Nmbrs. Otherwise it works as usual; the journal goes to Dynamics after the run.
We have several Nmbrs companies. How does the integration know where the journal goes?
Per Nmbrs company we record which Dynamics company it belongs to. Each journal only goes to that company.
Does this work with Business Central and with Dynamics 365 Finance?
Yes. The process is the same for both; only the connection on the Dynamics side differs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read and written through the SOAP API (CompanyService, including CostCenter_Insert and CostUnit_Insert for cost centres and cost units, and the journal operations per run). Where the REST API offers the same operations we switch; the SOAP API is retired from 1 March 2027.
- Business Central through the standard API (dimensionValue, journal with the post action, journalLine with dimensionSetLines, one signed amount, RunId in documentNumber).
- Dynamics 365 Finance through the OData entities for journal headers and lines; the financial dimension configuration for integrations must be set up.
- Access with a dedicated Nmbrs token and a dedicated app registration in Microsoft Entra ID.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Microsoft Dynamics 365 | Field in Nmbrs | Notes |
|---|---|---|
dimensionValue.code (kostenplaats) | Code (CostCenter_Insert) | |
dimensionValue.displayName | Description | |
dimensionValue.code (kostendrager) | Code (CostUnit_Insert) | Only if the customer uses cost units in Nmbrs |
Company | CompanyId | Fixed mapping between Dynamics company and Nmbrs company |
Rekening in het Nmbrs-journaal | accountNumber | Through a chart of accounts mapping |
Kostenplaats in het Nmbrs-journaal | dimensionSetLines (kostenplaats) | |
Debet en credit | amount | Credit as a negative amount |
RunId | documentNumber | Makes every posting traceable to the run |
Related
ADP Workforce Now → Microsoft Dynamics 365
ADP Workforce Now to Dynamics 365 integration: workers from ADP as employees in Business Central, with dimensions and status
BambooHR → Microsoft Dynamics 365
BambooHR to Dynamics 365 integration: BambooHR job info as employee and dimensions in Business Central
BuddeeHR → Microsoft Dynamics 365
BuddeeHR to Dynamics 365 integration: employees and dimensions from Buddee in Business Central
Dayforce → Microsoft Dynamics 365
Dayforce to Dynamics 365 integration: employees from Dayforce in Business Central, with department and approver