financial-diligence
Financial Diligence
The Quality of Earnings report directly dictates final purchase price adjustments and protects buyers from overpaying for inflated performance. This skill automates the foundational labor of financial due diligence.
When to Use
- Performing a Quality of Earnings analysis on a target
- Validating management-proposed EBITDA adjustments
- Reconciling trial balances against audited financials and tax returns
- Identifying off-balance-sheet liabilities and debt-like items
- Analyzing net working capital for purchase agreement peg negotiations
Quality of Earnings Report Structure
| Section | Focus |
|---|---|
| Quality of Earnings Summary | Bridge between reported and run-rate adjusted EBITDA |
| Revenue & Margin Analysis | Customer concentration, product mix, volume vs. price trends |
| EBITDA Adjustments | Validate or refute each management add-back |
| Net Working Capital (NWC) | Historical peg calculation, seasonality, aged receivables, obsolete inventory |
| Debt and Debt-Like Items | Off-balance-sheet liabilities, deferred revenue, unpaid bonuses, unfunded capex |
AI-Assisted Workflow
Trial Balance Reconciliation
- Ingest trial balances, audited financials, bank statements, and tax returns (3-5 year lookback)
- Map granular account codes to standard FDD analytical groupings
- Reconcile across data sources, flagging discrepancies
- Detect anomalies — sudden expense spikes, unusual journal entries near deal launch
EBITDA Adjustment Analysis
For each proposed management add-back:
## EBITDA Bridge
### Reported EBITDA: $[X]M
| # | Adjustment | Amount | Category | Defensibility | Notes |
|---|-----------|--------|----------|---------------|-------|
| 1 | Owner excess compensation | $[X]K | Recurring normalization | HIGH | Benchmarked against market rate |
| 2 | One-time litigation | $[X]K | Non-recurring | HIGH | Settlement confirmed, no ongoing exposure |
| 3 | "COVID impact" | $[X]K | Disputed | LOW | Revenue decline appears structural |
| ... | ... | ... | ... | ... | ... |
### Adjusted EBITDA: $[X]M
### Buy-Side Recommended EBITDA: $[X]M (variance: $[X]K)
Net Working Capital Analysis
## NWC Peg Analysis
### Trailing 12-Month Average NWC: $[X]M
| Component | Avg Balance | Seasonality | Flags |
|-----------|------------|-------------|-------|
| Accounts Receivable | $[X]M | [Pattern] | [Aged AR > 90 days: $X] |
| Inventory | $[X]M | [Pattern] | [Obsolete: $X] |
| Prepaid Expenses | $[X]M | | |
| Accounts Payable | ($[X]M) | | [Stretched beyond terms?] |
| Accrued Liabilities | ($[X]M) | | |
### Recommended NWC Target: $[X]M
### Mechanism: [Dollar-for-dollar adjustment / collar]
Operating Guidelines
- Always validate management's reported EBITDA independently — never accept at face value
- Distinguish between truly non-recurring items and items management wishes were non-recurring
- Flag revenue recognition policy changes during the lookback period
- Identify related-party transactions and verify arm's-length pricing
- For NWC, exclude cash and debt from the calculation unless specified in the purchase agreement
- AI outputs are analytical aids — the subjective debate over valid add-backs requires human judgment
- Time saved: automates tie-out process that traditionally takes 40+ hours
Examples
Input: "Run a QoE analysis on this target's three-year P&L."
EBITDA bridge output:
| Item | Amount | Type |
|---|---|---|
| Reported EBITDA | $18.2M | — |
| + Owner salary above market | +$1.2M | Non-recurring |
| – One-time insurance recovery | –$0.8M | Non-recurring |
| – Understated capex (lease restructure) | –$1.4M | Run-rate |
| Adjusted EBITDA (QoE) | $17.2M | — |
Finding: Reported EBITDA overstated by $1.0M (5.5%) — material enough to impact valuation by ~$10M at 10x multiple.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Trial balance doesn't tie to P&L | Accounting errors or plug entries | Request a full GL export; flag any journal entry >5% of EBITDA without documentation |
| Working capital peg disputes | Different normalization methodologies | Align on peg definition (12-month average vs. spot) in the LOI |
| Revenue recognized incorrectly | ASC 606 misapplication | Engage accounting advisors for revenue recognition memo |
| Hidden liabilities in debt schedule | Off-balance-sheet items | Request all operating leases, earnouts, and contingent liabilities |
More from lauraflorentin/skills-marketplace
multi-agent-collaboration
A structural pattern where multiple specialized agents communicate and coordinate to solve a problem that is too complex for a single agent. Use when user asks to "build a multi-agent system", "agents working together", "agent collaboration", or mentions team of agents, distributed agents, or swarm.
21reflection
A recursive pattern where an agent evaluates and critiques its own output to iteratively improve quality and catch errors. Use when user asks to "add self-reflection", "agent introspection", "self-critique", or mentions self-evaluation, meta-cognition, or quality self-assessment.
18human-in-the-loop
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
16planning
A high-level cognitive pattern where an agent formulates a structured sequence of actions (a plan) before executing any of them, ensuring goal-directed behavior. Use when user asks to "add planning to my agent", "task planning", "agent planning", or mentions plan generation, plan execution, or step-by-step planning.
14parallelization
A concurrency pattern where multiple agent tasks are executed at the same time to speed up processing or gather diverse perspectives. Use when user asks to "run agents in parallel", "parallelize tasks", "concurrent execution", or mentions parallel processing, fan-out, or batch execution.
13routing
A control flow pattern where a central component classifies an input request and directs it to the most appropriate specialized agent or tool. Use when user asks to "route between agents", "agent routing", "task dispatch", or mentions classifier routing, intent detection, or agent selection.
12