A GST defence assembled after a notice is slower, weaker and more expensive than a monthly evidence file.
Quick View
Close every tax period with source records, reconciliations, exceptions and named owners.
Create monthly folder template.
GSTR-1 and 3B files.
Screenshots only.
Why It Matters
The vault should reproduce every material figure in GSTR-1 and GSTR-3B and every major ITC or legal judgement.
Source files should be retained in exportable form rather than screenshots alone. Portal acknowledgements and signed or downloaded documents matter.
Exceptions should show the issue, amount, owner, action date and closure evidence.
Control Framework
| Area | What to establish | Operating rule |
|---|---|---|
| Returns | Filed forms and ARN. | Lock final versions. |
| Output | Invoices, IRN and e-way bills. | Reconcile turnover. |
| Input | 2B, purchases, RCM and reversals. | Track eligibility. |
| Issues | Notices, refunds and legal positions. | Maintain chronology. |
Action Checklist
- Create monthly folder template.
- Download portal files.
- Save signed reconciliations.
- Index high-value invoices.
- Maintain exception register.
- Back up offsite with access controls.
Practical Example
Evidence to Keep
- GSTR-1 and 3B files.
- Electronic ledgers.
- Purchase and 2B reconciliation.
- IRN and e-way data.
- RCM and refund files.
- Exception and legal-position register.
Warning Signs
- Screenshots only.
- Overwriting monthly workings.
- No document owner.
- Files stored in employee email.
- No link between return and evidence.
Detailed Review
GST control should connect five records: commercial contract, tax invoice, movement or service evidence, accounting entry and portal return. A filing that cannot be traced back to all five records is difficult to defend.
Every reconciliation should have a clear opening balance, current-period additions, corrections, reversals, payments and closing balance. Avoid unexplained plugs that make the total match but do not identify the invoice or legal reason.
Portal data is important but not conclusive by itself. GSTR-2B, e-invoice, e-way bill and ledger data should be read with the statute, rules, notifications, contracts and actual supply evidence.
Keep original source files and final filed versions. Screenshots help explain a portal event but should not replace downloaded returns, JSON, signed invoices, acknowledgements or bank records.
For material exposure, prepare a written position memo stating facts, issue, law, alternatives, conclusion, amount and approval. The memo should record uncertainty rather than hide it.
Management should review high-value exceptions monthly with owner and due date. A tax process is incomplete until the correction, payment, refund or response is acknowledged.
Annual return preparation should begin from locked monthly reconciliations rather than rebuilding twelve months of data.
Escalation Route
Start with the GST portal record, responsible business owner and tax working. Where the issue is operational, correct the source system and retain the acknowledgement. Where it is legal or disputed, obtain a reasoned professional position before payment, reply, refund or appeal.
Track the statutory or portal deadline separately from internal approval. Preserve helpdesk tickets, ARN, hearing requests, orders and payment records so a later reviewer can reproduce the entire path.
Transaction Test
Before filing or replying, prepare a one-page issue sheet showing GSTIN, tax period, transaction type, amount, applicable provision, portal form, evidence owner and due date. This prevents different teams from solving different versions of the same problem.
Reconcile tax by CGST, SGST, IGST and cess rather than only by total. A total can match even when the wrong tax head, state or period has been used, which can still create interest, cash-flow and customer-credit consequences.
Build an exception register with five statuses: identified, evidence pending, vendor or customer action, tax treatment approved and closed. Every exception should retain its original amount even after correction so the audit trail remains visible.
Test the position against the counterparty’s records. Customer ITC, vendor GSTR-1, transporter data, marketplace statements and bank receipts can expose differences that are invisible in the taxpayer’s own ledger.
The final approval should record who reviewed the legal position and who approved the return, reply, payment, refund or appeal. Material GST decisions should not remain buried in informal email chains.
Select a monthly sample of high-value and unusual transactions and trace them from contract to return. Sampling often identifies master-data errors before they become annual mismatches.
Maintain a legal-change register for notifications, circulars and portal advisories with effective date, impacted process and system change owner.
Common Questions
How long should records be kept?
Follow GST record-retention requirements and preserve longer where proceedings remain open.
Should every invoice be stored?
Maintain complete source records with an index and high-risk review.
What makes a vault useful?
The ability to reproduce return figures and explain exceptions quickly.
Who should own it?
Finance or tax should own the process, with inputs from operations, sales and procurement.
Official Sources
Use the latest Act, Rules, notifications, circulars, portal advisories and transaction documents. GST outcomes depend on facts, dates and the law applicable to the period.