Integrations

• Rate feeds. Import approved spot and closing rates from the selected provider by currency pair, type and date. Agree provider access, supported pairs and the process for resolving gaps before enabling scheduled loads.
• Treasury management system. Exchange rate schedules, approved treasury journals and exposure reports through a configured connection. Hedge valuation and hedge accounting remain in the treasury system and require finance review before journals reach the ledger.

• Statement feeds. Import statements through supported APIs or files in each account’s currency. Configure matching rules and exception ownership; unmatched incoming cash is recorded as unapplied cash before allocation.
• Payment files. Agree and test each required bank format, whether ACH, SEPA, wire or another supported route. Export authorised runs to verified beneficiary details. Bank acknowledgements identify accepted, rejected and returned payments, with reversal and retry handling tested before launch.

• Billing and order management. Map invoices, credit memos and payment status to the correct entity and currency. Preserve source identifiers so resending a document does not create another posting.
• Procurement and expenses. Keep purchase orders and receipts in the procurement system where appropriate and return reference-check results to the bill. Use the reviewed non-PO route for bills that do not require those references.
• Payroll. Import balanced salary journals per entity, with the required approval and a source reference for reconciliation. Payroll calculation stays in the payroll system.
• Card processors. Map gross receipts, fees and withheld amounts separately so the net bank movement reconciles with customer applications in their respective currencies.

• Tax engines. Scope the required jurisdictions, rate sources and filing formats with the finance owner. Verify calculation and export mappings; the presence of tax records does not establish coverage for every authority.
• E-signature. Where needed, connect the selected signature service and retain the approved evidence with the relevant decision. Confirm that the integration supports the required signing workflow.
• Audit export. Give auditors read-only access to the permitted entity and period evidence. Verify the required export format and the records that must accompany it.

• BI and planning. Export approved ledger and consolidation results with their entity, period and rate context. Review budget-version imports separately from actual postings.
• Group ledger. If consolidation remains elsewhere, agree the closed trial-balance export, mappings and adjustment ownership. Reconcile the receiving ledger to the export totals.

Use a separate identity and entity scope for each connection, and retain source references and processing outcomes. Test replay protection, error recovery and pause controls during implementation. Missing required rates block the affected posting until an approved rate is supplied; feed failure does not silently authorise an older rate. An integration cannot bypass the approvals or access rules applied to the same work in the interface.