Integrations and source ownership

• Custodian. Receive order acknowledgements, executions and as-of position snapshots with the custodian’s own IDs.
• Instruction provider. Send authorized instructions through the approved transport and receive acknowledgements and execution evidence with provider event IDs.
• Fund administrators. Receive subscription and redemption evidence for private and pooled funds.
• Market data. Supply mark prices for position snapshots where the custodian does not.
• Client reporting and accounting. Export confirmed instructions and approved household values for client statements and the general ledger.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their platform access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A repeated provider event must not create a second evidence line or execution, and a retry must not submit an instruction twice. 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.