Connecting to any packageNo partner contract
No IT project to start. An export or a forwarded email is enough. After that we connect through the API with your own key, or with a connector that only reads.
- No partner contract needed
- Read-only by default
- Nothing written back without approval
How we connect
We need no partnership with an ERP vendor. We start with what every package can do: forwarding by email and a scheduled export. For cloud packages such as Exact Online, AFAS Profit and Business Central it can then run through the official API, with access you create and revoke yourselves. For packages on your own server, such as Ridder iQ, Isah and King, a small connector reads read-only and makes an outbound connection itself, with no open ports. Writing back only happens after approval, through the package’s API or import function.
Works with what is there. Including your package
- 1From day one, with any system
Forward by email
Every company gets its own email addresses for purchasing, orders and returnables. Forwarding an invoice, an order or a photo of a return slip is enough; the verdict comes back by email.
Works with any package, and without one
- 2The default to start with
Scheduled export
Almost every package can schedule a report or export, as CSV or Excel to a folder, SFTP or mailbox. We read it at fixed times. No installation, no access to your system.
Exact, AFAS, Business Central, SAP Business One, Odoo, Ridder iQ, Isah, King and virtually any other package
- 3For cloud packages with an open API
API with your own key
You create the access yourselves, with only the rights needed, and can revoke it at any time. AFAS with an app connector and token, Exact Online through Exact’s own login, Business Central through an app registration in your own Microsoft tenant.
AFAS Profit, Exact Online, Business Central, Odoo, SAP Business One (Service Layer)
- 4For packages on your own server
Our connector on your server
A small service on your own server that reads read-only from the API or database, and makes an encrypted outbound connection itself. No ports open in your firewall.
Ridder iQ, Isah, King, Navision, SAP Business One on-premise, your own SQL databases
- 5When an action has to land in the package
Writing back, after approval
What we prepare (an approved order, a deposit line, a blocked invoice) goes back through the package’s API or import function. Only after a person has approved it.
Through your package’s API or standard import
What we do not do
No robots clicking through screens: that breaks with every update. No admin rights. No integration promised that we have not tested with you first.
Per package
What is possible per package depends on version, licence and setup. This is where we start; we only promise an integration once we have tested it with you.
| Package | Where it runs | Start | Daily | Writing back |
|---|---|---|---|---|
| Exact Online | Cloud | Export of invoices and orders (Excel or CSV) | REST API, access through Exact’s own login (OAuth) | Through the API, after approval |
| AFAS Profit | Cloud | Export or scheduled report | GetConnectors with an app connector and token you create yourselves | Through UpdateConnectors, after approval |
| Business Central | Cloud or own server | Export to Excel | Cloud: API with an app registration in your own Microsoft tenant. Own server: connector | Through the API, after approval |
| SAP Business One | Own server or hosting | Export or scheduled query | Service Layer (REST), directly or through the connector | Through the Service Layer, after approval |
| Odoo | Cloud or own server | Export to Excel or CSV | External API with an API key, if your plan allows it; otherwise scheduled export | Through the API, after approval |
| Ridder iQ | Own server or hosting | Export from Ridder iQ | Connector on your server, read-only through the API or database | Through import, after approval |
| Isah | Own server | Export or report | Connector on your server, read-only from the database | Through import, after approval |
| King ERP | Own server | Export or report | Connector on your server, read-only from the database | Through import, after approval |
| Older packages (Navision, own SQL) | Own server | Export or report | Connector on your server, read-only | Through import, after approval |
| Time registration (AFAS, Nedap and others) | Cloud or own server | Export of clocked hours | Scheduled export or API where available | Not needed |
| Outlook, Microsoft 365, Gmail | Cloud | Forward to the address we give you | A forwarding rule on the mailbox for invoices or orders | Draft emails from your own domain |
What we need from your IT
A forwarding rule, or someone who forwards. Nothing more.
Export
A scheduled export to a folder, SFTP or mailbox. The package does the work; we only read.
API
A token or app registration with read rights only, created by you. Write rights only when something has to go back.
Connector
A Windows or Linux server allowed outbound HTTPS, and a read account on the database. No open ports.
How it stays secure
- You create the access and can revoke it at any time
- Only the rights the check needs; reading is the default
- Nothing is written back without a human’s approval
- Every action logged, with who approved it
- Storage in the EU and a data processing agreement
Frequently asked questions
About connecting, your ERP and what we need from your IT.
Do you need a partnership with Exact or AFAS?
No. With AFAS you create an app connector and token in Profit yourselves. With Exact Online you grant access through Exact’s own login and can revoke it at any time. With Business Central you make an app registration in your own Microsoft tenant. And to start, no integration is needed at all: an export is enough.
Our package has no API. Can it still work?
Yes. Almost every package can schedule an export or report to a folder or mailbox. For packages on your own server we install a small connector that reads read-only. And invoices and orders can always come in by email.
Do we need to open firewall ports?
No. The connector makes an encrypted outbound connection itself, like your browser. Nothing needs to come in from outside.
Do you write into our ERP?
Only after a human approves, and only when it adds something: an approved order, a deposit line, a blocked invoice. That goes through your package’s API or standard import.
More questions?
Call or email. You get an answer from the people who build the checks, not from a sales team.
Start with an export
For the Leak Check, an export of 12 months of supplier invoices is enough. No integration, no IT project.