Ellipse Gradient for Header
Workday Spend Management logo

Workday Spend Management Integration Guide

Workday Spend Management integrates with enterprise systems through Workday REST and SOAP APIs, reports, scheduled integrations, files, and selective outbound event patterns.

Workday Spend Management integration options at a glance

Workday Spend Management can be integrated through versioned REST APIs, extensive SOAP web services, Reports-as-a-Service, Enterprise Interface Builder, scheduled integrations, and selected outbound or event-oriented processes. REST is suitable for supported transactional objects such as Suppliers, Requisitions, Purchase Orders, Receipts, Supplier Invoices, and Expense Reports, while SOAP remains relevant for operations not exposed through REST. Batch and file-based exchanges support larger extracts. Martini can authenticate with Workday using tenant-approved OAuth 2.0, integration-user credentials, or certificates, then orchestrate workflows, paginate data, map formats, apply business rules, and expose controlled APIs.

Integration pointSupported by Workday Spend Management?Common use casesHow Martini supports it
REST APIsYesRead and update supported Suppliers, Requisitions, Purchase Orders, Receipts, Supplier Invoices, and expense-related resources, subject to tenant configuration, API version, and permissions.Martini can consume Workday REST APIs from workflows, handle paginated responses, transform JSON, apply business rules, and expose a controlled downstream API.
SOAP APIsYesUse Workday Web Services when an operation is not available through REST, an existing WSDL contract must be preserved, or a business process is exposed through SOAP.Martini can consume SOAP services, manage tenant-configured authentication, parse XML, and map SOAP responses into downstream formats.
Reports-as-a-ServiceYesExtract supplier, purchasing, invoice, expense, or accounting datasets using authorized reports, filters, prompts, and scheduled or incremental queries.Martini can invoke accessible report endpoints, process XML or delimited output, validate schemas, and checkpoint incremental extracts.
Webhooks and outbound callbacksLimitedSupport selected event-oriented or outbound processes such as business-process notifications and transaction status changes; coverage depends on the tenant and process configuration.Martini can receive supported outbound HTTP notifications or invoke a configured receiver, then retrieve authoritative Workday data before processing it.
Bulk, asynchronous, and batch processingLimitedProcess larger volumes through reports, EIB, scheduled integrations, selected asynchronous services, and batch-oriented workflows.Martini can schedule extraction, paginate and batch records, maintain checkpoints, reconcile results, and separate rejected rows from transport failures.
File and attachment integrationsLimitedExchange XML or delimited files through integration services and handle selected documents associated with suppliers, invoices, expenses, or procurement transactions.Martini can orchestrate accessible file transfers, parse supported formats, and process attachment metadata and binary content separately where the Workday operation permits it.
AuthenticationYesAuthenticate REST integrations with applicable OAuth 2.0 configurations and use tenant-approved integration users, credentials, WS-Security, or certificates for other patterns.Martini can store secrets and certificates by environment and apply the configured authentication method to API and service calls.
Database accessNoDirect customer access to the Workday transactional database is not a standard integration mechanism; approved reports, APIs, EIB, and exports should be used instead.Martini can consume approved Workday data interfaces and write results to external databases, but should not connect directly to the Workday application database.

How Workday Spend Management exposes data and business events

Workday REST APIs

Workday provides versioned REST APIs for selected Spend Management objects and operations. REST is appropriate for supported transactional reads and updates, reference data, status retrieval, and selected business-process actions, with availability controlled by tenant configuration and Workday security.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates to the configured Workday REST endpoint, retrieves paginated resources, validates response status and schema, maps JSON into a canonical model, applies business rules, and writes to the target system. For writes, the workflow records the Workday transaction identifier and models accepted, intermediate, approved, rejected, and canceled states separately.

Implementation sequence

Authenticate with the tenant-approved Workday REST configuration
Retrieve the current resource or filtered collection
Process pages and preserve a checkpoint or overlap window
Validate identifiers, schema, and business fields
Map the response to the canonical integration model
Apply business rules and idempotency checks intended for the target system

Workday SOAP APIs

Workday Web Services provide extensive SOAP operations and remain relevant when REST coverage is insufficient, an existing WSDL contract must be preserved, or a business process or report operation is exposed through SOAP.

Martini implementation pattern

Martini implementation pattern: a workflow invokes the required Workday SOAP operation with the tenant-configured credentials or certificate, parses the XML response, separates SOAP faults from business-process errors, and transforms the result for downstream applications. Reusable workflow logic can standardize correlation IDs, fault handling, and XML-to-JSON or canonical mappings.

Implementation sequence

