Payroll to finance
Nmbrs to Sage Intacct integration: every Nmbrs payroll run as a journal entry on the right entity
With an integration between Nmbrs and Sage Intacct, the journal of every payroll run in Nmbrs arrives in Sage Intacct automatically as a journal entry, per Nmbrs company on the matching entity and split over departments and projects. Bonus and correction runs each get their own journal, so finance can see in Intacct per run what was posted.
What the integration does
Organisations that run Dutch payroll in Nmbrs and report to a parent that uses Sage Intacct export the journal after every run, put it into the Intacct import template and look up entity and department. Bonus runs and corrections easily get mixed up with the regular monthly run.
- KoppelHet sees in Nmbrs that a new run has been completed.
- The journal of that run is fetched per cost centre and cost unit, for the year the run belongs to.
- KoppelHet translates accounts, cost centres and cost units to Intacct and picks the entity of the Nmbrs company.
- The journal goes to Intacct as a draft, with company, year and run number in the title.
- Finance posts the journal after review.
What to watch for with Nmbrs and Sage Intacct
- Nmbrs can supply the journal per company, per department, per cost centre, per cost centre with cost unit or per employee. For Intacct we choose the variant with cost centre and cost unit, so both can land as department and project without any per-person data going along.
- The default variant of the Nmbrs journal takes the company's active year. A December run fetched only in January would then look in the wrong year. KoppelHet uses the variant in which the year is passed, with the year the run belongs to.
- Every Nmbrs company is its own employer. If the group uses several entities in Intacct, every journal line needs an entity. KoppelHet records the entity per Nmbrs company and creates a separate journal entry per company and run.
- A bonus run or correction run is a separate run in the Nmbrs list for the year. KoppelHet puts the run number as reference in Intacct, so finance finds a bonus run apart from the monthly run and a run is never offered twice.
- Nmbrs posts in euro. If the Intacct environment has multi-currency enabled, because the parent reports in dollars or pounds, KoppelHet passes EUR per line, and Intacct converts with the rate type finance has set.
- Intacct posts through the API directly by default, unless the journal arrives as a draft. KoppelHet chooses draft, so finance reviews the payroll costs of the Dutch entity before they appear in the group figures.
- Nmbrs stops the SOAP API currently used to fetch the journal on 1 March 2027. Nothing changes on the Intacct side with the switch; KoppelHet moves to the REST equivalent as soon as it supplies the journal.
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 several Nmbrs companies post to one entity?
Yes. The integration then puts the company in the title and reference, so the journals can be told apart in Intacct.
Do departments from Intacct also go to Nmbrs?
Not in this integration. Putting cost centres from Intacct into Nmbrs can be added later as an extension.
What happens if a cost centre has no translation?
Then KoppelHet holds that run's journal and reports which code is missing. After it is added, the whole journal goes through.
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, and Journals_GetByRunCostCenterCostUnitPerYear (companyId, runId, year) for the journal as XML. Other variants - Journals_GetByRunCompany, Journals_GetByRunDepartment, Journals_GetByRunCostCenter, Journals_GetByRunEmployee. Journals_GetByRunCostCenterCostUnit without PerYear takes the company's active year.
- To Sage Intacct through the XML API, create on GLBATCH (JOURNAL, BATCH_DATE mm/dd/yyyy, BATCH_TITLE, REFERENCENO, STATE Draft) with GLENTRY lines (ACCOUNTNO, TR_TYPE, TRX_AMOUNT, DEPARTMENT, PROJECTID or CLASSID, LOCATION, CURRENCY and EXCH_RATE_TYPE_ID with multi-currency).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Sage Intacct | Notes |
|---|---|---|
Grootboekrekening uit het Nmbrs-journaal | ACCOUNTNO | Through a lookup table |
Debet of credit | TR_TYPE (1 of -1) en TRX_AMOUNT | |
Kostenplaats | DEPARTMENT | |
Kostendrager | PROJECTID of CLASSID | |
Nmbrs-bedrijf | LOCATION (entity) | |
Run, jaar en periode | BATCH_TITLE, REFERENCENO en BATCH_DATE |
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