Is it not just the integration but the system itself that matters? On applatenmaken.com you can read when it makes sense to build a custom ERP system, and when you are better off wrapping custom development around a standard core.

For a concrete example of a B2B webshop-to-ERP integration, with customer-specific price tiers and OCI or PunchOut, see Building a CloudSuite integration.

Category
Knowledge base
Subject
ERP & integrations
Reading time
14 minutes
Level
Decision maker
Updated
May 2026

ERP integrations: everything you need to know.

An ERP rarely stands alone. Almost every organisation connects SAP, AFAS, Exact or Microsoft Dynamics to a CRM, webshop, HRIS or BI tool. This guide explains which forms of integration exist, which pitfalls we see time and again, and how to set up a project realistically — for founders, IT managers and CFOs considering an ERP integration.

What is an ERP and why is integration so important?

An ERP (Enterprise Resource Planning) is your organisation's central administrative system. It tracks finance, inventory, purchasing, production and often HR. Well-known names on the Dutch market include SAP (S/4HANA, Business One, Business ByDesign), Oracle (NetSuite, Fusion Cloud, JD Edwards), Microsoft Dynamics (365 Business Central and Finance & Operations), AFAS, Exact (Online and Globe), Unit4 and, for scale-ups growing internationally, NetSuite.

An ERP does a lot itself, but rarely everything. Marketing runs in HubSpot or Salesforce. The webshop sits in Shopify or Magento. Payroll runs through Nmbrs or Visma. Reports are built in Power BI or Tableau. Without integrations, someone retypes orders, hours or customer data again and again, with all the errors and delays that come with it. That is why a well-integrated ERP is the rule rather than the exception.

i
In short

An ERP is your operational source of truth. Integrations determine how well that truth flows through the rest of your organisation, to CRM, webshop, HR, BI and compliance.

Why you want to integrate your ERP

The question is rarely "if", almost always "when and how". Over the past few years we have built dozens of ERP integrations and see the same drivers come up again and again.

Single source of truth

One place where the real number lives. One place where the customer data is correct. No more debates about whether the webshop, the CRM or the ERP is "right": the ERP is right, and everything else syncs. This alone prevents a huge amount of noise between sales, finance and operations.

Automating repetitive work

Orders that land in the ERP automatically. Purchase invoices that are read in automatically. Hours from a field-service app that end up in the payroll run. The effect is not just time saved; it also means less pressure on people to retype everything without errors.

Speed and growth

What still works manually at a hundred transactions a day does not scale to thousands. Many growing organisations only discover during a peak that their administration has become the bottleneck. A good integration solves that structurally.

Reporting and management information

An integrated ERP feeds BI dashboards with reliable, up-to-date figures: real-time revenue, margins, stock turnover and debtor position — not after the month-end close, but right now. For CFOs this is often the main reason to start an integration project: not the direct savings, but being able to steer on current figures instead of a month-old truth.

Customer satisfaction and internal frustration

A less discussed but very real effect: employees who no longer have to retype data are both more productive and happier. Customers who see accurate stock levels in the web shop and receive correct invoices complain less. It's not a romantic story, but you notice it in practice.

At the same time, an integration is not a throwaway project. You are tying two systems together, and replacing either one becomes more complex. Choosing a new web shop gets harder if the integration is deeply hooked into your processes. That's no reason not to do it, but it is a reason to approach it deliberately. Also read how we handle this in our smart API integrations.

Types of ERP integration

There are roughly five integration patterns you'll encounter in practice. The right choice depends on data volume, speed, complexity and what the other systems support.

1. Direct REST/SOAP API

The other system talks directly to your ERP's API. For modern ERPs (NetSuite, Business Central, SAP S/4HANA via OData) this is the most common route. The advantage is full control and low latency. The drawback is that you have to set up authentication, error handling, retries and version management yourself. For a fuller explanation of what API integrations actually are, see our guide on what an API integration is.

2. iPaaS (Integration Platform as a Service)

Platforms such as Mulesoft, Boomi, Workato, Make or n8n take a lot of the plumbing off your hands: connectors, mapping, monitoring, retries. For mid-sized organisations with multiple SaaS tools this is often a sensible choice. We compare both routes in detail in our guide API vs. integration platform — in short: iPaaS scales faster in breadth, a direct API scales better in depth.

3. EDI