Configure the Workday SOAP endpoint and approved security method
Build the request from validated canonical input
Invoke the WSDL-defined operation
Parse the XML response or SOAP fault
Map returned reference IDs and statuses
Route retryable faults and business rejections independently

Reports-as-a-Service

Workday reports and Reports-as-a-Service support authorized extracts for supplier, purchasing, invoice, expense, and accounting data. Reports can use tenant-defined filters, prompts, calculated fields, and output formats, but they are not a replacement for transactional APIs.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow requests the authorized report, parses the configured XML or delimited output, validates the expected columns, transforms rows into canonical objects, and stores the extraction checkpoint. Martini can then load batches into a target system and record rejected rows without treating a report extract as a transactional update.

Implementation sequence

Start the workflow on an approved schedule
Request the authorized Workday report with filter parameters
Validate the report format and expected columns
Parse and transform each report row
Upsert the resulting objects into the target system
Store the extraction checkpoint and report exceptions

Outbound and event-oriented integrations

Workday supports selected outbound and event-oriented integration patterns through business processes, scheduled integrations, EIBs, reports, or outbound services. Coverage is process- and tenant-specific, so conventional webhook coverage should not be assumed for every Spend Management object.

Martini implementation pattern

Martini implementation pattern: where the tenant can deliver an outbound notification or callback, Martini receives the notification through an API or workflow trigger, verifies the request, and retrieves authoritative Workday data before applying changes. Where no callback is available, a scheduled workflow can poll a filtered REST resource or report and use overlap windows and idempotency keys.

Implementation sequence

Confirm the event or outbound integration available in the Workday tenant
Receive the notification or start the scheduled poll
Authenticate and retrieve authoritative transaction details
Validate the event, object identifier, and current state
Apply canonical mapping and downstream business rules
Record the event or checkpoint and retry safe failures

Common Workday Spend Management integration patterns

Pattern 1: Synchronize suppliers with an ERP

When to use this pattern

Use this pattern when Workday is the source for supplier master data and an external ERP or procurement platform requires current supplier status, contacts, addresses, and reference identifiers. Scheduled REST, SOAP, or report extraction is appropriate when universal event coverage is not available.

Integration direction
Workday Spend Management
Martini
SAP S/4HANA
Example Mapping
Workday Spend Management FieldCanonical FieldTarget Field
Supplier Reference IDsupplier.externalIdBusiness Partner External ID
Supplier Namesupplier.nameBusiness Partner Name
Supplier Statussupplier.statusSupplier Status
Primary Addresssupplier.addressSupplier Address
Martini implementation pattern

A scheduled Martini workflow retrieves changed Suppliers with pagination and an overlap window, validates required reference IDs, maps effective-dated attributes, and performs idempotent upserts. It records a checkpoint, rejects incomplete suppliers for review, and retries only transient transport failures.

Martini capabilities used
  • workflows
  • scheduled triggers
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Process requisition and purchase-order status

When to use this pattern

Use this pattern when downstream applications need Workday approval, fulfillment, or purchase-order status, or when an external request must be submitted through a supported Workday operation. Workday business-process state must be distinguished from an accepted API response.

Integration direction
Workday Spend Management
Martini
ServiceNow
Example Mapping
Workday Spend Management FieldCanonical FieldTarget Field
Requisition Reference IDprocurement.requestIdRequest Number
Approval Statusprocurement.statusApproval State
Requester Reference IDprocurement.requesterIdRequested For
Purchase Order Numberprocurement.purchaseOrderIdRelated Purchase Order
Martini implementation pattern

Martini can receive a downstream request or poll Workday for status changes, validate tenant-specific reference values, and map Workday states to the target workflow. It returns Workday identifiers, routes business-process rejections separately from connectivity failures, and prevents duplicate submissions with an idempotency key.

Martini capabilities used
  • API consumption
  • API exposure
  • workflows
  • data mapping
  • conditional routing
  • error handling

Pattern 3: Export expense reports for reimbursement processing

When to use this pattern

Use this pattern when finance or payroll systems require approved Expense Reports, expense lines, Spend Categories, currencies, and reimbursement status from Workday. Reports or filtered REST resources can support scheduled incremental extraction.

Integration direction
Workday Spend Management
Martini
Oracle Fusion Cloud ERP
Example Mapping
Workday Spend Management FieldCanonical FieldTarget Field
Expense Report Reference IDexpenseReport.externalIdExpense Report Number
Worker Reference IDexpenseReport.workerIdEmployee ID
Spend CategoryexpenseLine.categoryExpense Category
Reimbursement StatusexpenseReport.reimbursementStatusPayment Status
Martini implementation pattern

