Payroll to finance
Nmbrs to Oracle Fusion ERP integration: every Dutch payroll run as a journal in the group ledger
With an integration between Nmbrs and Oracle Fusion Cloud ERP, the journal of every completed Nmbrs run automatically arrives through the journal import in the ledger of that Nmbrs company, in the Oracle period the run belongs to. KoppelHet checks that Oracle really imported the journal, so Dutch payroll costs are not silently missing from the group figures.
What the integration does
Organisations with Dutch employees in Nmbrs and an international parent running on Oracle Fusion Cloud ERP often send the payroll journal as a spreadsheet to the shared service centre. It is retyped there into Oracle's import template, so Dutch payroll costs only appear in the group figures days after the run.
- Payroll completes a run in Nmbrs.
- KoppelHet sees the run in the company's run list and fetches the journal with the year of the run.
- Accounts, cost centres and cost units from Nmbrs become segment values in the chart of accounts of the matching ledger.
- KoppelHet creates an import file per run, loads it into Oracle and starts the journal import.
- KoppelHet follows the import job until it finishes and records per run whether the journal is in Oracle.
What to watch for with Nmbrs and Oracle Fusion ERP
- Nmbrs delivers the journal at several levels, including per company, per department, per cost centre, per cost centre with cost unit or per employee. Which level we choose depends on the segments in the Oracle chart of accounts. If it has no segment for cost units, we request the journal per cost centre.
- Every Nmbrs company is a separate employer with its own runs. In Oracle every journal line belongs to one ledger. KoppelHet records the ledger per Nmbrs company, so a run from one company can never end up in another company's ledger.
- Oracle determines the period from the accounting date. A December run that only happens in January is fetched by KoppelHet with the year it belongs to, and gets an accounting date in December. If that Oracle period is already closed, Oracle rejects the lines and KoppelHet reports this to finance.
- Nmbrs posts in euros. A ledger in Oracle can have another currency, for example dollars for an American parent. KoppelHet passes the amounts in euros with currency code EUR, and Oracle fills in the amount in the ledger currency.
- A bonus or correction run appears in Nmbrs as its own run in the year's run list. KoppelHet gives every run its own group number in Oracle, so every run becomes its own journal and the import errors of one run can be found separately.
- Loading and importing are two steps in Oracle that run in the background. KoppelHet only marks a Nmbrs run as processed when both steps have succeeded. A run that gets stuck halfway is offered again the next day.
- Nmbrs stops the SOAP API currently used to fetch the journal on 1 March 2027. Nothing changes on the Oracle side when moving to the REST API, because the import file and the journal source stay the same.
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
Who posts the journal in Oracle?
Finance, or the shared service centre. The integration imports the journal; posting stays a step in Oracle.
What happens if a period in Oracle is already closed?
Oracle rejects the lines. KoppelHet reports the run to finance, who opens the period or agrees another accounting date. The run then goes again.
Can several Nmbrs companies post into one ledger?
Yes, if finance wants that. The integration then records the company in a segment or in the description, so the companies can be told apart in Oracle.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the SOAP CompanyService - Run_GetList for the runs per company and year, Journals_GetByRunCostCenterCostUnitPerYear (companyId, runId, year) or Journals_GetByRunCostCenter for the journal as XML. When moving to the REST API we choose the equivalent as soon as it delivers the journal.
- Oracle Fusion through POST /fscmRestApi/resources/11.13.18.05/erpintegrations with OperationName importBulkData, ContentType zip, DocumentAccount fin$/generalLedger$/import$ and the journal import ParameterList; status through the ReqstId. A CallbackURL can report the status afterwards.
- Import file following GL_INTERFACE - LEDGER_NAME, ACCOUNTING_DATE, USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME, CURRENCY_CODE (three-letter ISO code), ACTUAL_FLAG A, SEGMENT1 onwards, ENTERED_DR, ENTERED_CR, GROUP_ID and the REFERENCE fields for batch, journal and line description. ACCOUNTED_DR and ACCOUNTED_CR are the amounts in the ledger currency.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Oracle Fusion ERP | Notes |
|---|---|---|
Grootboekrekening uit het Nmbrs-journaal | Segment natuurlijke rekening | Translation table per ledger |
Kostenplaats | Segment kostenplaats | |
Kostendrager | Segment kostendrager of project | Empty if the chart of accounts has no such segment |
Bedrag debet of credit | ENTERED_DR of ENTERED_CR | |
Valuta (euro) | CURRENCY_CODE EUR | |
Jaar en periode van de run | ACCOUNTING_DATE | |
Nmbrs-bedrijf | LEDGER_NAME | |
Run-ID en bedrijf | GROUP_ID, REFERENCE1 en REFERENCE4 |
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