Integrations

• Banking provider. Send approved instructions through the agreed provider connection and retain its instruction identifier and response.
• Provider statements and notices. Bring source-identified confirmations, settlements and corrections into the instruction’s evidence trail.
• Account movement feed. Bring provider event identifiers, account references, amounts and receipt dates into movement matching.
• Account balance source. Supply dated principal and interest snapshots with the provider’s snapshot identifier.
• Identity directory. Keep user identity and team membership aligned with the organization that owns each instruction.

Agree which system owns each provider identifier and who may correct imported evidence. Keep the original source identity when a response is delayed, repeated or corrected. A local operation receipt should be read against its persisted effects before anyone repeats an external call. Map organization and role scope through each connection, including imports and reports, so a provider event cannot be linked to another organization’s instruction simply because its amount matches.