Acumatica and Anaplan integration

What moves between them

The main flow runs from Acumatica into Anaplan. On a schedule tied to your close calendar, ml-connector reads posted Acumatica journal transactions and GL account figures and loads them as actuals into the matching Anaplan model through its Import action. GL accounts and cost centers are aligned so each figure maps to a valid Anaplan list member and dimension. The return flow runs from Anaplan into Acumatica: once a budget or plan is approved, ml-connector exports those line items from Anaplan and posts them into Acumatica as GL journal transactions against the right accounts and subaccounts.

How ml-connector handles it

ml-connector stores both credential sets encrypted and obtains an Acumatica OAuth2 token, refreshing it when a call returns 401, while pinning the tenant URL and endpoint version per customer so requests do not 404 on a version mismatch. On the Anaplan side it acquires an AnaplanAuthToken by basic or certificate auth, or a device-grant token where SSO is off, and reuses it within the 35-minute lifetime rather than minting one per call. Anaplan import and export actions are run by their action IDs, which the connector discovers at runtime, and because actions lock the model it serializes them so concurrent runs against the same model do not fail. Acumatica field values are wrapped as value objects on every read and write, and the connector maps the chart of accounts and cost centers first so each Anaplan member resolves to a real Acumatica account. Both sides return HTTP 429 under load, so it backs off with jitter, and every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized professional services firm with around 600 employees runs Acumatica Cloud ERP for its general ledger and AP, and uses Anaplan for annual budgeting and rolling forecasts across a dozen cost centers. Before the integration, the FP&A team exported trial balances from Acumatica each month and pasted them into Anaplan to refresh actuals, then re-keyed the approved budget back into the ledger by hand, which left plan-versus-actual reporting days behind and prone to mismatched account codes. With Acumatica and Anaplan connected, posted journals flow into the Anaplan model automatically and approved budget lines post back as journal entries, so variance reporting is current and the manual copy steps are gone.

What you can do

• •Load posted Acumatica journal transactions and GL balances into the matching Anaplan model as actuals.
• •Post approved Anaplan budget and plan line items back into Acumatica as GL journal entries.
• •Map Acumatica accounts and cost centers to Anaplan list members so every figure lands on a valid dimension.
• •Run Anaplan asynchronous import and export tasks by action ID and serialize them around model locks.
• •Bridge Acumatica OAuth2 or session login with Anaplan basic, certificate, or device-grant tokens, with retries and a full audit trail.

Questions

Which direction does data move between Acumatica and Anaplan?

Both directions. Posted GL actuals move from Acumatica into Anaplan to refresh the planning model, and approved budgets or forecasts move from Anaplan back into Acumatica as GL journal transactions. Account and cost-center codes are aligned in both directions so each figure resolves to a valid dimension on the other side.

How does the integration deal with Anaplan having no native finance objects?

Anaplan stores everything as lists, modules, and line items inside a workspace and model, not as invoices or accounts. The connector loads Acumatica data through a named Import action and reads results through a named Export action, both built in advance by your Anaplan model builder. It discovers those action IDs at runtime and maps Acumatica accounts and cost centers to the corresponding Anaplan list members.

Does Anaplan support webhooks, or does ml-connector poll?

Anaplan has no outbound webhooks, so ml-connector polls. Because Anaplan imports and exports are asynchronous, it POSTs to start a task, polls task status until it reports COMPLETE, then downloads the file for an export. It runs on a schedule tied to your close calendar and serializes actions because each one locks the Anaplan model during execution.