Integrations and source ownership

• Driver authority source. Configure the source used to confirm driver eligibility and retain its external reference. Agree who checks renewal evidence and how the team handles a date that expires during an assignment.
• Fleet and telematics system. Map the external fleet identity and the meaning of each timestamp before importing vehicle activity. Route optimization and driver-hours assessment are separate connection choices when the operation needs them.
• Warehouse system. Agree the relationship between loading evidence and the warehouse’s inventory movement. Keep the dispatch handover time and the warehouse confirmation traceable without treating either as proof of the other system’s action.
• Carrier proof source. Map the load and stop identity for delivery documents or carrier portal references. Decide which evidence may be shared and who checks a document that arrives after the delivery time is recorded.
• Carrier accounting. Pass agreed operational references into the finance process when required. Delivery completion does not settle an invoice; accounting retains authority over charges and payment confirmation.

Each connection is a setup choice with a named owner, source identity and agreed field mapping. Use stable operation references, keep credentials in the approved secret store and limit access to the required organization. Preserve original timestamps and normalize their time-zone meaning before comparing appointments with actual events.

Rehearse duplicate messages, changed source evidence and a timeout after the external system may have acted. Check the existing receipt and linked effects first. Leave uncertain results visible for review until the authoritative source confirms the outcome. The reconciliation process reads existing effects and never repeats external work simply to clear a failure.

Plan the implementation and review reconciliation responsibilities.