Skip to content

Five steps from a fresh OAuth connection to recovered money. Read-only, evidence-backed, and always yours to send or ignore.

01

Connect your accounting system

Sign in with OAuth to QuickBooks Online, Xero, or Zoho Books. Leaki requests read-only scopes only and cannot post, edit, or delete a transaction in your books.

Two minutes end to end. The refresh token is stored encrypted; revoke it in your accounting provider and Leaki loses the ability to read.

02

Leaki audits your full history

On first connect, Leaki pulls every invoice, bill, payment, credit memo, and vendor record. Forty-five deterministic rules and a Gemini reasoning pass run across the whole population, not a sample.

Typical first audits cover 24 to 36 months. A ledger with 50,000 line items finishes in about fifteen minutes.

03

Findings arrive ranked by severity

Every finding lands in the dashboard with the source transactions, the rule ID that flagged it, a recommended action, and a dollar figure. Severity is calibrated against your ledger, not an industry average.

You see the evidence, not just the alert: two invoice IDs, a diff, the vendor's contract clause, and the exact amount recoverable.

04

Recover with drafted disputes

For every recoverable finding, Leaki drafts a dispute letter or credit request pre-filled with the vendor's contact, the invoice numbers, and the amount overpaid. You send it. You remain the party in the conversation.

Nothing leaves your outbox without your action. Leaki never sends on your behalf.

05

Keep watching with continuous audit

After the historical pass, Leaki keeps re-auditing as your ledger changes. New transactions are checked in near real-time and you get an email the moment a critical finding appears.

Set thresholds per severity. Route findings to email, or leave them in the dashboard for a weekly review.

Security posture

Read-only by design, encrypted end to end.

Leaki is built so that even a total compromise of Leaki cannot cost you a dollar in your books. It never has the ability to move money because it never has the ability to write.

AccessRead-only OAuth2 to QuickBooks, Xero, Zoho Books
StorageAES-256 at rest, TLS 1.3 in transit
TenancyIsolated per-workspace data
RetentionDelete your workspace and data purges in 24 hours
AuditabilityEvery finding traceable to its source transactions
Write scopeNone. Leaki cannot alter a transaction under any circumstance

Questions

The things finance teams ask first.

Can Leaki change anything in my books?

No. Leaki connects with read-only OAuth scopes and has no write permission. It cannot post, edit, or delete a transaction in QuickBooks, Xero, or Zoho Books under any circumstance.

How far back does the first audit look?

By default, everything your accounting provider exposes, usually 24 to 36 months of history. You can shorten the window in settings if you only want the most recent quarters.

What if the audit finds nothing?

You pay nothing. Leaki is contingency-priced at 15% of what it actually recovers for you. An empty audit costs you the ten minutes it took to connect and nothing else.

Who has access to my data inside Leaki?

Only the users you invite to your workspace. Support cannot read your ledger without an explicit break-glass authorisation you approve in the app.

Ready to run the first audit?

Connect your books in two clicks. Findings start appearing as the scan progresses, and you pay nothing unless money is recovered.