A scheduled Martini workflow retrieves authorized Expense Reports, processes pages or report rows, transforms currencies and dates, and validates category and worker references. It checkpoints the extraction, upserts downstream expenses, and places malformed rows or rejected business states on an exception path.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • JSON and XML handling
  • data mapping
  • validation
  • checkpointing
  • error handling

Pattern 4: Reconcile supplier invoices, purchase orders, and receipts

When to use this pattern

Use this pattern when an accounts-payable or procurement application needs Workday data combined across Supplier Invoices, Purchase Orders, Receipts, and Suppliers to detect unmatched or duplicate transactions.

Integration direction
Workday Spend Management
Martini
NetSuite
Example Mapping
Workday Spend Management FieldCanonical FieldTarget Field
Supplier Invoice Numberinvoice.externalIdVendor Bill Number
Purchase Order Reference IDinvoice.purchaseOrderIdPurchase Order Reference
Receipt Quantityreceipt.quantityReceived Quantity
Invoice Matching Statusinvoice.matchStatusApproval or Match Status
Martini implementation pattern

Martini retrieves the relevant Workday objects, joins them by stable reference identifiers, validates supplier, currency, and receipt relationships, and applies duplicate and missing-receipt rules. Matched results are sent to NetSuite, while exceptions are logged and routed for review without retrying permanent validation failures.

Martini capabilities used
  • workflow orchestration
  • API consumption
  • data mapping
  • business rules
  • correlation
  • exception routing

Applications commonly integrated with Workday Spend Management

Workday Spend Management can exchange procurement, supplier, expense, invoice, and reference data with adjacent enterprise applications. The appropriate direction and ownership depend on the tenant configuration and the system responsible for each business object.

Application Scenario Direction Martini Pattern
Salesforce Synchronize approved worker, organizational, customer, or finance context where sales operations require Workday reference data. Workday Spend Management → Martini → Salesforce Martini can retrieve authorized Workday data through REST, SOAP, or reports, normalize identifiers and effective dates, and upsert Salesforce records with validation and retry handling.
ServiceNow Align procurement requests, supplier information, employee data, and approval-related workflows with service-management processes. Workday Spend Management → Martini → ServiceNow A Martini workflow can receive or schedule Workday transactions, map statuses and reference IDs, create or update ServiceNow items, and route business-process exceptions separately from transport failures.
SAP S/4HANA Exchange suppliers, purchase orders, invoices, receipts, accounting data, and procurement status between Workday and an enterprise ERP. Workday Spend Management → Martini → SAP S/4HANA Martini can combine Workday REST, SOAP, report, or file extracts with SAP API calls, apply canonical mappings, reconcile identifiers, and checkpoint scheduled or batch processing.
Oracle Fusion Cloud ERP Coordinate supplier, invoice, procurement, expense, and financial data across Workday and Oracle financial processes. Workday Spend Management → Martini → Oracle Fusion Cloud ERP Martini can orchestrate bidirectional workflows, validate Workday business-process states, transform currencies and reference values, and retry only safe transient failures.
NetSuite Synchronize supplier, purchasing, expense, and financial information for organizations using NetSuite alongside Workday. Workday Spend Management → Martini → NetSuite A scheduled Martini workflow can extract Workday objects, map stable Workday identifiers to NetSuite fields, perform controlled upserts, and store checkpoints and rejected-row details.
Coupa Coordinate procurement requests, suppliers, purchase orders, invoices, and spend information where Coupa and Workday coexist. Workday Spend Management → Martini → Coupa Martini can exchange supported objects through Workday APIs, reports, or files and Coupa endpoints, applying ownership rules, duplicate detection, and exception routing.
Jira Create implementation, procurement, or exception-management work items from Workday transaction outcomes. Workday Spend Management → Martini → Jira Martini can detect rejected, delayed, or unmatched Workday transactions, map the relevant identifiers and diagnostics, and create Jira issues while preventing duplicate issue creation.
Microsoft Power BI Deliver authorized supplier, invoice, expense, purchasing, and spend datasets for reporting and analysis. Workday Spend Management → Martini → Microsoft Power BI Martini can retrieve approved Workday reports or exports, transform them into a reporting-oriented model, deliver them through an approved data platform, and monitor extract completeness.

How to build a Workday Spend Management integration in Martini

Objective

Establish tenant-specific access to Workday and the target system without embedding credentials in workflow logic.

