Ellipse Gradient for Header
Workday Expenses logo

Workday Expenses Integration Guide

Integrate Workday Expenses with enterprise applications through tenant-configured REST APIs, SOAP services, reports, EIB, and scheduled Martini workflows.

Workday Expenses integration options at a glance

Workday Expenses supports REST APIs for supported expense resources, Workday Web Services for SOAP-based operations, reports-as-a-service for configured extracts, and Enterprise Interface Builder for file-oriented or batch exchanges. Authentication may use OAuth 2.0, an Integration System User with Basic Authentication, or Workday-supported SOAP security, depending on the tenant and service. General expense webhooks are not confirmed, so scheduled incremental polling is often required when no suitable business-process notification exists. Martini can orchestrate these calls, transform expense data, validate accounting dimensions, process files, expose controlled APIs, and maintain checkpoints for reliable synchronization.

Integration pointSupported by Workday Expenses?Common use casesHow Martini supports it
REST APIsYesRetrieve Expense Reports, Expense Items, Workers, reference data, and supported expense resources; submit or update resources where the tenant exposes those operations.Martini can consume tenant-specific, versioned Workday REST endpoints, transform responses, apply validation, and orchestrate downstream writes.
SOAP APIsYesUse Workday Web Services for Financial Management and expense operations that are unavailable through REST or already implemented through WSDL-based integrations.Martini can consume Workday SOAP services using configured WSDLs, endpoints, authentication, XML mappings, and error handling.
Reports-as-a-serviceYesProduce scheduled expense-report extracts, reconciliation data, accounting reports, or tenant-specific combinations of fields.Martini can invoke or retrieve configured report outputs, parse the returned structure, map fields, and deliver the result to downstream systems.
Bulk / async / batch APIsLimitedUse EIB and other Workday file-oriented or batch mechanisms for larger scheduled exchanges or tenant-specific integrations.Martini can schedule exchanges, retrieve generated files or reports, transform batches, and submit approved files or API requests.
File / attachment APIsLimitedProcess receipt and supporting-document metadata or binaries when the tenant and selected Workday resource expose suitable operations.Martini can handle confirmed file exchanges and separate attachment workflows, while treating receipt availability and binary transfer as tenant-dependent.
Webhooks / outbound callbacksNot confirmedWorkday may support business-process notifications or outbound integration patterns, but a general Workday Expenses webhook API was not confirmed.Martini can receive webhook-style input where the tenant provides a compatible notification endpoint; otherwise it can use scheduled polling and checkpoints.
AuthenticationYesUse OAuth 2.0 for configured REST access, Integration System User security and Basic Authentication for selected scenarios, or Workday-supported SOAP security.Martini stores credentials, tokens, endpoints, and environment configuration securely and applies them when workflows consume Workday services.
Database accessNoDirect customer database access is not the expected approach for Workday Expenses integrations.Martini should use Workday REST, SOAP, reports, EIB, or other approved integration mechanisms instead of a direct database connection.

How Workday Expenses exposes data and business events

Workday REST APIs

Workday provides versioned REST APIs for supported business objects and functional areas. Expense resource availability, fields, operations, and permissions depend on the tenant, enabled products, and API version.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates to the tenant-specific REST endpoint, retrieves reports or related resources using bounded windows and pagination, maps the response into a canonical model, and writes validated data to downstream systems.

Implementation sequence

Authenticate with the configured Workday REST client
Retrieve Expense Reports or related resources
Follow pagination and retrieve required details
Map Workday objects to the target model
Validate statuses, totals, currencies, and worktags
Write the result and store the successful checkpoint

Workday SOAP APIs

Workday Web Services expose SOAP and WSDL operations across functional areas, including operations that may not be available through the relevant REST resources.

Martini implementation pattern

Martini implementation pattern: a workflow consumes the selected WSDL operation, applies Workday-supported SOAP authentication, transforms XML request and response structures, and classifies business, authorization, and transport errors.

Implementation sequence

