Working capital peg disputes are one of the most predictable sources of late-stage deal friction — yet most buy-side teams only engage with the mechanics after a seller's number has already landed on the table. This episode of VDR.ai reframes the peg not as a closing-week negotiation but as a diligence workstream that should begin the moment data room access is granted, with a defensible counter-position built before the seller's proposal ever arrives.

The episode walks through the structural reasons seller-proposed pegs systematically favor the sell side, and the specific analytical moves that give buyers the upper hand. Key topics covered include:

• Why seller-presented pegs are rarely neutral. The choices embedded in a trailing average — which months are included, how line items are classified — compound quietly and can shift the effective deal price in ways that look reasonable on a summary schedule.
• Seasonality as a negotiating lever. Month-by-month balance sheet analysis across at least 18–24 months exposes whether a proposed peg overweights high-receivable periods, an advantage buyers miss when they look only at annual figures.
• Classification drift and one-time items. Accruals that are genuinely operational versus those tied to litigation reserves or transaction-related bonuses can artificially depress the historical average peg — invisible unless the buyer rebuilds the calculation from underlying line items.
• Payables timing manipulation. Tracking days payable outstanding across the full monthly data series reveals whether a seller stretched vendor payments in the pre-signing window, inflating delivered working capital in a way the historical average never anticipated.
• Building a parallel framework before the seller's number lands. Teams that enter the peg conversation with their own classification definitions — not a reaction to the seller's — shift from defending a gap to comparing two legitimate methodologies.

The episode also touches on how diligence Q&A workflow discipline — logging payables anomalies and pressing on them directly — keeps the analysis on record and prevents findings from slipping through the cracks. For teams managing large volumes of financial documents across the monthly balance sheet series, cross-document reconciliation can surface inconsistencies across periods that manual review would likely miss. And for a broader framework on how buy-side teams structure the full diligence process, the M&A due diligence guide is a useful companion resource.

More from the show: if you found this episode useful, the earlier instalment Seller Management Accounts: How to Read the Numbers Behind the Numbers covers how to interpret the financial narrative sellers present before the peg conversation even begins — a natural precursor to the analysis discussed here.

VDR.ai

Audited financials are built for external audiences. Management accounts are built for the people actually running the business. When a deal team treats those two sets of numbers as interchangeable, they risk missing the most important signals in the data room. This episode of VDR.ai explores how to use seller management accounts as a live diligence tool — not just a box to check — and what the gap between internal and audited figures really tells you about a business.

The episode covers the structural reasons management accounts diverge from audited financials, and how to exploit that divergence to surface risk early. Key topics include:

• Purpose-driven differences: Audited accounts reflect consensus after the fact; management accounts reflect how the operator was thinking in real time — and that distinction shapes everything you should be looking for.
• Profitability definitions: When the seller's internal EBITDA consistently runs ahead of the audited figure, the adjustments driving that gap deserve direct scrutiny — legitimate normalising items look very different from recurring costs dressed up as one-offs.
• Pattern mapping, not point-in-time reconciliation: Comparing a single period is not enough. A consistent gap across twelve months is explainable; a gap that widens sharply in the final two or three periods is a specific red flag warranting its own Q&A thread.
• Cost timing errors: Management accounts often log costs on payment or invoice date rather than accrual, which can silently distort a normalised EBITDA bridge — tracing two or three major cost lines through both sets of accounts before building the model is a straightforward safeguard.
• The early-warning system hiding in plain sight: The metrics a finance team chooses to track month-to-month reveal what the business believes matters most — and a management pack that has grown thinner or less granular in the run-up to a sale is itself a data point worth probing.
• Sequencing the work: Pulling management accounts early — in parallel with audited financials, not after — lets deal teams set sharper questions before the CFO meeting, using diligence Q&A to capture and track those threads systematically.

The broader takeaway is about sequencing and framing: the audited accounts describe what the business agreed had happened; the management accounts describe what the business believed was happening while it was happening. Running both tracks together, and using tools like cross-document reconciliation to surface inconsistencies automatically, gives deal teams a materially sharper picture before they sit down with management. For teams who want to go further, the AI risk register provides a structured way to log and prioritise the gaps that emerge from exactly this kind of parallel analysis.

For more on navigating seller disclosure documents, listen to Seller Disclosure Letters: How to Read the Carve-Outs That Carry the Real Risk — a natural companion to this episode.

VDR.ai

Disclosure schedules are the part of a deal package that receive the least scrutiny and carry the most consequence. While rep and warranty negotiations dominate the attention of most deal teams, the disclosure letter is where the seller has already limited their exposure — item by item, schedule by schedule. This episode of VDR.ai unpacks the mechanics of reading seller disclosure letters as the adversarial documents they actually are, and what disciplined practitioners do differently.

The episode covers the structure, strategy, and hidden risk embedded in disclosure schedules, including:

• How disclosed items transfer risk: Once a seller lists something on a schedule, it is no longer a warranty breach — it is an accepted carve-out, making early, thorough schedule review essential before any pricing or renegotiation conversation.
• Reading schedules against the data room, not just the reps: Each disclosed item should be traced back to its source documents; gaps between what is listed and what the underlying materials suggest are the real diligence target.
• Strategic bundling of disclosures: Sellers sometimes place items on schedules where they are least likely to trigger scrutiny — an employment matter buried under a contracts schedule, for instance — making it critical to read the disclosure letter as a whole document, not schedule by schedule in isolation.
• Materiality qualifiers and the invisible class of undisclosed items: When reps are scoped by materiality, sellers may have knowingly omitted items they judged immaterial; data room documents that look disclosable but appear on no schedule are a key signal worth flagging.
• Building a delta record: For every disclosed item where the source documents tell a larger story, practitioners should log the specific schedule reference and the corresponding data room evidence in a risk register — creating the paper trail needed if the point becomes a renegotiation lever at close.

The episode frames the disclosure letter not as the seller's confession but as the seller's defense — and argues that the discipline of cross-document reconciliation between schedules and underlying data room materials is where experienced teams consistently find the risk that junior reviewers miss. Tracking those findings systematically in the AI risk register ensures that nothing discovered in the schedules gets lost before it can influence deal terms. Teams running structured diligence workflows can also use diligence Q&A to formally request source documents when a disclosed item has no corresponding backup in the data room — creating a timestamped record of every outstanding question.

For additional context on the rep and warranty side of this analysis, the episode Rep and Warranty Review: How to Read the Schedules Before You Read the Reps covers how to sequence that review before diving into the disclosure letter itself. The full M&A due diligence guide on VDR.ai offers practitioner-level guidance across the complete diligence workflow.

AI Virtual Data Room