Instructions in Martini

  • Confirm the required Workday REST, SOAP, report, EIB, or outbound endpoint in the target tenant
  • Choose OAuth 2.0, an Integration System User, WS-Security, or certificate authentication as applicable
  • Store client secrets, passwords, tokens, and certificates in environment-specific Martini secrets
  • Document Workday security-domain and business-process permissions

Objective

Select an event-oriented, scheduled, API-led, or batch trigger based on the Workday process and confirmed tenant capabilities.

Instructions in Martini

  • Use a supported outbound notification or callback when the required event is available
  • Use a scheduler for reports, incremental REST extraction, or batch processing
  • Use an exposed Martini API when another application initiates a Workday transaction
  • Define the checkpoint, overlap window, and expected processing frequency

Objective

Obtain authoritative Workday data and manage pagination, report formats, and asynchronous or batch behavior.

Instructions in Martini

  • Call the confirmed REST resource or SOAP operation, or request the authorized report
  • Process paginated collections and bounded extraction windows
  • Retrieve full transaction details after receiving a notification when necessary
  • Record Workday reference IDs, correlation identifiers, and processing checkpoints

Objective

Coordinate retrieval, validation, enrichment, target writes, and exception paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate transport failures from Workday validation and business-process failures
  • Use conditional routing for approved, pending, rejected, canceled, and exception states
  • Apply controlled concurrency for tenant-specific throughput limits
  • Keep reusable Workday access and normalization logic in maintainable workflow assets

Objective

Convert Workday JSON, XML, report, or file structures into a canonical model and target-specific payloads.

Instructions in Martini

  • Map stable reference IDs rather than relying only on display names
  • Preserve effective dates, currencies, statuses, and source identifiers
  • Transform XML, JSON, or delimited report data as required
  • Validate required fields, data types, and tenant-specific reference values

Objective

Enforce ownership, matching, duplicate, approval, and retry rules before changing downstream systems.

Instructions in Martini

  • Use Workday transaction identifiers or external references as idempotency keys
  • Detect duplicate invoices, missing receipts, invalid suppliers, and unmatched purchase orders
  • Do not treat an accepted API response as proof that a business process completed
  • Route permanent validation failures to an exception process

Common Workday Spend Management data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
SuppliersSynchronize supplier master data, status, contacts, addresses, and payment-related attributes.SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Coupa, supplier portalsMartini retrieves supported fields through REST, SOAP, or reports, preserves stable reference IDs and effective dates, validates required attributes, and performs idempotent upserts.
RequisitionsExchange requests for goods or services, approval state, requester information, and procurement references.ServiceNow, Coupa, SAP S/4HANA, Oracle Fusion Cloud ERPMartini maps requisition lines and statuses, validates tenant-specific reference values, and distinguishes accepted transactions from completed or rejected business processes.
Purchase OrdersSynchronize approved purchasing commitments, supplier details, lines, amounts, and fulfillment status.SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, CoupaMartini retrieves or submits supported operations, maps identifiers and currencies, applies duplicate controls, and routes business-process errors for review.
ReceiptsConfirm delivery of goods or services and support invoice and purchase-order reconciliation.SAP S/4HANA, Oracle Fusion Cloud ERP, Coupa, reporting platformsMartini correlates receipt references with Purchase Orders, validates quantities and dates, and sends reconciliation results or exceptions downstream.
Supplier InvoicesExchange invoice references, supplier details, amounts, currencies, matching state, and payment-related status.SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, CoupaMartini validates supplier and invoice identifiers, detects duplicates, correlates invoices with Purchase Orders and Receipts, and separates mapping errors from Workday rejection states.
Expense ReportsExport employee-submitted expenses, lines, Spend Categories, approval state, reimbursement data, and accounting information.Oracle Fusion Cloud ERP, SAP S/4HANA, NetSuite, payroll and reporting platformsMartini retrieves authorized data through APIs or reports, transforms dates, amounts, currencies, and categories, and uses checkpoints for incremental synchronization.

Authentication and security considerations

Tenant-specific authorization

Workday authentication does not by itself grant access to Spend Management objects. OAuth scopes, integration-user permissions, Workday security domains, and business-process permissions must all support the required operations.

Supported security patterns

  • Use OAuth 2.0 for applicable Workday REST integrations.
  • Use an Integration System User with explicitly assigned permissions where required.
  • Use tenant-approved SOAP credentials, WS-Security, or certificates for applicable services.
  • Store credentials, client secrets, tokens, and certificates in Martini environment-specific secrets.

Controlled exposure

When Martini exposes an API façade, restrict operations, validate input, and apply authentication and authorization appropriate to the calling application. Do not expose Workday credentials or unrestricted tenant operations to downstream consumers.

