Integrations and source ownership

• Telematics provider. Configure a feed for reported load milestones and location observations. Map the provider’s equipment and load references, retain the occurrence time and identify the reporting source before using the event in dispatch work.
• Partner dispatch system. Agree how carrier or broker messages map to the load and its stops. Keep appointment changes distinct from actual arrival or delivery confirmation, and route conflicting reports to Dispatcher.
• Delivery document service. Connect the source used for receiving documents and signature references. Map each document to the correct load and delivery stop, then confirm that authorized reviewers can retrieve the evidence.
• Accounting platform. Agree the exchange of approved freight charges and invoice or payment outcomes. Keep amounts with their currency and reconcile the external document before updating commercial progress.

These connections are setup choices. Give each one an operating owner, a source reference format and a clear correction procedure. Test a normal event, a duplicate message, an unknown load and a provider timeout before enabling scheduled exchange. A reported milestone needs the same operating review regardless of how it arrives.

Admin configures access to the connection while the domain owner checks its meaning. Dispatcher reviews load events, Evidence Reviewer checks delivery references and Finance Reviewer reconciles charge outcomes. Keep rejected inputs available for investigation with their original source identifiers. Agree the retry behavior and verify that reprocessing does not create another operational result for the same source case.

Use the implementation plan to define acceptance examples for each connection.