Invoice Check
When a supplier connector reports an invoice, Trading matches it against the ordered value. This is the third leg of the match — after the purchase order itself and the goods receipt.
What is compared
Deviation % = (Invoice Amount − Landed Cost) ÷ Landed Cost × 100
The comparison uses the landed cost of the run — what Trading based its decision on, including freight and insurance.
The amount is net
Connectors report the net amount. A gross amount would make every invoice deviate by the VAT rate and render the check worthless — at 19 % every single invoice would be flagged.
If suddenly all invoices from one supplier deviate by the same percentage, that is the first suspicion.
Only the expensive direction
Only an invoice exceeding the ordered value is flagged.
An invoice below the order value is a discount, not a problem. Flagging it would train people to click past the warning — and make them miss exactly the cases that matter. The deviation is still recorded, with a negative sign.
The tolerance
Max. Invoice Deviation % in the Trading Setup defines how far an invoice may deviate before it is flagged.
| Value | Effect |
|---|---|
0 |
Every deviation upwards is flagged — down to a single cent |
2 (default) |
Freight, rounding and recycling fees rarely land to the cent; small differences are normal |
The boundary is inclusive: with a tolerance of 2 %, a deviation of exactly 2 % is still fine.
The results
| Result | Meaning |
|---|---|
| Not Checked | No invoice reported yet |
| Matched | Within tolerance — or cheaper than ordered |
| Deviation | Above tolerance |
| No Reference | Trading knows the purchase order but never costed it |
"No Reference" is not an error, but not a free pass either
This happens with purchase orders assigned to Trading for which no landed cost exists — for instance a run created before a setup change.
The invoice is then not silently waved through as correct; it appears on the Invoice Deviations cue instead: an invoice nobody checked should not look like a checked one.
Corrected invoices
If a connector reports another invoice for the same purchase order, the check runs again. A corrected invoice clears an earlier deviation.
Connectors typically report corrections as a new message against the same order number — the check is therefore built to be repeatable rather than a one-off verdict.
Invoices for other orders
If a connector reports an invoice for a purchase order Trading did not create, nothing happens. Trading only checks what it is responsible for.
Where you see it
- "Invoice Deviations" cue — the number of cases; click opens the list
- On the run — fields Invoice Amount, Invoice Deviation % and Invoice Match
- In the activity log — every deviation is recorded with invoice number, ordered and invoiced amount