SAP S/4HANA and Amazon Seller Central integration

What moves between them

The flow runs from Amazon Seller Central into SAP S/4HANA. ml-connector reads Amazon orders and, after each settlement, the settlement report lines that hold gross sales, marketplace fees, refunds, and chargebacks, then posts the resulting journal entries into the SAP general ledger against the matching company code, GL accounts, and cost centers. Marketplace buyers can be created or updated as customer business partners in SAP using role FLCU00. Amazon is treated as a read-only accounting source, so ml-connector never writes financial entries back into Seller Central. Cadence is tied to your settlement and posting calendar, with orders polled more frequently than the periodic settlement reports.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Amazon side it exchanges the seller refresh token for a one-hour access token through Login with Amazon, caches and refreshes it before expiry, and includes the marketplace ID and region on each call. On the SAP side it requests a client-credentials token from the tenant OAuth2 endpoint, then for every general ledger post it first issues a GET with X-CSRF-Token: Fetch, captures the returned token and session cookies, and replays them on the posting request. Amazon settlement is asynchronous, so the Reports API workflow is followed: create the settlement report, poll until it is DONE, download the document from the presigned S3 URL, and map each line to a SAP GL account and cost center, which are aligned first so every journal line lands on a valid dimension. Because Amazon delivers events only through EventBridge or SQS and SAP cloud cannot be pushed to, both systems are polled on a schedule. Amazon returns HTTP 429 from its token-bucket limiter and SAP returns 429 with a Retry-After header, so ml-connector backs off with jitter and retries. Each Amazon order and settlement line is posted under a stable job id so a re-run does not double-post, and SAP's own duplicate-invoice and document checks add a second guard. Every record carries a full audit trail and can be replayed if a SAP post fails.

A real-world example

A mid-sized consumer goods brand with around 150 employees sells through its own Amazon Seller Central account across the US and Canada and keeps its books in SAP S/4HANA Cloud. Before the integration, the accounting team downloaded the Amazon settlement report every two weeks and manually entered the gross sales, FBA and referral fees, and refunds into SAP, then spent the first days of month-end close trying to tie the Amazon bank deposit back to the orders and fees it covered. With SAP S/4HANA and Amazon Seller Central connected, each settlement report posts into the SAP general ledger automatically, split across the right revenue, fee, and refund accounts and cost centers, so the deposit already reconciles. The manual re-keying step is gone and close starts from numbers that already agree.

What you can do

• •Post Amazon settlement report lines into the SAP S/4HANA general ledger after each disbursement, split across revenue, fee, and refund accounts.
• •Turn Amazon orders into SAP journal entries mapped to the correct company code and cost centers.
• •Create and update Amazon marketplace buyers as customer business partners in SAP using role FLCU00.
• •Bridge Amazon's Login with Amazon refresh token and SAP's tenant OAuth2, and fetch the X-CSRF-Token every SAP post requires.
• •Poll Amazon orders, finances, and settlement reports on a schedule with backoff, job-id dedup, and a full audit trail on every record.

Questions

Which direction does data move between SAP S/4HANA and Amazon Seller Central?

The flow is Amazon Seller Central into SAP S/4HANA. Orders and settlement report lines move from Amazon into SAP as general ledger journal entries, and marketplace buyers can be created as customer business partners. Amazon is treated as a read-only accounting source, so ml-connector does not write financial entries or instructions back into Seller Central.

Why does the integration poll Amazon instead of receiving webhooks?

Amazon Seller Central has no plain HTTP webhook. The Selling Partner API delivers push events only through AWS EventBridge or an SQS queue, which require AWS infrastructure on the seller's side. ml-connector instead polls the Orders, Finances, and Reports APIs on a schedule, which is the standard path for REST connectors and covers settlement reconciliation reliably.

How does ml-connector handle SAP's X-CSRF-Token requirement for posting journals?

Every write to SAP S/4HANA OData services requires an X-CSRF-Token, and omitting it returns HTTP 403. Before each general ledger post, ml-connector sends a GET with the X-CSRF-Token: Fetch header, captures the returned token and session cookies, and includes them on the posting request. If a write returns 403 because the session expired, it re-fetches the token and retries.