How to Prepare for a Quality of Earnings Review (and Why the Work Starts a Year Early)

A quality of earnings review doesn't grade your company. It grades your records. The buyer isn't asking whether you run a good business. They're asking one much narrower question: is the EBITDA you're claiming real, repeatable, and backed by something other than your word.

That distinction changes what you should do about it. You can't improve a QoE outcome in the four weeks after someone signs an LOI. By then the trailing twelve months are already written, and the diligence team is just reading them back to you.

Quick definition, since people mix this up with an audit. A quality of earnings review is an independent analysis that tests whether reported EBITDA reflects sustainable, recurring earnings, by re-examining revenue recognition, expense timing, add-backs, and working capital.

The numbers, including the part nobody quotes

GF Data looked at 360 transactions closed since Q3 2024 and found that sellers who ran their own sell-side QoE averaged 7.4x TEV/EBITDA, against 7.0x for sellers who didn't.

Read the fine print, though. That lift concentrated in deals above $50 million of enterprise value. Smaller deals didn't see much of a bump. So if you're a $15M business, buying a sell-side QoE is not a magic half-turn on your multiple.

The more useful number in the same reporting is the adoption gap. Around 90% of PE-backed deals come with a sell-side QoE, because sponsors treat it as standard playbook. Only about half of founder-led lower middle market companies commission one. That gap tells you who gets surprised during diligence and who doesn't.

The honest read: paying for a QoE doesn't raise your price. Being the kind of company that survives one does.

What a QoE actually digs into

Revenue recognition and cut-off

This is where most of the damage happens, and it's rarely fraud. It's usually a business that recognizes revenue when it invoices instead of when it earns.

Long-cycle work is the classic trap. If you do commercial roofing, construction, or any multi-month project work, revenue should track percent of completion against costs incurred. Plenty of lower middle market companies don't track that well, so their margins bounce around by month for no operational reason. A diligence team sees lumpy margins and doesn't assume the best. They normalize, and normalizing almost never moves in your favor.

Add-backs, and which ones actually survive

Everyone knows the fun add-backs. The owner's car, the boat, the family member on payroll who doesn't work there. Those are usually fine, because the expense genuinely won't carry into new ownership.

The ones that die are the vague ones. "One-time" costs that showed up in three consecutive years aren't one-time. A restructuring charge with no supporting documentation is just a cost. The test isn't whether the expense felt unusual to you. It's whether you can hand someone a document that proves it won't recur.

Keep an add-back log as the year happens, with the invoice or memo attached to each entry. Reconstructing that log from memory eighteen months later is how good add-backs get thrown out.

Working capital, the part that quietly costs real money

Most sellers focus on EBITDA and multiple and forget that working capital is a separate, very literal transfer of cash. You agree to deliver a normal level of working capital at close. Miss it and the purchase price adjusts dollar for dollar.

As one advisor put it, if you said you'd deliver $100 and you deliver $80, your price drops by $20. That's not a negotiation. It's arithmetic in the purchase agreement. The peg gets set from your trailing monthly balances, which means the months you weren't paying attention are the months that set your target.

Margin consistency, month by month

Buyers pay more for boring. A company with 34%, 33%, and 35% gross margin across three quarters reads as a real operating pattern. One with 41%, 22%, and 38% reads as either a mess or an accrual problem, and the QoE will go find out which.

The surprises that aren't really accounting

A QoE frequently turns up things that have nothing to do with EBITDA quality. Sales tax you never collected in a state where you'd established nexus. A lawsuit whose expected cost was never recorded. Inventory that piled up during a supply scramble and never got written down.

None of these are unfixable. All of them are much cheaper to fix on your own schedule than to discover in week three of exclusivity, when every problem doubles as leverage.

What's the difference between an audit and a QoE? An audit asks whether your financial statements comply with accounting standards. A QoE asks whether your earnings are sustainable and what a buyer can actually expect to repeat next year. You can pass an audit and still have a rough QoE, which surprises a lot of owners.

Why the work starts a year out

A QoE examines a trailing twelve month period, usually month by month. You can't retroactively create a clean monthly cut-off. If your December was heavy because you pushed invoices out the door before year end, that's visible, and it's visible in a way that makes the diligence team wonder what else moved.

Advisors generally suggest starting a sell-side QoE three to six months before a process. That's fair advice for the report itself. But the report only reads what your books already say. The reporting discipline it depends on takes about a year to build, because it needs roughly twelve consistent months to look at.

So the real preparation isn't hiring the QoE firm earlier. It's making sure that when they show up, the trailing twelve months tell one coherent story.

What that looks like in practice

Close the books on a real calendar every month, same cut-off rules each time, so no month is special. Track revenue by customer and by product monthly, not just in the annual roll-up, because concentration and mix are the first two questions anyone asks. Keep working capital components on a monthly trend instead of checking them at year end. Log add-backs with documentation as they occur. And reconcile the operational numbers you report to your board against the accounting numbers, so you're not walking into diligence with two versions of the same year.

None of that is exotic. It's just monthly discipline, which is exactly the thing that slips when finance is one overloaded controller and a founder signing contracts.

A QoE is a mirror. It doesn't make your company better or worse, it just shows the buyer what's actually there, in higher resolution than you're used to seeing. The time to like what you see is before you're standing in front of it. Plametrix builds and runs that monthly reporting layer as an outsourced FP&A function, so the trailing twelve months hold up when someone finally goes looking.