Workday Financial Management and UPS integration

What moves between them

The flow runs from UPS into Workday Financial Management. ml-connector reads shipment records and tracking data from UPS (either via Track Alert webhooks for newly shipped items or by polling Quantum View), extracts freight charges and cost data, and posts them into Workday as supplier invoices or cost-center-allocated journal entries to the designated freight or shipping GL account. The direction is read-only from UPS (shipments and charges are never written back), while Workday receives the freight cost records. The cadence depends on your shipping volume and billing cycle; typical configurations poll every 4 to 24 hours or subscribe to Track Alert events for real-time visibility.

How ml-connector handles it

ml-connector stores Workday ISU credentials and UPS OAuth2 secrets encrypted in its vault. For Workday, it uses SOAP for invoice creation or REST for lighter queries, refreshing the OAuth2 access token when requests return 401. For UPS, it presents the client credentials and optional merchant ID on every call, refreshes the bearer token before the 4-hour window expires, and handles the 14-day Track Alert subscription expiry by renewing subscriptions on a schedule. Because UPS Track Alert subscriptions are capped at 100 tracking numbers, high-volume shippers use Quantum View polling instead. Freight charge amounts are mapped to the appropriate Workday GL account and cost center based on shipment origin or destination; when cost center is unknown, charges default to a suspense account for later allocation. Every shipment record carries its UPS tracking number, shipment date, destination, and amount in the Workday audit trail, allowing drill-down from the general ledger back to the original carrier record. If a UPS API call fails, ml-connector retries with exponential backoff before flagging the record for manual review.

A real-world example

A mid-sized e-commerce retailer ships thousands of packages monthly through UPS across multiple fulfillment centers. Before the integration, the accounting team received UPS invoices weeks after shipments and manually entered freight charges by shipment batch into Workday, allocating by fulfillment center based on carrier reports. Month-end close required reconciling Workday charged-to date against actual ship dates, causing weeks of delay. Now, shipments flow from UPS into Workday within hours of pickup, with costs allocated automatically to the originating center. The accounting team no longer spends days chasing discrepancies, and the freight accounts are reconciled by week two of month-end close.

What you can do

• •Automatically post UPS shipment charges into Workday Financial Management as supplier invoices or cost-center-allocated journal entries.
• •Refresh Workday OAuth2 tokens and UPS bearer tokens before expiry to prevent authentication failures.
• •Route charges to the correct general ledger account and cost center based on shipment metadata.
• •Receive real-time Track Alert notifications from UPS or poll Quantum View for high-volume shipments, with automatic subscription renewal.
• •Maintain a complete audit trail linking each Workday invoice line back to the UPS tracking number and shipment record.

Questions

Which direction does data move between Workday Financial Management and UPS?

Data flows from UPS into Workday Financial Management. Shipment records, tracking data, and freight charges move from UPS into Workday as supplier invoices or journal entries, typically posted to a freight or shipping GL account. Workday never writes shipment or charge data back to UPS.

How does ml-connector handle UPS Track Alert subscription expiry and UPS account numbers?

UPS Track Alert subscriptions are valid for 14 days and must be renewed before they expire. ml-connector tracks subscription dates and automatically renews them on a schedule, so new shipments stay visible without manual intervention. If your company uses multiple UPS account numbers, ml-connector routes each call with the correct x-merchant-id header per customer account.

What happens if Workday and UPS tokens expire or if a shipment charge fails to post?

ml-connector monitors token expiry times and refreshes Workday OAuth2 and UPS bearer tokens before the window closes, preventing 401 errors mid-sync. If a shipment charge fails to post to Workday, the record is flagged with the error reason in the audit trail, and ml-connector retries on the next scheduled sync cycle. High-priority charges can be marked for manual review and replay from the audit log.