Load the tenant-approved Workday WSDL configuration
Authenticate the SOAP request
Invoke the required expense or financial operation
Parse the XML response and fault details
Map the response to the canonical model
Retry eligible transient failures and record the outcome

Workday Reports and EIB

Reports-as-a-service and Enterprise Interface Builder support configured extracts and file-oriented or batch exchanges. Their exact output, prompts, templates, and permissions are tenant-specific.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow invokes or retrieves the configured report or EIB output, parses the returned file or structure, applies validation and transformations, and delivers the result to a target application or storage layer.

Implementation sequence

Start the scheduled report or EIB exchange
Retrieve the generated report or file
Validate the schema, row counts, and control totals
Transform the batch into the target format
Deliver the output to the target endpoint or file store
Record the batch identifier and processing checkpoint

Workday event and outbound integrations

A general Workday Expenses webhook API was not confirmed. Workday event-driven and outbound patterns are dependent on business processes, integration configuration, and tenant capabilities.

Martini implementation pattern

Martini implementation pattern: first verify whether the tenant can provide a suitable notification, callback, or outbound integration. If not, Martini uses scheduled incremental polling with overlap windows and state tracking instead of assuming universal expense webhooks.

Implementation sequence

Verify the tenant-supported notification or outbound mechanism
Receive the notification or start the polling schedule
Retrieve the current Workday resource
Check the event or resource against the processing checkpoint
Apply mappings and business rules
Acknowledge or record the result and retry eligible failures

Common Workday Expenses integration patterns

Pattern 1: Export approved expenses to an ERP

When to use this pattern

Use this pattern when approved Workday Expenses must be posted to a financial system such as NetSuite or Oracle Fusion Cloud ERP. The workflow should export only eligible lifecycle states and preserve Workday identifiers for reconciliation.

Integration direction
Workday Expenses
Martini
NetSuite
Example Mapping
Workday Expenses FieldCanonical FieldTarget Field
Expense Report IDexpenseReportIdexternalReference
Expense Report Lines.amountlineAmountexpenseAmount
Expense Report Lines.worktagaccountingDimensionsegmentValue
Expense Report.statusapprovalStatuspostingEligibility
Martini implementation pattern

A scheduler starts an incremental retrieval workflow. Martini obtains reports and lines, validates approval status, company, currency, worktags, totals, and effective-dated worker data, then transforms and submits the target transaction. It stores the target identifier and uses idempotency checks, retries, and an exception path for rejected postings.

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

Pattern 2: Reconcile corporate-card transactions

When to use this pattern

Use this pattern when Expense Credit Card Transactions must be compared with Expense Reports or Expense Report Lines to identify unmatched, duplicated, or financially inconsistent activity.

Integration direction
Workday Expenses
Martini
ServiceNow
Example Mapping
Workday Expenses FieldCanonical FieldTarget Field
Expense Credit Card Transactions.transactionIdcardTransactionIdexternalReference
Expense Credit Card Transactions.amountcardAmountreportedAmount
Expense Report Lines.receiptReferencereceiptReferenceattachmentStatus
Expense Report.statusreportStatuscaseState
Martini implementation pattern

Martini retrieves card transactions and related expense data within an overlapping time window, matches stable identifiers and amounts, applies tolerance and duplicate rules, and creates ServiceNow cases for exceptions. Successful matches are checkpointed; temporary Workday or ServiceNow failures are retried without creating duplicate cases.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • conditional routing
  • idempotency
  • error handling

Pattern 3: Synchronize reimbursement status

When to use this pattern

Use this pattern when another application needs approved, paid, rejected, or corrected Expense Report status and reimbursement information from Workday.

Integration direction
Workday Expenses
Martini
Salesforce
Example Mapping
Workday Expenses FieldCanonical FieldTarget Field
Expense Report.reportNumberexpenseReferenceexpenseReference
Expense Report.statusexpenseStatusreimbursementStatus
Expense Report.totalAmountapprovedAmountreimbursementAmount
Workers.workerIdworkerReferenceemployeeReference
Martini implementation pattern

