MONEY FOUND · WORKED EXAMPLES
No human chases $31. AI does.
Five leakage patterns from AP and contract portfolios, each traced from the finding back to the line it came from.
- INPUT
- your contracts, or one month of AP
- PASSES
- one, over the whole corpus
- OUTPUT
- a row per discrepancy: value, clause, page, and what was invoiced
- WHO DECIDES
- your AP or contract owner, line by line
- ELAPSED
- days, not a project
Five patterns, one corpus pass.
Invoice paid twice
Same vendor, same invoice number, same amount, under two different scan filenames.
$18,400
Price escalation never billed
The contract indexes the unit price. Fourteen months on, the invoices still show the old one.
$31,200
Auto-renewal caught in time
Notice window read from the contract, flagged 96 days before it closed.
$54,000
Credit note never applied
An open credit with no matching deduction on any later invoice.
$7,950
Freight billed above rate card
Carrier lines checked against the contracted lane rate. A few dollars over, several hundred times.
$12,300
Found in one corpus pass
$123,850
Representative findings from AP and contract portfolios, in USD as printed in the SSOW briefing. Every line traces back to a value, a source line and the scan it came from.
Margin is lost in the details.
A price escalation clause hides on page 14 of a contract addendum. The rate card sits in a spreadsheet. A notice about a supplier rebate sits in someone’s email. None of it is queryable, so none of it is checked at the moment of billing.
It is not worth a person’s time to chase a $31 billing error. It is worth an agent’s. One pass through the platform and the details are in a database, with context and provenance, and the same terms can be checked against every invoice that arrives after.
Each finding, walked back to its source.
The finding
Where the term lives
What the system did
Price escalation never billed, $31,200
The largest recurring pattern in contract-heavy portfolios, and the easiest to miss by hand.
Escalation clause, addendum, page 14
The clause indexes the unit price to a published index once a year. The base value and the index reference are captured as separate fields.
Fourteen invoices at the old unit price
Each invoice line carries the price actually charged. The difference to the indexed price is the row, with both pointers attached.
Invoice paid twice, $18,400
A duplicate is two records that are the same thing, not two files that look alike.
Two scans, one invoice
Vendor, invoice number and amount agree. The filenames do not, which is why the AP system treated them as two.
Two payments, one obligation
Both payment records are pulled beside the invoice fields. The row is the second payment, with the first one cited.
Credit note never applied, $7,950
The smallest of the five, and the kind nobody would open a ticket for.
Credit note, open
Captured with its vendor, amount and date, and held as an open credit against that vendor.
No later deduction
Every subsequent invoice from the vendor is checked for a matching deduction. None found is the finding.
The three columns are the shape of every row we return: the finding, the clause or record it rests on, and the system-of-record side it was compared against. A finding without the third column is a list of clauses, not money.
How the pass runs.
Extract everything
no field list required
Reconcile against reality
Review with evidence
- Extract everything. Every value a document holds is captured and typed. Escalation formulas, index references, rate cards, credit terms, notice windows. Not only the fields somebody asked for.
- Reconcile against reality. Contract terms checked line by line against what was invoiced, paid, credited or renewed in your systems.
- Review with evidence. Each discrepancy arrives with the value, the relevant terms, and pointers to the pages they came from. Your owner decides, row by row.
What a finding must carry.
- A value, or a pointer to one. Every concept is tagged as money, where the captured value is itself an amount, or as pointing at money, where it enables a check without being an amount. Pointers never sum into a headline number.
- The clause and the page. A bare value with a page number is not provenance. The clause under it is what makes a row worth acting on.
- The other side. The estate holds the terms. A finding needs what your system actually applied. Give us only the contracts and you get a list of clauses and no information.
This is the same discipline the standing query runs on inside the platform. The agent behind it is described at /agents/money-found; the contract estate it runs over, read once and held for whoever asks next, is the GETEC case.
Bring us your contracts, or one month of AP.
We run one pass and hand back what we find, cited to the line that produced it. Your owner checks the rows; nothing leaves as a finding ahead of that.
Note: Figures on this page are representative findings from AP and contract portfolios, in USD as printed in the SSOW briefing. Customer-specific results are released by the customer, on their case page, or not at all.