Leakproof starts with two CSVs: contracts and invoices. It runs locally in the browser and surfaces potential missing-invoice or underbilling candidates with source-row evidence.
For finance teams: before you would use something like this during month-end close, what would you need to see? Examples: contract-line provenance, invoice-status handling, currency controls, reviewer sign-off, export format, or an audit log.
The demo is synthetic, and findings are review candidates not claimed recovered revenue. I m using the answers to shape the first design-partner workflow.
Leakproof compares contracts.csv with invoices.csv locally in your browser, then flags potential missing invoices and underbilling for human review. No integrations, no AI guessing, and no financial-data upload. Every candidate links back to source rows. The public demo uses synthetic data; findings are opportunities to investigate, not claimed recovered revenue.