A scheduled workflow retrieves status changes, enriches reports with Workers where permitted, translates Workday lifecycle values into the target status model, and updates Salesforce only when the canonical state has changed. Martini records the last successful state and target reference to prevent duplicate updates and propagates corrections explicitly.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data transformation
  • business rules
  • state tracking
  • retry handling

Pattern 4: Expose an expense reporting API façade

When to use this pattern

Use this pattern when downstream applications need approved expense data without receiving Workday credentials, tenant-specific endpoints, or Workday-specific response structures.

Integration direction
Consumer Application
Martini
Workday Expenses
Example Mapping
Workday Expenses FieldCanonical FieldTarget Field
Expense Report IDexpenseIdresponse.expenseId
Expense Report.totalAmounttotalAmountresponse.totalAmount
Expense Report.currencycurrencyresponse.currency
Expense Report.statusstatusresponse.status
Martini implementation pattern

Martini exposes a controlled REST API, authenticates and authorizes the caller, orchestrates Workday REST or SOAP retrieval, filters the permitted lifecycle states and fields, and returns a stable canonical response. It applies request validation, correlation logging, timeout handling, and controlled retries while keeping Workday credentials internal.

Martini capabilities used
  • API exposure
  • workflow orchestration
  • API consumption
  • data mapping
  • authentication and authorization
  • business rules
  • error handling

Applications commonly integrated with Workday Expenses

Workday Expenses can be integrated with named financial, operational, reporting, and storage applications when the tenant configuration and target-system requirements support the use case. These relationships do not imply a dedicated native integration from Workday or Martini.

Application Scenario Direction Martini Pattern
SAP Concur Reconcile or migrate travel and expense activity, corporate-card transactions, and reimbursement data between platforms. Workday Expenses → Martini → SAP Concur Use scheduled REST, SOAP, report, or file retrieval to obtain approved expense data, normalize identifiers and statuses, and apply duplicate checks before exchanging records with SAP Concur.
Salesforce Make approved employee expense or reimbursement information available to customer, project, or account-related processes. Workday Expenses → Martini → Salesforce Retrieve eligible Expense Reports, enrich them with Workers and accounting dimensions, map the result to Salesforce objects, and route validation or API failures for retry.
ServiceNow Create cases or tasks for expense exceptions, failed integrations, audit issues, or employee support requests. Workday Expenses → Martini → ServiceNow Detect unmatched transactions, rejected reports, missing receipts, or processing failures in a Martini workflow and create ServiceNow records with correlation identifiers and status updates.
NetSuite Transfer approved expense and accounting data for financial posting, reconciliation, and reporting. Workday Expenses → Martini → NetSuite Poll approved Expense Reports, validate currencies, worktags, totals, and companies, transform lines into the NetSuite accounting model, and persist target posting identifiers.
Oracle Fusion Cloud ERP Synchronize approved expenses, accounting distributions, workers, and reimbursement-related financial data. Workday Expenses → Martini → Oracle Fusion Cloud ERP Use a scheduled workflow to retrieve report and line details, apply effective-date and approval rules, map accounting distributions, and retry transient target-system failures.
Coupa Coordinate expense, procurement, supplier, and spend-control data where both platforms participate in spend processes. Workday Expenses → Martini → Coupa Exchange approved expense and spend-related data through confirmed tenant endpoints, using canonical mappings, status translation, and reconciliation checkpoints.
Microsoft Power BI Provide curated expense data for reporting, audit, and management analysis. Workday Expenses → Martini → Microsoft Power BI Retrieve Workday reports or API data, flatten report and line structures, apply privacy and business filters, and deliver curated data through an approved reporting or storage layer.
Amazon S3 Store exported expense reports, reconciliation files, or approved receipt-related files for controlled downstream processing. Workday Expenses → Martini → Amazon S3 Schedule a Workday report, EIB, or API extraction, transform the output into the required file format, and write it to S3 with controlled naming, metadata, and retry handling.

How to build a Workday Expenses integration in Martini

Objective

Configure tenant-specific Workday endpoints, API versions, credentials, scopes, and permissions without embedding secrets in workflow logic.

