An evidence index should connect each point in a GST notice to the exact record supporting the reply. Give every annexure a stable identifier, meaningful description and page or transaction reference. A large attachment folder is not an evidence index if the officer and reviewer must guess which document answers which allegation.
Start with the notice’s issue structure
Read the notice and annexures into an issue sheet. Preserve the paragraph number, period, amount and question asked. If one paragraph contains several allegations, split them into separate working rows while retaining the original reference.
Decide what fact each proposed document proves. An invoice supports what was billed; a goods-receipt record supports receipt; a bank record supports a payment movement. None automatically proves every legal condition for input credit or the correct tax treatment.
The index should support an issue-wise explanation, not substitute for it. Write a short conclusion for each issue, then identify the records that let a reviewer verify that conclusion.
Preserve originals and label working copies
Keep original downloaded notices, filed returns and source records unchanged in an archive. Create clearly named working copies for annotations, page numbering and compilation.
When converting spreadsheets to PDF, retain the native workbook with formulas and a dated export. A printed total without the underlying calculation can be difficult to review when one invoice changes.
Distinguish filed returns from drafts, internal summaries and portal previews. The label “GSTR-3B” is not enough if the file does not establish which GSTIN, period and filing status it represents.
An illustrative evidence index
A Ludhiana manufacturer is explaining a ₹1,26,000 sales-tax difference. Its working identifies timing and amendment items that need independent support.
| Annexure | Evidence | Notice link | What it supports |
|---|---|---|---|
| A1 | Filed return extracts by period | Paragraph 2 | Original reported amounts |
| A2 | Invoice-level reconciliation | Paragraph 2 | Bridge between compared totals |
| A3 | Six amended invoices and filing references | Paragraph 2(a) | Location of later corrections |
| A4 | Payment debit and liability records | Paragraph 2(b) | Treatment of identified tax payments |
| A5 | Unresolved-item schedule | Paragraph 2(c) | Matters requiring further review |
These are illustrative categories, not a conclusion that the whole ₹1,26,000 is explained. The index should distinguish supported explanations from outstanding questions rather than presenting every attachment as proof of success.
Give numerical workings a reproducible trail
Show the starting figure, adjustments and closing figure. Every adjustment should have a transaction key and annexure reference. Keep positive and negative signs consistent throughout the reply.
Suppose the reconciliation includes ₹54,000 attributed to later-period reporting. The supporting row should identify the original invoice, original period, later return period and filed amendment reference. A narrative saying “timing difference” without those details is incomplete.
Avoid unexplained netting. A ₹20,000 overstatement and ₹20,000 omission can cancel in the total while involving different invoices and legal consequences. The index should preserve both gross items.
Page and name the documents consistently
Use a logical naming convention such as Annexure A3, invoice list, pages 14–21, without placing unnecessary sensitive details in filenames. Keep annexure labels identical in the reply, index and uploaded documents.
For large bundles, add a contents page and bookmarks where the format allows. Check that a reviewer can reach the cited invoice quickly. A page reference should identify the final compiled file, not a page number from an earlier draft.
Keep the total page count and document version in the submission checklist. Late additions can shift page numbers and leave the reply pointing to the wrong record.
Handle gaps honestly
Mark missing or pending evidence explicitly, with the responsible person and action. A vendor’s promise to send a document is different from the document being available.
Where a record cannot be recovered, explain the actual limitation and assess alternative evidence with the adviser. Do not manufacture a retrospective receipt note or present a newly created statement as a contemporaneous record.
If an annexure contains an estimate or management explanation, label it accurately. Original records, calculations and explanations serve different roles and should remain distinguishable.
Respect the filing route’s actual limits
GSTN’s notice guidance shows that replies and attachments are filed within the relevant case workflow. Check the live module’s permitted file types, sizes and number of attachments before final compilation; limits can differ by proceeding.
Do not assume that emailing a file to someone replaces required portal filing. Where an additional submission route is directed or used, retain the authority, delivery evidence and exact material supplied.
Open every final upload locally and inspect legibility. Small invoices, landscape spreadsheets and scanned stamps often become unreadable after compression.
Protect relevant information without obscuring evidence
Include the details needed to establish the transaction and taxpayer identity. Avoid attaching unrelated employee or customer information merely because it shares a spreadsheet with the relevant records.
Any redaction should preserve the evidence needed for the issue and follow the adviser’s assessment. Do not conceal a relevant date, tax identifier or amount while claiming the document proves the transaction.
Freeze the submitted set
After approval, save the exact reply, index and annexures that were filed, together with the acknowledgement. Later working revisions should carry a new version and must not overwrite the submitted record.
A strong index makes the reply verifiable: each allegation has a clear answer, each answer has evidence and each evidence reference leads to the right record. That is more useful than submitting the largest possible bundle.