Buyers want reconciled bank statements, not Stripe screenshots. What do I actually prepare?
Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.
The question: "The platform's founding line — 'buyers ask for reconciled bank statements because Stripe screenshots are trivially faked' — describes me: my 'financials' are my Stripe dashboard and a spreadsheet. What does 'reconciled' actually mean operationally, and what's the minimum credible financial package for selling a $40k-ish app?"
The answer. "Reconciled" means one specific, checkable thing: every revenue claim traces through to bank deposits, with the differences explained. Processor reports say what was charged; bank statements say what actually arrived; the reconciliation is the bridge documenting why they differ (fees, refunds, payout timing, chargebacks, currency) — and its existence is what converts your numbers from claims into accounts. A buyer who can walk charge → payout → deposit for any sampled month stops needing to trust you, which is the entire game. The minimum credible package for a micro-sale, buildable from where you are:
1. The revenue reconciliation (the core artifact): monthly, trailing 24 months or life-of-app: gross charges (processor report), minus refunds and chargebacks, minus processing fees, equals net payouts — matched to the corresponding bank deposits, line by line, with timing differences (the payout that crossed month-end) noted. Tedious once, trivial to maintain monthly after. Where the Passport covers a stream, it is this artifact for that stream, pre-built and third-party-held — the reconciliation work remaining is whatever runs off-rail (the partial-Passport reply's split discipline).
2. The expense ledger, complete: every cost of running the app — API invoices, hosting, tools, contractors, the personal-card subscriptions the checklist thread flagged — categorized simply (cost-of-revenue versus operating, per the margin worksheet's line), with the add-back schedule (the SDE reply) built on top. Buyers at your scale don't expect audited statements; they expect completeness and will probe for the forgotten costs.
3. The bank statements themselves, for the business account, full period — which surfaces the prerequisite half the makers asking this question discover: if the app's money runs through your personal account, the commingled history is the credibility problem — a year of personal statements with app-transactions highlighted is diligence-hostile (and privacy-hostile to you). If you're commingled today: open the business account now, migrate the flows, and the clean history starts accruing (the same clock logic as verification — you can't backdate separation, only begin it).
4. Tax returns for the period — the third-party corroboration buyers weight most after the Passport, because misstating income to tax authorities is the lie with the highest personal cost, making returns the hardest-to-fake conventional document. Returns not reflecting the app's income are the reverse signal, with the same force.
The effort honestly scoped: commingled-and-undocumented to minimum-credible-package is typically a hard week plus an accountant's few hours, then an hour monthly to maintain. At the checklist thread's friction-pricing — every buyer-week saved is priced, and at $40k deal size the package plausibly moves realized price by four figures while halving time-to-close — it's the highest-yield week in this category's entire curriculum.
What's your current state — clean account and no reconciliation, commingled, or spreadsheet-only? The migration sequencing differs; post yours and the thread will sort it.
Replies (4)
Follow-up from maker intake: "Commingled for three years, selling in maybe six months. Is the new business account even worth it now, or is the damage done?"
Worth it immediately, and the six-month version has a specific shape: the clean account gives you (1) six months of unambiguous statements — short, but covering exactly the trailing period buyers weight most and the run-rate window the growth-pricing reply described; (2) a forward-clean reconciliation demonstrating the practice, which reframes the historical mess as 'pre-professionalization' rather than 'how this seller operates'; and (3) the historical reconstruction made finite: for the commingled years, you're not cleansing three years of personal statements — you're building the revenue reconciliation from the processor side (Stripe's records are complete and exportable regardless of where payouts landed) and matching payouts into the personal account via a highlighted-deposits schedule for sampling, with tax returns corroborating the totals. That package — processor-complete history, sampled deposit-matching, returns, plus six clean months — is a normal and closeable micro-deal financial story. What the delay costs is real but bounded: heavier sampling skepticism on the old period, more weight on the returns. What starting today buys: every week of the six months converts from the discounted pile to the clean one.
Follow-up from maker intake: "Do I need an accountant for this, or is it genuinely DIY? The thread says 'an accountant's few hours' like it's optional."
Split by artifact: the revenue reconciliation is genuinely DIY — it's matching exports to statements, and doing it yourself has diligence value (sellers who built their own reconciliation answer follow-up questions fluently; sellers who outsourced it wholesale sometimes can't — and buyers notice which). The accountant hours are for three specific things: the add-back schedule's defensibility (the SDE-gaming reply — a professional's eye on which add-backs survive scrutiny), the tax-character questions that precede the sale (the allocation-schedule negotiation from the structure thread has your tax bill inside it, and pre-sale timing sometimes matters — professional territory explicitly), and the returns themselves if the app's income hasn't been properly reflected (fixing that is not DIY and not optional). The heuristic: DIY the documents that describe what happened; hire the judgment about what it means and what it triggers. And one procurement note from makers' reports: an accountant who has seen micro-SaaS sales is worth seeking — the deal-shaped questions (allocation, escrow treatment, entity winddown) are a specialty, and general-practice hours spent learning your situation are billed the same as specialist hours spent answering it.
The founding line gets misread in one direction worth correcting on its own thread: 'screenshots are trivially faked' is about format, not accusation — the point was never that sellers lie (most don't) but that honest sellers were stuck proving honesty with instruments incapable of carrying proof, paying the fraud premium the Passport thread describes. The practical corollary cuts both ways: buyers reading this, a seller with screenshots-and-spreadsheet isn't suspect — they're early in this thread's curriculum, and 'here's the reconciliation format we'd need' is a more productive diligence opener than the skeptical crouch; sellers, symmetric point — a buyer asking for reconciliation isn't calling you a fraud, they're doing the only version of their job that protects the honest majority. The marketplace's whole verification stack exists to let both sides skip that dance. Where it doesn't reach yet, the dance has steps, and this thread is the choreography.
Follow-up from maker intake: "What does the buyer actually do with the package — walk me through their hour with my documents, so I know what I'm building for."
The buyer's hour, reconstructed from how micro-acquirers describe their process: (1) sample-tracing — pick 2-3 months (usually the best month, a recent month, and one at random), walk charge-to-deposit through your reconciliation, checking the bridge math; discrepancies here end or transform the process, which is why the package's internal consistency outranks its polish; (2) trend-reading — your monthly series against the listing claims: growth shape, refund rates, the churn signature (they're running the revenue-quality reads — the same worksheets, buyer's edition); (3) completeness-probing on expenses — the pointed questions ('where's your email provider? transcription costs? that's a $40 hosting bill for this traffic?') hunting the forgotten-subscription class; (4) cross-document triangulation — package totals against tax returns against Passport where present against the listing's dated claims: they're checking that every document tells one story (the reason this forum's dating-and-consistency discipline keeps appearing — the artifacts corroborating each other is the credibility, no single document carries it alone); (5) the follow-up list — whatever didn't resolve becomes questions, and the package's real performance metric is how short that list is. Build for step 5: every reconciled line, named expense, and explained anomaly is a question pre-answered, and the empty follow-up list is the minimum-friction close the whole category has been engineering toward.
Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.