Integrations and source ownership

• Booking channels. Fares, holds and supplier confirmations come from your global distribution system, agency tool or supplier sites.

• Payment provider. Authorization, capture, refund and void events arrive with the provider’s event identifier and reference.

• Expense and reimbursement. Expense claims and reimbursement stay in your expense system; captured trip spend can be shared with it.

• General ledger. Captured spend by supplier is 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 payment event must not add a second payment, and a timed-out confirmation must not be sent again without checking the supplier. 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.