Workday Financial Management and Walmart Marketplace integration

What moves between them

The main data flow runs from Walmart Marketplace into Workday Financial Management. Orders placed on Walmart flow into Workday as sales transactions, mapped to the correct GL accounts and cost centers based on product category and channel. Returns and refunds are tracked separately and posted to Workday as debit or credit adjustments. Settlement and reconciliation reports from Walmart are polled periodically and matched against Workday payment records to ensure accounting accuracy. Workday supplier and GL account reference data is read to validate the mappings before posting any transaction.

How ml-connector handles it

ml-connector stores both credential sets encrypted and refreshes the Walmart OAuth2 access token before it expires at the 15-minute boundary, preventing requests from failing mid-sync. On the Workday side it uses the tenant-specific domain for SOAP operations and the workday.com domain for REST reads, validating GL accounts and cost centers before posting any journal entry. Because Workday has no webhooks, ml-connector polls Workday for supplier and GL reference data on a daily schedule and Walmart for orders and returns on a 15 to 30 minute schedule, aligning with typical daily settlement batches. It also listens for Walmart webhooks where configured and can replay failed postings if a Workday journal entry submission times out. Returns are mapped based on the return order ID and matched to the original order to calculate the correct refund amount and GL impact. All postings carry a full audit trail tied to the original Walmart order or return ID.

A real-world example

A mid-sized retail seller runs Workday Financial Management for accounting and GL reporting, and sells across multiple channels including Walmart Marketplace. Before the integration, the finance team exported daily order and settlement reports from Walmart manually and re-entered revenue totals into Workday at month-end close, then spent days reconciling the marketplace transactions against the GL postings. Returns and refunds were tracked separately on a spreadsheet and often posted late or in the wrong GL period, causing close delays and audit questions. With Workday and Walmart Marketplace connected, each day's orders and returns flow into Workday automatically, posted to the correct GL accounts and cost centers, and settlement reports are matched against Workday payment records daily. Month-end close starts with marketplace revenue already reconciled, and the manual re-keying and matching work is eliminated.

What you can do

• •Post Walmart orders as sales transactions into Workday's general ledger, mapped to the correct GL accounts and cost centers based on product and channel.
• •Sync Walmart returns and refunds as separate postings so revenue is adjusted accurately when items are returned.
• •Validate Workday GL accounts and cost centers before posting any marketplace transaction, preventing invalid entries.
• •Refresh Walmart OAuth2 tokens automatically before expiry so polling and webhooks never fail due to authentication timeouts.
• •Maintain a full audit trail tied to Walmart order and return IDs, with replay capability if a Workday posting fails.

Questions

Which direction does data move between Workday and Walmart Marketplace?

The main flow is Walmart into Workday. Order and return transactions flow from Walmart Marketplace into Workday Financial Management as sales transactions and adjustments, mapped to the matching GL accounts and cost centers. Workday supplier and GL reference data flows back to Walmart to validate mappings before any posting. Workday journal entries are read-only from Walmart's perspective, so ml-connector does not write back to the marketplace.

How does the integration handle Walmart's 15-minute token expiry and polling without webhooks?

ml-connector pre-emptively refreshes the Walmart OAuth2 access token before it expires at the 15-minute boundary, ensuring every request succeeds. Since Workday has no native webhooks, ml-connector polls Workday for GL reference data daily and Walmart for orders and returns every 15 to 30 minutes, aligned with typical settlement batches and Walmart's webhook retry cadence.

How are returns and refunds mapped and posted to Workday?

Each Walmart return maps to the original order ID to identify the product, quantity, and original GL impact. ml-connector calculates the refund amount and posts it as a debit or credit adjustment to the same GL account and cost center as the original order. WFS (Walmart Fulfillment Services) returns are read-only, so only seller-managed returns result in Workday postings.