Integrations and source ownership

• Accounting platform. Invoices for approved trip charges are issued in your accounting system. Agree how the invoice number is kept so a charge marked Invoiced can be traced to its invoice.

• Payment provider. Charter deposits and balances are collected in your payment system. Agree what payment evidence the Charter Coordinator needs before confirming a booking.

• Booking channels. Enquiries from your website or a charter broker can create Requested bookings through an agreed connection, matched to an existing customer by email.

• Identity provider. Map crew and office staff to user accounts. Disabling a person’s sign-in must also remove their access here.

• Maintenance and survey records. Survey reports and maintenance history stay in your maintenance system. Enter the next inspection due date on the vessel when a certificate is renewed.

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 booking enquiry must not create a second request, and a repeated invoice event must not mark a charge 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.