QuickBooks Desktop and Amazon Seller Central integration

What moves between them

The main flow runs from Amazon Seller Central into QuickBooks Desktop. ml-connector reads Amazon orders and, after each settlement closes, the settlement report, then posts the results into QuickBooks Desktop: order revenue as sales receipts or invoices, and Amazon fees, refunds, and the net payout as journal entries against the right GL accounts. Item and inventory counts flow the other direction, from QuickBooks Desktop out to Amazon listings and FBA stock, so quantities stay aligned. Reference data such as SKU-to-item and fee-type-to-account mappings is set up first so every line lands on a valid QuickBooks record. Amazon settlement data is treated as a read-only accounting source, so ml-connector never writes financial entries back into Amazon.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Amazon side it exchanges the seller refresh token for an access token, caches it, and refreshes before the one-hour expiry; it passes the marketplace ID on each call and routes to the correct regional base URL. On the QuickBooks side it implements the SOAP service the Web Connector calls, validates the session ticket on every method, and returns QBXML AddRq messages to create transactions. Because neither system pushes the relevant events by plain HTTP webhook, the connector polls: it reads Amazon orders and financial events on a schedule, drives the async Reports workflow (createReport, poll getReport, then getReportDocument) for the authoritative settlement figures, and queries QuickBooks with a ModifiedDateRangeFilter for changed items. Each Amazon SKU maps to a QuickBooks item and each fee type to a GL account, so payouts split cleanly into revenue, fees, and refunds. Amazon returns HTTP 429 under its token-bucket rate limits, so the connector backs off with jitter and retries. QuickBooks has no idempotency key, so the connector checks for an existing record by AmazonOrderId before adding and stores the returned TxnID, and it re-queries EditSequence before any update. A real gotcha is that QuickBooks must be open on the Windows machine for the Web Connector to run, and another is that financial events only appear once Amazon releases a settlement, so deposit reconciliation waits on the settlement report.

A real-world example

A consumer goods seller of about 40 people sells on Amazon as their main channel and runs QuickBooks Desktop Enterprise for accounting at their warehouse office. Before the integration, a bookkeeper downloaded the Amazon settlement report every two weeks and hand-entered the gross sales, FBA and referral fees, refunds, and the net deposit as a lump journal, which made it hard to tie a deposit back to specific orders and slowed month-end close. With QuickBooks Desktop and Amazon Seller Central connected, orders post as sales transactions, each settlement's fees and net payout post to the matching GL accounts automatically, and item counts stay aligned with on-hand stock. The deposit on the bank statement now matches the posted payout, and the manual re-keying is gone.

What you can do

• •Post Amazon orders into QuickBooks Desktop as sales receipts or invoices using the Selling Partner API.
• •Record Amazon fees, refunds, and net payouts from each settlement report as journal entries on the correct GL accounts.
• •Sync QuickBooks Desktop item and inventory counts out to Amazon so listings reflect on-hand stock.
• •Bridge Amazon LWA OAuth2 tokens and the QuickBooks Web Connector session ticket, with each SKU mapped to a QuickBooks item.
• •Poll both systems on a schedule with rate-limit backoff, retries, and a full audit trail on every record.

Questions

Which direction does data move between QuickBooks Desktop and Amazon Seller Central?

The main flow is Amazon Seller Central into QuickBooks Desktop. Orders, fees, refunds, and net payouts move from Amazon into QuickBooks as sales transactions and journal entries, while item and inventory counts flow the other way to keep listings aligned. Amazon settlement data is read-only here, so ml-connector does not write financial entries back into Amazon.

Does QuickBooks Desktop need to be running for the sync to work?

Yes. QuickBooks Desktop has no cloud API, so the QuickBooks Web Connector must be installed on the Windows machine and QuickBooks must be open with the company file loaded for the Web Connector to relay QBXML messages. ml-connector hosts the SOAP service the Web Connector polls and validates a session ticket on every call.

How does the integration handle Amazon settlements and rate limits?

Amazon financial events only appear once a settlement closes, so ml-connector drives the async Reports workflow to pull the authoritative settlement figures and posts the net payout, fees, and refunds to QuickBooks. Because the Selling Partner API enforces per-operation token-bucket limits and returns HTTP 429 when exceeded, the connector backs off with jitter and retries rather than hammering the API.