Electronic Data Interchange is the classic way of exchanging B2B data between the ERPs of trading partners. Think EDIFACT or X12 messages for orders, delivery notes and invoices — still common, especially in retail, logistics and wholesale. EDI is solid but cumbersome: validation rules per partner, VAN providers, AS2 tunnels. We often combine it with modern API layers to hide the complexity from the business.

4. File drop

A simple route where CSV, XML or JSON files are exchanged via SFTP or a shared folder. It works well for batch processes that run once or twice a day, and is often the only option when one of the two systems has no API. The points to watch: idempotency, error handling and clear agreements on who cleans up what.

5. Message queue / event bus

For higher volumes or stricter SLAs we use Kafka, RabbitMQ, Azure Service Bus or AWS SQS. An event from the ERP lands on a bus, and every interested system consumes it at its own pace. The advantage: a failure in one consumer doesn't bring down the rest. The drawback: heavier infrastructure and more operational discipline.

!
Practical tip

Don't hesitate to combine several patterns: real-time orders via REST, daily batches for master data via file drop, suppliers via EDI. One integration architecture doesn't mean one technology.

Typical ERP integrations

Every integration is different, but in practice a few patterns come up again and again. Below are the most common directions we build.

ERP ↔ CRM

Synchronise customer and contact data between Salesforce, HubSpot or Microsoft Dynamics CRM and your ERP. Sales sees open items and credit limits in the CRM, while finance sees the sales pipeline alongside actual revenue. The key decision: which side is authoritative for which field — and what you do when they conflict.

ERP ↔ e-commerce

Connect webshops in Shopify, Magento, WooCommerce or a headless storefront to the ERP for products, prices, stock and orders. Orders flow from the webshop to the ERP, while stock and prices flow the other way. Real-time stock is the classic pitfall here: watch out for excessive load on the ERP API at peak times.

ERP ↔ accounting and invoicing

Some organisations run their operations in the ERP but keep their accounting separate in Exact, Twinfield or Yuki. Purchase invoices, sales invoices, bank transactions and general ledger mappings then flow between the two systems. For public tenders and e-invoicing, a Peppol integration is often part of that layer.

ERP ↔ HRIS and payroll

Employee data from AFAS, Visma, Nmbrs or Workday flows into the ERP for cost allocation, project staffing and authorisation. Hours and expense claims flow the other way towards payroll processing. Role changes (joining, leaving, contract changes) cause most of the bugs, and that is where most of the time goes.

ERP ↔ BI and data warehouse

For management information, a nightly or near-real-time export to Snowflake, BigQuery, Synapse or your own warehouse is common. Power BI, Tableau or Looker run on top of that. Data modelling is what matters here, because a raw ERP table is rarely report-ready as it stands.

ERP ↔ operational apps

Field service apps, warehouse scanners, shop-floor systems and customer portals all feed the ERP with operational data and read data back from it. We have plenty of experience with this: see, for example, our page on integrations within web development for concrete examples.

ERP ↔ logistics partners and marketplaces

For trading organisations, integrations with carriers (PostNL, DHL, DPD, Transsmart), 3PL warehouses and marketplaces (Bol, Amazon, eBay) are a category of their own. Track-and-trace, customs declarations, returns flows and commissions all come into play. Often it is a mix of direct APIs and EDI, sometimes routed via a transport management layer.

ERP ↔ document flows

Invoices, contracts, delivery confirmations and order confirmations are increasingly processed via Peppol or via specialised document platforms (DocuSign, PandaDoc, Klippa, Basware). The integration ensures that an incoming invoice lands in the ERP as a draft purchase invoice, with the OCR results already filled in.

APIs and pitfalls by ERP vendor

Not all ERPs are equally pleasant to integrate with. Below is a brief practical look at each platform. It is inevitably a snapshot, as vendors are constantly changing their APIs.

SAP

SAP S/4HANA offers OData and REST APIs via the SAP Gateway and, increasingly, via SAP BTP (Business Technology Platform). The pitfall: the documentation is extensive but scattered, and authorisations are complex (Communication Users, Scopes, RBAC). With older ECC installations you will still come across RFC, BAPI and IDoc. They are workable, but specialists are scarcer.

Oracle NetSuite

NetSuite has a SuiteTalk SOAP API, a newer REST API, and SuiteScript for in-platform logic. Token-Based Authentication is mandatory. The pitfall: rate limits are strict, and saved searches and REST records behave subtly differently.

