An ITAT e-filing document checklist is useful only when it matches the selected proceeding and the live portal. A generic folder of tax records is not a filing set. The operator needs to know which order is challenged, which appeal subtype was selected, what the official matrix currently requests, and which reviewed version of each document belongs in the submission.
This article provides an operational control framework. It intentionally does not prescribe the documents required in every matter. The responsible professionals must consult the Income Tax (Appellate Tribunal) Rules, the Income-tax Act, current ITAT directions, and the live portal.
Which sources should control the document list?
Start with the official ITAT required-documents tool. Select the relevant Act, appeal type, and subtype, then save the resulting list with the date checked. The displayed requirements can differ with the procedural path. The ITAT e-Filing help page also links its practice note, instructions, and checklist.
Build a requirements register rather than pasting the list into an email:
| Requirement | Source and date checked | Matter document | Owner | Status |
|---|---|---|---|---|
| Portal-listed item | Official URL or notice | Stable file ID | Named person | Missing, draft, approved, uploaded |
| Rule-based item | Rule and version | Stable file ID | Named person | Review required |
| Matter-specific item | Counsel instruction | Stable file ID | Named person | Optional or approved |
If sources appear inconsistent, stop and escalate. Do not silently adopt the shortest list. Record the conflict, the professional decision, and the authority relied upon.
What belongs in the source-document inventory?
Inventory every candidate document before choosing upload files. Common categories may include the impugned order, proof of communication, assessment order, earlier appellate materials, Form 36 data, grounds, fee evidence, authorisation, limitation material, applications, and supporting affidavits. Whether any item is required depends on the matter and current procedure.
For each file, capture:
- exact document title and date;
- issuing authority and proceeding reference;
- assessment year and party identifiers;
- source location and person who obtained it;
- original format, page count, language, and legibility;
- signature, certification, or authorisation status;
- confidentiality and personal-data classification;
- relationship to a portal requirement; and
- approved upload filename and checksum, if used.
The inventory should expose duplicates. Two PDFs with the same label may contain different annexures or signatures. Compare them page by page before marking one as authoritative.
How should each PDF be prepared and checked?
Work from controlled source copies. Apply OCR only through an approved process, keep the original scan, and visually compare the result. OCR can misread amounts, section numbers, dates, names, and negative signs. Searchability is valuable, but it does not establish accuracy.
Use this file-level checklist:
- The first and last pages belong to the same document.
- All pages are present, upright, readable, and in the right sequence.
- Signatures, seals, annotations, and annexure references remain visible.
- No unrelated return, identity record, or client document was included.
- Redaction, if authorised, is irreversible and does not obscure required material.
- Scanning and compression did not alter colour-dependent or fine-detail evidence.
- The filename identifies purpose and version without revealing needless sensitive data.
- The PDF opens in a second viewer and on a separate device.
- The document register contains the final page count and approval.
Avoid public conversion tools for confidential tax material. Gotham's security overview can support an evaluation of access and deployment controls, but each organisation must approve the tools and handling route it actually uses.
How do you reconcile Form 36 with the enclosures?
Form entries and attachments form one representation. Compare them through a field matrix. One reviewer should check the form, while another reads values from the underlying sources rather than from the preparer's notes.
| Form field | Primary comparison source | Cross-check |
|---|---|---|
| Appellant and respondent details | Impugned order and authorised records | Earlier appeal papers |
| PAN, assessment year, address | Official order and approved client record | Portal profile |
| Order date and communication date | Complete order and receipt evidence | Limitation workpaper |
| Sections and authority | Operative portions of orders | Issue map |
| Disputed amounts | Order, computation, and reconciliation | Grounds and relief |
| Representative details | Current authority document | Filing account |
Log every discrepancy. A typo carried consistently across several older documents does not become correct through repetition. Obtain a matter-specific decision about correction, explanation, or retention.
What signature and authorisation controls are needed?
Do not assume that possession of a portal login establishes authority to sign, verify, or file. Identify the appellant, authorised signatory, representative, filing operator, and reviewer separately. Confirm their roles under the current law, rules, portal process, and matter instructions.
Maintain a signature sheet showing the document, required signatory, signing method, date, verified final version, and reviewer. If a signed PDF is replaced after correction, route it through approval again. Never paste a signature image into an altered document merely because an earlier version was signed.
The ITAT's official e-Filing portal explains its current access routes and Appeal Dashboard. Contact details, OTPs, and credentials should be controlled under the organisation's security procedures, never stored in the filing checklist.
What should the pre-submission assembly review cover?
Freeze an “approved for upload” folder. It should contain only the files selected in the requirements register. Generate a submission manifest listing filename, document ID, description, page count, approval, and portal slot.
Then conduct a screen-share or four-eyes review:
- Confirm the correct account, party, proceeding, Act, type, subtype, and bench inputs.
- Compare form values with the field matrix.
- Open every selected file from the upload folder.
- Match every portal slot to the manifest.
- Review the complete portal preview, not just local PDFs.
- Confirm limitation, fee, signature, and authorisation approval.
- Submit only after the responsible person gives recorded clearance.
Use the court filing quality-control guide for additional assembly controls. The ITAT appeal workflow places this checklist within the wider lifecycle.
What evidence proves that e-filing finished?
A completed data-entry screen does not prove filing. Preserve the official acknowledgement, reference or appeal details, submission date and time, and the exact files submitted. Export or screenshot responsibly, omitting credentials and irrelevant personal data. Save the evidence in a read-only filing record.
Create a post-filing reconciliation:
| Check | Expected evidence | Owner |
|---|---|---|
| Submission completed | Portal acknowledgement | Filing operator |
| Filed content preserved | Manifest and immutable file set | Matter manager |
| Dashboard status checked | Dated status record | Docketing owner |
| Defects monitored | Defect log and alerts | Named professional |
| Client or team informed | Approved status communication | Matter lead |
The filing remains operationally open while acknowledgements, defects, or registry questions are unresolved.
How should later documents and defects be controlled?
Do not reopen or edit the original filed folder. Create a new event for every defect response, corrected document, petition, paper book, or later submission. Link it to the originating communication and record who approved it.
A good audit trail answers five questions: what was requested, when it was received, what was submitted, who approved it, and what evidence shows closure. Maintain the current dashboard status alongside the documentary trail, without replacing one with the other.
The final checklist should feel almost boring. Every portal requirement has a mapped file or documented decision, every file opens, every key value reconciles, and the receipt is preserved. Teams can review Gotham's legal workflows, explore the legal corpus, or contact Gotham to discuss document control around filing and research.
