Skip to content

Connectors overview

Spend is the system of engagement; your ERP stays the book of record for suppliers, POs, the GL and payments. Connectors move records between them on a schedule.

Every ERP adapter turns its system’s API into the same normalized records (suppliers, POs, receipts, invoices out, payments back). The sync engine does matching, idempotency, dead letters and ledger events the same way for every ERP.

SystemHow
Workday FinancialsRaaS custom reports in (JSON), SOAP web services out, settlement read back
Oracle E-Business Suite R12.2Integrated SOA Gateway REST, the Payables open interface and import
Oracle Fusion CloudREST
SAP S/4HANAOData
IBM MaximoREST/OSLC object structures for requisitions, POs and receipts
CMIS 1.1 repositoriesBrowser binding, for OpenText eDOCS, Documentum, Alfresco and SharePoint Server
Fixed-width filesFor batch interfaces with legacy systems

Every connector refuses plain HTTP.

Each run is a sync run with its counts (read, created, updated, skipped, failed). Records that fail go to the dead-letter queue with the error, and can be retried after the cause is fixed. Repeated failures open an integration case.

GET /api/integrations lists each connector’s health, its schedule and recent runs. Administration › Integrations shows the same.

For report-driven feeds (such as Workday RaaS), administrators map the report’s columns to Spend fields on Administration › Integrations › Field mapping: paste a sample, get a suggested map, adjust it and save. The next sync uses the saved map.

pnpm validate:connectors checks the EBS and CMIS connectors against the sandbox set in the environment before go-live.

  • Oracle EBS and CMIS archiving run from environment settings on the hosted server; see Oracle EBS.
  • Workday, Maximo, Oracle Fusion and SAP are configured for each customer during implementation, after their request and response bodies are checked against the customer’s own tenant.