Amazon does not pay per order. It pays in settlement cycles, and each deposit nets sales, fees, refunds, ads and reimbursements into one number. If you are building the bridge between Amazon and an ERP, the settlement report is where most integrations quietly break.
Here is a pattern that holds up.
Pull the right source
Use the SP-API Reports API with report type GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2. Amazon generates these on its own schedule, so you list and download them rather than request them. For a view between settlements, the Finances API (listFinancialEvents) returns events as they post.
Batch by settlement, not by order
Every row carries a settlement-id. Treat one settlement as one batch. The first row holds total-amount and deposit-date, which become your control total.
Map on two keys
The GL account depends on amount-type plus amount-description, not either one alone. For example:
ItemPrice + Principal: 4000 Sales Amazon
ItemPrice + Shipping: 4010 Shipping Income
ItemFees + Commission: 6100 Marketplace Fees
ItemFees + FBAPerUnitFulfillmentFee: 6110 FBA Fulfillment
other-transaction + Storage Fee: 6120 FBA Storage
Anything unmapped: 1999 Suspense
The suspense fallback matters. Amazon introduces new descriptions without notice, and unmapped lines should land in suspense, never disappear. Check the values against your own files, since descriptions vary by marketplace.
Handle the awkward rows
Refunds arrive with transaction-type set to Refund and negative amounts. Post them as revenue reversals and match back to the original order-id.
Reimbursements for lost or damaged FBA units come in as credits. Route them to other income so they stay visible instead of netting away.
Multi-currency settlements stay in the marketplace currency until you convert at the deposit date.
Reconcile before you post
Sum every mapped line per settlement. If the total does not equal the control total to the cent, block the journal and raise an exception. Only a batch that balances should reach the ledger.
Keep inventory out of it
Settlement data tells you about money, not stock. FBA units sit in Amazon fulfillment centers, so sync them through the FBA Inventory API into a dedicated warehouse or location in the ERP. Mixing the two is how stock figures drift.
Where AI agents fit
Rule tables cover the known cases. An agent layer earns its keep on the long tail: classifying a fee description it has not seen, matching a reimbursement to the unit it covers, and routing an exception to the right person with context attached. That is the approach appse ai takes for ERP-first marketplace automation.
If you run Sage X3 specifically, this walkthrough covers orders, FBA stock and settlements end to end: appse.ai
Top comments (0)