Microsoft Dynamics 365 Business Central and F&O

Business Central has modern OData and custom API pages. Finance & Operations works via OData and the Data Management Framework for batches. Authentication goes through Azure AD with OAuth2. The pitfall: per-environment configuration and version upgrades that sometimes bring breaking changes.

AFAS Profit

AFAS offers GetConnectors (read), UpdateConnectors (write) and SubscribeConnectors (events). It is well documented and fairly strict on authorisation. The pitfall: custom fields require separate configuration on the AFAS side, and large datasets demand disciplined paging.

Exact Online and Globe

Exact Online has a REST API with OAuth2; volume and rate limits are restrictive for larger accounts. Exact Globe is a desktop product with different integration patterns (XML, ODBC, SDK). Don't simply combine the two.

NetSuite, Unit4, IFS and smaller vendors

For vendors with a less mature ecosystem, custom connectors or an iPaaS are often more practical. Always verify early on that the APIs actually support the objects and fields you need: brochure text is not a contract.

!
Essential preliminary research

A question for every vendor: documentation, sandbox access, rate limits per endpoint and the official policy on breaking changes. We always do this before a quote is finalised.

What does an ERP integration cost and how long does it take?

The cost and lead time of an ERP integration depend on four factors: the number of systems to integrate, the complexity of the mapping (how many fields, how many exceptions), the operational requirements (real-time or batch, retries, monitoring) and organisational maturity (are sandboxes available, is there a product owner, is the documentation complete).

ScopeLead timeIndication
Simple integration
Familiar systems, little business logic, batch
a few sprintsShorter project
Custom integration
Custom mapping, validation and exceptions
multiple sprintsMedium-sized project
Production architecture
Multi-system, message queue, monitoring, SLA
a programme of multiple sprintsLonger programme

What we don't do: give a fixed price tag at page level. ERP projects differ too much for that. What we do: after an introductory meeting and a short scoping, we give you an honest indication of complexity, lead time and budget, based on what we have built before. For the broader context on how costs are determined, see also our page on building a custom ERP system.

Compliance, GDPR and audit trail

An ERP integration often moves personal data and financial data between systems. That brings serious obligations. Three points you should explicitly think about before you go live:

GDPR

Which personal data passes through the integration? Do you have a data processing agreement with every party, including the iPaaS vendor? Is data stored in EU regions, or does anything leave the EEA? Logging must not capture personal data unnecessarily; PII in error logs is a classic audit finding.

Audit trail

Every successful or failed transaction must be traceable: who sent what to which system and when, and what the response was. For SOX, ISO 27001 and internal accountancy work, this is not a nice-to-have but a requirement. Build in audit logging from day one, not as an afterthought.

Access control and secrets

API tokens, OAuth credentials and passwords belong in a secrets manager, not in an env file or YAML. Rotate them regularly. Give integration accounts minimal permissions (least privilege), not the IT manager's service account.

Common mistakes

The technical pitfalls we encounter most often, and which you can avoid by thinking about them in advance.

  • No idempotency: the same order sent twice because of a retry, and your customer ends up with two invoices. Every write action should have an idempotency key.
  • No versioning: your ERP vendor publishes API v2 with breaking changes and your integration grinds to a halt. Pin versions, schedule upgrade windows, monitor deprecation headers.
  • No monitoring: an outage is only discovered when finance calls to say orders are missing. Always build in alerts on success rate, latency and queue depth.
  • No retry strategy: system B is briefly unavailable; without exponential backoff and a dead-letter queue, you lose the messages that arrived at exactly that moment.
  • No rollback plan: you release a new version and orders are processed incorrectly. Without a feature flag or version pinning, rolling back is a nightmare.
  • Tight coupling: ERP and CRM so tightly intertwined that neither can function without the other. A queue or event bus between the two prevents a single failure from bringing everything down.
  • Ignoring master data: customer numbers, product codes and general ledger accounts drift apart between systems. Agree a source of truth per dataset, not per system.
  • No sandbox discipline: testing in production because the test environment is "not up to date". Invest in good test data; it pays off quickly.

How does an integration project start?

We always start with a short discovery phase before we build anything. In a half-hour introductory call we cover the key questions: which systems, which data, which direction, how often, which security requirements, what volume. Based on that, we put together a brief scoping document that sets out the architecture, the assumptions and the approach. Only then do the sprints with concrete deliverables begin: first the minimum working integration, then robustness, monitoring and extensions.

