Quality of Earnings, Explained for Fintech Founders
· 7 min read · by Michael Kaminski
What a Quality of Earnings (QoE) analysis actually looks at, why fintech QoE is different, and how founders can be ready before a buyer or lender runs one.
If you're heading toward a raise, a sale, or a credit facility, someone is going to run a Quality of Earnings analysis on your business. Founders often hear "QoE" and picture a normal audit. It isn't. An audit asks "are these numbers correct?" A QoE asks a sharper question: "how much of this profit is real, repeatable, and transferable?"
What a QoE actually digs into
- Revenue quality: Is it recurring or one-time? Concentrated in a few customers? Recognized correctly under ASC 606? For a lender, is the interest income durable or juiced by a vintage that hasn't seasoned yet?
- EBITDA adjustments: Which "add-backs" are legitimate (truly one-time) and which are a founder trying to flatter the number? This is where most of the negotiation happens.
- Working capital: What's the normal level needed to run the business, so the buyer isn't surprised post-close?
- Run-rate vs. reported: What does the business earn going forward, not what it happened to report last year?
Why fintech QoE is its own animal
In fintech, the "earnings" question collides with credit and accounting judgment. Loss reserves (ASC 326 / CECL), the treatment of loan origination fees, how you account for a servicing asset, and the seasoning of a loan book all move EBITDA materially — and they're all judgment calls a diligence team will stress-test. A vintage of loans that looks profitable at month three can look very different at month eighteen. If your data model can't slice performance by vintage, cohort, and product, you'll be answering these questions manually under time pressure, and that erodes buyer confidence fast.
How to be QoE-ready before anyone asks
- Keep a clean, monthly-close discipline with a documented revenue-recognition policy.
- Maintain a defensible reserve methodology you can walk through, not just a plug.
- Instrument your platform so cohort/vintage performance is a query, not a fire drill.
- Pre-build your own "adjusted EBITDA" bridge — know your add-backs and be able to defend each one.
- Reconcile your product/ledger data to your financials continuously, not at year-end.
The founders who sail through QoE are the ones whose finance and engineering were built together, so the numbers a diligence team asks for already exist in the system. If you want a pre-diligence read on where your story is strong and where it's thin, let's talk.