Workday Financial Management and Amazon Seller Central integration

What moves between them

The main flow runs from Amazon Seller Central into Workday Financial Management. After each Amazon settlement, ml-connector reads the FinancialEventGroup records, which contain ShipmentEvent, RefundEvent, and ServiceFeeEvent line items. Each settlement group is transformed into a Workday supplier invoice record for the Amazon seller account, with individual line items mapped to Workday GL accounts (revenue, refunds, fees, chargebacks). The invoice is posted to the GL with the settlement date and the Amazon settlement ID as the external reference. Workday remains the source of truth for vendor management and GL account structure; ml-connector reads only Amazon's financial data.

How ml-connector handles it

ml-connector stores both credential sets encrypted and bridges Workday's ISU SOAP authentication and Amazon's OAuth2 token flow. On the Amazon side, it polls the Orders API and Finances API on a schedule tied to your settlement cycle (typically twice weekly), refreshing the OAuth2 access token when it approaches expiry, and handling Amazon's regional endpoints and 3600-second token lifetime. On the Workday side, it calls the SOAP Financial_Management service to submit journal entries and create supplier invoices, using ISU credentials sent as WS-Security headers on each request. Because Amazon returns settlements in FinancialEventGroup batches with multiple event types (shipment proceeds, refund fees, service fees, adjustments), ml-connector first consolidates these by settlement date and Amazon settlement ID, then splits them into GL account lines based on the event type (net proceeds to revenue, refunds to a refund account, service fees to an expense account). The ISU account must have security group assignments that allow supplier and journal entry creation in Workday. ML-connector tracks the last settlement ID read to avoid re-processing the same settlement, and it retries failed posts with exponential backoff.

A real-world example

A mid-sized seller operating on Amazon across North America uses Workday Financial Management for accounts payable and general ledger. Before the integration, the finance team downloaded the Amazon settlement report twice weekly, manually extracted the revenue, refunds, and fees, and hand-entered them into Workday as journal entries or supplier invoices. This took 4 to 6 hours per week and introduced keying errors. With Workday Financial Management and Amazon Seller Central connected, each settlement automatically creates a vendor invoice in Workday split by event type (proceeds, refunds, fees), posts to the correct GL accounts, and carries the Amazon settlement ID for traceability. The weekly reconciliation step is eliminated, and the GL is always aligned with Amazon's actual payouts.

What you can do

• •Read Amazon financial events, shipment proceeds, refunds, and service fees on a schedule and post them into Workday accounts payable as vendor invoices.
• •Map Amazon settlement amounts by event type to Workday GL accounts so proceeds, refunds, and fees post to the correct expense categories.
• •Authenticate Amazon Seller Central with OAuth2 and Workday Financial Management with ISU SOAP credentials, handling token refresh and credential expiry.
• •Consolidate Amazon FinancialEventGroup batches by settlement ID and date, then split them into Workday invoice line items by event type.
• •Prevent duplicate settlements by tracking the last Amazon settlement ID read and retrying failed GL posts with exponential backoff.

Questions

Which direction does data move between Workday Financial Management and Amazon Seller Central?

The main flow is Amazon into Workday. Settlement data, financial events, and order amounts move from Amazon Seller Central into Workday Financial Management, where they are posted as supplier invoices and journal entries to the GL. Workday does not write back to Amazon. Workday remains the source of truth for vendor accounts and GL structure.

How does ml-connector handle Amazon's OAuth2 tokens and Workday's ISU authentication?

ml-connector stores both credential sets encrypted and refreshes Amazon's OAuth2 access token on a schedule before it expires (tokens last 1 hour). On the Workday side, it sends ISU credentials as WS-Security UsernameToken headers with every SOAP request. The ISU account must be set up in Workday with security group assignments that allow supplier and journal entry operations.

How are Amazon financial events consolidated into Workday invoices?

Amazon returns financial data in FinancialEventGroup batches with multiple event types (shipments, refunds, fees, adjustments). ml-connector groups these by settlement date and settlement ID, then creates a single Workday supplier invoice with line items split by event type (net proceeds to revenue, refunds to a refund account, service fees to expense accounts), so the invoice is fully allocated across GL accounts and can be reconciled by settlement.