What we want to know during discovery

A few examples of the questions we ask early on: which ERP product and which version are you running? Is there a test environment, and how does it differ from production? Which licences do you have for the API layer (some vendors charge extra for API volume)? Who in your organisation is the functional owner of the data? Which integrations already exist, and are they documented? How often does a transaction occur, and what is the maximum peak? Which compliance requirements apply (GDPR, ISO 27001, NEN 7510, sector-specific)? The answers shape the architecture more than whichever technology you choose.

The role you play

An ERP integration touches finance, IT, operations and often HR. A single internal contact is rarely enough. We work best with a product owner who can make decisions, plus a subject-matter reviewer for each domain. The richer that consultation, the less rework there is. In our experience, organisations that think this through beforehand save a lot of time during delivery.

What you can expect from us

Experience with the major ERP platforms, a team that builds rather than just advises, and a way of working in which you remain the owner of the code and the architecture. No black box, and no lock-in to a specific iPaaS unless it is genuinely needed. We deliver documentation, monitoring dashboards and a transferable codebase, so that you or another party can continue the work later without being held hostage.

From our experience, most projects start small: one critical integration where the pain is greatest. Only once that is in place and stable does the scope expand to a second and third. A big-bang approach in which everything is integrated at once sounds efficient on paper but rarely works out well. We almost always advise against it.

Frequently asked questions

What exactly is an ERP, and when do I need one?

An ERP is the central system for your administrative and operational processes: finance, inventory, purchasing, sales, production and often HR. Once you outgrow separate spreadsheets and small packages, and figures no longer match between departments, an ERP becomes relevant. Which one you choose depends on your sector, international presence and the flexibility you need: SAP and Oracle for larger or more complex organisations, Business Central, AFAS and Exact for SMEs and mid-sized companies, NetSuite for cloud-first scale-ups.

Should I choose a direct API integration or an iPaaS?

There is no universal answer. A direct API works well if you need one deep integration between two systems that you intend to keep using for the long term: you get maximum control and minimal latency. An iPaaS is stronger if you want to connect several SaaS tools quickly, have little in-house ops capacity, or want standard flows without custom code. Many organisations combine the two: critical real-time integrations built directly, peripheral ones via an iPaaS. Our guide API vs. integration platform goes into the trade-off in more depth.

Roughly what does an ERP integration cost?

An honest answer: it is too variable to capture in a single figure on a general page. A simple integration takes a few sprints, while a production architecture with monitoring and an SLA is a project of several sprints. After a short scoping we can give you an honest indication for your specific situation, without hiding anything or inflating it.

What about GDPR and privacy in ERP integrations?

Any integration that carries personal data falls under the GDPR. Key points: data processing agreements with all parties (including the iPaaS vendor), data storage within the EEA unless you explicitly agree otherwise, no PII in error logs, an audit trail of who sent what and when, and least privilege for integration accounts. Healthcare organisations also have NEN 7510 to consider, and financial institutions DORA requirements.

How does an integration project start at Appfront?

With a half-hour introductory meeting in which we map out the current situation, goals and constraints. Then comes a scoping document covering architecture, assumptions and approach. Only then do the sprints begin: first the minimum working integration, then robustness and monitoring, then extensions. You can always start with one specific pain-point integration and scale up later.

What if my ERP vendor doesn't have a good API?

Then we look at alternatives: file drop via SFTP, ODBC connections, database replication, or an adjacent integration product from the same vendor. For older on-premises systems this is common. It works, but discipline around error handling and monitoring becomes more important, precisely because the vendor offers less support.

The three key points.

01

One source, many consumers

The ERP is your source of truth. CRM, webshop, HRIS and BI synchronise with it, not the other way round. Agree per dataset which system is authoritative.

02

Five integration patterns

Direct API, iPaaS, EDI, file drop and message queue. Feel free to combine them: real-time for orders, batch for master data, EDI for trading partners.

03

Operations determine success

Idempotency, retries, versioning, monitoring and an audit trail are not extras. They make the difference between a working integration and a source of incidents.

Talk to us about your ERP integration.

A half-hour introductory meeting. We listen to which systems you want to integrate and give you an immediate indication of architecture, complexity and lead time, honestly, based on what we have built before.

Edit content