Every invoice checked against the contract behind it.
Duplicate invoices, underbilling, unbilled work and irregular timing — GuardPilot links every invoice line to the underlying contract clause and execution data. Proven on €23M invoicing coverage in production.
Why invoice control has to be line-level.
Total-based invoice checks only find what stands out at the total level. Structural errors — duplicate lines, missed indexation, wrong tariffs — sit in the lines, not the totals. GuardPilot links every invoice line to the contract clause authorising it and the execution data backing it. Differences are surfaced with evidence, verified by two independent models.
Where invoice errors originate.
Duplicate invoices
The same deliverable lands on the invoice twice — via a second system, a manual correction that never retracts the original line, or a migration in which old and new sources overlap. Risky for customer relationship and cash flow alike.
Underbilling
Delivered hours, quantities or scope extensions do not fully reach the invoice. Usually visible as a structural gap between time tracking or delivery data and the corresponding invoice line.
Unbilled change orders
Extra scope agreed verbally or via email that never went through the invoicing flow. The work is delivered, the evidence sits in tickets and correspondence — not in the accounting system.
Irregular billing cadence
A month skipped, two months doubled, a quarterly invoice missing calendar months. Cash-flow impact is immediate; the revenue impact only appears when the lines are reconstructed against the contract.
Wrong indexation on the invoice
The contract prescribes CBS/CPI, the invoice runs on an old or wrong series. One wrong series compounds through every subsequent invoice until someone notices — usually years later.
Tariff diverges from contract
Invoiced tariffs diverge from what the contract prescribes at that date — through a missed escalation step, a manual adjustment that was never reverted, or a side letter that isn't in the invoicing system.
Line-level, every night, with evidence.
Every outgoing and incoming invoice is automatically linked to the underlying contract after processing. Tariff, indexation, quantity, period and escalation step are tested against what the contract prescribes at that date. Differences get an evidence file: source line, contract clause, execution data and model verdicts. Only after the four-eyes check does the signal reach a human.
€23M invoicing coverage in production.
About invoice control.
What is invoice control?
Invoice control is the line-level check that every outgoing and incoming invoice matches the contract behind it — right tariffs, right indexation, right quantities, right period. Classically this is sampled or only triggered when a customer complains; automated, it happens on every invoice before anything goes wrong. It is not only about underbilling: duplicate invoices and cadence errors damage the customer relationship just as much.
Which invoice errors does GuardPilot find?
Four main categories. (1) Underbilling: delivered work that is not on the invoice or billed too low, usually visible in the gap between time tracking and the invoice line. (2) Duplicate billing: the same deliverable lands on the invoice twice, often through a second system or a correction that never retracts the original line. (3) Unbilled change orders: scope extensions agreed verbally that never became an invoice line. (4) Irregular billing cadence: a month skipped, two months doubled, a quarterly invoice missing calendar months.
How is every invoice matched to every contract?
Every contract is extracted from the source at line level: tariffs, indexation clauses, billing cadence, escalation paths, side letters. Every invoice is then linked per line to the corresponding contract clause and to the execution data. Differences are investigated, backed by evidence, and confirmed by two independent models before a signal is raised. This runs on €23M of invoicing coverage in our own production.
Does invoice control also work on incoming invoices?
Yes. The same logic works both ways: outgoing invoices against contracts where you are the supplier, incoming invoices against contracts where you are the customer. On the incoming side the patterns are often mirror images — unjustly passed-on indexation, invoiced hours that were never delivered, duplicate items from accounts-payable systems. Both flows require the same line-level comparison.
See invoice control on your flows?
Request access to the waitlist for the first external pilots, or contact us for an intake call.
More of the GuardPilot system.
Revenue leakage
5.2% of annual revenue leaks structurally — missed indexation, underbilling, side letters.
Contract monitoring
27 agents read along every night; 98.6% coverage where manual reaches 3%.
Contract audit
No sampling, 100% of the portfolio. Four-eyes principle, <4% false positives.
AI in controlling
Not a stalled pilot — a human-in-the-loop system that already runs non-stop.