Payroll to finance
Nmbrs to AllSolutions integration: the journal of every payroll run in the AllSolutions ledger
With an integration between Nmbrs and AllSolutions, the journal of every completed payroll run in Nmbrs lands automatically as a posting in AllSolutions, per Nmbrs company in the matching AllSolutions company, on GL account, cost centre and cost unit. An extra or correction run becomes its own posting with the run number attached, so finance can trace every posting back to Nmbrs.
What the integration does
Organisations that run payroll in Nmbrs and keep projects, hours and finance in AllSolutions download a journal per company after every run and retype the totals. If cost units in Nmbrs stand for projects, which cost unit belongs to which project is often only recorded in a spreadsheet.
- Payroll completes the run in Nmbrs, as today.
- KoppelHet sees the new run and fetches the journal per Nmbrs company, split by cost centre and cost unit.
- Account, cost centre and cost unit are translated to the AllSolutions codes, through tables that finance maintains.
- One posting per run lands in the matching AllSolutions company, with run number and period in the description.
- Finance reviews the posting in AllSolutions and completes processing there.
What to watch for with Nmbrs and AllSolutions
- Every legal entity is its own company in Nmbrs with its own runs. The AllSolutions integration account always starts in one company, so KoppelHet switches company in AllSolutions per entity before posting that entity's journal.
- AllSolutions records one line per call through the integration and charges above 20,000 calls per month. A per-employee journal from Nmbrs would quickly exceed that. We therefore request the journal per cost centre and cost unit, not per employee.
- AllSolutions is built for project organisations; Nmbrs has no projects but does have cost units. If you use cost units in Nmbrs as a project code, the cost unit becomes the project in AllSolutions, so payroll costs land directly on the project.
- Nmbrs fetches the journal within the company's active year. A run after year end that still belongs to December is posted, by agreement, in the old AllSolutions financial year and not in January.
- AllSolutions checks account, cost centre and journal book with the same rules as on the posting screen. A cost centre that only exists in Nmbrs therefore gives the same error as manual posting; KoppelHet holds the whole run and shows the line.
- Nmbrs can have several runs per month, for example an extra run for a bonus. KoppelHet records per run which posting was created in AllSolutions, so a run is never posted twice when the integration restarts.
- AllSolutions processing functions are closed to integrations. The Nmbrs journal is therefore staged as a recorded posting, and finance does the processing itself.
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 cost centres also go from AllSolutions to Nmbrs?
That can be added later as an extension. Nmbrs lets an integration add cost centres and cost units per company, so HR only picks codes that exist in AllSolutions.
What if a run in Nmbrs is rolled back?
Then KoppelHet reports that a posting already exists in AllSolutions for that run. Finance decides whether to reverse it; the integration does not delete postings.
Do we need an AllSolutions acceptance environment for this?
We recommend it. AllSolutions lets you export the REST API settings from acceptance and import them into production, so we test with a real run first.
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 API (CompanyService) - Run_GetList for the runs per year and Journals_GetByRunCostCenterCostUnit for the journal per run with cost centre and cost unit; the year comes from the company's active year. The SOAP API stops in 2027; where the REST API returns the same data, we move over.
- AllSolutions through the REST API - login with POST /api/v1/Login (ClientId, Secret ID and SHA1 signature), switching company through MWZBDR and the afdelingWijzig action, records with POST /api/v1/{browserlabel}, lines through a shortcut with one POST per line. Field names are the REST API labels the customer sets.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in AllSolutions | Notes |
|---|---|---|
Grootboekrekening in het Nmbrs-journaal | Grootboekrekening | Through a lookup table between both charts of accounts |
Kostenplaats | Kostenplaats | |
Kostendrager | Project | Only when the cost unit in Nmbrs stands for a project |
Bedrag | Bedrag | Decimal with a point |
Bedrijf (CompanyId) | Inlogbedrijf in AllSolutions | Fixed mapping per entity |
Run en periode | Omschrijving en boekdatum | The run number makes the posting traceable |
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