INTEGRATIONSAFAS PROFIT + NMBRSConnect AFAS to Nmbrs
Nmbrs and AFAS meet in two situations. The books are in AFAS and payroll is in Nmbrs. Or HR works in AFAS Profit while a payroll firm runs payroll in Nmbrs. Nmbrs has its own integration for the journal entry; it doesn't cover employees.
ISO 9001 & 27001
- Journal entries comes from Nmbrs
- New employees goes to Nmbrs
- Changes and leavers goes to Nmbrs
- Payroll status comes from Nmbrs
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
Nmbrs has integrations with AFAS Profit and AFAS SB, built and maintained by Nmbrs, that send journal entries from Nmbrs to AFAS automatically. They're available in Nmbrs at no cost. So for the accounting side, you rarely need an integration of your own.
It's different when AFAS Profit is also your HR system. Then a new employee, a change of address or a leaver exists in AFAS first and has to reach Nmbrs. The Nmbrs integration with AFAS doesn't do that. You build it on AFAS's GetConnectors and the Nmbrs REST API.
For each item: which direction it goes, when, and why. This is the starting point; in the first conversation we fit it to your situation.
- 01Journal entriesNmbrs → AFAS Profitafter payroll
The Nmbrs integration sends the journal entries to AFAS Profit or AFAS SB automatically.
- 02New employeesAFAS Profit → Nmbrswhen someone joins in AFAS
A GetConnector returns name, address, start date and employment. The integration creates the employee in Nmbrs through the REST API.
- 03Changes and leaversAFAS Profit → Nmbrson a change in AFAS
AFAS doesn't send a webhook when an employee changes. So the integration requests the changed records periodically and passes them on to Nmbrs.
- 04Payroll statusNmbrs → AFAS Profitwhen a run is finished
A Nmbrs webhook reports that a run is finished or a journal has been created. The integration can then create a file item or task in AFAS.
Not always. If an existing integration for AFAS Profit and Nmbrs does exactly what you need, we'll tell you.
For journal entries there's the Nmbrs integration with AFAS Profit and AFAS SB, free in Nmbrs. How to set it up is in the Nmbrs knowledge base.
For employees from AFAS HR you build your own integration. Nmbrs itself describes a scenario for builders to synchronise employees, with the REST API and consent per employer. We can connect AFAS to any system, Nmbrs included.
- HR works in AFAS Profit and new employees have to reach Nmbrs without retyping.
- Leavers recorded in AFAS have to be in Nmbrs in time, before the next run.
- Your integration between AFAS and Nmbrs still runs on the Nmbrs SOAP API, which stops on 1 March 2027.
- You want to see the payroll status back in AFAS.
AI reads, sorts and prepares a suggestion. Where it matters, a person decides.
Checking changes
AI compares the changes from AFAS with what's in Nmbrs and flags anything unusual, such as a start date in the past or a second employment. The payroll administrator decides.
No payroll data to AI
Only let an AI step work with the HR data it needs, and don't give it write access in Nmbrs. Pay and BSN don't belong in a prompt.
Which system leads
AFAS for what HR records, Nmbrs for what payroll needs. Decide per field which system wins, especially for address and bank account.
Periods
Nmbrs works in periods. Decide per change which date determines the period, the effective date or the processing date. Otherwise a correction follows in the next run.
Consent per employer
With the Nmbrs REST API, consent is per employer, not through a master login. If you have several employers in AFAS, keep track per employer of whether the integration is still running.
No webhook from AFAS
AFAS sends webhooks for file items and workflows, not for employees. Request changed employees periodically, and now and then compare the full set to catch missed changes.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Journal entries, New employees, Changes and leavers, Payroll status.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: Which system leads, Periods, Consent per employer, No webhook from AFAS.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Does Nmbrs have an integration with AFAS?
Yes, for journal entries. Nmbrs has integrations with AFAS Profit and AFAS SB that send journal entries to AFAS automatically. They're built and maintained by Nmbrs and available at no cost.
Do employees from AFAS go to Nmbrs automatically?
Not with the Nmbrs integration, which covers journal entries. For that you build an integration on AFAS's GetConnectors and the Nmbrs REST API.
What does the end of the Nmbrs SOAP API mean for my AFAS integration?
If your integration still runs on the Nmbrs SOAP API, it has to move to the REST API before 1 March 2027. With REST, you arrange consent per employer.
How quickly does a change in AFAS show up in Nmbrs?
That's up to you. AFAS doesn't send a webhook when an employee changes, so the integration checks for changes at set times. Schedule those well before the payroll run, so the payroll administrator can still review the changes.
Can I see payroll costs from Nmbrs per department in AFAS?
That depends on how the journal entry comes in. Make sure departments and cost centres have the same codes in Nmbrs and AFAS, and agree in which system a new one is created first.
Related services
- Connect AFAS to HubSpotConnect AFAS to HubSpot: a won deal becomes a customer account and order in AFAS, and sales sees in HubSpot which invoices are still outstanding.
- Connect AFAS to SalesforceConnect AFAS to Salesforce: accounts, opportunities and invoices flow both ways, within the API limits and with AFAS as the financial source of truth.
- Connect AFAS to TOPdeskConnect AFAS to TOPdesk: employees, departments and branches flow from AFAS into the service desk, and a new starter or leaver triggers a request.
- Connect AFAS to Microsoft 365Connect AFAS to Microsoft 365: a new employee in AFAS gets an account and groups in Entra ID, and the account is blocked when they leave the organisation.
- Connect AFAS to ChatGPTConnect AFAS to ChatGPT: give an AI assistant safe access to AFAS through an MCP server with limited permissions, and keep salary and BSN data out of it.
- AFAS KVK integrationAFAS KVK integration: what Zoeken in KvK in Profit already does, when to connect the KVK API yourself, and how UpdateConnectors keep organisations current.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.
- Nmbrs: AFAS integration (in Dutch)
- Nmbrs: Building a Nmbrs integration
- Nmbrs Developer Portal: Documentation
- Nmbrs Support: Webhooks
- AFAS Help Center: Webhooks on file items and workflows (in Dutch)
- AFAS Help Center: Retrieving changed data with a GetConnector (in Dutch)
- AFAS Help Center: REST API for developers (in Dutch)