.png)
Zycus Integration Guide
Zycus can integrate with enterprise systems through deployment-specific APIs, callbacks, scheduled file exchange, and procurement data exports.
Zycus integration options at a glance
Zycus supports enterprise source-to-pay processes involving Suppliers, Requisitions, Purchase Orders, Invoices, Contracts, and Sourcing events. The exact integration interfaces are deployment- and module-specific: a public REST or SOAP reference, webhook catalog, bulk API specification, and standard file-transfer protocol were not confirmed. Customer implementations may provide APIs, outbound callbacks, scheduled files, reports, or exports. Martini can consume documented Zycus endpoints, receive validated callbacks, orchestrate scheduled exchanges, transform procurement data, and expose APIs for downstream applications. Authentication, pagination, incremental-change behavior, attachments, network controls, and error formats should be confirmed with Zycus before implementation.
| Integration point | Supported by Zycus? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Not confirmed | Zycus product or tenant-specific REST endpoints could support Suppliers, Requisitions, Purchase Orders, Invoices, Contracts, or Sourcing events if supplied by Zycus. | Martini can consume documented REST endpoints, map JSON requests and responses, apply business rules, and expose a separate API to downstream systems. Obtain the applicable API reference or OpenAPI definition first. |
| SOAP APIs | Not confirmed | A SOAP service may be available for a legacy or product-specific Zycus integration, but no current public reference was confirmed. | If Zycus supplies a WSDL and authentication details, Martini can consume the SOAP service, transform XML messages, and handle service-level errors. |
| Webhooks / outbound callbacks | Not confirmed | Zycus may provide outbound notifications for selected products or implementation projects, but universal event coverage was not confirmed. | Martini can receive and validate documented callback requests, retrieve the current object when possible, apply idempotency, and route the event through a workflow. |
| Bulk / asynchronous / batch APIs | Not confirmed | High-volume supplier, purchasing, invoice, or spend exchanges may use customer-specific batch or asynchronous mechanisms, although a public specification was not found. | Martini can orchestrate batch workflows, schedule polling or file processing, split and transform payloads, and persist checkpoints and rejection results when the interface is documented. |
| File / attachment exchange | Not confirmed | Scheduled files may be used for procurement master data, transactions, invoice documents, contract data, or acknowledgments. Protocols and formats require confirmation. | Martini can process confirmed CSV, XML, JSON, or other structured files and coordinate attachment handling through the supplied API or managed file-transfer process. |
| Authentication | Not confirmed | The applicable Zycus authentication method is product- and deployment-specific and may involve API credentials, API keys, client credentials, OAuth 2.0, certificates, or network controls. | Martini can keep credentials and certificates in environment-specific configuration and apply the authentication method required by the documented Zycus endpoint. |
| Database / analytics access | Not confirmed | Direct access to a Zycus-managed production database was not confirmed. Reports or exports may be available for analytics and reconciliation. | Martini can consume supported exports or reports, but should not connect directly to a Zycus production database without explicit vendor support. |
How Zycus exposes data and business events
Zycus REST APIs
A public, generally accessible Zycus REST API reference was not confirmed. A customer deployment may nevertheless provide product-specific REST endpoints for procurement objects, subject to tenant access, module scope, and vendor documentation.
Martini implementation pattern
Martini implementation pattern: Martini consumes the supplied REST contract, authenticates with the confirmed credential or token method, retrieves or submits Zycus objects, maps JSON payloads, applies validation and business rules, and records source identifiers and response details.
Implementation sequence
Zycus outbound callbacks
Public documentation confirming a universal Zycus webhook catalog was not found. Selected Zycus products or implementation projects may provide outbound callbacks for particular objects and events, which must be validated event by event.
Martini implementation pattern
Martini implementation pattern: Martini exposes or receives the documented callback endpoint, validates the request, applies an idempotency key, and retrieves the current Supplier, Requisition, Purchase Order, Invoice, Contract, or Sourcing event when the callback contains only a notification.
Implementation sequence
Zycus file and batch exchange
Zycus procurement implementations may use scheduled files, reports, exports, or customer-specific batch exchange for high-volume data. Supported protocols, formats, payload limits, acknowledgments, and rejection reports require confirmation.
Martini implementation pattern
Martini implementation pattern: Martini schedules or receives the confirmed file exchange, validates naming and structure, parses the payload, processes objects in controlled batches, writes accepted data to target systems, and stores acknowledgments or rejected rows for reconciliation.
Implementation sequence
Zycus SOAP services
No current public Zycus SOAP reference was confirmed. SOAP should be considered only when Zycus provides a product-specific WSDL, endpoint, security model, and message contract.
Martini implementation pattern
Martini implementation pattern: When a documented SOAP service is supplied, Martini consumes the WSDL-defined operation, transforms XML requests and responses, applies workflow rules, and captures SOAP faults separately from transport failures.
Implementation sequence
Common Zycus integration patterns
Pattern 1: Synchronize Suppliers with an ERP
When to use this pattern
Use this pattern when Zycus is the procurement source for supplier onboarding, qualification, or supplier master attributes and an ERP requires validated supplier data. The incremental mechanism must be confirmed; if no change endpoint or callback exists, use scheduled extraction and comparison.
Integration direction
Example Mapping
| Zycus Field | Canonical Field | Target Field |
|---|---|---|
| Supplier ID | supplier.externalId | Business Partner External ID |
| Supplier Name | supplier.legalName | Business Partner Name |
| Supplier Status | supplier.status | Supplier Lifecycle Status |
| Tax Identifier | supplier.taxIdentifier | Tax Number |
Martini implementation pattern
A Martini workflow retrieves or receives changed Suppliers, validates tax, payment, address, legal-entity, and status data, maps identifiers into the ERP model, and upserts only approved and complete records. It stores the Zycus Supplier ID and processing state, routes validation failures to reconciliation, and retries transient target failures without creating duplicates.
Martini capabilities used
- scheduled workflows
- API consumption
- file processing
- data mapping
- business rules
- validation
- error handling
- reconciliation
Pattern 2: Deliver Purchase Orders to an ERP
When to use this pattern
Use this pattern when approved Zycus Purchase Orders must be delivered to an ERP or supplier-facing system. It is suited to order creation, revisions, amendments, and acknowledgment processing where the customer deployment exposes the required API, file, or callback interface.
Integration direction
Example Mapping
| Zycus Field | Canonical Field | Target Field |
|---|---|---|
| Purchase Order ID | purchaseOrder.externalId | Purchase Order Number |
| Revision Number | purchaseOrder.revision | Document Revision |
| Supplier ID | purchaseOrder.supplierExternalId | Supplier Number |
| Line Amount | purchaseOrder.lines[].amount | Line Amount |
Martini implementation pattern
Martini retrieves approved Purchase Orders, maps headers and lines, resolves suppliers, currencies, tax, delivery dates, and business units, then submits the target document. It uses the Purchase Order ID and revision as correlation keys, handles amendments separately, records acknowledgments, and applies bounded retries for temporary failures.
Martini capabilities used
- workflow orchestration
- API consumption
- data mapping
- business rules
- idempotency
- retry handling
- audit logging
Pattern 3: Synchronize Invoices and Payment Status
When to use this pattern
Use this pattern when Zycus manages invoice validation or matching and a finance platform requires invoice details, outcomes, or payment status. It supports separate handling of invoice metadata and attachments when the vendor exposes them through different interfaces.
Integration direction
Example Mapping
| Zycus Field | Canonical Field | Target Field |
|---|---|---|
| Invoice ID | invoice.externalId | Invoice Reference |
| Invoice Number | invoice.number | Vendor Invoice Number |
| Purchase Order ID | invoice.purchaseOrderExternalId | Purchase Order Number |
| Payment Status | invoice.paymentStatus | Settlement Status |
Martini implementation pattern
A Martini workflow retrieves or submits Invoices, validates invoice-number uniqueness, Purchase Order matching, tax, currency, rounding, and credit-memo rules, and maps results to the finance platform. It separately retrieves documents when attachment support is confirmed, records vendor error codes and correlation IDs, and sends failed items to a replayable exception path.
Martini capabilities used
- API consumption
- scheduled workflows
- data transformation
- validation
- business rules
- attachment handling
- error handling
- replay processing
Pattern 4: Distribute Contracts and Sourcing Events
When to use this pattern
Use this pattern when approved Contracts or completed Sourcing events must be shared with analytics, relationship-management, contract, or ERP applications. Because public Zycus event coverage was not confirmed, scheduled extraction or file exchange may be required.
Integration direction
Example Mapping
| Zycus Field | Canonical Field | Target Field |
|---|---|---|
| Contract ID | contract.externalId | External Contract ID |
| Contract Version | contract.version | Contract Version |
| Effective Date | contract.effectiveDate | Start Date |
| Awarded Supplier | sourcingEvent.awardedSupplierExternalId | Supplier External ID |
Martini implementation pattern
Martini retrieves approved data through the confirmed Zycus interface, maps identifiers, dates, categories, suppliers, negotiated values, and statuses, and filters records by approval and effective-date rules. It writes Salesforce updates with durable correlation keys and produces reconciliation results for missing, changed, or rejected objects.
Martini capabilities used
- scheduled synchronization
- workflow orchestration
- data mapping
- date and status transformation
- business rules
- reconciliation
- monitoring
Applications commonly integrated with Zycus
Zycus commonly participates in enterprise procurement architectures that connect source-to-pay processes with ERP, finance, workforce, workflow, and analytics applications. The following are realistic integration targets based on common enterprise designs; specific Zycus endpoints, certified integrations, objects, and directions must be confirmed for each deployment.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize Suppliers, Requisitions, Purchase Orders, Invoices, accounting information, receipts, and payment status across procurement and ERP processes. | SAP S/4HANA → Martini → Zycus | Martini can orchestrate bidirectional workflows using the Zycus interfaces supplied for the deployment. It maps supplier, purchasing, invoice, currency, tax, and organizational identifiers, applies approval and duplicate-prevention rules, and routes rejected transactions for reconciliation. |
| Oracle Fusion Cloud ERP | Connect supplier, purchasing, invoice, financial, and procurement data between Zycus and Oracle Fusion Cloud ERP. | Oracle Fusion Cloud ERP → Martini → Zycus | Scheduled or event-driven workflows can retrieve or receive Zycus data, transform it to Oracle payloads, preserve source identifiers, process acknowledgments, and retry transient failures without duplicating Purchase Orders or Invoices. |
| Workday | Exchange worker, organization, cost-center, and reference data needed for procurement approvals and supplier-related processes. | Workday → Martini → Zycus | Martini can retrieve approved reference data from Workday, normalize organizational identifiers, validate required mappings, and deliver the result through the Zycus API, file, or customer-specific interface confirmed for the tenant. |
| Salesforce | Share supplier, contract, sourcing, or relationship information with sales, partner, and account-management processes. | Zycus → Martini → Salesforce | A Martini workflow can extract approved Zycus Suppliers, Contracts, or Sourcing events, map them to Salesforce objects, apply filtering by business unit or status, and record correlation identifiers for updates and retries. |
| ServiceNow | Connect procurement requests, supplier onboarding, approvals, exceptions, and service-related purchasing workflows. | ServiceNow → Martini → Zycus | Martini can receive approved requests or task updates from ServiceNow, transform them into Zycus Requisitions or supplier-process inputs, and return status or rejection details through a controlled workflow. |
| Jira | Create and track supplier onboarding, procurement implementation, sourcing, and exception-management tasks. | Zycus → Martini → Jira | Martini can create Jira issues from selected Zycus workflow outcomes or exceptions, map supplier and procurement identifiers into issue fields, and synchronize status changes using scheduled retrieval or confirmed callbacks. |
| Microsoft Dynamics 365 Finance | Synchronize supplier master, Purchase Orders, Invoices, tax, currency, and payment information. | Microsoft Dynamics 365 Finance → Martini → Zycus | Martini can coordinate bidirectional data exchange, validate legal entity and financial dimensions, map invoice and purchase-order lines, and use durable processing keys to protect against duplicate writes. |
| Coupa | Coordinate procurement, supplier, sourcing, and spend information when organizations operate both platforms during transition or across business units. | Coupa → Martini → Zycus | Martini can support a staged migration or synchronization flow by extracting mapped Suppliers, Purchase Orders, Contracts, or Sourcing events, applying cross-platform identifiers, and producing reconciliation results. |
How to build a Zycus integration in Martini
Objective
Establish the Zycus integration contract before building workflows, including the modules, environments, endpoints, authentication, network controls, payload formats, and supported objects.
Instructions in Martini
- Confirm whether the deployment provides REST, SOAP, callbacks, files, reports, or exports
- Obtain tenant-specific endpoint documentation, sample payloads, and credentials
- Store secrets and certificates in environment-specific Martini configuration
- Confirm IP allowlisting, VPN, private connectivity, or mutual TLS requirements
Objective
Select a trigger based on the interface that Zycus actually provides rather than assuming that every object supports real-time events.
Instructions in Martini
- Use a documented callback only for validated object and event coverage
- Use a scheduler for extraction, reconciliation, or batch file processing
- Define polling intervals, watermarks, cursors, or revision checkpoints
- Record how deleted, rejected, suspended, and archived objects are represented
Objective
Receive or retrieve the current Zycus object and preserve enough source metadata to support traceability, retries, and reconciliation.
Instructions in Martini
- Retrieve Suppliers, Requisitions, Purchase Orders, Invoices, Contracts, or Sourcing events through the confirmed interface
- Capture source identifiers, revisions, statuses, timestamps, request IDs, and correlation IDs
- Handle pagination, maximum-result limits, and attachment retrieval when documented
- Avoid direct database access unless Zycus explicitly supports it
Objective
Use a Martini workflow to coordinate the source call, transformations, business rules, target write, acknowledgments, and exception paths.
Instructions in Martini
- Separate transport, validation, transformation, and target-write stages
- Branch by object status, approval state, and validation outcome
- Use reusable logic for identifiers, status mapping, and reconciliation
- Preserve an auditable processing state for each source object
Objective
Convert Zycus procurement data into a canonical or target-specific model while making business assumptions explicit and configurable.
Instructions in Martini
- Map supplier, business-unit, legal-entity, category, currency, tax, and cost-center identifiers
- Preserve Zycus IDs alongside target IDs
- Validate required fields, line totals, tax values, dates, and status combinations
- Handle custom fields and unknown values through configuration or exception routing
Objective
Deliver transformed data to the ERP, finance, workflow, CRM, analytics, or other target system and process its response.
Instructions in Martini
- Use stable external identifiers for upsert and duplicate prevention
- Process acknowledgments and target validation responses
- Handle Purchase Order revisions, invoice matching outcomes, and payment-status changes explicitly
- Store target identifiers and response details for subsequent updates
Common Zycus data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Suppliers | Supplier profiles, onboarding information, qualification data, tax, payment, address, status, and supplier master attributes. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance, Salesforce | Martini validates required supplier fields, preserves the Zycus Supplier ID, maps legal and financial attributes, and uses status-aware upsert and reconciliation logic. |
| Requisitions | Internal requests for goods or services before purchasing approval. | SAP S/4HANA, Oracle Fusion Cloud ERP, ServiceNow, Microsoft Dynamics 365 Finance | Martini maps requesters, business units, cost centers, categories, lines, approvals, and statuses while applying validation and routing rules. |
| Purchase Orders | Approved purchasing documents issued to Suppliers, including lines, quantities, prices, currencies, delivery dates, revisions, and amendments. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance, supplier-facing systems | Martini tracks the Purchase Order ID and revision, prevents duplicate delivery, transforms line-level data, and processes acknowledgments or downstream rejection responses. |
| Invoices | Supplier invoices submitted for validation, matching, approval, payment processing, and financial reconciliation. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance, payment platforms | Martini maps invoice headers and lines, Purchase Order references, tax, currency, credit memos, and statuses, while separately handling attachments when supported. |
| Contracts | Procurement agreements, clauses, obligations, versions, suppliers, effective dates, expiration dates, and approval status. | Salesforce, contract repositories, analytics platforms, SAP S/4HANA | Martini distributes approved contract data, preserves versions and identifiers, applies effective-date rules, and supports scheduled reconciliation when events are unavailable. |
| Sourcing events | Sourcing projects, bids, auctions, requests for supplier responses, awarded suppliers, and negotiated values. | Salesforce, Coupa, analytics platforms, ERP applications | Martini transforms event, supplier, category, award, and value data and routes completed events to target systems through confirmed APIs, exports, or scheduled files. |
Authentication and security considerations
Confirm the Zycus security model
Zycus authentication was not confirmed from a public developer reference. Confirm whether the deployment uses customer-issued credentials, API keys, client credentials, OAuth 2.0, certificates, mutual TLS, IP allowlisting, VPN, or another control.
Protect procurement data
- Store credentials and certificates in environment-specific Martini secrets.
- Use least-privilege permissions for procurement, supplier, invoice, contract, and attachment data.
- Keep financial, tax, employee, supplier, and contract information out of ordinary logs.
- Encrypt files and attachments during transfer and storage where applicable.
- Separate development, test, and production credentials and endpoints.
Operational considerations for Zycus integrations
Plan for incomplete vendor interface information
Confirm endpoint behavior, pagination, sorting, rate limits, quotas, payload sizes, attachment handling, acknowledgments, and error formats with Zycus. These details were not publicly confirmed.
Make synchronization durable
- Use stable source identifiers and Purchase Order revisions or Contract versions for idempotency.
- Store watermarks, processing state, correlation IDs, and target identifiers.
- Use bounded retries and exponential backoff for transient failures.
- Respect vendor retry guidance and queue high-volume batch work.
- Distinguish validation, authentication, network, throttling, and server errors.
- Test lifecycle states including draft, submitted, approved, rejected, cancelled, closed, suspended, and paid where applicable.
- Reconcile Suppliers, Purchase Orders, Invoices, Contracts, and Sourcing events after each batch or synchronization window.
Why use Martini instead of scripts or point-to-point integrations?
Coordinate multiple procurement flows
Martini provides a workflow layer between Zycus interfaces and ERP, finance, workflow, CRM, analytics, and file-based systems. This avoids duplicating authentication, transformation, status mapping, retry, and reconciliation logic in separate scripts.
Make changes maintainable
Workflows can separate transport, mapping, validation, business rules, target writes, and exception handling. The same patterns can be reused for Suppliers, Requisitions, Purchase Orders, Invoices, Contracts, and Sourcing events as the Zycus interface evolves.
Support controlled operations
- Centralize environment-specific configuration and secrets.
- Preserve source and target identifiers for traceability.
- Provide bounded retries, replay paths, and reconciliation workflows.
- Expose controlled Martini APIs when downstream applications need a stable façade.
- Monitor workflow outcomes without embedding integration behavior in every consuming application.
Frequently asked questions
Zycus can be integrated through the interfaces available in a specific product and tenant, such as customer-specific REST APIs, SOAP services, outbound callbacks, scheduled files, reports, or exports. These mechanisms can exchange Suppliers, Requisitions, Purchase Orders, Invoices, Contracts, and Sourcing events with ERP, finance, workflow, and analytics systems. The exact endpoints, formats, authentication, and event coverage must be confirmed with Zycus.
Yes. Martini can integrate with Zycus using the native APIs, callbacks, files, reports, exports, or other documented interfaces supplied for the customer deployment. Martini can authenticate to confirmed endpoints, orchestrate workflows, map procurement data, apply business rules, and deliver results to other enterprise applications. A public standard Zycus API specification was not confirmed in this research.
No. A dedicated Zycus connector is not required. Martini can use Zycus's confirmed native integration mechanisms, such as documented REST or SOAP services, selected callbacks, scheduled file exchange, reports, or exports. The available mechanism should be validated for each Zycus module and tenant.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Zycus. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Zycus, cloud infrastructure, managed file-transfer services, or other third-party systems depending on subscriptions, usage, and deployment arrangements.
Use the current, vendor-supported interface supplied for the relevant Zycus product and tenant. REST APIs, batch interfaces, files, reports, exports, SOAP services, and callbacks are all possible implementation categories, but public confirmation was not available for a standard Zycus API or universal event catalog. Direct database access should not be assumed.
Public documentation confirming universal Zycus webhook coverage was not found. A particular product or implementation project may provide outbound callbacks for selected events. Event types, security, payloads, retries, and coverage for Suppliers, Purchase Orders, Invoices, Contracts, or other objects must be validated with Zycus.
Use a Zycus-supported change timestamp, cursor, revision, change token, batch marker, or callback when available. If no incremental mechanism is provided, Martini can run scheduled extractions with durable watermarks, comparison state, and reconciliation reports. Stable identifiers such as Supplier ID, Purchase Order ID and revision, Invoice ID, Contract ID and version, or Sourcing event ID should protect against duplicates.
Martini can map Zycus fields into canonical and target-specific models, validate identifiers and lifecycle states, apply rules for tax, currency, approvals, and duplicates, and route invalid data to exception handling. Workflows can capture vendor error codes and correlation IDs, retry transient failures with bounded backoff, and provide replay and reconciliation paths for corrected data.
Related Martini documentation
Plan your Zycus integration with Martini
Connect Zycus procurement processes to your enterprise systems with maintainable workflows, secure configuration, data mapping, and operational controls.