Who built this.

Why this exists

Third-party logistics contracts are priced in twenty to fifty lines. The invoices that settle against them arrive with six lines and a total. Nobody has time to rebuild that arithmetic monthly, so it gets paid — and the errors that survive are the ones that look like ordinary line items.

None of this requires bad faith. A tier that has nowhere to live in a billing system, a rate change applied from the wrong date, a pre-packed carton decomposed into picks: each is a system doing what it was told. But the money is real, and the brand pays it.

The engine exists because the comparison is mechanical and nobody was doing it mechanically.

Who to ask

Johny Hernández built the engine and answers questions about it, at hello@spendverify.com.

What it does not do yet

Kept here rather than buried, because the list is short and the omissions matter:

Hand-entered figures are marked unverified. There is no order-feed integration, so volumes are typed. A finding that rests on a typed number says so, on screen, before it goes anywhere.

Outbound cartons and channel-specific rates are detected but not yet priced. The engine sees them and reports them as uncovered rather than pricing them from a guess.

A charge that cannot be matched to a clause is reported as uncovered, not passed as correct. Unverifiable and wrong are different things, and the difference is reported.

Check it on your own invoice

Send a contract and one invoice. You get back what the engine found, including the claim letter, whether or not you become a customer.

It is the one claim on this page you do not have to take on trust. Every finding arrives with the clause it came from and the arithmetic that produced it, against an invoice you already have in front of you.