Workday, Maximo and other systems
Workday Financials
Section titled “Workday Financials”Workday stays the book of record for suppliers, POs, receipts and the GL; Spend sends back approved invoices, card journals and expense reports.
- Inbound uses RaaS (custom reports as JSON), because the customer controls the fields. Suppliers, POs, receipts and the Budget vs. Actual report come in this way, mapped on the field mapping screen.
- Outbound uses the SOAP web services: supplier invoices, P-Card journals and
Submit_Expense_Report. - Settlement is read back, so payment status matches Workday.
The XML follows Workday’s public Resource Management and Financial Management schemas, but element names and reference id types vary by tenant and API version, so every request is validated against the tenant’s WSDL before go-live.
IBM Maximo
Section titled “IBM Maximo”Maximo raises purchase requisitions from work orders and inventory reorder. They arrive in Spend as requisitions coded to the work order and GL account, and PO numbers flow back so planners see order status in Maximo. POs placed in Spend are created in Maximo (and kept in step when they change), storerooms receive against them there, and those receipts come back for three-way match. The connector uses the REST/OSLC API with the MXAPIPR, MXAPIPO and MXAPIRECEIPT object structures; field names are confirmed against the customer’s object structures.
Oracle Fusion and SAP S/4HANA
Section titled “Oracle Fusion and SAP S/4HANA”Both use the shared ERP sync engine: Oracle Fusion over its REST API and SAP S/4HANA over OData.
Document repositories (CMIS)
Section titled “Document repositories (CMIS)”Approved and paid invoices are filed with their audit packet to any CMIS 1.1 repository over the browser binding: OpenText eDOCS, Documentum, Alfresco or SharePoint Server. Files go under a base path by fiscal year and supplier, with your repository’s document type and property ids. Set CMIS_ROOT_URL_<TENANT>, CMIS_USERNAME, CMIS_PASSWORD and CMIS_BASE_PATH, and optionally CMIS_OBJECT_TYPE and CMIS_PROPERTIES.
Banks and payment networks
Section titled “Banks and payment networks”| Connection | Notes |
|---|---|
| NACHA ACH | Files with prenotes for new accounts |
| Check and positive pay | Check files with the bank’s positive pay file |
| Visa VCF 4.4, Mastercard CDF3 | P-Card bank files with level 3 data; confirm each against a sample from the issuing bank |
| Card issuer API | Virtual cards and rebates, once the bank’s API is contracted |
| Peppol access point | ACCESS_POINT_URL, ACCESS_POINT_API_KEY |
| Early-pay funder | EARLY_PAY_FUNDER_URL and related settings |
| Account ownership | GIACT or Early Warning, once contracted |
Data sources
Section titled “Data sources”| Source | Setting |
|---|---|
| OFAC SDN list | On by default; OFAC_SCREENING=off to disable |
| SAM.gov exclusions | SAM_GOV_API_KEY |
| Financial, safety and environmental risk providers | RISK_FINANCIAL_URL, RISK_SAFETY_URL, RISK_ENVIRONMENTAL_URL |
| BLS price indices | Works without a key; BLS_API_KEY raises the daily limit |
| RAMPLA, Cal eProcure | RAMPLA_POST_URL, CAL_EPROCURE_POST_URL and their tokens |