Financial due diligence india work has a structural blind spot built into its own name: the exercise is defined around reviewing financial statements, but the exposures that most often destroy post-acquisition value are, by definition, not fully visible in those statements. They surface instead in notes, correspondence files, and regulatory databases that a standard review may never touch. Three categories account for a disproportionate share of the acquisitions that face real value destruction after closing, and understanding why each one evades a conventional review matters more than knowing the categories exist in the abstract.
An acquirer who discovers an undisclosed tax demand or a provident fund shortfall eighteen months after closing is rarely dealing with a target that lied outright. More often, the exposure was sitting in a notes disclosure, a pending correspondence file, or a regulatory database the original acquisition due diligence never checked, because it was technically outside the scope of a financial statement review as most teams define it.
The three categories, and why each one hides from a standard review
Indirect tax disputes that have not yet become confirmed demands. Pending GST audit assessments, Show Cause Notices, and pre-GST excise or service tax disputes before CESTAT or the High Courts sit in the tax correspondence file, not in the financial statements, unless a demand has already been confirmed and provisioned. For any dispute relating to tax periods up to FY 2023-24, the relevant framework is CGST Act Sections 73 (non-fraud short payment) and 74 (fraud or suppression). For FY 2024-25 onwards, both were replaced by the newly consolidated Section 74A, introduced by the Finance (No. 2) Act, 2024, which governs demands for underpaid tax, wrongly availed input tax credit, and erroneous refunds regardless of whether fraud is alleged. A target’s exposure frequently spans both regimes, an older dispute still working through Sections 73 or 74 alongside a fresher one that will fall under 74A, and a review that only asks about “GST notices” in general terms, without checking correspondence against both frameworks and their different timelines, can miss which years remain genuinely open to further assessment. The same care applies to direct tax exposure: a target’s income tax position should be checked against the amended reassessment window under Section 149, not an assumed limitation period that may no longer reflect current law.
Employee benefit scheme shortfalls that have not been recognised as liabilities. Provident fund contribution disputes, ESIC liability determinations for contract labour that was not correctly classified as covered employment, and gratuity fund actuarial shortfalls that were never properly provisioned all fall under this category. The governing statute here is the Employees’ Provident Funds and Miscellaneous Provisions Act, 1952, administered by the Employees’ Provident Fund Organisation; the two are often conflated, but EPFO is the administering body, not the source of the legal obligation itself. Contract labour misclassification is a particularly common and expensive version of this exposure, since a target that has treated a large contract workforce as outside its PF and ESIC obligations for years can face a retrospective liability determination covering that entire period once the classification is challenged.
Environmental and regulatory licence conditions in breach. Emission limit violations with pending closure notices, factory licence conditions that have been breached over multiple reporting periods, and pollution control board orders that were never escalated into the financial statements as a disclosed matter all fall here. These exposures are structurally invisible to a financial review because they originate entirely outside the finance function; the people managing environmental compliance rarely interact with the people preparing statutory accounts, and a closure notice sitting in a plant manager’s file may never reach the data room unless someone specifically asks for it. A target’s environmental compliance history is often tracked, if at all, at the individual plant or facility level rather than consolidated centrally, which means a due diligence request for “any pending environmental notices” addressed only to the CFO’s office can return a clean answer that is accurate as far as it goes but incomplete as a picture of the target’s actual exposure.
What “off-balance-sheet” actually means, and why IND AS 37 does not fix this
Off balance sheet liabilities india exposures exist because the accounting framework itself distinguishes between obligations serious enough to reduce reported profit and obligations serious enough only to require a footnote. Under IND AS 37 (Provisions, Contingent Liabilities and Contingent Assets), equivalent to IAS 37, a provision is recognised directly on the balance sheet only where three conditions are met: a present obligation exists as a result of a past event, an outflow of resources is probable, generally read as more likely than not, and the amount can be estimated with reasonable reliability. Where any of these conditions is not met, but the possibility of an outflow is more than remote, the obligation is disclosed as a contingent liability india matter in the notes rather than recognised as a liability on the face of the balance sheet. Disclosure is skipped entirely only where the possibility of outflow is genuinely remote.
This is precisely the mechanism that lets a target’s disputed tax demand sit in a footnote rather than on the balance sheet, without any accounting irregularity whatsoever. A company facing a disputed GST demand that its lawyers assess as merely possible rather than probable to succeed is following IND AS 37 correctly by disclosing it as a contingent liability in the notes rather than recognising it as a provision. The problem for an acquirer is not that the target did anything wrong; it is that a review limited to the balance sheet and profit and loss statement, without a complete read of every note, will never see this disclosure at all.
The verification protocol that actually catches these exposures
A financial due diligence checklist built to catch off-balance-sheet exposures needs to extend well past the financial statements themselves, and past what a purely accounting-trained review team would think to check on its own. Seven checks form the practical minimum, spanning both tax correspondence and non-financial regulatory records. First, review all correspondence from GST, income tax, customs, and excise authorities in the target’s records, checking against both the legacy Section 73/74 framework and the current Section 74A regime depending on the tax period involved, and confirming the target’s exposure to reassessment under the amended Section 149 of the Income Tax Act, which now sets a standard reassessment window of three years from the end of the relevant assessment year, extendable to ten years where the escaped income is estimated at Rs 50 lakh or more. Second, search the MCA21 portal for all company filings and any charges registered against the target. Third, check DRT and DRAT databases for any proceedings naming the target as defendant. Fourth, search the NCLT e-court system for pending IBC proceedings or Company Law Board matters. Fifth, check pollution control board records and other state-specific regulatory databases relevant to the target’s sector. Sixth, obtain management representations, backed by an indemnity or penalty clause, specifically addressing pending regulatory proceedings not otherwise disclosed. Seventh, review every arbitration clause in the target’s significant contracts and confirm whether any dispute is currently pending under one.
The regulatory databases a comprehensive review actually covers
A comprehensive m&a due diligence india exercise draws on a specific set of government and quasi-government databases beyond the financial statements themselves: the MCA21 portal for company filings, registered charges, and director disqualifications; the DRT e-court portal for debt recovery proceedings; the NCLT e-court system for insolvency and company law matters; the GSTN portal for outstanding returns and demands, where accessible; the income tax e-filing portal, accessed with the target’s authorisation, for outstanding demand and refund status; state pollution control board records; the Registrar of Companies annual filing database; Employees’ Provident Fund Organisation records; ESIC records; RERA registration and complaint records where the target holds real estate interests; and the national Consumer Forum database. No single source in this list substitutes for any other, since each captures a distinct category of exposure that the others do not.
Why these exposures are structurally hard to price, not just hard to find
Finding one of these three exposures during due diligence is only the first problem; the second, often harder problem is pricing it into the transaction. A confirmed tax demand has a fixed number attached to it and can be handled through a straightforward price adjustment or escrow. A pending Show Cause Notice under Section 74A, or a disputed GST audit finding that has not yet resulted in any order, has no fixed number at all: it has a range of possible outcomes, a probability distribution across those outcomes, and a timeline to resolution that is entirely outside the acquirer’s control. The same is true of a factory licence breach under review by a state pollution control board, where the possible outcomes range from a compounding fee to an actual closure order, with no way to know in advance which end of that range will materialise.
This is precisely why these exposures derail transactions rather than simply reducing the agreed price. A price adjustment mechanism generally requires a number both sides can agree to negotiate around; a genuinely open-ended contingent exposure resists that kind of negotiation, and deals frequently stall not because the acquirer found a problem, but because neither side can agree on how to price a problem that does not yet have a determinate size. The practical responses available, an indemnity with a survival period long enough to cover the likely resolution timeline, an escrow sized to a reasonable worst-case estimate, or in some cases a purchase price adjustment mechanism tied to the eventual outcome of a specific named proceeding, all require the exposure to have been identified with enough specificity, during diligence, for either side to structure around it at all. An exposure discovered after signing, when the only remaining options are renegotiation under pressure or litigation over the acquisition agreement’s representations, is a materially worse position for both parties than the same exposure identified and priced before signing.
Timing the review relative to the transaction timeline
The categories described above are also disproportionately likely to be missed when a due diligence review is compressed into a short window relative to the overall transaction timeline, a common pattern in competitive acquisition processes where a target is running a tight sale process across multiple bidders. Correspondence file reviews, regulatory database searches, and management representation negotiations each take real calendar time, and a review compressed to fit a shortened exclusivity period tends to preserve the financial statement analysis, since that work is well understood and can be scoped quickly, while the correspondence and database checks described above are the first items cut when time runs short. A recurring and avoidable pattern: acquirers who accept a compressed diligence timeline in a competitive process are taking on a specific, identifiable category of additional risk, not a generic increase in overall diligence risk, and structuring around that reality, whether through a longer exclusivity period, a phased diligence approach that front-loads the correspondence and database checks, or explicit risk allocation for the categories not fully reviewed, is a more useful response than treating a compressed timeline as an unavoidable cost of a competitive process. Acquirers who have been through this once tend to build the phased approach into every subsequent process by default, front-loading exactly the checks that a compressed timeline would otherwise sacrifice first, rather than relearning the same lesson on each new transaction.
What this means for structuring a due diligence engagement
None of the three categories above guarantees a material problem exists in any specific target, and a complete review across every source listed does not guarantee an outcome free of post-closing surprises; some exposures, particularly a regulatory proceeding filed after the diligence cutoff date but before closing, fall genuinely outside what any review conducted before that date could catch. What the pattern does support is a specific, practical adjustment to how a review is scoped: a financial due diligence engagement that stops at the audited financial statements and management representations has structurally excluded the three categories most likely to surface as value-destroying surprises after closing, not because the review was performed carelessly, but because those categories were never within its defined scope in the first place. Extending that scope to the notes, the correspondence files, and the regulatory databases listed above is not an enhancement to a standard review; for an acquisition of any real size, it is closer to the review a target’s actual risk profile requires.
Frequently asked questions
What are the most common off-balance-sheet exposures in Indian company acquisitions?
Three categories recur most often: indirect tax disputes under CGST Sections 73, 74, or the newer Section 74A that have not yet become confirmed demands; employee benefit shortfalls including provident fund and ESIC misclassification and unprovisioned gratuity liabilities; and environmental or regulatory licence breaches with pending closure notices or orders never escalated into the financial statements.
How do you identify contingent liabilities in a financial due diligence?
A minimum protocol includes reviewing tax authority correspondence against the applicable limitation period, searching MCA21 for filings and charges, checking DRT and NCLT e-court databases for pending proceedings, reviewing pollution control board records, obtaining indemnified management representations on undisclosed proceedings, and reviewing arbitration clauses in significant contracts for pending disputes.
What regulatory databases should financial due diligence cover in India?
A comprehensive review checks MCA21, the DRT and NCLT e-court portals, the GSTN and income tax e-filing portals with authorisation, state pollution control board records, the Registrar of Companies database, EPFO and ESIC records, RERA registration and complaints where applicable, and the national Consumer Forum database.
How does IND AS 37 govern contingent liability disclosure in Indian financial statements?
