Does ml-connector handle Exact Online's regional base URLs and Division IDs?

Yes. ml-connector accepts the Exact Online region and Division ID per customer, since each division may operate independently within a single Exact Online instance. The Division ID is fetched once from the /api/v1/current/Me endpoint and then cached for all subsequent API calls. The OAuth token is refreshed every 9 minutes to stay ahead of the 10-minute expiry.

How does ml-connector manage Anaplan's rate limit and lack of webhooks?

ml-connector respects Anaplan's 600-request-per-minute tenant-wide limit by queuing requests and backing off with exponential jitter when HTTP 429 is returned. Since Anaplan has no outbound webhooks, ml-connector polls Anaplan task status (Import and Export actions) on a schedule you define, typically aligned with your financial close or planning cycle.

What if Exact Online and Anaplan have mismatched GL accounts or cost centers?

ml-connector validates every invoice line item against the GL accounts and cost centers that exist in both Exact Online and Anaplan. If a line item references an account or cost center that does not exist in Anaplan, it is held in an audit queue with a detailed error message so you can resolve the mismatch and replay the record.

Exact OnlineAnaplan

Exact Online and Anaplan integration

Exact Online runs accounting and operations for SMEs across Europe and North America. Anaplan runs financial planning and budgeting. Connecting the two brings actuals from Exact Online into Anaplan's planning models, so forecasts stay current against real invoices, orders, and GL postings. Finance teams see variances between plan and actuals in real time, without manual data pulls from Exact Online.

How Exact Online works

Exact Online exposes accounts, sales invoices, purchase invoices, sales orders, purchase orders, GL accounts, cost centers, journal entries, items, contacts, and goods deliveries through a REST API using OData v3 query syntax (filter, select, orderby, top, skip). Regional base URLs vary by country: Netherlands, Belgium, UK, Germany, France, Spain, or USA. All requests require a Division ID, fetched once from the /api/v1/current/Me endpoint. Authentication uses OAuth 2.0 Authorization Code Grant with 10-minute access tokens and 30-day rotating refresh tokens. Webhooks push change notifications (entity key and action only) for significant resources including Accounts, SalesInvoices, PurchaseInvoices, SalesOrders, PurchaseOrders, GLAccounts, and Projects, with HMAC-SHA256 signature verification. The endpoint does not support the $expand parameter, so related data must be fetched in separate requests.

How Anaplan works

Anaplan exposes workspaces, models, modules, lists, and line items through a REST API that accepts JSON and CSV payloads. All requests target a single tenant-wide base URL at api.anaplan.com. Authentication uses Basic Authentication (username and password with 35-minute tokens), Certificate-Based Authentication (client certificate pair with 35-minute tokens), or OAuth2 (Authorization Code Grant). The platform supports polling only; there are no outbound webhooks. All data operations (Import and Export) must be started as asynchronous Actions defined within the model, and ml-connector polls for task completion before downloading results. The tenant-wide rate limit is 600 requests per minute, shared across all integrations, and bulk operations lock the model during processing, blocking concurrent reads.

What moves between them

Sales invoices, purchase invoices, GL transactions, and sales orders flow from Exact Online into Anaplan planning models on a schedule tied to the financial close cycle, typically daily or weekly. Exact Online webhooks alert ml-connector to new and changed records, which are then fetched via the REST API and transformed into Anaplan list items and line items within the planning models. Anaplan is read-only from Exact Online; there is no write-back flow. Cost centers and GL accounts are synchronized in both directions to ensure that Anaplan's planning dimensions match Exact Online's actual accounting structure.

How ml-connector handles it

ml-connector stores Exact Online OAuth credentials encrypted and refreshes the access token every 9 minutes to stay ahead of the 10-minute expiry. Each Exact Online customer specifies their Division ID, which ml-connector caches and uses for all subsequent REST API calls. When an Exact Online webhook fires (signed with HMAC-SHA256), ml-connector verifies the signature using the webhook secret from the Exact Online App Center, then fetches the full entity from the REST API. For Anaplan, ml-connector starts Import or Export Actions defined in the planning model, polls the task status until completion, and handles the 600-request-per-minute rate limit by queuing requests and backing off with exponential jitter when HTTP 429 is returned. Cost center and GL account synchronization uses Anaplan lists as the source of truth and validates that every invoice line item references a GL account and cost center that exist in both systems. The webhook CallbackURL domain must match the redirect_uri domain registered in the Exact Online App Center, and refresh tokens must be used at least once every 30 days or the user must re-authorize.

A real-world example

A mid-sized European SME operates on Exact Online for invoicing, procurement, and GL accounting, and uses Anaplan to forecast cash flow and budget by cost center for the coming year. Before the integration, the finance team exported GL transactions and invoices from Exact Online weekly and manually created or updated list items in Anaplan, a process that took 4 to 6 hours and was error-prone. With Exact Online and Anaplan connected, new invoices and GL postings flow automatically into the planning model every night, and the finance team refreshes forecasts each week against live actuals with no manual data entry. Month-end reconciliation against the GL is now automated, and cash flow forecasts incorporate real purchase commitments and payment terms from Exact Online.

What you can do

Sync sales invoices, purchase invoices, and GL transactions from Exact Online into Anaplan planning models on a webhook-triggered or scheduled basis.
Map Exact Online GL accounts and cost centers to Anaplan lists so that financial data lands in the correct planning dimensions.
Handle Exact Online's multi-regional OAuth endpoints, Division ID routing, and token rotation at 10-minute intervals.
Respect Anaplan's 600-request-per-minute rate limit with exponential backoff and queue management.
Verify Exact Online webhook signatures (HMAC-SHA256) against the webhook secret and fetch full entity payloads via REST API.

Questions

Does ml-connector handle Exact Online's regional base URLs and Division IDs?: Yes. ml-connector accepts the Exact Online region and Division ID per customer, since each division may operate independently within a single Exact Online instance. The Division ID is fetched once from the /api/v1/current/Me endpoint and then cached for all subsequent API calls. The OAuth token is refreshed every 9 minutes to stay ahead of the 10-minute expiry.
How does ml-connector manage Anaplan's rate limit and lack of webhooks?: ml-connector respects Anaplan's 600-request-per-minute tenant-wide limit by queuing requests and backing off with exponential jitter when HTTP 429 is returned. Since Anaplan has no outbound webhooks, ml-connector polls Anaplan task status (Import and Export actions) on a schedule you define, typically aligned with your financial close or planning cycle.
What if Exact Online and Anaplan have mismatched GL accounts or cost centers?: ml-connector validates every invoice line item against the GL accounts and cost centers that exist in both Exact Online and Anaplan. If a line item references an account or cost center that does not exist in Anaplan, it is held in an audit queue with a detailed error message so you can resolve the mismatch and replay the record.

Connect Exact Online and Anaplan

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started