Operational considerations for Workday Spend Management integrations

Tenant and API versions

Validate the target tenant's API catalog, enabled modules, security domains, report definitions, and API versions before finalizing the integration contract. Monitor version and schema changes.

Throughput and extraction

  • Handle REST pagination and use stable date, effective-date, or status filters.
  • Use checkpoints and overlap windows for incremental synchronization.
  • Confirm tenant-specific rate limits and use controlled concurrency and exponential backoff.
  • Prefer reports, scheduled integrations, EIB, or batch patterns for large extracts.

Business-process and data quality

  • Distinguish accepted requests from completed, approved, rejected, or canceled business processes.
  • Use stable Workday reference identifiers rather than display names alone.
  • Preserve effective dates, currencies, statuses, and source identifiers.
  • Separate document metadata from binary attachment content and verify object-specific support.

Reliability and testing

Use idempotency keys based on Workday transaction identifiers, supplier identifiers, invoice numbers, or external references. Test authentication, pagination, schema changes, duplicate handling, business-process rejection, retry behavior, and downstream reconciliation with representative tenant data.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond point-to-point calls

Workday Spend Management integrations often combine REST or SOAP calls, reports, scheduled extraction, files, business rules, and downstream writes. Martini provides a workflow layer for coordinating these steps without embedding the entire process in a single script or tightly coupling two applications.

Maintainable transformations

Martini can map Workday JSON, XML, report, and file formats into canonical and target-specific models. Reusable workflow assets, validation, conditional routing, and controlled error paths make changes easier to manage as tenant configuration and downstream schemas evolve.

Operational reliability

  • Store environment-specific credentials and certificates securely.
  • Implement checkpoints, pagination, overlap windows, idempotency, and retry policies.
  • Separate transport failures from Workday validation and business-process failures.
  • Expose controlled APIs when downstream applications need a stable façade rather than direct Workday access.
  • Use workflow logs and monitoring to trace correlation IDs, rejected rows, and reconciliation results.

Frequently asked questions

How can Workday Spend Management be integrated with enterprise systems?

Workday Spend Management can integrate through versioned REST APIs, SOAP Web Services, Reports-as-a-Service, Enterprise Interface Builder, scheduled integrations, files, and selected outbound or event-oriented processes. The available objects, operations, fields, and authentication methods depend on the Workday tenant, enabled modules, API version, and security configuration.

Can Martini integrate with Workday Spend Management?

Yes. Martini can integrate with Workday Spend Management by consuming confirmed Workday REST APIs, SOAP services, reports, files, and supported outbound integration endpoints. It can orchestrate workflows, transform JSON or XML, apply business rules, manage checkpoints, and expose controlled APIs for downstream applications.

Do I need a connector to integrate Workday Spend Management with Martini?

No. A dedicated Workday connector is not required. Martini can use Workday's supported REST APIs, SOAP services, reports, files, authentication methods, and outbound integration mechanisms through workflows and APIs.

Is there any extra Lonti cost to integrate Workday Spend Management with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday Spend Management. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workday, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Workday integration method should an implementation use?

Use REST when the required resource and operation are available and JSON-based access is suitable. Use SOAP when REST coverage is insufficient, an existing WSDL contract must be preserved, or the required business process is exposed through Workday Web Services. Use reports, RaaS, EIB, or scheduled integrations for approved bulk and extraction workloads.

Are Workday webhooks or event notifications available?

Workday supports selected outbound and event-oriented patterns, but universal webhook coverage for Spend Management objects should not be assumed. The available mechanism may be a business-process notification, scheduled integration, EIB, report extract, outbound service, or callback, and must be confirmed in the target tenant.

How does Martini synchronize Workday Spend Management data?

Martini can run scheduled workflows that call filtered REST resources or retrieve authorized reports, using last-updated or effective-date criteria where available. The workflow can paginate consistently, use overlap windows, preserve checkpoints, and apply Workday transaction identifiers or external references for idempotent downstream updates.

How does Martini handle Workday errors, retries, and data transformation?

Martini can map Workday JSON, XML, report, and file data into canonical and target-specific models, validate reference values, and apply business rules. Workflows can distinguish authentication, transport, validation, business-process, duplicate, and downstream errors, retry safe transient failures, and route permanent exceptions for review. Martini can also expose an API façade around supported Workday operations.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Integrate Workday Spend Management with Martini

Use Martini to connect Workday Spend Management with enterprise applications through secure APIs, workflows, reports, files, and controlled event-driven processes.

EXPLORE MARTINI
BOOK A DEMO