Instructions in Martini

  • Select REST or SOAP based on the confirmed tenant resource and operation
  • Store OAuth, Integration System User, SOAP, and endpoint settings in environment configuration or secrets
  • Confirm Workday domain security and business-process permissions

Objective

Select an event, scheduled, report, EIB, or API-led trigger that matches the tenant capability and synchronization requirement.

Instructions in Martini

  • Use a scheduler for incremental polling when general expense webhooks are unavailable
  • Use a configured outbound notification only after tenant support is verified
  • Define overlap windows and checkpoint rules for late-arriving changes

Objective

Obtain the required Expense Reports, lines, items, workers, card transactions, or report outputs efficiently and consistently.

Instructions in Martini

  • Request bounded date or status windows
  • Follow pagination and retrieve related details only when required
  • Use reports or EIB for suitable large or file-oriented extracts

Objective

Coordinate retrieval, enrichment, validation, target calls, state management, and exception handling in a maintainable Martini workflow.

Instructions in Martini

  • Separate extraction, transformation, validation, delivery, and checkpoint stages
  • Use conditional routing for approval and reimbursement lifecycle states
  • Record Workday identifiers, workflow runs, and target references

Objective

Transform Workday structures into a canonical or target model while preserving financial accuracy and audit context.

Instructions in Martini

  • Map Expense Report Lines, worktags, currencies, tax, workers, and statuses explicitly
  • Validate totals, accounting dimensions, required fields, and effective dates
  • Handle optional fields and tenant-specific schema differences defensively

Objective

Write validated expense data, statuses, exceptions, or files to the target application or controlled API consumer.

Instructions in Martini

  • Apply idempotency checks before creating target transactions
  • Use target-specific mappings and correlation identifiers
  • Treat receipt binaries as a separate capability when required

Common Workday Expenses data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
Expense ReportsSynchronize submitted, approved, rejected, paid, or accounting-related expense reports with downstream systems.NetSuite, Oracle Fusion Cloud ERP, SAP Concur, Salesforce, Power BIMartini retrieves reports incrementally, obtains related lines, filters by lifecycle status, validates totals, maps fields, and stores processing checkpoints.
Expense ItemsRepresent individual meals, mileage, lodging, travel, and other reimbursable expenses.NetSuite, Oracle Fusion Cloud ERP, SAP Concur, reporting storesMartini maps item types, amounts, currencies, dates, tax, worktags, and receipt references into the target model.
Expense Credit Card TransactionsReconcile corporate-card or purchasing-card activity with Expense Reports and Expense Report Lines.SAP Concur, NetSuite, ServiceNow, reporting platformsMartini matches stable identifiers and amounts, detects unmatched or duplicate transactions, and routes exceptions for review.
Expense Report LinesCarry detailed amounts, worktags, tax information, payment information, and accounting distributions.NetSuite, Oracle Fusion Cloud ERP, Power BI, Amazon S3Martini flattens nested lines, validates accounting dimensions and totals, and transforms distributions into target posting structures.
WorkersAssociate expense reports, submitters, approvers, and card transactions with employees or contingent workers.Salesforce, ServiceNow, ERP platforms, reporting storesMartini retrieves permitted worker attributes, applies effective-date rules, and minimizes sensitive fields before enrichment or synchronization.
Spend AuthorizationsRelate pre-approved spending requests to subsequent expense activity where supported by the tenant.Coupa, ERP platforms, reporting storesMartini uses confirmed tenant operations to correlate authorization identifiers, validate policy relationships, and preserve audit references.

Authentication and security considerations

Tenant-specific authentication

Workday REST access may use OAuth 2.0 with tenant-specific clients and scopes. Selected integration scenarios may use an Integration System User and Basic Authentication, while SOAP services use Workday-supported SOAP security patterns.

Authorization and data protection

Permissions depend on Workday domain security policies, business-process permissions, report permissions, and enabled resources. Store credentials, tokens, endpoints, and environment settings in Martini secrets or secure configuration.

  • Limit access to required Workday domains and operations.
  • Protect employee, financial, card, travel, and receipt data.
  • Do not log credentials, tokens, receipt contents, or unnecessary sensitive fields.

