What is AFAS Software, in brief and honestly?
AFAS Software is a Dutch ERP vendor based in Leusden with a dominant position in the Dutch SME and mid-market segment. Its flagship product, AFAS Profit, is an integrated suite that brings financial administration, payroll processing, HRM, project administration, tax filing, order management and CRM together in one environment. The stack was originally on-premise; the vast majority of the installed base now runs on AFAS Online, the cloud version.
AFAS has one trait that sets it clearly apart from international ERP players: the product was born in the Dutch context of tax, payroll and collective labour agreements (CAOs). Payroll tax, holiday allowance, CAO provisions, VAT returns, ICP listings: all of this belongs natively in the product and is updated every year for new legislation. At the same time, Profit, like any package, embodies a specific view of how an organisation works: great when your processes match it, restrictive as soon as they deviate. This article is about that trade-off: not bashing AFAS, not claiming that custom is always better, but getting clear on when each option fits.
AFAS Profit covers standard Dutch SME processes in an integrated way: finance, payroll, HR, projects. Custom software pays off when you have industry-specific workflows the modules don't cover, want customer or employee experiences that call for your own branding and flow, or want to build a data layer that works on top of AFAS.
The Profit modules at a glance
If you are weighing up AFAS, you need to know which modules do the work. These are the three clusters we come across most often.
Finance
Financial administration is historically the core: general ledger, accounts receivable, accounts payable, fixed assets, project administration, tax returns and consolidation. For Dutch SMEs, this layer covers practically everything a controller needs, with a direct link to Dutch Tax Authority flows. It is robust and well maintained — most organisations running AFAS do so primarily for this reason.
HRM, Payroll and InSite
The HR and payroll modules are AFAS' strongest card in the Dutch market. Payroll calculation, expense claims, absence, personnel files and the InSite employee portal all sit on the same database as the financial administration. For organisations with standard Dutch collective labour agreements, payroll errors occur less often in the handover between systems, because there is hardly any handover.
CRM, order management and projects
The picture is more nuanced here. AFAS CRM and order management work well for organisations with a transactional sales process and common quote and invoice formats. For commercial organisations with complex deal structures, multi-channel sales or their own customer experience, we more often see AFAS stay in place for finance and HR, while CRM and sales tooling sit outside Profit.
Where AFAS excels
An honest comparison starts by acknowledging where the package simply gets it right. Here are four areas where AFAS consistently scores well.
Dutch compliance built in
Payroll tax, holiday entitlements, transition payments, VAT supplements, EC sales list returns — AFAS builds all these Dutch tax and employment law updates into the product every year. If you write a payroll engine yourself, or have one written, you take on that maintenance burden. That is no small task. For organisations with no reason to carry that burden, there is a lot of value here.
End-to-end integration between modules
Because finance, HR, payroll, projects and CRM share a single data model, many classic integration bottlenecks disappear. Time logged on a project flows automatically through to payroll calculation and invoicing. A new employee gets a personnel file, salary statement, project role and user account in a single step. That is work that would have to be stitched back together with separate SaaS tools.
Dutch mid-market fit
AFAS is built for the scale and complexity at which most Dutch mid-market organisations operate. Getting it implemented takes work, but nowhere near the scale of an SAP or Oracle programme. The Dutch implementation partner market is also mature; you can find people who know the package well fairly quickly.
InSite and OutSite portals
The built-in portals for employees and external parties cover a reasonable range of self-service needs: leave, expense claims, file access, applicant flows. For organisations without their own branding requirements on these touchpoints, that is often enough. Later in this article we cover when it starts to fall short.
Where package limits appear
No package covers everything. Here is a pragmatic set of places where we see AFAS users hit a wall.
Industry-specific workflows
As soon as a sector has work processes that are not in the standard modules — for example inspection rounds with photo and GPS evidence, production traceability through batches and lot numbers, planning boards with domain rules that fall outside AFAS' project model — you hit the limit of what the package models. Additions via custom fields help up to a point; after that, you end up working against the tool.
Customer or supplier portals with your own branding
InSite and OutSite are handy for internal and standard external flows, but they are no replacement for a commercial customer portal with its own brand identity, custom UX and more complex ordering or case-file functionality. For organisations that see their own customer portal or dealer portal as part of their proposition, a separate application with an integration to AFAS is almost always the better route.
Atypical integrations
Connecting to other systems is possible via AFAS Connect and the REST API, but the quality of the result varies by use case. Simple master data exchange works smoothly; more complex flows with event-driven updates, high frequency or bidirectional synchronisation call for a well-thought-out integration architecture around them. You can read more about how we set that up on the page about smart API integrations.
Reporting and customer-facing apps
AFAS has reporting, but as soon as you want to analyse broadly across modules, combine external data or provide dashboards for people without a Profit account, you end up needing your own data layer — a data warehouse or BI platform that pulls data from Profit via GetConnectors and enriches it elsewhere. The same pattern applies to customer experiences: mobile apps, commerce layers, booking platforms or service apps are built separately and then connected. AFAS is back office, not front office.
What is custom software in this context?
Custom software in an AFAS context rarely means "replacing AFAS entirely". Far more often it is software that lives alongside or on top of AFAS: a dedicated application for a specific process, a portal for a specific target group, an integration layer that links several systems together, or a data and AI layer that works on top of AFAS data.
A good implementation builds on standards — REST/JSON, OAuth 2.0, OpenAPI contracts, common event buses — so that the custom layer doesn't just talk to AFAS but to the rest of your stack as well. Its design depends on where the centre of gravity lies: close to AFAS (an extension of InSite with its own UX), alongside it (an operational application with asynchronous synchronisation of master data), or clearly above it (a data platform that draws on multiple sources and uses AFAS as just one of the inputs).
The hybrid approach: AFAS as the backbone, custom software on top
The route we see working most often in practice is a hybrid one. AFAS remains the backbone for finance, HR and payroll; custom software fills the gaps where AFAS has no suitable module or where the standard functionality falls short. In practice, that means:
- AFAS Profit as the system of record for financial administration, payroll, personnel files and the core registration of projects and relationships.
- Custom application(s) for industry-specific operations: planning, inspections, production traceability, customer experiences, dealer or partner portals, AI-assisted work.
- An integration layer that synchronises master data and transactions bidirectionally — employees, projects, customers, hours and invoicing where useful — via AFAS Connect or the REST API.
- Optionally, a data platform that combines data from Profit with operational data from the custom application, plus external sources, for analytics, BI and AI applications.
The key design principle is to determine, for each data element, which system is the system of record. An employee lives in AFAS, a production batch in the custom application, an inspection photo in the custom application, a payslip in AFAS. Clear ownership prevents synchronisation spaghetti, recurring double entry and conflicts where two systems overwrite each other's data.
AFAS Connect, REST API and GetConnectors
The integration side deserves its own section because many hybrid projects stand or fall on it. AFAS offers roughly three integration routes; they are not mutually exclusive, and most serious integrations combine them.
UpdateConnectors and GetConnectors
The classic AFAS integrations run via Connectors: GetConnectors for reading data from Profit, UpdateConnectors for writing it back. You configure in AFAS which fields you make available, and your custom system retrieves or writes that data via the Connect layer. For reporting and data warehouse purposes this is a solid route: stable, explicitly configured, and transparent about who sees what.
REST API
For several years now, AFAS has offered a more extensive REST layer that makes more modern integration patterns workable: synchronising master data, writing back transactions, running queries across the data model. For real-time use cases this is the more practical route. As with any vendor API, read the rate limits, plan for version changes and build proper error handling.
File exchange and EDI
For specific financial and HR flows, file exchange (XML, CSV, UBL) is still a serious option — bank statements, external payroll runs or government filings. Not glamorous, but in compliance-heavy contexts often more stable.
Which route fits depends on data volume, real-time requirements and the complexity of the mapping. An honest proposal phase maps out the flows per data element before building begins — more on that approach on our page about integrations with existing systems.
For every AFAS integration, explicitly ask for a sandbox/test environment and testable retry and monitoring flows. Production integrations that can only be tested in production cause problems at the worst possible moments.
An AI layer on top of AFAS data
One topic that comes up in almost every conversation is what you can do with AI on AFAS data. AFAS itself is building AI functionality into parts of the package, which covers a number of generic use cases. For organisations that want to go further — their own models, prompts, knowledge sources and governance — a custom layer is the obvious choice.
The practical design choice is not to build AI functionality inside AFAS, but in a separate environment that reads via GetConnectors or REST, enriches data with other sources, and returns results through its own interface. Examples we see: invoice preparation with general ledger suggestions, contract analysis per creditor, HR alerts based on absence or expense claim patterns, or a copilot for finance staff with questions about their own administration. Two points of attention: data governance (AFAS contains personal and financial data, so handle models, prompts and logs in a GDPR-compliant way) and human-in-the-loop (for finance and HR decisions, people remain responsible; AI flags and prepares).
A customer or employee portal with your own branding
InSite (employees) and OutSite (external parties) are AFAS's built-in portal solutions. For standard internal flows — leave, expense claims, file access — they work fine. For commercial customer portals, dealer environments, supplier sites with a distinctive UX, or employee apps with a strong brand identity, we more often see that a custom front end is the better route.
That custom front end reads from AFAS via REST or GetConnectors — invoices, contract details, project status, file elements — and writes back via UpdateConnectors where needed. The UX can be designed entirely freely, while the data stays in Profit as the source of truth. The trade-off depends on what a portal needs to deliver: only access to AFAS information, or also new functionality (interaction, configuration, content) that doesn't belong in AFAS. The more the second category applies, the stronger the case for a custom portal.
GDPR, Dutch payroll and eIDAS
With AFAS projects, compliance questions are rarely about AFAS itself and more often about everything around it. Three areas worth pausing on.
GDPR and data residency
AFAS hosts AFAS Online in the Netherlands and has a DPA model that is familiar territory for Dutch organisations. For data that lives in AFAS, a large part of the GDPR context is therefore covered. It becomes important as soon as you pull data from AFAS into a custom layer: where does that layer run, who has access, which sub-processors are involved, how long do you retain data? That belongs explicitly in the design.
Dutch payroll collective agreements (CAOs)
Payroll tax, holiday allowance, transition payments, collective agreement (CAO) rules: it's a complex moving target that AFAS actively tracks. Building this yourself is feasible for edge cases (temp-agency arrangements, international elements), but rarely makes sense as a wholesale replacement. The pragmatic rule: keep payroll in AFAS and build custom software around it.
eIDAS, audit trail and logging
For sectors where eIDAS-compliant signatures or identification flows matter (legal, healthcare, government), AFAS offers integrations with a few providers; more specific flows go through a custom integration. AFAS keeps logs within Profit, which is enough for most finance and HR audits. Custom applications get their own audit trail that fits sector requirements: append-only logs, events linked to users, exportable evidence trails.
TCO and ownership: look beyond the licence
The TCO discussion is often skewed. A package licence looks predictable; custom looks expensive in the short term. Over the longer term, which is usually what matters, the picture is more nuanced.
What gets underestimated in the TCO of off-the-shelf packages: implementation costs at the start, licence escalation as users and modules grow, maintenance of custom fields and integrations, implementation-partner work with every release, and workaround systems because the package can't handle one particular process. None of these costs is unique to AFAS; they are simply the reality of packaged software.
What gets underestimated in the TCO of custom software: maintenance after go-live, security patches, framework upgrades, an ongoing dev budget, and the attention the integration layer between custom software and AFAS requires. Anyone who buys custom software and lets it age pays again later. In most hybrid projects, the AFAS licences stay what they are and the custom budget goes to the parts where the package is not the right solution. For a deeper look at custom software budgets, read our guide to custom software costs.
When AFAS is enough
The pragmatic test: AFAS probably covers your needs if you can agree with three of the statements below.
- Our financial processes are standard for a Dutch SME: general ledger, accounts receivable, accounts payable, VAT, annual accounts.
- Our payroll follows common Dutch collective agreements (CAOs) without unusual arrangements.
- Our HR processes fit within standard leave, absence and personnel-file flows.
- Our order process is straightforward: quote, order, invoice in predictable formats.
- Our customers don't need a distinctive, branded portal; standard portals will do.
- Our reporting needs fall within what AFAS offers natively or within a simple BI integration.
In that case you'd be short-changing yourself by spending money on custom software where you don't need to. AFAS rolls out faster than a greenfield build project, the Dutch network of implementation partners is broad, and they largely take care of compliance maintenance. Our advice, though: don't deploy the package as an island. Make sure the integration routes (Connect, REST, GetConnectors) are set up clearly, that data export paths are defined, and that you have a view of where you might want to add custom software in a few years.
When custom development pays off
Custom software pays off when you do something distinctive that doesn't fit the standard modules, or when the package's limits force you into workarounds that become more painful every year. Patterns we see time and again:
- Industry-specific operational processes that don't fit AFAS's project or order structure, from production tracking to inspection flows, from planning boards with domain rules to logistics fleet-management routines.
- Customer portals with a distinctive brand identity, for example a dealer portal, a client environment in construction, or a service portal for healthcare relations with its own UX and functionality beyond what OutSite offers.
- Mobile apps for customers or employees that need offline capabilities, push notifications or native UX, and that combine data from AFAS with operational sources.
- AI applications on your own data, such as copilots for finance, alerts on HR patterns, or contract and invoice analysis, where governance and model choice must stay in your own hands.
- Multi-system integrations where AFAS is one of several systems and the integration layer is more complex than a simple Connect mapping.
- Operational data warehouses and analytics platforms that combine data from Profit with other sources, with dashboards that also work for people without an AFAS licence.
- Specific compliance or industry evidence flows that require their own registration and audit layer, which doesn't belong in AFAS.
Not every pattern means a large greenfield project. Often the first custom step is deliberately small: one process that clearly doesn't fit AFAS, delivered as a standalone application with an integration to Profit for the relevant master data. If you work with Exact Online, or are considering it, you'll find a similar trade-off in our guide on Exact Online vs custom software, as many of the patterns overlap.
How to decide: a workable process
No flowchart can make this decision for you. What does work is a four-step process.
1. Write down the processes, not the tool
Don't start with an AFAS shortlist or a request for custom software. Start with a document of a few pages describing what finance, HR, sales and operations actually look like at your company: who does what, which decisions are made, which data is involved, which laws and standards apply, and which other systems are involved. That document is your touchstone.
2. Run an honest fit analysis on AFAS
Hold that document up against AFAS Profit. Not "what does the brochure say?" but "what does the system do when we want this specific process in it?". Preferably with a proof of concept or an implementation partner with experience in your segment. What fits, what fits with adjustments within the package, and what clearly doesn't fit?
3. Make the custom question concrete
If some processes fit AFAS poorly or not at all, describe what the custom layer should actually do, and be more specific than "a system of our own". Which users, which flows, which integrations with AFAS, which compliance requirements? The less vague you are, the faster a serious build partner can come back with a sound proposal.
4. Plan for growth, not for an end state
Custom projects land best in phases: a minimum workable version first, get it live in production, gain experience, then keep building. The same applies to AFAS implementations (don't roll everything out at once) and to the integration layer (start with one bidirectional flow and expand based on what works).
For every project, whether an AFAS implementation, a custom build or a hybrid, ask for a testable data export procedure. A real extraction on real data, not just a promise in the DPA. That tells you whether an exit is ever feasible.
Frequently asked questions
Can AFAS be replaced entirely by custom software?
Technically, a lot is possible, but in practice it almost never pays off. AFAS's core value, financial administration and payroll with Dutch compliance maintenance, is a large body of work to build yourself and keep up to date. For most organisations, the hybrid route (AFAS for finance/HR, custom for the rest) is wiser than a full replacement.
Is AFAS Online cloud-native?
AFAS Online is a hosted version of the package run by AFAS itself, on Dutch infrastructure. Operationally that is cloud-like (no server management of your own), but architecturally it is not multi-tenant SaaS in the modern sense. In practice that rarely matters, but it can for specific integration or performance requirements.
What if we're already deep into AFAS?
Then the pragmatic question is not "should we migrate away?" but "where does a custom layer add value?". Start with one process that fits poorly in AFAS, deliver it as a separate application integrated via Connect or REST, and build on from there. Many hybrid projects start small.
How does AFAS compare to Exact Online?
Both are Dutch vendors with overlapping territory, but different characters. Exact Online is cloud-native by origin and stronger as a pure financial SaaS administration; AFAS has the broader suite (HR, payroll, projects, CRM). For organisations that only want finance, an Exact comparison is more relevant; for organisations with integrated HR/payroll needs, AFAS is closer to what they are looking for. Also read our guide on Exact Online vs custom software for that side.
Does AFAS work well with external BI tools?
Yes. Power BI, Tableau, Looker and your own data warehouses can pull data from AFAS via GetConnectors or REST. Keep data modelling in mind: AFAS's internal model is not a one-to-one analytics-friendly star schema, so there is usually a transformation layer between Profit and your BI tool.
How much does a custom layer on top of AFAS cost?
That depends on scope: the number of flows, integration complexity, the number of users, the compliance context, and whether a mobile version is involved. A figure without context is misleading; a scoping conversation gives a more reliable picture. For background on how custom software budgets are built up, see our page on custom software costs.
How do you approach AFAS integrations?
For each data element, we determine which system is the source of truth. Then we choose the Connect route (UpdateConnectors/GetConnectors, REST API or a combination), model the mappings explicitly, and build retry, monitoring and logging paths. You can read more about this approach on the smart API integrations page.