QuickBooks Desktop and Anaplan integration

What moves between them

The main flow runs from Anaplan into QuickBooks Desktop. ml-connector runs an Anaplan export action to pull approved budget and forecast values, then posts them into QuickBooks as journal entries through JournalEntryAddRq, mapped to the correct chart of accounts and classes. Actuals move the other direction: account balances and posted transactions are read from QuickBooks by polling and imported into the Anaplan planning model so plan and actual sit side by side. Reference data such as accounts and cost centers is aligned so each posting and each imported figure lands on a valid dimension on both sides. The cadence follows your planning cycle, typically after each budget approval and at month-end close.

How ml-connector handles it

ml-connector stores both credential sets encrypted. For Anaplan it holds the Basic auth or OAuth2 token and refreshes it before the 35-minute expiry. For QuickBooks it runs the Web Connector SOAP service: it returns the session ticket from authenticate, hands QBXML request blobs to the agent through sendRequestXML, and processes the responses, all while QuickBooks is open on the Windows machine. It maps Anaplan list members to QuickBooks accounts and classes up front, because Anaplan has no native chart of accounts and a JournalEntryAddRq must reference accounts that already exist in the company file. QuickBooks has no idempotency key, so before posting a journal entry the connector queries by reference number to avoid duplicates and stores the returned TxnID; any Mod re-queries for the current EditSequence first. Because neither side pushes events, it polls the Anaplan export task to COMPLETE with backoff, and detects QuickBooks changes with a ModifiedDateRangeFilter on each Web Connector cycle, paging large reads with the QBXML iterator. It serializes work against a single Anaplan model since a model locks during a task, backs off on the Anaplan 600-per-minute rate limit, and keeps each QBXML request under the roughly 60-second QuickBooks timeout. Every record carries a full audit trail and can be replayed if a step fails.

A real-world example

A mid-sized professional services firm with around 250 staff keeps its books in QuickBooks Desktop Enterprise on a Windows server and builds its annual budget and rolling forecast in Anaplan. Before the integration, the FP&A team approved the budget in Anaplan, exported it to a spreadsheet, and a bookkeeper keyed the opening budget and monthly accruals into QuickBooks by hand, then exported a trial balance each month and re-typed the actuals back into Anaplan to compare against plan. With QuickBooks Desktop and Anaplan connected, each approved plan version posts into QuickBooks as journal entries allocated to the right accounts and classes, and the ledger actuals import back into the model automatically. The double re-keying disappears and budget versus actual stays current without manual work.

What you can do

• •Post approved budget and forecast figures from Anaplan into QuickBooks Desktop as journal entries against the correct accounts and classes.
• •Read QuickBooks account balances and posted transactions and import them into the Anaplan model as actuals for variance analysis.
• •Map Anaplan list members to QuickBooks accounts and cost centers, since Anaplan has no native chart of accounts.
• •Bridge the Anaplan token auth and the QuickBooks Web Connector SOAP handshake, driving each sync cycle while QuickBooks is open.
• •Query before posting to avoid duplicate journal entries and back off on Anaplan rate limits, with a full audit trail on every record.

Questions

Which direction does data move between QuickBooks Desktop and Anaplan?

Both directions. Approved budget and forecast values are exported from Anaplan and posted into QuickBooks Desktop as journal entries, while account balances and posted transactions are read from QuickBooks and imported back into the Anaplan model as actuals. This keeps the ledger aligned with the approved plan and keeps plan-versus-actual current in the planning model.

Does Anaplan hold invoices or GL accounts that can post to QuickBooks Desktop?

No. Anaplan is a planning platform and has no native invoice, vendor, or GL account objects. Its data lives in a workspace and model as lists, modules, and line items, so ml-connector exports the planned values and maps them to QuickBooks accounts and classes that already exist in the company file before it posts a journal entry.

How does the integration reach QuickBooks Desktop when it has no cloud API or webhooks?

QuickBooks Desktop has no hosted API, so ml-connector works through the QuickBooks Web Connector, a Windows agent the customer installs that polls a SOAP service and exchanges QBXML while QuickBooks is open. Because neither QuickBooks nor Anaplan pushes events, the connector polls the Anaplan export task to completion and detects QuickBooks changes with a modified-date filter on each Web Connector sync cycle.