Workday Financial Management and Ramp integration

What moves between them

The main flow moves from Ramp into Workday. When a bill is created or a corporate card transaction clears in Ramp, ml-connector receives the webhook notification, extracts the amount, vendor, and expense category, maps the category to a Workday GL account and optional worktag, and posts a journal entry into Workday's general ledger. Reference data such as GL accounts and vendors are synced from Workday to Ramp so expense allocations land on valid accounts.

How ml-connector handles it

ml-connector listens for Ramp webhooks and validates the HMAC-SHA256 signature on each event. For Workday, it accepts either the SOAP or REST transport and the customer's choice of ISU or OAuth2 credentials, storing credentials encrypted. When a bill or transaction arrives from Ramp, ml-connector looks up the GL account by expense category, verifies the account exists in Workday, and submits a journal entry via SOAP if complex, or REST for simpler posts. Ramp GL accounts and vendors are validated against Workday's supplier and account lists so every post references an existing account. If Workday returns a validation error, ml-connector retries and logs the failure for audit. Rate limiting on either side is handled with exponential backoff.

A real-world example

A mid-sized consulting firm uses Workday for accounting and procurement, and Ramp for employee corporate cards and vendor bill management across three offices. Before the integration, the finance team exported bills and cleared transactions from Ramp each week, categorized each one by hand, and entered them into Workday's journal as expense allocations. Month-end reconciliation required manual cross-checks between Ramp transaction reports and Workday's GL postings, and discrepancies appeared frequently. With Workday and Ramp connected, each bill and transaction in Ramp flows into Workday automatically on the correct GL account and allocated to the matching cost center or project, and the finance team has a single audit trail across both systems. Month-end close now starts with complete visibility into spend and no reconciliation gaps.

What you can do

• •Post Ramp bills into Workday's general ledger as journal entries, mapped to GL accounts and suppliers.
• •Sync corporate card transactions from Ramp to Workday in real-time via webhooks, reducing manual re-keying.
• •Validate GL accounts and vendors in Workday before posting to prevent errors.
• •Authenticate Workday via SOAP/ISU or REST/OAuth2, and Ramp via OAuth2 client credentials, with encrypted credential storage.
• •Receive Ramp webhook notifications with HMAC-SHA256 signature validation and maintain a full audit trail.

Questions

Which direction does data move between Workday and Ramp?

The primary flow is from Ramp into Workday. Bills and corporate card transactions created or cleared in Ramp are posted as journal entries into Workday's general ledger, mapped to the GL accounts you define. GL accounts and vendor lists are synced from Workday to Ramp so that expense categorizations reference valid accounts.

Does ml-connector support Workday's SOAP interface, or only REST?

ml-connector supports both. For simple journal entry posts and account reads, REST is sufficient. For complex operations or customers with legacy Workday on-premise integrations, the SOAP/XML interface with WS-Security and ISU credentials is available. You choose the transport per customer.

How does ml-connector handle Ramp webhooks and real-time bill creation?

Ramp pushes webhook events when bills are created, transactions clear, or vendors are updated. ml-connector listens for these webhooks, validates the HMAC-SHA256 signature on each event, and immediately processes the bill or transaction into Workday's journal entry table. No polling required; the latency is seconds from Ramp to Workday.