- Who is this for?
- Transport management, operations, sales administration and finance teams
- Question addressed
- Understand the end-to-end continuity of a transport record.
Key takeaways
- The record is not a new software application: it connects facts distributed across several tools.
- An amendment must retain the previous value and its source.
- Performed-service data enriches the information that will be checked when the invoice is received.
- Operational memory relies on traceable records, not isolated statistics.
The record exists across systems
The TMS stores the structured part of the order. The inbox holds the request and its amendments. The portal confirms a status. The CMR consignment note records the performed service. The invoice arrives later with its own representation of the operation.
When these elements are not connected, every check becomes an investigation. Continuity means knowing which event changed which information, what decision followed and what evidence confirms the outcome.
A minimum timeline
- 01Request received
The source, intent and initial documents are retained.
- 02Record created
The selected values and their sources become visible.
- 03Amendment applied
The previous value, the new value and the reason remain connected.
- 04Performed service documented
Statuses, waiting times and evidence complete the record.
- 05Invoice checked
Charges are compared with what was requested and what was actually performed.
- 06Knowledge consolidated
Discrepancies and decisions inform the next check once validated.
Example: dock waiting time that became billable
The time slot is confirmed in the record. On the day of delivery, a “42-minute dock wait” event is linked to the CMR consignment note and the actual timestamp. When the invoice is received, the check can look for the expected surcharge instead of starting from a single total amount.
If the surcharge is missing, the discrepancy record already contains the facts and supporting documents. The validated contractual rules still need to be applied, and the sensitive decision remains with the team.
What this continuity makes observable
- customers who frequently amend their requests;
- stages that require the most rework;
- recurring missing information;
- invoice discrepancies linked to actual events;
- rules that still require frequent human decisions.
Frequently asked questions
Direct answers
Does the record replace the TMS?
No. Vigilo connects the context and operates within the tools included in scope; the TMS remains the business system selected by the company.
Do both entry points have to be deployed?
No. Order intake and invoice control can be activated separately. Their continuity becomes useful when both are included in scope.
What is operational memory?
It is the structured knowledge derived from records, rules, decisions and actual observed outcomes, together with their context.
Sources and methodology
This resource describes Axonovia's product approach based on transport workflows. The examples are illustrative and do not constitute a performance commitment or a universally applicable contractual rule.
Product review: Axonovia team · next review recommended before 31 August 2027 or following a material change in scope.