Financial Due Diligence

The Problem

A buy-side financial due diligence engagement on a mid-market Indian target typically lands in the deal team's inbox as a 600–1,200 file data room: audited statements, ITR-6 returns, Form 3CD, bank statements across 8–14 accounts, debt schedules, AR and AP agings, revenue contracts, and a cap table that may or may not foot to the share capital note. A senior associate spends 60–90 hours classifying documents, keying numbers into Excel, and chasing reconciling differences before the QoE work even begins.

The break point is volume. A target with 50–500 active customers, 100+ vendors, and three years of monthly bank statements produces extraction work that does not parallelize across a four-person team without errors. Numbers get transposed, the FY24 provisional trial balance gets compared to the FY23 audited balance sheet, and a 51 lakh accrued interest variance under Ind AS 109 gets buried in a tab called "Debt v3 final FINAL".

By the time the diligence report goes to the IC, the team has spent 70 percent of its hours on document plumbing and 30 percent on judgment. Material exceptions — a cap table that doesn't foot to issued capital, related-party receivables hidden in the 90+ AR bucket, revenue recognized on a straight-line basis against milestone contracts under Ind AS 115 — surface late or not at all.

Why It Matters: Context

Financial due diligence is governed by the diligence team's own quality standards rather than a single external regulation, but every workpaper in the file must reconcile to source documents that are regulated: financial statements under Ind AS or US GAAP, audit reports under SA 700, external confirmations under SA 505, related-party disclosures under Ind AS 24, revenue under Ind AS 115 / ASC 606, and the share register maintained under Section 88 of the Companies Act, 2013. A diligence verdict that cannot be traced to those sources is indefensible in front of a lender's counsel or an investment committee.

Mid-market targets compound the problem. Most have no consolidation system, no contract repository, and a finance team of four to seven people who produce schedules in Excel with manual links. Provisional management accounts for the latest stub period sit alongside audited statements for the prior year, and the differences are rarely documented. The diligence team is expected to identify and quantify those differences anyway.

When a diligence report misses a debt variance, an unrecorded related-party exposure, or a revenue recognition gap, the cost is not a comment letter — it is a price chip the buyer cannot make, an indemnity the SPA does not cover, or a closing condition that fails on day 90 post-signing.

What This Workflow Automates

1. Ingests the entire data room and classifies each file into one of ten document types — FINANCIAL_STATEMENTS, AUDIT_REPORT, TAX_RETURNS, BANK_STATEMENTS, DEBT_SCHEDULE, AR_AGING, AP_AGING, REVENUE_CONTRACT, CAP_TABLE, DD_CHECKLIST — using the description and structural fingerprint of each document, not filename heuristics.
2. Extracts the line items each diligence area requires: revenue, EBITDA, working capital, and cash flow from financial statements; opinion type and emphasis-of-matter paragraphs from audit reports; principal, interest rate, and maturity from debt schedules; aging bucket totals from AR and AP; performance obligations and acceptance clauses from revenue contracts; share class, count, and percentage from the cap table.
3. Validates each document against its own internal arithmetic — debit equals credit, aging buckets sum to total, cap table percentages sum to 100, debt principal plus accrued interest equals carrying amount under Ind AS 109 EIR.
4. Cross-references documents against each other: debt schedule against bank statement closing balances and lender confirmations under SA 505, AR aging customer names against cap table shareholders to surface Ind AS 24 related-party gaps, revenue contracts against recognized revenue under Ind AS 115 / ASC 606 performance obligations, cap table fully diluted count against the share capital note in the financial statements, ITR-6 taxable income against audited book profit with the Form 3CD reconciliation.
5. Issues a per-area verdict — PASS, FAIL, or NEEDS_REVIEW — for each of equity, debt, revenue, working capital, tax, and audit coverage, with the reconciling difference quantified and the regulation cited.
6. Generates an exception schedule that lists every variance with its source documents, the page reference inside each, and a recommended follow-up (external confirmation request, share register under Section 88, missing tax audit report, QoE adjustment).
7. Produces a DD checklist update mapping each item in the original information request to the document that satisfied it, the verdict, and the open items.

All of this happens in roughly 90 seconds per data room with deterministic outputs every controller can audit.

Edge Cases We Simulate

The workflow ships with a battery of synthetic test scenarios that exercise every failure mode we have seen in real-world data. Each scenario produces a deterministic outcome that an auditor or controller can verify in seconds.

Sample Documents

Download or inspect the seeded sample files used to demonstrate this workflow:

Sample Results

On a representative buy-side data room, the workflow classifies the document set across the ten registered types, extracts every line item the diligence template requires, and issues area-level verdicts in under two minutes. A typical run surfaces six distinct exception classes: a 51 lakh debt variance attributable to accrued interest under Ind AS 109 EIR that the management schedule excluded, a 2,52,300-share reconciling difference between the cap table fully diluted count and the issued and paid-up shares in the share capital note, a 30 percent share of the 90+ AR bucket owed by common-control affiliates not disclosed under Ind AS 24, a revenue recognition gap on milestone-based contracts recognized straight-line in violation of Ind AS 115 paragraph 35, an FY24 provisional trial balance lacking an SA 700 opinion, and an ITR-6 to book profit delta of 1.7 Cr without a Form 3CD reconciliation.

The exception class diligence teams most often miss in manual review is the cap table to share capital note difference — the workflow breaks the 2,52,300-share gap into ESOP pool, SAFE conversions, and unallotted warrants, and opens a checklist line for the share register maintained under Section 88 of the Companies Act, 2013, before the associate has finished reading the audit report.

Why Automation Wins Here

A diligence engagement that consumed 60–90 associate hours of document classification and extraction is reduced to roughly two minutes of compute plus four to six hours of judgment review on the exception schedule — an 85 percent reduction in cycle time and the elimination of transcription errors that account for most workpaper rework. Each variance carries a quantified amount, the source documents, the regulation cited, and a recommended follow-up.

The output drops directly into the diligence file as a structured exception schedule, a per-area verdict log with PASS, FAIL, or NEEDS_REVIEW reasoning, and an updated DD checklist mapping every information request to the document that closed it. The IC memo references the schedule by line number, the SPA disclosure list pulls from the FAIL items, and the post-closing integration team inherits a workpaper that traces every number back to the data room file and page where it was found.

Frequently Asked Questions