Building a Defensible Evidence File for a Notice or Dispute
Chronology, document indexing and the Bharatiya Sakshya Adhiniyam's electronic-evidence certificate — what a real evidence file needs.
Building a Defensible Evidence File
A well-argued reply built on a disorganised or uncertifiable document set is still a weak reply.
ExplainerWorked example1. Why the evidence file matters as much as the legal argument
A notice reply or a court filing is only as strong as the documents behind it. A correct legal argument attached to an unindexed folder of scanned emails and undated screenshots invites exactly the kind of scrutiny that turns a defensible position into a contested one. The discipline below applies whether the matter is a GST show-cause notice, an Income Tax reassessment, or a civil dispute — only the substantive law changes; the standard for organising and certifying the underlying facts does not.
2. The Bharatiya Sakshya Adhiniyam, 2023 — what changed for electronic records
The Bharatiya Sakshya Adhiniyam, 2023 (BSA) came into force on 1 July 2024, replacing the Indian Evidence Act, 1872 in its entirety. Section 63 of the BSA is the direct successor to the old Section 65B of the Evidence Act and governs the admissibility of electronic records — emails, WhatsApp messages, ERP exports, digitally signed filings, CCTV footage and similar records. It retains the earlier requirement that such a record be accompanied by a certificate, but Section 63(4) adds a materially stricter dual-certification requirement: the certificate must now be signed both by the person responsible for the device or system that produced the record and by an independent expert, given in two parts (Part A completed by the party producing the record, Part B by the expert) using the format set out in the Schedule to the BSA. A litigation or notice-response evidence file assembled without this certificate risks the underlying electronic records being challenged on admissibility grounds, regardless of how relevant they are on the facts. It follows that the device or system that generated a record relied upon — the email server, the accounting or ERP system, the CCTV recorder — should itself be identified and retained in usable condition for as long as the matter is live, since the certificate speaks to that specific device or system and cannot later be produced against one that has since been replaced or wiped.
3. Building a chronology and document index
Every evidence file should open with a chronology table, not a narrative — a table forces every fact to carry a date and a document reference, which is exactly what a reviewing officer, tribunal or opposing counsel will look for first.
| Column | Purpose |
|---|---|
| Date | The actual date the event occurred, not the date it was discovered or discussed internally |
| Event | One factual sentence — what happened, who did it, to whom |
| Document reference | The specific document proving the event occurred as described |
| Annexure number | A single, consistent numbering scheme used identically in the chronology, the reply, and the physical or digital file itself |
The single most common defect in a self-assembled evidence file is inconsistent annexure numbering — a document called "Annexure 4" in the reply but filed as "Annexure 4A" or left unlabelled in the actual folder. This sounds minor until a reviewing authority cannot locate the document the reply relies on, at which point the argument built on it effectively disappears from consideration.
4. Authority and approvals belong in the file too
Where a company is a party, the evidence file should independently establish who had the authority to act — a board resolution or power of attorney authorising the signatory, and proof that the person who actually signed a document, email or filing held that authority on the date in question. This is a distinct question from whether the underlying transaction was proper, and reviewing authorities frequently test it separately. The board and shareholder resolution module in the Legal Drafting Hub covers how these authorisations should be drafted in the first place.
5. Reconciliation statements as evidence
For a tax matter in particular, a reconciliation statement is often the single most persuasive document in the file — because it shows the underlying numbers agree with each other rather than merely asserting that they do. A GST reconciliation between GSTR-3B, GSTR-2B and the books of account, or a bank-to-ledger reconciliation, converts a bare claim ("our input tax credit was correctly claimed") into a demonstrable one. An unreconciled mismatch, left unexplained in the evidence file, is one of the most common reasons a technically correct legal argument is still rejected on the facts.
6. A worked example
A company facing a GST Section 74 demand assembles its evidence file in this order: a chronology table covering the disputed period; a GSTR-3B/GSTR-2B/books reconciliation identifying and explaining every variance rather than only the ones favourable to the company; the underlying contracts and e-way bills for the specific transactions questioned in the notice; the correspondence trail with the counterparty, each item BSA Section 63-certified where produced from an email system or ERP; and a signed authority document confirming who is responding on the company's behalf and since when. Each item carries the same annexure number in the file, the chronology, and the reply drafted using the Notice Reply Structure Builder on this hub — so a reviewing officer can move from any paragraph of the reply straight to the exact supporting document without a separate index.
7. Q&A
| Question | Finin2min answer |
|---|---|
| Does every WhatsApp message or email need a BSA Section 63 certificate? | Where the electronic record itself is being relied on as evidence — rather than merely referenced in passing — yes, the certificate should be obtained; the dual-signature requirement under Section 63(4) applies to the record's admissibility, not to how important the message seems. |
| Is a reconciliation statement itself "evidence," or just a working paper? | Once relied on to support a submission, it becomes part of the evidence file and should be dated, referenced by annexure number, and retained in the same disciplined manner as any other document — not treated as an internal draft that can stay informal. |
| What is the most common reason a well-argued reply still fails? | Inconsistent or missing annexure references, and an unreconciled numerical variance left unexplained — both are evidence-file defects, not defects in the legal argument itself. |
Finin2min Crux
Build the chronology and annexure index before drafting a single argument, certify every relied-upon electronic record under BSA Section 63(4)'s dual-signature format, and reconcile the numbers rather than merely asserting they are correct — an evidence file that fails on any of these three points can undermine an otherwise sound legal position.
Source log
- Bharatiya Sakshya Adhiniyam, 2023 (Section 63, in force from 1 July 2024) — India Code
- India Code — Central Goods and Services Tax Act, 2017 (Sections 73, 74, for the worked example) — India Code
- MCA — Companies Act, 2013 (authority and board-resolution questions) — Companies Act page