Features

Everything between the charge and the cash.

Policy, mapping, reconciliation and review in one subledger.

Accounting policy

Accrual, cash or Stripe 1099-K basis
Recognise revenue when the sale happens, when the cash reaches the bank, or on the Stripe 1099-K basis (available-on date; timing only): when Stripe makes the funds available, the date the form is reported on. One setting, applied consistently.
Discount mapping
Present discounts on their own line or net them, and choose where they post. Revenue and promotions each land where they belong.
Refunds and tax on refunds
Reverse a refund proportionally across the sale's products, tax and shipping, or as a lump sum to contra-revenue. Tax follows the sale it came from.
Period cutoff enforced
Revenue and the Stripe clearing asset are recorded in the month the charge belongs to, so that month closes cleanly. When the cash arrives in the next month, the subledger moves it from clearing to cash in the new period.

Revenue by product or service line
See and post revenue per Stripe product, class or service line, not one Stripe lump. $5,000 to SaaS subscriptions and $4,000 to professional services, each tied to the charges it came from.
Rules you can read
Stripe products, prices and metadata criteria. You set the rules and their priority.
Your chart of accounts
A role for every kind of money: revenue, discounts, refunds, fees, chargeback fees, clearing and suspense, alongside your own accounts, including deferred revenue liability. Each maps to a QuickBooks Online account.
Post to QuickBooks Online
At month end, one summarised accounting CSV, laid out by account and QuickBooks Online activity, for you to import into QuickBooks Online. Posting straight into QuickBooks Online is work in progress.
Bank fees and suspense, handled
A bank's cut posts to your bank-fee account and unexplained cash parks in suspense, automatically. Nothing gets plugged.
Summarised, so QuickBooks Online stays fast
One balanced entry per account and activity per month instead of thousands of individual transactions. The detail stays here, one click away.

Payouts matched to bank deposits
Payouts match deposits automatically within a tolerance you set, zero by default. Anything outside it is flagged, never forced.
Variance analysis
The gap between revenue, payouts and the bank is broken down by cause: timing, fees, refunds, chargebacks and open items. A $20 dispute inside a $5,000 payout is named as a $20 dispute.
Data lineage
Every figure opens to its exact source: the upload row or the Stripe object behind it. Audit questions answer themselves.
Balance tracking
Stripe's available and pending balances are read on every pull, rolled forward, and tied out against the balance Stripe reports before you close.
Manual payouts, explained
Stripe's reports do not itemise a manual payout. ClearDeposits associates each one with the charges it paid out when the amounts tie exactly, and otherwise shows it as Stripe reported it.
Open items tracking
Unmatched deposits, aging items, failed payments and failed payouts: one worklist of what still needs you.

A draft plan all month
With a restricted key, Stripe is pulled daily at an hour you choose and the draft posting plan is always current. Reconcile during the month, not only at the end.
Review, reclassify, approve
Change an account or a match and the plan redrafts. Record an adjustment with the account, side and date you choose. Approve the plan, then post and close.
Immutable once closed
A closed month cannot be edited or deleted. A correction is a new entry in the current period, so the lineage from checkout to bank deposit is never broken.
Nothing counted twice
Every transaction is keyed by its Stripe id. Re-uploading a file or pulling from Stripe again never creates a duplicate, and a posting is never sent twice.
Settings with an effective date
Tolerances, account roles, and discount and refund policies change from a date you choose, after a preview of what will move. Closed history is never rewritten.
A trail for every change
Who changed what, when, and what it was before. Consequential changes go to a reviewer, or an audited self-review when you work alone.
A workspace per client
Each company is its own workspace under a single login, isolated from every other by the database itself.

On the roadmap

Stripe only, today. No dates promised.

Posting straight into QuickBooks Online (work in progress)
Native QuickBooks Online documents, such as sales receipts and deposits, after journal entries
Deferred revenue recognition
Bank feeds, so statements no longer need uploading
Connecting Stripe without a key, with near-real-time updates