Workday Financial Management and Adobe Commerce integration

What moves between them

The main flow is Adobe Commerce into Workday. When a B2B purchase order is placed in Commerce or an order reaches invoiced status, ml-connector receives the webhook notification, extracts the order details and line items, and creates a supplier invoice or journal entry in Workday's accounts payable and general ledger. Cost allocations are mapped to the correct Workday cost center and GL account based on the product category and purchase order attributes. Supplier master data is synced from Workday into Commerce on a daily poll so that Commerce displays only valid suppliers in the B2B portal.

How ml-connector handles it

ml-connector subscribes to Adobe Commerce webhook events (order.placed_after and invoice.save_commit_after) and validates each payload via the x-adobe-commerce-webhook-signature header using the shared secret. On receipt, it parses the order, retrieves the matching Workday supplier by name or external ID, and builds a journal entry or AP invoice with the correct GL account and cost center. Workday credentials are stored encrypted and refreshed via OAuth2 before token expiry. If a GL post fails due to an invalid account or cost center, ml-connector logs the record, retries with exponential backoff, and surfaces the error in the audit trail so the finance team can validate the GL mapping before resubmitting. Supplier data flows the opposite direction: ml-connector polls Workday's supplier list daily and updates the Commerce B2B portal so the catalog reflects current approval status.

A real-world example

A mid-market B2B industrial parts distributor runs Workday Financial Management for GL, AP, and procurement, and uses Adobe Commerce B2B for customer self-service orders and purchase orders. Before the integration, the AP team received orders from Commerce, verified supplier validity against the Workday vendor master, and manually keyed each line item into the GL as a journal entry before the invoice could clear for payment. Duplicate entries and missed cost allocations meant month-end close took five days to reconcile. With the integration live, each order that reaches invoiced status flows automatically into Workday AP and GL, mapped to the correct supplier and cost center, and payment is ready on time. The supplier catalog stays in sync with Workday approvals, so customers see only valid vendors in the portal.

What you can do

• •Receive Adobe Commerce webhook notifications when orders place and invoices save, then write the detail into Workday accounts payable and general ledger as journal entries or supplier invoices.
• •Map Commerce orders to Workday suppliers and GL accounts using product category, purchase order attributes, and cost center rules defined per customer.
• •Validate order data against Workday supplier master and GL account dimensions before posting, and surface mapping errors for correction.
• •Sync Workday supplier master data daily into Adobe Commerce B2B portal so customers see only approved vendors.
• •Store all credentials encrypted, validate webhook signatures, retry failed GL posts, and maintain a complete audit trail of every transaction.

Questions

How does the integration handle the fact that Workday has no native webhooks?

Adobe Commerce is the source of webhooks in this pair. ml-connector listens to Commerce webhook events (order placed, invoice saved) and then polls Workday to validate supplier and GL dimensions before posting. Reference data like the supplier master is pulled from Workday on a daily schedule and synced back into Commerce.

What happens if a GL account or cost center does not exist in Workday when an order arrives?

ml-connector validates the GL account and cost center against Workday before posting the journal entry. If validation fails, the record is held in the audit trail with the error reason, and the finance team can correct the GL mapping or update the order attributes in Commerce before asking ml-connector to retry.

How are supplier invoices created in Workday from Commerce orders?

ml-connector extracts the supplier, order total, and line-item detail from the Commerce order or invoice, matches the supplier to the Workday vendor master by name or external ID, and creates an AP invoice with GL coding rules applied per customer. If the supplier does not exist in Workday, the record is flagged so the procurement team can add the vendor before the invoice can be posted.