.png)
Ivalua Integration Guide
Connect Ivalua procurement and spend processes with enterprise systems through REST APIs, web services, files, scheduled workflows, and selected outbound notifications.
Ivalua integration options at a glance
Ivalua supports enterprise integration through REST APIs and, in some implementations, SOAP-style web services. File-based imports and exports are also relevant for supplier data, purchasing documents, invoices, catalogs, and bulk processing. Selected processes may expose outbound notifications or callback-style integrations, although universal webhook coverage is not publicly confirmed. Authentication, available objects, pagination, and file-transfer methods must be validated for each tenant. Martini can consume the confirmed Ivalua interfaces, run scheduled or event-driven workflows, transform JSON, XML, and files, apply validation and business rules, and deliver results to ERP, finance, workflow, or supplier-management applications.
| Integration point | Supported by Ivalua? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Ivalua positions APIs as an enterprise integration mechanism for procurement, supplier, contract, requisition, purchase-order, and invoice processes. Public documentation does not provide a complete resource or authentication catalog. | Martini can consume tenant-exposed Ivalua REST endpoints, transform responses, apply business rules, and send results to downstream APIs or files. |
| SOAP APIs | Limited | SOAP-style enterprise web services have been used in some Ivalua implementations, but current availability depends on tenant, version, modules, and architecture. | Martini can consume an Ivalua SOAP service when the tenant supplies a supported WSDL and authentication details. |
| Webhooks / outbound callbacks | Limited | Selected processes may use outbound notifications, callbacks, or an intermediary integration layer. Universal webhook coverage for all objects and events is not confirmed. | Martini can expose an HTTP API or receive webhook-style requests, then retrieve the current Ivalua object and process it idempotently. |
| Bulk / async / batch APIs | Limited | Bulk processing is relevant for suppliers, catalogs, purchasing documents, invoices, and historical loads, although no universal public bulk or asynchronous API specification was verified. | Martini can orchestrate batch workflows with scheduling, pagination, checkpoints, validation, reconciliation, and retries. |
| File import/export | Yes | File exchanges are relevant to supplier master data, purchasing documents, invoices, and other bulk processes. Formats, schedules, and transfer endpoints are tenant-specific. | Martini can process CSV, XML, and other confirmed files, transform them, and deliver or consume them through supported enterprise file-transfer workflows. |
| Attachment and document handling | Limited | Ivalua processes may include contracts, supplier certificates, sourcing documents, purchase-order files, and invoice attachments. A universal public attachment API was not verified. | Martini can transfer attachments through confirmed API or file operations and apply controlled retention and error handling. |
| Authentication | Limited | Ivalua supports enterprise identity and access controls, but public sources do not confirm a complete API authentication model. OAuth, service-account, token, or legacy web-service options must be verified per tenant. | Martini stores confirmed credentials, certificates, and tokens in environment-specific secrets and uses them in workflows with least-privilege access. |
| Database access | Not confirmed | Direct production database access was not verified and should not be assumed. Supported APIs, web services, and exports are preferred. | Martini can use databases for checkpoints, reconciliation, or canonical integration state without requiring direct access to Ivalua’s production database. |
How Ivalua exposes data and business events
Ivalua REST APIs
Ivalua publicly positions APIs as part of its enterprise integration capabilities. The exact resources, operations, authentication flow, pagination model, and rate limits must be confirmed for the customer tenant and enabled modules.
Martini implementation pattern
Martini implementation pattern: a workflow calls the tenant’s confirmed Ivalua REST endpoint, retrieves the current object or page, maps it into a canonical model, applies validation and business rules, and writes to the target system with durable processing state.
Implementation sequence
Ivalua SOAP Services
Some Ivalua implementations use SOAP-style enterprise web services. Availability and scope are tenant-specific, so a supported WSDL, operations list, and authentication configuration should be obtained before implementation.
Martini implementation pattern
Martini implementation pattern: configure a SOAP-consuming workflow from the supplied WSDL, construct the required request, transform the response, and route SOAP faults or validation failures through workflow error handling.
Implementation sequence
Ivalua File Exchanges
File-based imports and exports are relevant to supplier data, purchasing documents, invoices, catalogs, and bulk or historical processing. Formats, transfer mechanisms, schedules, and validation rules depend on the implementation.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow receives or retrieves an approved file, validates its structure, processes rows or documents, maps them to a target format, and records file-level and item-level reconciliation results.
Implementation sequence
Ivalua Outbound Notifications
Selected Ivalua processes may use outbound notifications, callbacks, or an intermediary integration layer, but public material does not verify universal webhook coverage across objects and events.
Martini implementation pattern
Martini implementation pattern: expose a controlled HTTP endpoint, validate the incoming notification, acknowledge appropriately, retrieve the authoritative Ivalua object when necessary, and process it through an idempotent workflow.
Implementation sequence
Common Ivalua integration patterns
Pattern 1: Synchronize suppliers to enterprise applications
When to use this pattern
Use this pattern when Ivalua is the source for supplier master, qualification, classification, or risk information and downstream applications need controlled, repeatable updates. A scheduled export, REST retrieval, or selected notification can initiate processing.
Integration direction
Example Mapping
| Ivalua Field | Canonical Field | Target Field |
|---|---|---|
| Supplier ID | supplier.externalId | Business Partner External ID |
| Legal Name | supplier.legalName | Business Partner Name |
| Supplier Status | supplier.status | Supplier Lifecycle Status |
| Tax Identifier | supplier.taxId | Tax Number |
Martini implementation pattern
Martini retrieves or receives changed Suppliers, validates legal entity, tax, address, and status fields, and performs an idempotent upsert in SAP S/4HANA. The workflow maintains a modification watermark with an overlap window, records source and target identifiers, and routes incomplete suppliers or transient target failures to separate operational handling.
Martini capabilities used
- scheduled workflows
- API consumption
- file processing
- data mapping
- validation
- business rules
- idempotent upserts
- error handling
Pattern 2: Transmit approved purchase orders to an ERP
When to use this pattern
Use this pattern when approved or released Ivalua Purchase Orders must be created or updated in an ERP without duplicating documents after retries or revisions.
Integration direction
Example Mapping
| Ivalua Field | Canonical Field | Target Field |
|---|---|---|
| Purchase Order ID | purchaseOrder.externalId | Purchase Order Reference |
| Supplier ID | supplier.externalId | Supplier Business Partner |
| Currency | purchaseOrder.currency | Document Currency |
| Purchase Order Lines | purchaseOrder.lines | Item Lines |
Martini implementation pattern
A Martini workflow retrieves an exportable Purchase Order after its configured approval state, normalizes header and line fields, validates supplier, cost-center, item, tax, unit, and amount values, and calls the ERP API. It uses the Ivalua identifier, version, and target identifier for duplicate prevention, returns downstream status to an integration store, and distinguishes validation failures from retryable transport errors.
Martini capabilities used
- workflow orchestration
- REST API consumption
- JSON and XML transformation
- data mapping
- business rules
- idempotency
- retry handling
- reconciliation
Pattern 3: Integrate invoices and matching status
When to use this pattern
Use this pattern when Ivalua Invoices and matching or approval statuses must be exchanged with an ERP or accounts-payable process, including controlled handling of invoice attachments where the tenant supports them.
Integration direction
Example Mapping
| Ivalua Field | Canonical Field | Target Field |
|---|---|---|
| Invoice ID | invoice.externalId | Invoice Source Identifier |
| Supplier Invoice Number | invoice.number | Supplier Invoice Number |
| Purchase Order Reference | invoice.purchaseOrderId | Purchase Order Reference |
| Matching Status | invoice.matchingStatus | Validation or Hold Status |
Martini implementation pattern
Martini consumes invoice API responses or batch files, validates invoice identity, supplier, purchase-order reference, tax, currency, and line totals, and maps matching and approval statuses to Oracle Fusion Cloud ERP. The workflow preserves version timestamps, attachment references where supported, correlation data, and retry state so a retried document does not create a second invoice.
Martini capabilities used
- file and API integration
- data validation
- mapping and transformation
- business rules
- attachment handling where confirmed
- duplicate prevention
- error routing
Pattern 4: Distribute contracts and supplier-risk changes
When to use this pattern
Use this pattern when approved Contracts or supplier qualification and risk changes from Ivalua need to reach legal, compliance, operational, or case-management applications.
Integration direction
Example Mapping
| Ivalua Field | Canonical Field | Target Field |
|---|---|---|
| Contract ID | contract.externalId | External Contract ID |
| Contract Status | contract.status | Case or Contract Status |
| Supplier Risk Rating | supplier.riskRating | Risk Rating |
| Approval Date | contract.approvalDate | Approved Date |
Martini implementation pattern
Martini filters Ivalua objects by approval state, module, supplier classification, or risk change, maps them to the target application, and creates or updates the appropriate case or contract reference. Routing rules prevent irrelevant data from being distributed, while error handling records the source identifier and supports replay after target correction.
Martini capabilities used
- event or schedule triggers
- API consumption
- conditional routing
- data mapping
- business rules
- workflow orchestration
- replay and error handling
Applications commonly integrated with Ivalua
Ivalua commonly participates in enterprise landscapes where procurement, finance, HR, service management, and commercial applications exchange supplier, purchasing, contract, and invoice information. The exact objects and direction depend on the tenant configuration and implementation.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize suppliers, purchase orders, invoice status, accounting data, and payment-related information across procurement and ERP processes. | Ivalua → Martini → SAP S/4HANA | Use scheduled or event-triggered workflows to retrieve approved Ivalua objects, validate and map headers and lines, upsert SAP documents, and store cross-system identifiers and retry state. |
| Oracle Fusion Cloud ERP | Exchange supplier, purchasing, invoice, accounting, and payment information between Ivalua and Oracle financial processes. | Ivalua → Martini → Oracle Fusion Cloud ERP | Consume Ivalua APIs or files, normalize supplier and transaction data, apply accounting rules, call Oracle APIs, and reconcile accepted and rejected documents. |
| Workday | Exchange organizations, cost centers, supplier references, and selected procurement or financial data. | Workday → Martini → Ivalua | Schedule Workday reference-data extraction, transform organizational structures into Ivalua-compatible payloads or files, validate required dimensions, and report rejected records. |
| Salesforce | Coordinate selected supplier, account, contract, sourcing, or commercial information where procurement and customer processes overlap. | Salesforce → Martini → Ivalua | Expose or consume controlled APIs, map Salesforce identifiers to Ivalua objects, apply routing rules, and synchronize only approved fields and statuses. |
| ServiceNow | Connect procurement requests, approvals, supplier issues, and service or asset purchasing processes. | ServiceNow → Martini → Ivalua | Receive ServiceNow requests or retrieve Ivalua statuses, transform request and approval data, invoke the target API, and return correlation and exception information. |
| Coupa | Exchange supplier, contract, catalog, requisition, purchase-order, or invoice information during coexistence, migration, or specialized process integration. | Ivalua → Martini → Coupa | Run controlled batch or API workflows with canonical procurement mappings, duplicate detection, reconciliation counts, and staged cutover checkpoints. |
| SAP Ariba | Exchange supplier, sourcing, contract, catalog, or purchasing data during procurement-suite coexistence or transition programs. | Ivalua → Martini → SAP Ariba | Process tenant-specific APIs or files, map procurement identifiers and statuses, route module-specific records, and retain source-to-target audit references. |
| Jira | Create and update implementation, supplier-remediation, contract-review, or integration-exception issues. | Ivalua → Martini → Jira | Use Martini rules to create Jira issues for qualifying Ivalua events or failures, include object and correlation identifiers, and synchronize selected status changes back. |
How to build a Ivalua integration in Martini
Objective
Confirm the Ivalua tenant, enabled modules, endpoints, technical identity, permissions, and authentication method for each environment.
Instructions in Martini
- Obtain tenant-specific REST, SOAP, file, or callback details from the Ivalua administrator.
- Use a dedicated least-privilege integration identity.
- Store credentials, certificates, and tokens in Martini environment secrets.
- Validate development, test, and production configuration separately.
Objective
Select the trigger that matches the confirmed Ivalua interface and required latency.
Instructions in Martini
- Use a scheduler for polling, exports, and batch exchanges.
- Use an HTTP trigger for confirmed Ivalua or intermediary callbacks.
- Define the eligible object statuses and change-detection rule.
- Set an overlap window or checkpoint strategy for incremental processing.
Objective
Receive or retrieve the authoritative Ivalua object and preserve enough metadata for traceability.
Instructions in Martini
- Call the confirmed REST or SOAP operation or process the approved file.
- Capture object identifiers, versions, timestamps, response status, and correlation information.
- Handle pagination, continuation markers, and file-level validation according to tenant behavior.
- Retrieve the full object when an event contains only a notification.
Objective
Coordinate validation, transformation, target delivery, state management, and exception paths in a maintainable Martini workflow.
Instructions in Martini
- Separate transport, business validation, mapping, and target-write stages.
- Use reusable services or workflow components for common supplier and document logic.
- Route permanent validation failures separately from transient technical failures.
- Persist checkpoints and source-to-target identifiers.
Objective
Convert Ivalua object structures into the canonical and target models required by downstream applications.
Instructions in Martini
- Map Suppliers, Contracts, Requisitions, Purchase Orders, and Invoices using stable identifiers.
- Transform JSON, XML, CSV, or other confirmed file formats.
- Normalize dates, currencies, units, amounts, statuses, and organization references.
- Validate required fields before creating or updating downstream documents.
Objective
Enforce tenant-specific approval, release, routing, and duplicate-prevention rules before data leaves the workflow.
Instructions in Martini
- Process only configured exportable or approved statuses.
- Use idempotency keys based on Ivalua identifiers and document versions.
- Route supplier, accounting, tax, and purchasing exceptions for review.
- Define behavior for withdrawn, rejected, revised, or cancelled objects.
Common Ivalua data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Suppliers | Synchronize supplier master, qualification, risk, classification, legal-entity, tax, address, and status information. | SAP S/4HANA, Oracle Fusion Cloud ERP, Workday, Salesforce, Coupa, SAP Ariba | Martini validates required supplier fields, maps stable Ivalua identifiers, performs idempotent upserts, and records rejected or incomplete suppliers. |
| Sourcing Events | Distribute RFIs, RFQs, auctions, bids, and related sourcing activity to downstream procurement or reporting processes. | SAP Ariba, Coupa, Salesforce, data platforms | Martini retrieves or processes confirmed event payloads or files, applies module-specific routing, and preserves event identifiers and status history. |
| Contracts | Synchronize contract records, clauses, terms, approvals, lifecycle data, and selected supporting documents. | Salesforce, ServiceNow, Coupa, SAP Ariba, legal and compliance applications | Martini filters approved or relevant contracts, maps lifecycle statuses, transfers confirmed attachments through supported interfaces, and protects sensitive data in logs. |
| Requisitions | Exchange internal requests for goods or services, approval information, cost centers, and accounting dimensions. | SAP S/4HANA, Oracle Fusion Cloud ERP, ServiceNow, Workday | Martini validates organizational and accounting references, applies approval-state rules, and routes accepted or rejected requisitions with correlation data. |
| Purchase Orders | Transmit approved purchasing documents, supplier details, lines, quantities, units, tax, currency, and accounting information. | SAP S/4HANA, Oracle Fusion Cloud ERP, Coupa, SAP Ariba | Martini transforms headers and lines, prevents duplicate creation with an idempotency key, stores downstream identifiers, and retries only transient failures. |
| Invoices | Exchange supplier invoices, lines, purchase-order references, matching and approval statuses, tax amounts, and payment-related information. | SAP S/4HANA, Oracle Fusion Cloud ERP, Coupa, finance and accounts-payable applications | Martini validates invoice identity and references, maps statuses and amounts, handles confirmed attachments, and maintains processing and reconciliation state. |
Authentication and security considerations
Tenant-specific authentication
Ivalua supports enterprise identity and access controls, but a complete public API authentication model was not confirmed. OAuth 2.0, API keys, and exact token flows should not be assumed without tenant documentation. Some legacy or tenant-specific web-service configurations may use Basic Authentication.
Least-privilege integration identities
Use a dedicated technical identity with access limited to the required Ivalua modules, objects, organizations, and operations. SAML-based SSO is primarily an interactive user-authentication mechanism and should not automatically be treated as an API authentication method.
Martini protection
- Store Ivalua credentials, tokens, and certificates in environment-specific Martini secrets.
- Keep supplier, contract, invoice, banking, and sourcing information out of unnecessary logs.
- Validate certificates and protect HTTP endpoints used for callbacks.
- Separate development, test, and production credentials and endpoints.
Operational considerations for Ivalua integrations
Tenant configuration
Confirm base URLs, modules, object operations, custom fields, statuses, file-transfer endpoints, permissions, certificates, and allowlists for each environment.
Pagination and change tracking
Do not assume a common pagination model across Ivalua interfaces. Confirm page limits, cursors or offsets, ordering, modification filters, deleted-object behavior, and time-zone semantics. Use durable watermarks with a controlled overlap.
Reliability and reconciliation
- Use stable Ivalua identifiers and document versions for idempotency.
- Limit concurrency and apply conservative throttling because public rate limits were not verified.
- Use exponential backoff for transient failures and separate validation failures from transport failures.
- Reconcile source counts, successful items, rejected items, retries, downstream identifiers, and synchronization watermarks.
- Test custom fields, configurable statuses, approval transitions, revisions, cancellations, and large attachments before production release.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable orchestration
Scripts and point-to-point interfaces often combine transport, mapping, business rules, and error handling in one implementation. Martini separates these concerns in workflows and reusable integration assets.
Adapt to Ivalua variability
Ivalua tenants can differ in modules, custom fields, statuses, APIs, web services, files, and authentication. Martini provides a controlled place to adapt those differences while preserving canonical mappings and operational state.
Enterprise controls
- Coordinate REST, SOAP, file, callback, and downstream API interactions.
- Apply validation, conditional routing, idempotency, retries, and reconciliation.
- Expose controlled APIs for internal applications where required.
- Use environment-specific secrets, logging, monitoring, and deployment configuration.
Frequently asked questions
Ivalua can integrate through REST APIs, tenant-specific SOAP or web services, file imports and exports, scheduled batch processes, and selected outbound notifications or callbacks. The available objects, authentication model, file-transfer method, and event coverage must be confirmed for the specific Ivalua tenant.
Yes. Martini can integrate with Ivalua by consuming confirmed REST APIs or SOAP services, processing Ivalua files, receiving configured HTTP notifications, and orchestrating scheduled workflows. A native Martini connector was not verified, so the implementation should use the tenant’s supported interfaces.
No. A dedicated Ivalua connector is not required. Martini can use Ivalua’s confirmed REST APIs, SOAP services, file exchanges, authentication methods, and selected outbound notifications or callbacks.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Ivalua. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Ivalua, cloud infrastructure, file-transfer providers, or other third-party systems based on subscription, usage, and deployment model.
REST APIs are the primary documented direction where the tenant exposes the required resources. File-based exchanges are relevant for bulk and scheduled processing, while SOAP services may be appropriate for legacy or tenant-specific implementations. Bulk APIs, asynchronous jobs, attachment APIs, and authentication details require tenant confirmation.
Universal webhook coverage was not publicly confirmed. Selected Ivalua processes may use outbound notifications, callbacks, or an intermediary integration layer. Martini can receive HTTP notifications when configured, while scheduled API polling or file exports may be needed for other objects and events.
Martini can use an Ivalua modification timestamp, change marker, export sequence, cursor, event, or equivalent filter when the relevant interface provides one. A durable watermark, controlled overlap period, stable object identifier, pagination handling, and reconciliation process help reduce missed updates and duplicates.
Martini can map and transform Ivalua JSON, XML, and file payloads, apply validation and business rules, and route results to downstream APIs or systems. Workflows can retry transient failures with backoff, avoid retrying permanent validation errors, preserve object and correlation identifiers, and use idempotency before document creation.
Related Martini documentation
Workflows
Data
Connect Ivalua to your enterprise systems
Use Martini to design maintainable Ivalua integrations across APIs, web services, files, workflows, and downstream applications.