Integrations and source ownership

• Banks and payment gateways. Authorized instructions are submitted through your bank connectivity, such as SWIFT, host-to-host files or bank portals. Statements, confirmations and settlement advices return as evidence with provider event identifiers.

• Trading platforms. FX and money market deals and counterparty confirmations can be imported from your dealing platform.

• Statement imports. Balance snapshots and statement entries arrive per account with provider identifiers for exact matching.

• General ledger. Confirmed movements and explained exceptions are posted to your ledger through an agreed connection.

• Identity provider. Map team members to user accounts; disabling a sign-in must remove access here too.

Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated submission must not pay twice, and a repeated statement must not add entries twice. Queue rejected records with their source identifier and a visible reason.

Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.