Seventy-Two Hours to Prove It: Why US Companies Collapse Under India's GST Audit Documentation Demands

The Clock Starts Before You Know It's Running

There is a particular kind of institutional shock that settles over a US finance team when they learn that an Indian GST audit has already begun — not when the auditor schedules a formal review, but when documentation is first requested on-site. Under India's GST audit framework, the moment an authorized officer issues a notice or initiates an inspection, a countdown begins. In many circumstances, that window is 72 hours or fewer. For companies whose Indian compliance records live in fragmented systems, or whose decision-making authority sits in a US time zone, 72 hours is not a deadline. It is a trap.

At RajExcise Advisors, we work with US-headquartered organizations operating in India across manufacturing, technology, pharmaceuticals, and consumer goods. One pattern appears with striking consistency: the companies best positioned to survive an Indian GST audit are not the ones with the cleanest compliance history — they are the ones with a documented response protocol. The companies that struggle are those treating audit preparation as something to address after the auditor arrives.

What GST Auditors Actually Request in the First 72 Hours

Understanding the scope of an initial GST audit document request is the first step toward preparing for one. Indian GST authorities are not conducting a casual review of summary financials. They are examining the mechanical integrity of your tax positions — specifically whether the credits you claimed, the exemptions you applied, and the returns you filed accurately reflect the underlying transactions.

In the opening phase of a GST audit or inspection, auditors commonly request:

• GSTR-1, GSTR-3B, and GSTR-9 filings for the period under examination, along with reconciliation workpapers demonstrating that reported figures align across returns
• Input tax credit (ITC) registers showing each credit claimed, the corresponding vendor invoice, and evidence that the credit was properly matched in the GSTN portal
• E-way bill records for goods movement, including documentation confirming that physical movement aligns with what was reported
• Purchase and sales ledgers in a format that can be cross-referenced against GST returns
• Original tax invoices from vendors whose credits are under scrutiny, particularly for high-value transactions
• Contracts or agreements that establish the commercial basis for intercompany or related-party transactions where tax treatment may be questioned
• Import documentation, including Bills of Entry and IGST payment records for goods brought into India

For a US company operating an Indian subsidiary, assembling this documentation in 72 hours requires that every item already exists, is properly organized, and can be accessed by someone with the authority to release it — ideally without waiting for a 9:00 a.m. approval call from a US executive who is asleep when the request arrives.

The Three Failure Modes US Finance Teams Repeat

When US companies fail during the 72-hour window, the failure typically traces back to one of three structural problems.

The first is document custody fragmentation. Many US-owned Indian subsidiaries operate with their accounting records split across local ERP systems, cloud platforms managed from the US, and physical files maintained by a local CA firm. When an auditor requests a specific vendor invoice from 18 months ago, no single person knows where it is. The scramble that follows does not inspire confidence, and auditors notice.

The second is authority bottlenecks. Indian compliance teams are often empowered to prepare documents but not to release them to government authorities without US headquarters approval. When the subsidiary's finance manager needs sign-off to hand over an ITC register and the CFO in Chicago is in back-to-back meetings, the clock keeps running. A pre-authorized response protocol — one that defines exactly what documents can be released, by whom, and under what circumstances — eliminates this bottleneck entirely.

The third is reconciliation gaps that only surface under pressure. GSTR-1 and GSTR-3B reconciliation is a routine compliance requirement, but many US-managed operations allow minor discrepancies to persist across filing periods without resolution. These discrepancies are invisible in normal operations. Under audit, they become the first question an officer asks — and if the answer is not immediately available, the audit's tone shifts.

Deemed Non-Compliance: What Happens When the Window Closes

The consequences of failing to respond within the required timeframe are not merely procedural. Under India's GST law, an inability to produce documentation on request can result in the denial of input tax credits, the imposition of interest and penalties on disputed amounts, and in serious cases, the issuance of a show-cause notice that formally asserts tax evasion. These outcomes are not automatic, but they are well within an auditor's discretionary authority when a taxpayer appears unprepared or uncooperative.

For US companies, the financial exposure can compound quickly. A single audit covering two or three fiscal years, with denied ITC claims across multiple vendors, can generate liability that dwarfs the original compliance cost of proper recordkeeping. The penalties themselves can range from a fixed percentage of the disputed tax to amounts equal to the full tax liability, depending on how the non-compliance is characterized.

Building a 72-Hour Response Protocol Before You Need One

The most effective preparation is not reactive — it is structural. US companies operating in India should treat the 72-hour audit window as a design constraint, building their compliance infrastructure around the assumption that a document request can arrive on any business day.

A practical response protocol includes the following elements:

1. A centralized document repository — all GST returns, ITC registers, vendor invoices, and reconciliation workpapers stored in a single, searchable system accessible from both India and the US without delay

2. A named response coordinator — a designated individual within the Indian operation who holds pre-authorized authority to gather and present documentation to auditors without requiring real-time US approval

3. Pre-reconciled filing records — a standing practice of reconciling GSTR-1 and GSTR-3B at the close of each filing period, with documented explanations for any discrepancy exceeding a defined threshold

4. An audit notification chain — a defined sequence of internal notifications triggered the moment an audit or inspection commences, ensuring that US headquarters is informed within hours rather than days

5. Periodic dry runs — at least once annually, a simulated document request exercise in which the response team assembles a representative set of audit documents against a defined time target

The Preparation Gap Is a Business Risk, Not a Compliance Detail

US companies sometimes treat Indian GST compliance as an operational footnote — a recurring cost managed by local staff and reviewed annually by an external auditor. That posture is sustainable until an audit begins. At that point, the absence of a preparation protocol transforms a manageable compliance review into a crisis that can absorb weeks of executive attention, generate significant financial exposure, and damage the subsidiary's relationship with Indian tax authorities for years.

The 72-hour window is not an anomaly in Indian tax enforcement. It reflects a broader philosophy within the GST regime: that compliant taxpayers maintain their records in a state of continuous audit readiness. US companies that internalize this expectation — and build their compliance infrastructure accordingly — are not just better prepared for audits. They are operating with a fundamentally lower risk profile across every dimension of their Indian tax obligations.

RajExcise Advisors works with US-headquartered organizations to assess their Indian GST audit readiness, identify documentation gaps before they become enforcement vulnerabilities, and design response protocols that function across time zones and organizational hierarchies. If your Indian operation has never tested its ability to respond to a document request in 72 hours, that test is worth conducting on your schedule — not the auditor's.