Microsoft Dynamics GP and Amazon Seller Central integration

What moves between them

The main flow runs from Amazon Seller Central into Microsoft Dynamics GP. ml-connector reads settled orders and the financial events tied to them, then posts the sales as receivables invoices in GP and the marketplace fees, refunds, and reimbursements as GL transactions against the right accounts. The authoritative source for payouts is the settlement report, so disbursement-level reconciliation is driven from there rather than from unsettled events. In the other direction, GP inventory item quantities flow out to Amazon listings so the stock advertised on the marketplace reflects what GP holds. Cadence follows your Amazon settlement and fulfillment rhythm: orders and inventory poll more often, settlements process as each statement closes.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Amazon side it exchanges the LWA refresh token for short-lived access tokens and refreshes them before the one-hour expiry. On the GP side it presents the Windows domain account over the customer-exposed SBA or SOAP endpoint and wraps SBA write bodies in the required Payload key. Because GP has no inbound endpoint and Amazon delivers events only through EventBridge or SQS, the integration polls Amazon on a schedule rather than relying on a push. Each Amazon Seller SKU is mapped to a GP item number, and Amazon fee and refund types are mapped to GP GL accounts so every posting lands on a valid account in an open fiscal period. Amazon rate limits return HTTP 429 under a token-bucket scheme, so ml-connector backs off with jitter and follows the NextToken cursor through every page. GP writes generally apply only to unposted transactions, so once a GP document is posted it is treated as read-only. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A consumer-goods seller with around 40 employees sells through both a wholesale channel and Amazon, and runs Microsoft Dynamics GP on a server in their office. Before the integration, a clerk downloaded the Amazon settlement report every two weeks and hand-keyed the sales, FBA fees, refunds, and reimbursements into GP, while warehouse staff updated Amazon stock counts separately. Month-end close stalled while finance reconciled the Amazon payout against what had been entered, and oversells happened when GP and Amazon inventory drifted apart. With the two systems connected, settled orders and fees post into GP automatically as receivables and GL entries, the payout reconciles against the settlement report, and GP inventory counts push out to Amazon listings so advertised stock stays accurate.

What you can do

• •Post settled Amazon orders into Microsoft Dynamics GP as receivables invoices without re-keying.
• •Record Amazon marketplace fees, refunds, and reimbursements as GP GL transactions against the correct accounts.
• •Reconcile each Amazon payout using the settlement report as the authoritative disbursement source.
• •Push GP inventory item quantities out to Amazon Seller Central listings so advertised stock stays current.
• •Bridge the Amazon LWA refresh token and GP Windows authentication, polling on a schedule with retries and a full audit trail.

Questions

Which direction does data move between Microsoft Dynamics GP and Amazon Seller Central?

The main flow is from Amazon into GP: settled orders post as receivables invoices and marketplace fees, refunds, and reimbursements post as GL transactions. In the other direction, GP inventory item quantities flow out to Amazon listings so advertised stock matches what GP holds. Posted GP documents are read-only through the API, so ml-connector only writes new or unposted records on the GP side.

How does the integration connect if Dynamics GP is on premises and has no webhooks?

Microsoft Dynamics GP has no cloud endpoint and no event stream, so the customer exposes their SBA REST or SOAP Web Services endpoint over HTTPS, or runs a local agent inside their network. The connector authenticates with a Windows domain account mapped to a GP user. Because neither side offers plain HTTP webhooks, ml-connector polls Amazon on a schedule and writes to GP over that exposed endpoint.

How are Amazon settlements and fees handled so the general ledger reconciles?

Amazon financial events appear at the event level immediately, but the settlement report is the authoritative record of what Amazon actually pays out. ml-connector drives payout reconciliation from the Reports API settlement data, posting captured sales, FBA fees, refunds, and reimbursements to mapped GP GL accounts. This keeps the GP ledger aligned with each Amazon disbursement rather than with unsettled activity.