.png)
Workday Financial Management Integration Guide
Integrate Workday Financial Management with enterprise applications through REST APIs, SOAP Web Services, reports, files, and configured outbound integration processes.
Workday Financial Management integration options at a glance
Workday Financial Management supports REST APIs for selected resources, Workday Web Services for broad SOAP-based business-object coverage, and integration technologies such as Enterprise Interface Builder, Report-as-a-Service, and structured file exchange. RaaS can provide XML, JSON, or CSV extracts for reconciliation and incremental synchronization. Outbound event and callback patterns are available for selected business processes and tenant configurations, but generic webhooks should not be assumed. Martini can securely consume REST and SOAP endpoints, orchestrate scheduled or callback-driven workflows, transform files and reports, track asynchronous submissions, and expose APIs for controlled inbound journal or master-data processes.
| Integration point | Supported by Workday Financial Management? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Selected Workday Financial Management resources and operations, including retrieval and supported transactional processing. Coverage varies by object, release, tenant, and permissions. | Martini can consume Workday REST endpoints, manage authentication, map payloads, apply business rules, and expose normalized APIs. |
| SOAP APIs | Yes | Workday Web Services provide broad business-object and operation coverage, including Financial Management capabilities that may not be available through REST. | Martini can consume WSDL-described services, construct XML requests, transform SOAP responses, and handle SOAP faults. |
| Webhooks / outbound callbacks | Limited | Workday supports outbound and event-based integration patterns for selected business processes and configured integrations; generic object-level webhooks should not be assumed. | Martini can receive a documented callback or outbound delivery through an API or webhook workflow where the Workday configuration supports it. |
| Bulk / async / batch processing | Yes | EIB, reports, SOAP operations, and other Workday integration technologies support high-volume or asynchronous supplier, invoice, journal, and payment exchanges. | Martini can submit batches, persist submission identifiers, poll for completion, separate rejected records, and retry transient failures. |
| File-based integrations | Yes | EIB and related Workday integration processes support structured inbound and outbound file exchange, including tenant-configured delivery mechanisms such as SFTP. | Martini can validate, transform, deliver, archive, and reconcile Workday files within scheduled or event-driven workflows. |
| Report-as-a-Service | Yes | RaaS can expose configured Workday reports as XML, JSON, or CSV for extracts, reconciliation, and incremental synchronization. | Martini can invoke report endpoints, supply prompts, validate schemas, transform results, and persist watermarks. |
| File and attachment operations | Limited | Some business objects expose document or attachment operations, but availability depends on the object, API version, tenant, and permissions. | Martini can process supported attachment or document payloads after the specific Workday operation has been verified. |
| Database / analytics access | Limited | Direct customer database access is not the normal transactional integration method; governed reports, RaaS, and supported analytics or extraction products are preferred. | Martini can consume approved report or extract endpoints and load downstream databases, but should not connect directly to Workday's underlying platform database. |
| Authentication | Yes | Workday supports OAuth 2.0 and integration-user security using tenant-specific endpoints, scopes, security groups, and domain permissions; Basic Authentication remains relevant for some SOAP configurations. | Martini can store tenant URLs and credentials in protected configuration, request and refresh tokens, and use least-privilege integration identities. |
How Workday Financial Management exposes data and business events
Workday REST APIs
Workday provides REST APIs for selected Financial Management resources and operations. Availability is not uniform across objects, releases, or tenants, so the required resource and operation should be confirmed before design.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates against the tenant-specific Workday endpoint, retrieves or submits resource data, handles pagination and status responses, maps the payload to a canonical model, and writes the result to the target system.
Implementation sequence
Workday SOAP Web Services
Workday Web Services expose SOAP operations for a broad range of business objects. SOAP remains important when a Financial Management capability is not available through REST or when an existing governed WSDL integration must be retained.
Martini implementation pattern
Martini implementation pattern: consume the documented WSDL, configure the Workday authentication and XML request structure, construct the SOAP message, transform the response, and distinguish SOAP faults from business-process errors.
Implementation sequence
Report-as-a-Service
Workday reports can be exposed through RaaS using XML, JSON, or CSV output. RaaS is report-driven rather than a transactional API, and report columns, prompts, filters, security, and pagination form part of the integration contract.
Martini implementation pattern
Martini implementation pattern: schedule a report retrieval with prompts or an incremental filter, validate the returned format and schema, transform the rows into canonical objects, load the destination, and advance the watermark only after successful processing.
Implementation sequence
EIB and file exchanges
Workday Enterprise Interface Builder and related integration processes support structured inbound and outbound files. Delivery mechanisms and file formats depend on the tenant configuration and integration design.
Martini implementation pattern
Martini implementation pattern: receive or retrieve a Workday file through the configured exchange, validate filenames and content, transform records, deliver the result to the target, archive the source and outcome, and isolate rejected records.
Implementation sequence
Workday outbound events
Workday supports outbound integration and event-based patterns for selected business processes and configurations. A general-purpose webhook for every Financial Management object or event should not be assumed.
Martini implementation pattern
Martini implementation pattern: expose a controlled Martini endpoint or receive a documented outbound delivery where configured; otherwise use scheduled REST, SOAP, or RaaS polling with a stable watermark. The workflow validates the notification and retrieves the authoritative Workday data before writing downstream.
Implementation sequence
Common Workday Financial Management integration patterns
Pattern 1: Synchronize suppliers and supplier invoices
When to use this pattern
Use this pattern when procurement, accounts-payable, or vendor-management applications need current Workday Suppliers and Supplier Invoices. Scheduled retrieval, RaaS, SOAP, REST, or configured file delivery can be selected based on the tenant and object coverage.
Integration direction
Example Mapping
| Workday Financial Management Field | Canonical Field | Target Field |
|---|---|---|
| Supplier ID | supplier.externalId | supplierNumber |
| Supplier Invoice Number | invoice.externalId | invoiceNumber |
| Invoice Status | invoice.status | status |
| Payment Terms | invoice.paymentTerms | paymentTerms |
Martini implementation pattern
A scheduled Martini workflow retrieves changed suppliers and invoices using a documented filter, report prompt, or file window. It validates supplier identifiers, currencies, payment terms, and invoice status, maps the records into the target schema, upserts using stable identifiers, stores the watermark only after successful delivery, and routes rejected records to an exception workflow.
Martini capabilities used
- workflows
- scheduler triggers
- API consumption
- file processing
- data mapping
- business rules
- error handling
Pattern 2: Synchronize customer invoices and payments
When to use this pattern
Use this pattern when customer-facing applications need Workday invoice status, due dates, amounts, currencies, or payment information for account management and customer communications.
Integration direction
Example Mapping
| Workday Financial Management Field | Canonical Field | Target Field |
|---|---|---|
| Customer Reference | customer.externalId | Account.ExternalId |
| Invoice Number | invoice.externalId | InvoiceNumber |
| Due Date | invoice.dueDate | DueDate |
| Payment Status | payment.status | PaymentStatus |
Martini implementation pattern
Martini retrieves incremental Customer Invoices and Payments through REST, SOAP, RaaS, or a supported outbound process. The workflow maps financial values and statuses, uses invoice or payment identifiers as idempotency keys, enriches target records with customer references, and separates technical failures from business-process rejections.
Martini capabilities used
- scheduled workflows
- API consumption
- incremental synchronization
- data mapping
- idempotency rules
- exception handling
Pattern 3: Submit and reconcile accounting journals
When to use this pattern
Use this pattern when a source application needs to submit Accounting Journals to Workday and receive controlled processing outcomes. It is appropriate for governed journal imports with validation and reconciliation requirements.
Integration direction
Example Mapping
| Workday Financial Management Field | Canonical Field | Target Field |
|---|---|---|
| Journal ID | journal.externalId | Journal Reference ID |
| Ledger Account | journal.lines[].ledgerAccount | Ledger Account |
| Company | journal.company | Company |
| Worktag | journal.lines[].worktag | Worktag |
Martini implementation pattern
A Martini API receives the source journal, validates required ledger, company, worktag, currency, balancing, and duplicate conditions, and transforms it into the applicable Workday REST or SOAP request. The workflow stores the Workday submission identifier, polls or receives the documented outcome, and distinguishes accepted, pending, completed, and rejected states.
Martini capabilities used
- API exposure
- workflow orchestration
- XML and JSON transformation
- validation
- business rules
- asynchronous processing
- error handling
Pattern 4: Load Workday financial extracts into a data platform
When to use this pattern
Use this pattern for reconciliation, historical reporting, and analytics workloads that require governed Workday extracts rather than transactional API access.
Integration direction
Example Mapping
| Workday Financial Management Field | Canonical Field | Target Field |
|---|---|---|
| Workday Company | company.externalId | company_id |
| Accounting Journal ID | journal.externalId | journal_id |
| Transaction Date | transaction.date | transaction_date |
| Amount | transaction.amount | amount |
Martini implementation pattern
A scheduled workflow invokes a Workday RaaS report with a prompt or last-modified watermark, validates XML, JSON, or CSV output, transforms rows into warehouse structures, and loads bounded batches. Martini records checksums or stable identifiers, reconciles counts and totals, archives processing metadata, and advances the watermark only after successful loading.
Martini capabilities used
- scheduler triggers
- API consumption
- XML and JSON handling
- file processing
- data mapping
- batch workflows
- monitoring
Applications commonly integrated with Workday Financial Management
Workday Financial Management can participate in broader enterprise processes involving customer management, procurement, reporting, service operations, and other financial platforms. These are implementation scenarios rather than claims of native Workday relationships; supported objects, direction, and business rules depend on the tenant and enabled modules.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customer, account, invoice, payment, or financial-status information for sales and account-management processes. | Workday Financial Management → Martini → Salesforce | Use scheduled REST, SOAP, or RaaS retrieval from Workday, map Customers, Customer Invoices, and Payments into Salesforce fields, and apply identifier and status rules before upserting data. |
| ServiceNow | Provide supplier, financial, procurement, or approval-related information to support service workflows and controlled requests. | Workday Financial Management → Martini → ServiceNow | Orchestrate Workday extracts or API calls, transform approved financial and supplier data, send it to ServiceNow, and return selected request or approval outcomes through a governed Martini API or workflow. |
| NetSuite | Exchange suppliers, customers, invoices, payments, and journals in organizations operating multiple financial platforms. | Workday Financial Management → Martini → NetSuite | Create bidirectional workflows with stable object identifiers, validate company and ledger semantics, map financial payloads, and use processing ledgers to prevent duplicate submissions. |
| Coupa | Synchronize suppliers, invoices, purchase-related financial data, and payment status between procurement and financial-management processes. | Workday Financial Management → Martini → Coupa | Use Workday REST, SOAP, RaaS, or file exchanges as appropriate, validate supplier and invoice references, transform procurement payloads, and route rejected records to exception handling. |
| SAP S/4HANA | Exchange accounting, supplier, customer, journal, and payment information across multiple enterprise platforms. | Workday Financial Management → Martini → SAP S/4HANA | Implement separate inbound and outbound workflows for master and transaction data, apply ledger and worktag validation, and track asynchronous batch or business-process status. |
| Snowflake | Load governed Workday financial extracts for analytics, reconciliation, and historical reporting. | Workday Financial Management → Martini → Snowflake | Schedule RaaS or supported extract retrieval, validate XML, JSON, or CSV schemas, transform data into warehouse structures, and reconcile counts and totals before completion. |
| Microsoft Power BI | Provide governed financial data for dashboards, management reporting, and reconciliation analysis. | Workday Financial Management → Martini → Microsoft Power BI | Deliver Workday extracts through a reporting data store or semantic-model ingestion process, with Martini handling prompts, incremental windows, transformations, and delivery monitoring. |
| Jira | Create and track work items for invoice exceptions, integration failures, or finance close activities. | Workday Financial Management → Martini → Jira | Detect rejected or failed Workday transactions, enrich them with correlation and business-process identifiers, create Jira issues, and synchronize issue status when operational follow-up is complete. |
How to build a Workday Financial Management integration in Martini
Objective
Establish tenant-specific Workday connectivity with credentials, endpoints, scopes, and permissions kept outside workflow logic.
Instructions in Martini
- Store tenant URLs, client identifiers, secrets, and environment values in protected Martini configuration
- Choose OAuth 2.0 or the approved integration-user authentication method
- Use separate sandbox and production credentials
- Grant only the Workday security domains and operations required
Objective
Select a trigger that matches the Workday capability and synchronization requirement.
Instructions in Martini
- Use a scheduler for REST, SOAP, RaaS, or report polling
- Receive a documented outbound callback only for configured Workday business processes
- Use a Martini API for controlled inbound journal or master-data submissions
- Use file arrival or delivery processing for EIB exchanges
Objective
Obtain the authoritative Workday data while respecting pagination, report prompts, file boundaries, and asynchronous status.
Instructions in Martini
- Retrieve changed data with supported filters or report prompts
- Handle paginated REST collections and bounded report windows
- Validate callback or file metadata before processing
- Persist submission identifiers for asynchronous operations
Objective
Coordinate Workday calls, target-system operations, enrichment, and state transitions in a maintainable Martini workflow.
Instructions in Martini
- Separate retrieval, validation, transformation, delivery, and status tracking stages
- Use reusable services or workflow logic for common authentication and normalization
- Track technical and business-process states separately
- Persist checkpoints only after downstream processing succeeds
Objective
Convert Workday-specific structures into a canonical or target model without losing identifiers or financial semantics.
Instructions in Martini
- Map identifiers, organizations, companies, ledgers, worktags, currencies, and effective dates
- Validate required fields, balancing, decimal precision, and status values
- Transform XML, JSON, CSV, or structured file payloads
- Preserve source references for reconciliation
Objective
Apply tenant- and process-specific controls before writing or submitting financial data.
Instructions in Martini
- Detect duplicate invoices, payments, journals, files, and asynchronous submissions
- Validate supplier, customer, company, ledger-account, and worktag relationships
- Route approval, validation, or accounting failures to an exception path
- Use overlap windows and stable identifiers for incremental synchronization
Common Workday Financial Management data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Suppliers | Synchronize supplier master data, identifiers, payment terms, and supplier status. | Coupa, NetSuite, SAP S/4HANA, ServiceNow | Martini retrieves or receives the object through REST, SOAP, RaaS, or files, validates required identifiers and security scope, and performs idempotent target upserts. |
| Customers | Exchange customer master data for billing, account management, and financial-status processes. | Salesforce, NetSuite, SAP S/4HANA | Martini maps Workday identifiers, organizations, currencies, and configurable fields into the target model while preserving source references. |
| Customer Invoices | Synchronize invoice numbers, customer references, amounts, currencies, due dates, and statuses. | Salesforce, NetSuite, Snowflake, Microsoft Power BI | Martini retrieves incremental changes, validates financial semantics, applies idempotency keys, and routes rejected invoices to an exception workflow. |
| Supplier Invoices | Exchange accounts-payable invoice details, status, supplier references, and payment-related information. | Coupa, NetSuite, SAP S/4HANA, Snowflake | Martini validates supplier and company relationships, maps invoice payloads, tracks asynchronous processing, and records technical and business-process outcomes. |
| Payments | Synchronize payment status, amounts, references, and settlement information. | Salesforce, NetSuite, Snowflake, Microsoft Power BI | Martini uses stable Workday identifiers, transforms payment status and currency data, and prevents duplicate downstream updates during retries. |
| Accounting Journals | Submit, monitor, reconcile, or extract journal batches and accounting results. | NetSuite, SAP S/4HANA, Snowflake | Martini validates ledger accounts, companies, worktags, balancing, and currencies, submits through the applicable REST or SOAP operation, and tracks pending, accepted, completed, and rejected states. |
Authentication and security considerations
Tenant-specific security
Workday endpoints, API versions, security domains, and enabled operations vary by tenant. Store tenant URLs, OAuth client details, integration-user credentials, tokens, and environment configuration in protected Martini configuration rather than workflow definitions.
Least-privilege access
- Use a dedicated Integration System User or OAuth client for each integration boundary where practical.
- Grant only the required Workday domain permissions, scopes, business-process permissions, and organization access.
- Separate sandbox and production credentials and rotate secrets according to organizational policy.
- Use OAuth 2.0 where available; retain Basic Authentication only for approved SOAP or integration configurations.
Operational considerations for Workday Financial Management integrations
Volume and synchronization
- Handle REST pagination, report prompts, bounded file sizes, and incremental date or watermark windows.
- Persist a watermark only after successful downstream processing and use overlap windows for late-arriving changes.
- Use stable supplier, customer, invoice, payment, journal, file, or submission identifiers for idempotency.
Business-process status
A technically accepted request may remain pending or later fail business validation, approval, or accounting. Track Workday transaction and batch identifiers and distinguish accepted, pending, completed, and rejected states.
Schema and error governance
- Capture HTTP errors, SOAP faults, validation failures, and business-process errors separately.
- Treat RaaS report columns, calculated fields, prompts, filters, and security as part of the integration contract.
- Version and test REST schemas, WSDLs, report outputs, file layouts, and custom Worktags before production changes.
- Preserve correlation identifiers and reconciliation metadata without logging credentials or unnecessary financial data.
Why use Martini instead of scripts or point-to-point integrations?
One orchestration layer
Martini coordinates Workday REST, SOAP, RaaS, file, and configured outbound processes with target applications in workflows that can be reused and maintained as integration requirements evolve.
Controlled transformation
Mappings, validation, business rules, XML and JSON handling, file processing, watermarks, and idempotency controls can be implemented explicitly instead of being duplicated across point-to-point scripts.
Operational reliability
- Separate technical failures from Workday business-process outcomes.
- Persist checkpoints and submission identifiers for safe retries and asynchronous processing.
- Expose controlled APIs for inbound processes while keeping authentication and secrets in protected configuration.
- Centralize monitoring, exception routing, reconciliation, and deployment configuration.
Frequently asked questions
Workday Financial Management can be integrated through REST APIs, Workday Web Services using SOAP, Report-as-a-Service, Enterprise Interface Builder and structured file exchanges, and selected outbound or event-based integration processes. The appropriate mechanism depends on the object, operation, tenant configuration, security permissions, and whether the process is transactional, extract-based, or asynchronous.
Yes. Martini can consume documented Workday REST APIs and SOAP Web Services, orchestrate RaaS, EIB, and file-based exchanges, process configured outbound deliveries, expose APIs for inbound processes, and map Workday financial data to enterprise applications.
No. A dedicated Workday connector is not required. Martini can use Workday's native REST APIs, SOAP services, reports, files, configured callbacks, and authentication methods through workflows and APIs.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday Financial 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 subscriptions, usage, and deployment model.
Use REST when the required resource and operation are available and meet the integration requirements. Use Workday Web Services when the required Financial Management capability is exposed through SOAP, when the WSDL provides broader business-object coverage, or when an existing governed SOAP integration must be retained.
No general-purpose coverage should be assumed. Workday supports outbound and event-based integration patterns for selected business processes and configurations. Martini can receive a documented callback or outbound delivery where available; otherwise, scheduled REST, SOAP, or RaaS polling with a watermark is the safer pattern.
Use supported REST filters, RaaS prompts, last-updated indicators, or configured outbound processes. Martini can persist a successful watermark, use overlap windows for late-arriving changes, and apply stable Workday identifiers to make reruns and downstream writes idempotent.
Yes. Martini can expose a controlled API that accepts normalized customer, supplier, journal, or other approved payloads, validates and transforms them, and invokes the applicable Workday REST or SOAP operation. The façade can centralize authentication, business rules, status tracking, and error handling.
Related Martini documentation
APIs
Connect Workday Financial Management with your enterprise systems
Use Martini to build governed Workday Financial Management integrations across REST APIs, SOAP Web Services, reports, files, and configured outbound processes.