Integrations and source ownership

• Transport booking system. If intake comes from an external booking service, agree how its transport reference maps to the load record number. Check repeated or changed requests before creating another load. Confirm which team owns contact corrections.
• Laboratory system. Agree how sample accession numbers and processing confirmations are exchanged. The laboratory supplies its results and the evidence for received, tested or rejected states. Review a mismatched accession number before changing the sample record.
• Billing and accounting system. Send reviewed service descriptions and amounts through an agreed handoff. The billing owner confirms invoice creation and retains detailed invoice allocation and accounting treatment. Reconcile charges by their related service stop.
• Payment source. Import or enter received funds from an approved payment or bank source. Keep the external reference with the load-level settlement and reconcile confirmed receipts and refunds with their source evidence.

Each connection is a setup choice with its own system owner and access requirements. Agree the direction of exchange, identity mapping and correction procedure before scheduling machine work. Keep credentials in the approved secret store and grant only the access needed by that connection.

Test a repeated delivery, a changed source record and an unavailable provider. Reconcile accepted records with the source before continuing after an interruption. A local state change should reflect the external event it describes. The team responsible for that event resolves conflicting evidence.

Use the implementation plan to define the pilot and review responsibilities.