Exact Online
Connect AI agents and workflows to Exact Online: accounts, items, sales orders, sales and purchase invoices, journal entries and reports, with webhooks.
Book a demoExact Online for AI agents and workflows.
engini lets your AI agents and workflows work in Exact Online, the cloud ERP widely used in the Netherlands, Belgium and the UK: read accounts, items and stock, enter sales orders, sales invoices and purchase invoices, post general journal entries, read balances and reports, and start a workflow when Exact Online reports a change. Subsidiaries on Exact stay in step with headquarters on another ERP. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Exact Online. Every tool is one you allow or leave out.
The Exact Online tools in engini, grouped by what they change. In an ERP a write is a financial event, so write tools go only to the agents that need them.
Read
Read customers, suppliers and items.
Read orders and billing.
Read supplier invoices.
Read balances and financial reports by period.
Write
Enter orders and bill customers.
Enter a supplier invoice.
Post a journal.
Keep master data current.
Any endpoint
Call any Exact Online API endpoint, with the sign-in added for you.
Triggers
Exact Online sends a webhook when a subscribed record changes.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Exact Online. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Exact Online connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Exact Online tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Exact Online and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Exact Online tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Exact Online through engini
{
"mcpServers": {
"engini-exact-online": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Exact Online connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Exact Online tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Exact Online. Agents and workflows, across systems.
Benelux entities that reconcile
A subsidiary on Exact Online sends sales and journals to headquarters on NetSuite or SAP, and both sides balance.
Store orders into Exact
Paid Shopify orders become Exact Online sales orders and invoices.
Supplier invoices from the inbox
A supplier invoice from email is read by an agent and entered in Exact Online.
Answers in plain words
An agent in Teams answers receivables, payables and revenue questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Exact Online and another system engini connects is available.
You decide what each agent may do in Exact Online. engini enforces it on every call.
Only the tools you allow
A toolset lists the Exact Online tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Exact Online account and engini acts as that person, with their Exact Online permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Exact Online in three steps. Then decide what each agent may do.
Sign in to Exact Online
Add an Exact Online connection, sign in with Exact Online and choose the division. Use a user whose rights cover only what the workflows need.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Exact Online from Claude, ChatGPT, Cursor or your own code.
Exact Online and engini. Straight answers.
Can an AI agent write to Exact Online, or only read?
Both. engini has tools to enter sales orders, sales and purchase invoices and journal entries, and to create and update accounts and items. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Exact Online?
It acts as the Exact Online user who signed in, with that user's rights in the division. Every run is recorded under the person who started it.
Can a change in Exact Online start work?
Yes. Exact Online sends webhooks when subscribed records change. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Exact Online API endpoint through the same connection, and give it only to the agents that need it.