Payroll to finance
SAP S/4HANA and Nmbrs integration: cost centres from SAP in Nmbrs, payroll journal back as a journal entry
With an integration between SAP S/4HANA and Nmbrs, the cost centres of the Dutch company code reach the right Nmbrs company automatically, and the journal of every payroll run then lands in S/4HANA as a journal entry. Payroll only picks cost centres SAP knows, and finance gets the payroll journal without a manual upload.
What the integration does
Organisations with SAP S/4HANA as group ERP and Dutch payroll in Nmbrs, often at a payroll bureau, pass on new cost centres by email and convert the Nmbrs journal into an SAP upload after every run. Without an integration the list in Nmbrs goes out of date and the upload gets stuck on a cost centre SAP no longer knows.
- Finance opens a cost centre in S/4HANA for the Dutch company code.
- It then appears with code and description in the Nmbrs company belonging to that company code.
- After a completed payroll run KoppelHet fetches that run's journal, per cost centre and cost unit.
- The Nmbrs accounts are translated to the SAP ledger.
- The journal entry goes to S/4HANA; KoppelHet checks whether SAP has processed it.
Back: Journal entry per Nmbrs run · Amounts per cost centre and cost unit
What to watch for with SAP S/4HANA and Nmbrs
- An SAP cost centre belongs to a controlling area and a company code. KoppelHet only takes the cost centres of the Dutch company code, so Nmbrs gets no cost centres from other countries.
- Through an integration Nmbrs can add and update a cost centre, but not close it. When a cost centre's validity ends in SAP, it stays in Nmbrs and KoppelHet reports which employees are still on it.
- Not every SAP cost centre is meant for payroll costs. With a custom field in the SAP master data finance marks which cost centres may go to payroll; the standard read API includes such a field after extension.
- Nmbrs can deliver the journal per run per cost centre and cost unit combined. That fits SAP, where cost centre and a second assignment sit on the same line.
- If document splitting is active in SAP, one payroll journal can produce far more lines than Nmbrs delivers. SAP then advises the asynchronous posting; KoppelHet uses that by default and reads back the result.
- Nmbrs ties the journal to the company's active year. If a December run is still processed in January, KoppelHet checks whether the SAP December period is still open before anything is posted.
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 works in Nmbrs. Does it notice the integration?
It sees new cost centres appear. The journal goes to SAP after the run by itself; the bureau gets no access to SAP.
Can the integration remove closed cost centres from Nmbrs?
No, Nmbrs does not allow that through an integration. KoppelHet reports them with the employees still on them.
Does this also work with S/4HANA on premise?
The process is the same; which SAP APIs are available differs per edition. We agree that with your SAP administrator.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- S/4HANA Cloud through Cost Center - Read (A2X), API_COSTCENTER_SRV (extensible with custom fields through FINS_COST_CENTER), and Journal Entry - Post (Asynchronous), JournalEntryBulkCreationRequest_In, with checks in the AIF message monitor.
- Nmbrs calls the SOAP API deprecated (retiring in 2027). The SOAP CompanyService includes CostCenter_Insert, CostUnit_Insert and Journals_GetByRunCostCenterCostUnit; whether the REST API has the same operations has not been checked because that documentation only loads with JavaScript.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP S/4HANA | Field in Nmbrs | Notes |
|---|---|---|
CostCenter (S/4HANA) | Code (kostenplaats in Nmbrs) | |
Omschrijving kostenplaats | Description | |
CompanyCode | Nmbrs-bedrijf (CompanyId) | Fixed mapping per company code |
Rekening in het Nmbrs-journaal | Grootboekrekening in SAP | Through a chart of accounts mapping |
Kostenplaats in het Nmbrs-journaal | Kostenplaats op de journaalregel | |
Kostendrager in het Nmbrs-journaal | Extra toewijzing, bijvoorbeeld WBS-element | Agreed per customer |
Debet en credit | Bedrag met debet- of creditkenmerk | |
RunId | Referentie in de kop van de journaalpost | Makes every posting traceable to the run |
Related
BambooHR → SAP S/4HANA
BambooHR to SAP S/4HANA integration: BambooHR employees as workforce persons with company code and cost centre
Dayforce → SAP S/4HANA
Dayforce to SAP S/4HANA integration: employees from Dayforce as workforce and business partner in S/4HANA
Deel → SAP S/4HANA
Deel to SAP S/4HANA integration: own employees and EOR from Deel as workforce persons, per company code
Exact HR → SAP S/4HANA
Exact HR to SAP S/4HANA integration: Dutch payroll costs from Exact Online payroll as a journal entry in S/4HANA