Integrations and source ownership

• Banks. Submit authorized instructions through the approved channel and receive acknowledgements, confirmations, statements and balances.
• Custodians. Receive settlement evidence, coupon and maturity receipts, custody movements and balance snapshots.
• Broker-dealers and auction platforms. Import trade tickets and auction results as documents on the instruction.
• Market data. Supply prices for valuation in your portfolio system.
• General ledger. Export confirmed instructions and approved cash flows for accounting entries.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their system access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. An uncertain submission outcome must never trigger an automatic resend, and a repeated provider event must not create a second movement or evidence line. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a provider timeout, a duplicate event and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.