The Invoice Nobody Can Dispute

A consulting firm in Tel Aviv invoices a manufacturer in Berlin for €87,000 split across three milestones. Standard B2B. Standard PDF. The firm has done dozens of invoices like this. The manufacturer has paid hundreds. Nothing about the transaction looks unusual at issuance.

Six weeks pass. Berlin's accounts payable runs into a question on the VAT line. €4,205 vs. €4,520 — a transcription difference of €315. Berlin's PDF says one number. Tel Aviv's PDF says the other. Both files were generated from the same accounting tool; both files were emailed; somewhere between the two send-times, one digit got transposed. Neither side can say which version was sent first. Neither side wants to absorb the loss.

The dispute escalates because nothing about a PDF can answer the question. PDF metadata records when each file was created or last edited; the metadata in this case is contradictory — Tel Aviv's file was edited an hour before Berlin's claim of receipt, Berlin's file was edited two hours after that, "to fix a typo." Mediation is requested. Lawyers retained on both sides. The dispute drifts into the next quarter. Both sides are now spending more on the fight than the original disputed amount.

The signed-invoice version of the same scenario closes in two business days. Tel Aviv's accounting tool produces a signed invoice — the amount, the parties, the line items, the VAT calculation, the due date all bundled into a fingerprint and signed. Berlin receives the signed file. Berlin's accounts-payable team verifies the signature against Tel Aviv's published key. The verification succeeds or fails. If it succeeds, the number Berlin's team reads is, mathematically, the number Tel Aviv sent. If it fails, the file in Berlin's hands is not the file Tel Aviv issued. Either way, the dispute about "which version is real" stops being a dispute.

The asymmetry of cost is the lesson. The signed-invoice flow takes the Tel Aviv accountant ten extra seconds at issuance — one click. The unsigned-invoice flow takes both companies' lawyers six weeks combined and tens of thousands in fees. The signed-invoice flow has been operating in the cryptographic literature since the early 2000s; the tools have only been usable-by-accountants since around 2024. The technology was ready before the workflow was ready to absorb it.

The marketplace recipe for this is one of the most-installed in the GI catalogue. It plugs into common accounting tools — QuickBooks, Xero, Israeli SAP — and signs every invoice as a side effect of "send." The recipient sees a normal-looking PDF with a small footer that reads "verifiable at /verify with hash …"; their accountant clicks the link, the hash matches, the dispute window closes before it opens. The accounting team's workflow does not change. The accounting team's lawyers stop being on retainer for invoice disputes.

"I have a different version" used to be a defense. In every market that has crossed the signed-invoice threshold — they're early but they exist — the defense doesn't survive contact with mathematics. Money is too important to send as a picture. Sign the invoice. End the dispute before it begins.