About
Why I built ClearDeposits
A note from the founder.
I am Ammar Haleem (LinkedIn), a senior product leader with 12 years in finance systems, most recently at Amazon, where I led payments and reconciliation products that moved hundreds of billions of dollars across millions of transactions. I have worked both sides of the ledger: configuring the books and building the tools. One product I led enabled pre-reconciliation: accountants cleared timing variances and known open items, and the close moved a day earlier. I hold a degree in computer science and an MBA.
What I kept seeing at month-end inspired ClearDeposits. Accountants and small businesses are stuck between two bad options. Context-less matching tools add reconciliation and context-switching overhead: you still have to work out what they did and why. Enterprise suites are so flexible, and so focused on accounting alone, that they know nothing about a standard business, so everything has to be configured and setup takes months.
ClearDeposits is the system in between. It does not claim to know everything about your accounting or everything about your business. It knows just enough of both to be up and running in a few minutes, and it puts every variance in front of you, so you save time on onboarding and on reconciliation, and close earlier.
I designed it with fractional CFOs, accountants and business owners around one conviction: you already know your business. Nothing hidden, nothing guessed, and nothing posted without your say.
ClearDeposits is live, with the first two months free. Write to me at ammar@cleardeposits.com.
Principles
What it is built around
Rules you can read
Every line lands on an account through a rule built from Stripe products, prices and metadata. You set the rules and their priority. The rule that placed a line is shown with the line.
Nothing posted without your say
The draft plan sits in the subledger until you approve it. Change an account or a match and the plan redrafts, with the change recorded.
Variances named, before the ledger
Charges less deductions are tied to each payout, the balance is tied to what Stripe reports, and payouts are matched to the bank. A difference is listed by its cause.
Closed means closed
A closed month is not edited or deleted. A correction is a new entry in the current period, linked to the original.
Limits stated first
Stripe only. A monthly summarised CSV for QuickBooks Online; posting straight into it is work in progress. No bank feed yet. US only. No SOC 2 audit yet.
How it is built
The engine, in plain terms
A subledger, not a pipeline
ClearDeposits keeps its own balanced debits and credits for every charge, fee, refund, dispute, payout and deposit, in a chart of accounts you map to QuickBooks Online. That is what lets it know what Stripe holds, what is in transit and what the bank has received.
Daily pulls through a restricted key
A Stripe key with read access and report generation, tested before it is stored, encrypted at rest, never shown again. Pulled daily at an hour you choose. Or CSV exports, through the same checks.
Keyed by Stripe id
Every row is keyed by its source id. Pulling again or re-uploading a file never creates a duplicate, and a posting is never sent twice.
Three bases, one setting
Accrual, cash when it reaches the bank, or Stripe's 1099-K basis (available-on date; timing only). Every component is dated by the chosen rule, and a change of basis takes effect from a date you choose, after a preview.
Hosted in the US
Amazon Web Services, behind Cloudflare, with the database reachable only from the application. Every infrastructure change goes through reviewed code.
Try it on a real month.
No card to start. US only.