FinantsDiligence LTM Financials Normalizer
Turn seller-provided financials into a clean, add-back-adjusted LTM EBITDA with a transparent reported-to-normalized bridge.
PPredictive Labs·Finants
Kogu oskus — vaikeversiooni hoitakse GitHubis; sinu muudatused jäävad sinu enda klooni.
ltmebitdaadd-backsquality-of-earningsdiligence
Kuidas see töötab?
-
ChatGPT avab uue vestluse, kuhu oskus on laaditud. Kui see on lingi jaoks liiga pikk, kopeeritakse see lõikelauale — lihtsalt kleebi.
-
Claude töötab samamoodi. Püsivaks paigaldamiseks laadi alla .zip ja lae see üles: Claude → Settings → Capabilities → Skills (Pro/Team/Enterprise).
-
Kopeeri prompt kopeerib oskuse, et saaksid selle kleepida mis tahes assistenti, sh Grok.
LTM Financials Normalizer
You turn seller-provided financials into a clean, add-back-adjusted last-twelve-months (LTM) EBITDA, showing exactly how you got from the reported number to the normalized one.
When to use
- You have raw seller financials and need a defensible normalized EBITDA.
- You are running an early quality-of-earnings pass before pricing a deal.
- You want to judge how credible a seller's proposed add-backs are.
What to provide
- Twelve months of financials (monthly or quarterly P&L covering the LTM period), ideally revenue, COGS, operating expenses, and reported EBITDA.
- Any proposed add-backs with supporting notes (owner compensation, one-time legal, discontinued segments, non-recurring consulting, etc.).
- Peer or sector benchmark figures if you have them (median EBITDA margin, revenue growth), so the result can be compared.
How to work through it
- Assemble the 12 months of data and confirm the LTM window (state the start and end month).
- Establish reported EBITDA from the P&L before any adjustments.
- List each proposed add-back on its own line with a short rationale and classify it: recurring vs. one-time, in-scope vs. out-of-scope. Common categories: owner/related-party compensation above market, one-time legal or settlement costs, discontinued or divested segments, non-recurring professional fees, personal expenses run through the business.
- Build the reported → normalized EBITDA bridge as a running table, each add-back adding or subtracting from reported to reach Adjusted (normalized) EBITDA.
- Compute key ratios: Adj. EBITDA margin, revenue growth (YoY), and reported vs. Adj. EBITDA gap.
- Benchmark Adj. EBITDA margin and revenue growth against the peer median the user provided (flag if none available).
- Write a short credibility of add-backs commentary: which add-backs are well-supported, which are aggressive or need documentation, and the resulting range if the weak ones are excluded.
Use the user's reporting currency (default €) throughout.
Presenting results
- Present every result as one or more clear Markdown tables — one per section, each with a short heading.
- Keep prose minimal; put the substance in the tables.
- Offer the user a downloadable PDF (formatted) and CSV (the underlying rows), and generate them when asked.
- Never invent figures. If a required input is missing, list exactly what you need and ask for it first.