Transportation Management / Tracking is where ERP discipline either begins or breaks.
Shipment Tracking and Delivery Event Monitoring looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Customer "where is my order" inquiry rate reduced by 40%; delivery exception resolution time under 4 hours; on-time delivery reporting available without manual data collection
The control flow a finance team actually needs.
Step 1
Track Shipments Across All Integrated...
Step 2
Translate Carrier-Native Status Codes...
Step 3
Push Customer Notifications At Minimum...
Step 4
Raise Exception Alert Within 1 Hour Of...
Step 5
Manual Tracking Number Entry For...
The ERP surface involved.
Module
Transportation Management / Tracking
Actors
Customer Service Agent, Customer, TMS Tracking Engine, Carrier APIs
Tier
Tier 2
Finance area
Supply Chain, Demand Planning & Logistics
Region lens
US and UK finance teams
Publication date
May 18, 2026
Track shipments across all integrated carriers with polling interval configurable per carrier (minimum every 2 hours); translate carrier-native status codes to standardized internal statuses; push customer notifications at minimum for "shipped" and "delivered" events; raise exception alert within 1 hour of carrier exception event; support manual tracking number entry for non-integrated carriers; provide shipment dashboard with on-time delivery rate, exception count, and average transit time; delivered event triggers downstream billing action
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Track shipments across all integrated carriers with polling interval configurable per carrier (minimum every 2 hours | Given a dispatched shipment with tracking number linked to a carrier integration |
| Control 2 | translate carrier-native status codes to standardized internal statuses | when the TMS polls carrier tracking APIs at least every 2 hours |
| Control 3 | push customer notifications at minimum for "shipped" and "delivered" events | then tracking events are stored with standardized internal status codes, customers receive proactive notifications at "shipped" and "delivered" milestones, delivery exceptions raise internal alerts within 1 hour, and confirmed delivered events trigger invoice-to-cash workflow |
| Control 4 | raise exception alert within 1 hour of carrier exception event | |
| Control 5 | support manual tracking number entry for non-integrated carriers | Customer "where is my order" inquiry rate reduced by 40%; delivery exception resolution time under 4 hours; on-time delivery reporting available without manual data collection |
| Control 6 | provide shipment dashboard with on-time delivery rate, exception count, and average transit time | Customer "where is my order" inquiry rate reduced by 40%; delivery exception resolution time under 4 hours; on-time delivery reporting available without manual data collection |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | After shipment, the TMS polls carrier tracking APIs at configurable intervals (every 2 - 4 hours) and ingests tracking events (in-transit, out-for-delivery, delivered, exception). Events are stored against the shipment record and mapped to internal status codes. Customer service agents can view real-time status from a shipment inquiry screen without leaving the ERP. Customers receive proactive email and SMS notifications at key milestones (shipped, out-for-delivery, delivered). When a delivery exception occurs (address issue, missed delivery, damage), an internal alert is raised to customer service for proactive resolution. Delivered events trigger invoice-to-cash workflow for shipment-linked invoices. |
| Control rules | Track shipments across all integrated carriers with polling interval configurable per carrier (minimum every 2 hours); translate carrier-native status codes to standardized internal statuses; push customer notifications at minimum for "shipped" and "delivered" events; raise exception alert within 1 hour of carrier exception event; support manual tracking number entry for non-integrated carriers; provide shipment dashboard with on-time delivery rate, exception count, and average transit time; delivered event triggers downstream billing action |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`shipment_tracking` { tracking_id: string, shipment_id: string, tracking_number: string, carrier_id: string, last_polled_at: timestamp, status: enum(IN_TRANSIT/OUT_FOR_DELIVERY/DELIVERED/EXCEPTION), carrier_native_status: string }; `tracking_event` { event_id: string, tracking_id: string, event_type: enum(IN_TRANSIT/OUT_FOR_DELIVERY/DELIVERED/EXCEPTION), occurred_at: timestamp, location: string, notified_customer: bool }; (reference, product may differ).API and events
`GET /v1/shipments/{shipment_id}/tracking`; `PUT /v1/shipments/{shipment_id}/tracking-status` { status, occurred_at, location } -> 200; emits `shipment.delivered` and `shipment.exception` events; idempotent via `external_id`.State transitions
`IN_TRANSIT -> OUT_FOR_DELIVERY -> DELIVERED`; exception path `IN_TRANSIT -> EXCEPTION -> IN_TRANSIT | DELIVERED`; terminal `DELIVERED`; guard: DELIVERED event triggers downstream billing action automatically.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.