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.
Love that every flag links back to the exact source rows. Makes it feel built for auditors who actually need to verify, not just take the tool's word for it.