How Leaki is built
Four decisions the product turns on.
These are the load-bearing choices, the ones that decide what Leaki can and cannot do, before any feature is discussed.
The auditor's view, on your own books
An internal team cannot see the ledger the way an outside auditor does, all at once, unattached to the decisions that produced it. Leaki reads your full transaction history in a single pass and reports what that view surfaces: duplicates, overcharges, credits nobody drew down, subscriptions still billing on retired services.
Read-only, always
Leaki connects with read-only OAuth scopes to QuickBooks, Xero, and Zoho Books. It has no write permission and cannot post, edit, or delete a transaction in your books under any circumstance. The corrective action is always yours to take, in your own system.
Paid out of what it recovers, not what it charges
Leaki charges 15% of money it actually recovers for you, invoiced only after the refund or credit lands. There is no seat count, no minimum, and no annual contract. An empty audit costs you the ten minutes it took to connect.
Every finding traces to a rule and a row
Detection is 45 deterministic rules across accounts payable and bank statements, then a reasoning pass for context and severity. Every finding carries its rule ID and its source transactions, so any controller can verify a claim in seconds rather than trusting a score.
Connections
Live today, in progress next.
- QuickBooks Online
- Xero
- Zoho Books
- Stripe
- SAP
- NetSuite