From invoice discrepancy to decision record

An alert is not yet a decision record

A missing line, different rate or unexpected total may result from an error, missing evidence, a misidentified contractual rule or an actual event that has not yet been linked. Treating every difference as a confirmed anomaly creates false disputes and transfers the investigation back to the team.

The first purpose of control is therefore to reconstruct the situation. Vigilo links the invoice to the relevant transport record, gathers the request and amendments, looks for evidence of the performed service and applies only rules validated for that scope. The output is a decision record, not an automatic verdict.

The three layers to reconcile

These layers do not always share the same reference or format. The reconciliation therefore retains the identifiers used, the confidence of the linkage and any competing candidates. If two shipments could match one line, the decision stops before calculation.

What a decision record contains

1. 01
   Identity

   Transport record, invoice, line and parties concerned, including linkage confidence.

2. 02
   Timeline

   Request, confirmations, amendments and performed-service events in sequence.

3. 03
   Expected

   Amount or condition reconstructed from an identified, versioned rule.

4. 04
   Observed

   Value actually invoiced and the calculated difference without premature interpretation.

5. 05
   Evidence

   Documents and data that support or contradict the discrepancy.

6. 06
   Uncertainties

   Missing information, conflicting sources, an inapplicable rule or required approval.

7. 07
   Proposal

   Prepared action, responsible person and the elements that still require judgment.

8. 08
   Resolution

   Human decision, rationale, action taken and verified final outcome.

Example: a missing surcharge after an actual event

The record contains documented dock waiting time or an amendment received less than 24 hours before the operation. The invoice contains no corresponding surcharge. Vigilo can identify this difference and bring together the timestamp, CMR consignment note, amendment, rate version and invoice line.

It cannot conclude that the surcharge is due without an applicable rule. The contract may specify a threshold, allowance, required form of evidence or exclusion for that customer. The record therefore identifies the rule found, the conditions that are met, those still requiring confirmation and the decision expected from the authorized person.

Classify the discrepancy before choosing an action

Each classification leads to a different next step: close, request evidence, correct data, prepare an exchange, route to finance or close with a rationale. This separation prevents an automated dispute when only the detection step was reliable.

• false discrepancy: a different rounding, period or presentation with a compliant result;
• incomplete record: a required document or event is still missing;
• ambiguous linkage: several transport records or lines are plausible;
• rule to confirm: the contractual source or its version does not support a conclusion;
• confirmed discrepancy: the facts and rule establish a difference;
• accepted exception: the team decides not to correct or dispute the item;
• internal error: the expected data or initial processing must be corrected.

Assign the work clearly between Vigilo and the team

The authorization level may vary by discrepancy type, amount, customer and evidence quality. The company defines this policy. Vigilo executes and explains it; it does not silently replace business accountability.

Adapt to systems without losing the method

Information may come from a TMS, ERP, portal, inbox or documents whose formats vary by partner. Vigilo is designed to adapt collection and action to those systems, using an API when appropriate or interacting with the interface when the workflow requires it.

The decision model remains stable: identify, link, reconstruct, compare, evidence, obtain a decision and verify. Company-specific mappings, rules, screens and responsibilities are versioned within its scope. This separation turns adaptability into a reusable asset rather than a succession of isolated projects.

Measure control using validated decisions

An amount is considered corrected, avoided or recovered only after a defined, verifiable resolution. The dashboard therefore separates detected difference, confirmed discrepancy, decision in progress and closed outcome. It also retains cases with no financial impact that still improve record quality.

• share of invoices and lines linked to the correct record;
• proposed discrepancies subsequently confirmed, corrected or rejected by the team;
• reasons for false discrepancies and incomplete records;
• time spent reconstructing, deciding and resolving;
• classified amounts awaiting a decision, without presenting them as recovered;
• actions executed and outcomes actually observed;
• rules that produce recurring corrections or judgments.

Turn resolutions into governed knowledge

A closed decision enriches the history: confirmed cause, applied rule, decisive evidence, action and outcome. When the same judgment recurs in comparable situations, Vigilo can surface a candidate rule or a control that needs improvement.

That proposal is not activated on its own. The team verifies that it is genuinely a rule, defines its scope and exclusions, then chooses whether it should remain informative, prepare a decision or authorize an action. Operational memory therefore preserves the connection between knowledge and the records that justify it.

Dispute file template to complete

This template is a working aid. It must be adapted to the contract, the document received, each party’s responsibilities and the company’s procedures. While facts or rules remain incomplete, the file stays “to be assessed”: a calculated difference does not, by itself, prove an invoicing error.

Neutral message template to adapt

The template below keeps a request for verification from becoming an accusation. Replace every passage in brackets, and only list attachments that are actually included or accessible.

Subject: Verification requested — [statement, draft invoice or invoice reference] / [transport reference]

Hello, while reconciling [document and reference] with transport record [reference], we found a difference between [value shown on the document] and [reconstructed value], amounting to [difference and unit]. Our calculation is based on [source, version or date] and the following verified operational facts: [facts]. We have included [list of evidence] for reference. At this stage, the difference requires verification and does not prejudge its cause. Could you confirm the inputs used in your calculation and, where relevant, identify the document or rule that explains it? If the reconciliation needs to be corrected, please specify the planned action and the document that will evidence the result. Kind regards, [name, role, contact details].

The wording, recipient, channel and approval level depend on the contractual relationship and internal rules. A company may set an internal follow-up target to manage its queue; that target is not, by itself, a right or a deadline binding on the other party.

Keep an evidence register that records limitations

One document does not establish every conclusion. The register states what each item can support, what it does not prove and whether a competing version exists. This prevents a proof of delivery, for example, from being treated as automatic proof of the applicable rate.

Track the reply through to verifiable closure

A single status such as “disputed” hides the remaining work. Tracking should separate the request’s state, the position received and execution of the decision. The labels below are an operational template to adapt, not universal legal classifications.

• link the reply and all new evidence to the original file;
• retain the author, date and rationale of the final decision;
• verify the credit note, corrected invoice, reconciliation or internal correction that was actually expected;
• record partial agreement line by line instead of closing the entire file;
• state the condition for reopening when a document or outcome is still missing.