Payroll to finance
Nmbrs to 4PS Construct integration: payroll journal after every run in 4PS, cost centres back to Nmbrs
With an integration between Nmbrs and 4PS Construct, the journal of every payroll run arrives per Nmbrs company as a batch in the right 4PS company, grouped by G/L account and cost centre. Cost centres that finance uses in 4PS are also in Nmbrs, so payroll only picks codes that exist in 4PS.
What the integration does
Anyone who has payroll run in Nmbrs, often by an external payroll firm, and keeps the books and projects in 4PS Construct enters the journal overview into a 4PS journal by hand after every run. A new cost centre sometimes only reaches Nmbrs months later, so labour costs end up in the wrong place.
- Finance creates a new cost centre in 4PS; shortly afterwards it is also in the right Nmbrs company.
- The payroll bureau completes the run in Nmbrs, as today.
- KoppelHet retrieves the journal of that run and totals the lines per G/L account and cost centre.
- The journal appears as a batch in the payroll journal of the 4PS company that belongs to that Nmbrs company.
- Finance reviews and posts. If a period or account is wrong, the batch is staged with a message instead of half posted.
Back: Cost centres from 4PS as cost centres in Nmbrs
What to watch for with Nmbrs and 4PS Construct
- One Nmbrs environment can hold several companies, and 4PS can have a separate company per operating company. We record per Nmbrs company which 4PS company receives the journal; a run of one company can never end up in the books of another.
- Nmbrs can deliver the journal for the whole company, per cost centre, per department or per employee. For 4PS we choose per cost centre by default, so a batch stays readable and the detail per employee stays in Nmbrs.
- In 4PS cost centres are dimension values managed by finance. KoppelHet reads them from 4PS and puts them in Nmbrs, because an integration cannot create them in 4PS. That makes 4PS the only place where a cost centre is born.
- Nmbrs lets an integration add and update cost centres, but not delete them. When finance closes a cost centre in 4PS, it stays in Nmbrs and KoppelHet reports which employees are still on it.
- A December run processed in January belongs in Nmbrs to the company's active year. KoppelHet checks year and period against the posting date in 4PS before staging the batch, so the costs do not fall into the new financial year.
- The payroll bureau works in Nmbrs and needs no access to 4PS. The integration has its own access to both systems, separate from the accounts of the bureau and of finance.
- Nmbrs will retire the old SOAP interface in March 2027. KoppelHet builds the journal retrieval so that the move to the REST API changes nothing on the 4PS side.
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
Our payroll bureau runs payroll. Does it have to do anything differently?
No. It sees new cost centres from 4PS appear in Nmbrs and completes runs as usual. The journal then goes to 4PS automatically.
Can the journal arrive in 4PS per employee?
It can, because Nmbrs also delivers the journal per employee. It does produce many more lines per batch and more salary detail in the ledger; finance usually chooses per cost centre.
What happens with a correction run?
It has its own run number in Nmbrs and arrives as a separate batch in 4PS. Finance then sees the correction next to the original posting.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the journal report per company (SOAP, Reports_GetJournalsReportByCompany, with run, period, year and G/L account). Cost centres go to Nmbrs through CostCenter_Insert in the SOAP CompanyService. The SOAP API ends on 1 March 2027; where the REST API offers the same data, we move over.
- 4PS Construct runs on Business Central. We write through the Business Central API v2.0 (journals and journalLines with dimensionSetLines, one signed amount) and read dimensionValues (GET only). Each company has its own route in the API.
- Business Central online limits API requests per user (6,000 per five minutes, at most 100 operations per batch request). A journal at cost centre level stays well below that.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in 4PS Construct | Notes |
|---|---|---|
Nmbrs-bedrijf | Company in 4PS | One fixed 4PS company per Nmbrs company |
Grootboekrekening in het journaal | accountNumber | Through a lookup table if the numbers differ |
Debet en credit | amount | Credit becomes negative |
Kostenplaats | dimensionSetLines (dimensie kostenplaats) | |
Run, periode en jaar | documentNumber en postingDate | The run number prevents a run from being posted twice |
dimensionValue.code en displayName (4PS) | Kostenplaats (code en omschrijving) in Nmbrs | Return direction |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll