Founders & Startups7 min read

Bookkeeping for Startups Using Stripe and Mercury

How to keep clean books when money moves through Stripe and Mercury—payout timing, fees, and the categories investors expect to see.

Financial dashboard with graphs on a computer screen

Stripe and Mercury are the default money stack for a huge slice of US startups. Stripe collects customer payments; Mercury holds cash and wires vendors. Simple until you try to reconcile them in QuickBooks and realize payouts lag charges by days, fees hide inside net deposits, and your bookkeeper has no idea what "Stripe balance transaction" means.

Good bookkeeping here isn't about fancy tools. It's about consistent rules: how you recognize revenue, how you map Stripe fees, and how you prove cash on your balance sheet matches Mercury statements investors can trust.

This article covers a practical workflow founders and bookkeepers use every month. Not tax or accounting advice for your specific books.

How money actually flows

Customers pay via Stripe. Stripe deducts processing fees and holds reserves if applicable. Stripe initiates payouts to Mercury on a rolling schedule—often T+2 business days in the US, but delays happen with disputes or account reviews.

Your books need to show gross revenue, processing fees as an expense (or net presentation, but be consistent), and cash hitting Mercury when payouts land—not when customers click pay.

Chart of accounts basics

Typical setup: a Stripe clearing asset account, Mercury checking, revenue by product line, Stripe fees in payment processing expense, and refunds/chargebacks contra-revenue or expense depending on policy.

Avoid dumping everything into "Sales" without fee separation—investors will ask about gross margin, and you won't have a clean answer.

Monthly reconciliation steps

Pull Stripe's balance activity export for the month. Match gross charges, refunds, and fees. Tie payouts to Mercury deposits line by line. Anything unmatched sits in clearing until you find it—usually timing at month-end.

Reconcile Mercury to your GL cash account. Every vendor payment (Gusto, AWS, Linear) should be categorized. Use rules for repeat merchants but spot-check new ones—founders love one-off SaaS trials that auto-renew.

Tools and integrations

QuickBooks Online and Xero both integrate with Stripe; Mercury syncs via Plaid or CSV. Tools like Puzzle, Ramp, or dedicated bookkeepers add automation layers. None remove the need for human review on equity, accruals, or weird edge cases.

Pick one source of truth for revenue recognition. If you bill annual subscriptions upfront, you may need deferred revenue schedules—even if Stripe shows the full charge on day one.

Common mistakes founders make

Booking revenue when cash hits Mercury instead of when earned. Ignoring Stripe fees entirely. Mixing personal Mercury transfers with operating expenses. Forgetting to record Stripe refunds in the month they occur.

Another classic: two cofounders both expensing the same AWS bill because reimbursements aren't tracked. Fix with a single company card policy and monthly review.

Key takeaways

  • Track gross revenue, fees, and payouts separately—don't conflate Stripe charges with Mercury deposits.
  • Use a Stripe clearing account and reconcile it monthly against balance activity exports.
  • Annual prepay and subscriptions may need deferred revenue even if cash arrives upfront.
  • Automate imports but keep a human review for accruals, equity, and month-end timing gaps.

This guide is for general education only and is not tax, legal, or accounting advice. Rules change, and your facts matter. Talk to a qualified professional before filing or making equity decisions.

Related guides