ERP integrations: which connectors OrderPilot supports and how to choose

OrderPilot is built to land real purchase orders inside your ERP — not just pull data out of an email. That means a large part of our value lives in the quality of the ERP connectors. This article is an overview of which ERPs we natively support, what each connector does, and what you need to go live.

The connector list

OrderPilot ships with certified connectors for:

ERP	Deployment	Protocol	Status
AFAS Profit	Cloud + on-prem	GetConnector + UpdateConnector REST	Production
Exact Online	Cloud only	REST API v1 + OAuth 2.0	Production
Microsoft Dynamics 365 Business Central	Cloud (SaaS + BYOL) + on-prem (BC14+)	Standard API v2.0 + Entra ID OAuth	Production
SAP S/4HANA	Cloud + on-prem	OData (API_PURCHASEORDER_PROCESS_SRV) or BAPI via RFC	Production
Odoo	Enterprise + Community + Odoo.sh + Online	XML-RPC	Production
NetSuite	Cloud (SuiteApp)	REST API + SuiteTalk	Production

Every connector delivers the same end result: a validated purchase order inside your ERP, linked to the original incoming email/PDF for audit. What differs under the hood are the auth flow, master-data sync cadence, and ERP-specific fields (cost centers, VAT codes, dimensions, fiscal positions).

Detail pages per ERP

• AFAS Profit connector — GetConnector + UpdateConnector, NL mid-market focus
• Exact Online connector — OAuth 2.0 REST, GL + VAT automation
• Business Central connector — Entra ID, Item No. resolution, Dimensions
• SAP S/4HANA connector — OData or BAPI, ECC-compatibility options
• Odoo connector — XML-RPC, multi-company support
• NetSuite connector — documentation in preparation

How to choose which connector to use

Often this is simple (you have the ERP you have), but not always:

Scenario 1: single ERP, straightforward choice

Most customers. Your ERP is what it is — the only decision is how deeply to integrate.

For AFAS, Exact, BC, Odoo we recommend direct API integration (not file-based). The direct API gives you real-time validation, idempotency, and automatic master-data sync.

Scenario 2: multi-ERP landscape

At larger companies it’s not unusual to run:

• SAP for finance / consolidation
• A local ERP (AFAS, Exact) for operational purchasing
• Odoo / Business Central for separate entities or acquired companies

OrderPilot supports multi-ERP in one workspace. You can set a rule per supplier, cost center, or company entity that determines where a PO goes. For example: “All Sony invoices → Exact, all RB2 invoices → AFAS.”

Scenario 3: legacy ERP we don’t natively support

Your ERP isn’t in the list. Options:

1. Custom connector — For customers with volume >5000 POs/year we build a dedicated connector if the ERP has a reasonable API. Scope: 4-8 weeks.
2. Generic REST / webhook — If your ERP has its own inbound API, we can send POs as generic REST POSTs. You build the mapping on your ERP side.
3. File export — If all else fails: OrderPilot exports validated POs as XML/CSV/JSON to SFTP or email, and your team (or an integration tool like Boomi) does the final push.

What you need per ERP

For a smooth implementation these are often the bottleneck. Sort them out up front:

AFAS Profit

• App Connector access (IT team configures in AFAS).
• The GetConnector and UpdateConnector configs we supply.
• Cleaned master data (no duplicate vendors / items).

Exact Online

• OAuth 2.0 consent by an admin user on the administration.
• Multi-entity: access to every administration you want to write POs into.
• GL and VAT mapping agreed (we help during onboarding).

Business Central

• Entra ID App Registration with Financials.ReadWrite.All scope.
• Environment + Company decision (Production / Sandbox).
• Dimensions strategy (if you use them): which dimension set is required on POs.

SAP S/4HANA

• OData service activated in the SAP Gateway, OR BAPI access via RFC.
• Technical user with permissions on API_PURCHASEORDER_PROCESS_SRV.
• Field mapping confirmed with your SAP team (material group, account assignment, etc.).

Odoo

• Technical user in Odoo with permissions on Purchase, Inventory, Accounting.
• XML-RPC accessible (valid SSL cert, no 2FA on this user).
• Product cross-references (product.supplierinfo) where relevant.

NetSuite

• Token-based authentication (TBA) set up for our integration.
• SuiteApp installed in your NetSuite account.
• Location + Subsidiary mapping confirmed.

Timeline

For a standard SaaS ERP (Exact Online, BC cloud, Odoo Online) the connection is typically live within one business day. For SAP on-prem or Odoo with many custom modules, count on 2-5 business days including testing.

Full implementation (connection + first 50-100 POs in production) typically takes 1-2 weeks.

FAQ

Do we get a sandbox environment from you? Yes. We provide an isolated workspace where you can process 20-50 real-world documents without anything ending up in your production ERP.

What if our ERP gets replaced (e.g. migration from Exact to Business Central)? We migrate the OrderPilot workspace. Master data is re-synced, rules re-linked, historical POs stay searchable.

Can I write to multiple ERPs from the same workspace? Yes, see scenario 2 above. Rules determine which PO goes to which ERP.

Does this also work if we don’t have an ERP yet (still Excel-based)? Yes, as a staging step. OrderPilot writes to CSV / Excel / webhook. When you later implement an ERP, we connect the connector and stop the CSV export. Your historical data stays searchable.