Operational considerations for Workday Expenses integrations

Reliability and scale

Use pagination, bounded date windows, checkpoints, and overlap periods for incremental synchronization. For larger extracts, evaluate reports, EIB, or batch mechanisms instead of repeated individual calls.

Financial and lifecycle controls

Define eligible Expense Report statuses and handle corrections, rejections, payment, currency, tax, rounding, worktags, and accounting distributions explicitly. Use idempotency checks before downstream posting.

Tenant and schema variation

Workday endpoints, API versions, fields, WSDLs, report columns, permissions, and attachment behavior vary by tenant. Test against the target environment, monitor schema changes, and classify authorization, validation, throttling, and transient failures separately.

Audit and monitoring

Record correlation information, Workday identifiers, workflow run IDs, timestamps, response status, and target references. Apply bounded concurrency, exponential backoff, and operational monitoring for long-running or failed exchanges.

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

Orchestrate more than a single API call

Workday Expenses integrations often require related objects, lifecycle rules, accounting validation, pagination, status translation, and target-system reconciliation. Martini brings these concerns into reusable workflows rather than scattering them across scripts.

Keep integrations maintainable

Martini separates secure configuration, API consumption, mappings, business rules, error handling, and checkpoints. The same patterns can support REST, SOAP, reports, EIB, and controlled API façades as tenant requirements change.

Improve operational control

  • Centralize retries, idempotency, validation, and exception routing.
  • Expose stable APIs without sharing Workday credentials or tenant-specific details.
  • Support scheduled, API-led, batch, and verified event-driven processing in one integration platform.

Frequently asked questions

How can Workday Expenses be integrated with enterprise systems?

Workday Expenses can be integrated through tenant-configured REST APIs, Workday Web Services using SOAP, reports-as-a-service, Enterprise Interface Builder, and approved file or outbound integration mechanisms. Scheduled incremental synchronization is appropriate when a suitable event or notification mechanism is not available.

Can Martini integrate with Workday Expenses?

Yes. Martini can consume Workday REST APIs and SOAP services, orchestrate scheduled workflows, process report or EIB outputs, transform Workday Expenses data, validate business rules, and expose controlled APIs for downstream applications. No native Martini Workday connector is documented in the supplied materials.

Do I need a connector to integrate Workday Expenses with Martini?

No. A dedicated Workday Expenses connector is not required. Martini can use Workday's confirmed native integration mechanisms, including REST APIs, SOAP services, reports, EIB, tenant-supported files, and configured authentication methods.

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

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

Should an integration use Workday REST APIs or SOAP services?

Use REST when the required Expense Reports, Expense Items, Workers, or related operation is available and enabled in the tenant. Use SOAP when the needed operation is exposed through Workday Web Services, an existing WSDL-based integration must be retained, or the tenant's supported implementation is SOAP-based.

Does Workday Expenses provide webhooks or event notifications?

A general Workday Expenses webhook API was not confirmed. Workday event and outbound integration options depend on the tenant, business process, and integration configuration. Martini can use a verified notification mechanism or fall back to scheduled incremental polling with state tracking.

How does Martini synchronize and transform Workday expense data?

Martini retrieves bounded and paginated data, optionally enriches it with related Workers or reference data, maps Workday objects to a canonical or target model, validates statuses, currencies, totals, and accounting dimensions, and records checkpoints keyed by stable Workday identifiers.

How are errors, retries, and duplicates handled?

A Martini workflow can distinguish authorization, validation, throttling, transport, and business-process errors; retry eligible transient failures with backoff; and route permanent exceptions for review. Idempotency keys, Workday identifiers, target references, overlap windows, and checkpoints help prevent duplicate processing.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Workday Expenses with your enterprise systems

Use Martini to build secure, maintainable Workday Expenses integrations across REST, SOAP, reports, EIB, scheduled workflows, and downstream APIs.

EXPLORE MARTINI
BOOK A DEMO