By
Muhammad Ashraf and Muhammad Yousha
The Appellate Tribunal Inland Revenue (ATIR) occupies a critical position in Pakistan's tax adjudication framework. It is the principal independent quasi-judicial forum where disputed questions of fact and law arising from tax proceedings are examined and determined. Consequently, the timely and efficient disposal of appeals before the Tribunal is not merely an administrative requirement; it is an essential component of the administration of justice and effective revenue collection.
A matter remaining pending before ATIR has a dual consequence. From the taxpayer's perspective, prolonged pendency may result in uncertainty, blockage of disputed amounts, continuing litigation costs and delayed access to finality. From the revenue perspective, legitimate tax demands remain unresolved and the Federal Board of Revenue (FBR) may be deprived, for an extended period, of revenue that may ultimately become lawfully recoverable. In this context, the principle that “justice delayed is justice denied” has equal relevance to the taxpayer and to the State: delayed adjudication delays both the taxpayer's right to finality and the State's right to realization of duly determined revenue.
The need for modernization has become even more pressing because the Federal Board of Revenue has progressively moved towards automation and digitalization of tax administration, including the use of electronic systems such as IRIS. The appellate side of tax administration should correspondingly evolve so that the benefits of digitalization do not end at the assessment or departmental stage but continue through the appellate process. The present framework, however, remains substantially dependent upon physical filing, paper documents, manual scrutiny, physical service, manually prepared cause lists, physical records and other processes that can now be substantially digitized.
The Income Tax Appellate Tribunal Inland Revenue (Functions) Rules, 2023 already provide the procedural framework for the complete lifecycle of an appeal—from filing and registration, respondent identification and documentation, scrutiny and limitation, hearing and cause lists, evidence and adjournments, orders and communication, stay applications, to record management. The Rules therefore provide a sufficiently structured procedural architecture upon which an integrated electronic case-management system can be built.
Importantly, Rule 45 expressly provides for computerization and automation for the effective and smooth functioning of the Tribunal. The proposed initiative should therefore not be viewed merely as the creation of an “e-Filing Portal”. Rather, it should be conceived as an integrated “ATIR e-Court / Electronic Case Management & Appeals System”, covering the entire lifecycle of a case. The proposed architecture encompasses e-Filing, e- Scrutiny, e-Case Management, e-Hearing, e-Record and e-Communication.
This article is accordingly aimed at bringing the procedural administration of ATIR in line with the broader digital transformation of FBR, while preserving the institutional independence and judicial character of the Tribunal.
The fundamental principle throughout remains the same: Digitization facilitates, records, monitors and communicates the Tribunal's process; it does not replace the legal authority, judicial discretion or decision-making vested in the Tribunal, the Bench, the Registrar or any authorized officer.
Automation should therefore be confined to mechanical, administrative and procedural functions—such as data capture, document validation, limitation calculation, deficiency identification, electronic service, hearing scheduling, cause-list generation, notifications, record management, workflow tracking and management reporting—while matters requiring judicial or quasi-judicial determination must remain with the competent authority. The proposed system would consequently not alter the substantive rights of an appellant, the powers of the Tribunal or the discretion available under the Rules. Instead, it would provide the technological infrastructure necessary to implement those Rules more efficiently, transparently, consistently and securely.
The objective is therefore not simply to make ATIR “paperless”. The objective is to transform ATIR from a paper-file-centric process into a case-centric digital system, in which every appeal can be electronically tracked from filing to registration, scrutiny, hearing, adjournment, order, communication and final preservation of the record. The proposed system would also create an institutional audit trail and management dashboard, enabling the Tribunal to identify pendency, procedural delays and cases requiring administrative attention. The attached proposal similarly envisages case tracking from “filed → scrutiny → registered → hearing → adjourned → reserved → decided → communicated”, supported by automated notifications and complete date/time/user tracking.
The 2023 Rules expressly cover the core processes from filing and registration (Rules 8–9), respondent identification and documentation (Rules 10–14), scrutiny and limitation (Rules
16–18), hearings and cause lists (Rules 19–22), evidence and adjournments (Rules 25–27), orders and communication (Rules 29–31), stay applications (Rule 32), record management (Rules 36–42), and computerization/automation (Rule 45). Below is the corresponding Rule- by-Rule Automation Matrix.
PROPOSED ATIR DIGITAL CASE MANAGEMENT SYSTEM — RULES, 2023 Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023 Online filing of Form A through an ATIR portal, replacing physical filing/post/courier; digital 1 e-Filing of Appeal Rule 8 upload of memorandum and supporting documents.
System-generated Diary No., date/time stamp Automatic Diary / 2 Rule 9 and electronic registration immediately upon Registration successful filing.
Automatic System identifies and populates the relevant 3 Identification of Rule 10 Commissioner Inland Revenue as respondent Respondent based on the impugned order and jurisdiction.
Structured online entry of numbered grounds; Digital Grounds of 4 Rule 11 system prevents/flags narrative or non- Appeal compliant grounds.
Mandatory checklist for impugned order, CIR Electronic Document 5 Rule 12 order, grounds of first appeal, appeal fee, Checklist certificate and other documents.
Automatic electronic transmission of Electronic Intimation memorandum and grounds to concerned 6 Rule 13 to Respondent CIR/Departmental Representative, with acknowledgement and audit trail.
Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023 Upload of sworn affidavit with digital document 7 Digital Affidavit Filing Rule 14 verification and linking to the relevant appeal/application.
Digital request/application for permission to Grounds 8 Rule 15 raise additional grounds; automatic placement Management before Bench.
Automated scrutiny of filing; defect memo Defect/Scrutiny 9 Rule 16 generated electronically with a maximum Management rectification period of 15 days.
Automatic calculation of limitation based on 10 Limitation Calculator Rule 17 date of communication of order; system flags delayed appeals.
Online application/explanation for delay with Condonation of 11 Rule 17(3) supporting documents and automatic Delay placement before Bench.
Digital submission and verification of Power of Attorney / 12 Rule 18 authorization/POA; representative profile linked Authorization to cases.
Automated generation and electronic service of 13 Hearing Notice Rule 19 Form C hearing notice to parties/representatives.
Email/SMS Hearing Supplementary email/SMS/portal notification of 14 Rule 19 Alert hearing date, time, Bench and venue.
Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023 Automated Bench-wise preparation of daily 15 Digital Cause List Rule 20 cause lists in Form B.
Email/portal distribution of cause lists to Electronic Cause List 16 Rule 20 parties, representatives and departmental Circulation representatives.
Digital allocation of cases to Benches; 17 Bench Management Rules 3 & 5 controlled transfer between Benches with complete audit trail.
Digital hearing dashboard recording 18 Hearing Management Rule 21 attendance, submissions, hearing status and next date.
Automatic monitoring of the three-month Order Deadline 19 Rule 21(4) period for passing orders after conclusion of Monitoring hearing and escalation where exceeded.
Ex-Parte System flags non-appearance and initiates 20 Rule 22 Management workflow for ex-parte proceedings.
Digital application for substitution/continuation Continuation on 21 Rule 23 against legal representative, successor, Death/Insolvency receiver or liquidator.
Respondent's Digital recording and filing of respondent's 22 Rule 24 Supporting Grounds grounds supporting the order appealed against.
Online application for permission to produce Additional Evidence 23 Rule 25 additional evidence, with document upload and Application Bench decision workflow.
Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023
Digital transmission of Tribunal directions to Evidence Remand / 24 Rules 25–26 Inland Revenue authority and tracking of Examination compliance/evidence received.
Online adjournment request with reasons and Adjournment supporting evidence; automatic placement 25 Rule 27 Application before Bench and tracking of repeated requests/costs.
Remand Electronic remand order, assignment to 26 Rule 28 Management concerned authority and compliance tracking.
e-Order / Digital Digital preparation, approval, signing/date 27 Rule 29 Signature stamping and secure storage of Tribunal orders.
Restricted Digital Role-based access to case records because 28 Rule 30 Hearing Record proceedings are not open to the public.
Automatic communication of order to Electronic appellant, respondent and concerned 29 Communication of Rule 31 Commissioner Inland Revenue through Order portal/email.
Dedicated online stay module linked to the 30 e-Stay Application Rule 32 main appeal; automatic scrutiny of mandatory particulars and early-hearing workflow.
Stay Application System validates demand, outstanding tax, 31 Information Rule 32(5) appeal number, previous stay Checklist applications/orders and reasons for stay.
Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023 Automatic urgent/priority listing and hearing- 32 Stay Hearing Priority Rule 32(7) date workflow upon receipt of stay application.
System automatically routes stay application to Same-Bench 33 Rule 33 the Bench that heard the main appeal, subject Allocation to Chairperson's direction.
Online application, fee calculation/payment, Online Certified 34 Rule 34 processing and electronic delivery of copies Copies where legally permissible.
Online Inspection Digital request and approval for inspection of 35 Rule 34(3) Request records with scheduled access and audit trail.
Complete e-file divided into Part-A and Part-B, 36 Electronic Case File Rule 36 with electronic documents expressly recognized by the Rule.
Digital Record Automated retention schedule based on 37 Rule 37 Retention prescribed preservation periods.
Digital Record Automated alerts when records become 38 Destruction Rules 38–40 eligible for destruction, approval workflow and Workflow permanent destruction audit trail.
Replacement of manual primary, subsidiary 39 Electronic Registers Rule 41 and statistical registers with integrated electronic registers.
Real-time statistics on institution, disposal, Statistical 40 Rule 41 pending cases, applications, Bench Dashboard performance and other returns.
Relevant Sr. Process / Area Proposed Automation / Digital Function Rule, 2023 Electronic retention and destruction Digital Records & 41 Rule 42 management for correspondence, returns and Returns other administrative papers.
Digitally generated notices with electronic e-Notice / 42 Rule 43 authentication, reference number and Authentication QR/verification facility.
Public/authorized-user case tracking: filed → Rules 8–43 43 Case Status Portal scrutiny → registered → hearing → adjourned → collectively reserved → decided → communicated.
Email/SMS/portal alerts for filing, defects, Automated Rules 13, 19, 44 hearings, cause lists, adjournments, stay Notifications 20, 27, 31, 32 applications and orders.
Date/time/user tracking for every filing, 45 Complete Audit Trail Rules 8–43 modification, notice, hearing, document, order and communication.
Rule-based automation of the entire case Automation / 46 Rule 45 lifecycle, subject to directions of the Workflow Engine Chairperson and availability of resources.
Particularly important provisions for an ATIR Portal are explained in the ensuing paragraphs.
1. RULE 8 — FILING OF APPEAL AND PROPOSED E-FILING WORKFLOW Rule 8 presently prescribes the procedure for filing an appeal before the Appellate Tribunal. Under sub-rule (1), the memorandum of appeal is required to be submitted in the prescribed Form “A” to the Registrar or an officer authorized in this behalf, either by physical presentation or through registered post/courier service. Sub-rule (2) further provides that an appeal sent by post is deemed to have been presented on the date on which it is received in the office of the Tribunal.
The prescribed Form “A” requires, inter alia, particulars of the appellant/applicant, NTN/STRN, advocate/representative, respondent(s), Inland Revenue Office, relevant tax year/period, statutory provision under which the impugned order was passed, Commissioner (Appeals) order, date of communication of the order and verification by the appellant/applicant. The prescribed enclosure list further requires supporting documents including the index, memorandum of appeal, power of attorney, affidavit, summary of the case, relevant notices and orders, grounds of first appeal, treasury challan and other relevant documents.
Accordingly, an e-filing mechanism would effectively digitize and operationalize the existing Rule 8 procedure, rather than create a new substantive right of appeal. The electronic system should therefore replicate the information and documentary requirements presently prescribed under Form “A” and its accompanying enclosure list.
A proposed electronic workflow may therefore be structured as follows:
Login → Select Appeal Type → Form “A” → Retrieve Order Details → Complete Appellant/Respondent Details → Enter Tax Year/Period and Relevant Sections → Upload Memorandum/Grounds → Upload Prescribed Enclosures → Upload Verification/Affidavit/Authority Documents → Pay/Verify Tribunal Fee → Electronic Submission → Generate Acknowledgment/Diary No. → Scrutiny → Removal of Deficiencies, if any → Registration of Appeal
The system should preferably retrieve the relevant assessment/appellate order details from IRIS or the connected Inland Revenue database, wherever technically feasible, to minimize manual entry and reduce errors.
Deemed Date of Filing Particular attention should be given to the existing deeming provision in Rule 8(2). At present, an appeal transmitted by registered post is deemed to have been presented only when it is received in the office of the Tribunal.
Under an electronic system, the equivalent legal event should be clearly defined, for example, the date and time at which the appellant successfully submits the complete electronic appeal and the system generates an electronic acknowledgment/diary number. This would remove uncertainty regarding the date of presentation, particularly in cases involving limitation.
Digitization of Form “A” The existing Form “A” should preferably be converted into an interactive electronic form rather than requiring the appellant to upload a scanned form. The portal may require the appellant to enter:
• Type of application/appeal; • Income Tax / Sales Tax / Federal Excise; • Name and address of appellant; • NTN/STRN; • Contact details; • Authorized representative/advocate; • Respondent details; • Relevant Inland Revenue Office; • Tax year/period; • Section under which the impugned order was passed; • Commissioner (Appeals) order, where applicable; • Date of communication of the impugned order; and • Verification details.
These fields correspond substantially with the information presently prescribed in Form “A”.
Electronic Management of Enclosures The current enclosure requirements should also be incorporated into the electronic filing process. The portal should provide separate upload fields/checklists for:
a. Index of documents; b. Memorandum of Appeal; c. Power of Attorney; d. Affidavit; e. Summary of the case; f. Recovery Memo/Seizure Report/FIR, where applicable; g. Show Cause Notice; h. Order-in-Original/Assessment Order; i. Order-in-Appeal; j. Other relevant documents; k. Grounds of first appeal; and l. Treasury Challan.
The system should also identify mandatory and conditional documents, rather than requiring every appellant to upload documents that may not be relevant to the particular category of appeal.
Scrutiny and Deficiency Management Following electronic submission, the appeal should be assigned a unique electronic Diary/Reference Number and routed to the scrutiny function. Where deficiencies are identified, the appellant/authorized representative should receive an electronic deficiency notice specifying:
• the deficiency; • relevant document/field; • date by which it is to be rectified; and • method of rectification.
The appellant should be able to rectify deficiencies electronically without having to submit the entire appeal afresh.
Registration and Electronic Record
Upon successful scrutiny, the system should generate an Appeal Registration Number and maintain a complete electronic case record containing:
Form “A” + Memorandum of Appeal + Grounds + Orders + Enclosures + Fee Record + Verification + Correspondence + Scrutiny Notes + Deficiency/Compliance History.
This would create a single digital case file and substantially reduce dependence on physical records.
Legal/Procedural Point Requiring Attention The present wording of Rule 8 specifically contemplates physical submission or registered post/courier. Therefore, if e-filing is to become the legally recognized mode of presentation rather than merely an administrative facility, the electronic mechanism should be supported by the applicable rule-making/notification framework.
The e-filing system should consequently specify, with legal certainty, when an electronically filed appeal is deemed to have been presented, particularly for purposes of limitation.
Proposed Digital Model The overall process may therefore be represented as:
IRIS/Login → Appeal Selection → Automated Order Retrieval → Form “A” → Grounds & Memorandum → Electronic Enclosures → Verification → Fee → Submit → Electronic Acknowledgment/Diary No. → Scrutiny → Deficiency Resolution → Appeal Registration → Digital Case File
This approach would preserve the substantive requirements of Rule 8 and Form “A”, while converting the existing paper-based process into a traceable, time-stamped and integrated electronic filing system.
2. RULES 12–13 — DOCUMENTS ACCOMPANYING APPEAL AND INTIMATION TO RESPONDENTS: PROPOSED ELECTRONIC WORKFLOW
Rule 12 — Documents to Accompany Memorandum of Appeal Rule 12 presently deals with the documents that must accompany a memorandum of appeal. Under sub-rule (1), every memorandum of appeal is required to be filed in triplicate and accompanied by clear and legible copies of specified documents, including:
• the order appealed against, including the original order; • the order of the Commissioner Inland Revenue or, as the case may be, the Officer of Inland Revenue; • a copy of the grounds of first appeal; • proof of payment of the appeal fee; and • the certificate prescribed under Rule 13.
Sub-rule (2) further requires a certificate to be appended to the memorandum showing the date of communication of the impugned order. This is particularly relevant because the date of communication may determine whether an appeal has been filed within the prescribed limitation period. Sub-rule (3) gives the Tribunal discretion to accept an appeal even where some or all of the prescribed documents have not initially been filed. Sub-rule (4) presently requires the appellant to place an index on the face of the memorandum of appeal, identifying the documents filed under the Rule, with pagination in the paper book in triplicate.
Accordingly, Rule 12 is substantially designed around a physical paper-based record, particularly through its requirements of triplicate copies, original orders, physical indexing and paper books.
Electronic Filing under Rule 12 Where Rule 8 is amended to recognize electronic filing, Rule 12 should correspondingly recognize that the documents required under the Rule may be submitted electronically. The objective should not be to dispense with the substantive documentary requirements of Rule 12. Rather, the amendment should convert the method of submission and record management from paper to electronic form.
The electronic system should therefore replicate the Rule 12 checklist as part of the filing process: Form A → Memorandum of Appeal → Impugned Order → Commissioner (Appeals) Order → Grounds of First Appeal → Appeal Fee → Rule 13 Certificate → Other Required Documents → Electronic Index → Submission
Digitization of the “Triplicate” Requirement The existing requirement that the memorandum be filed in triplicate should be expressly addressed. For electronic appeals, the requirement for three physical copies should not be necessary because the electronic filing system itself can create and distribute the required digital copies to:
1. the Tribunal's electronic case file; 2. the appellant/appellant's authorized representative; and 3. the respondent/designated officer.
The rule could therefore provide that the requirement of filing in triplicate shall not apply to an appeal filed electronically, where the electronic system generates and maintains the requisite digital record. This would avoid the somewhat artificial situation of requiring an appellant to upload documents electronically and then reproduce the same documents in three physical sets. However, the honorable members should also be equipped with laptops.
Electronic Index and Document Management The present Rule 12(4) requires an index showing the documents filed, together with pagination in the paper book. In the electronic environment, this should be replaced by an electronic index generated by the system. The portal could automatically assign:
• document number; • document description; • page range; • date of upload; • document type; • file name; • uploader identity; and • electronic timestamp.
For example: Document No. Document Pages Date Uploaded Status 1 Order appealed against 1–25 19-08-2026 Uploaded 2 Commissioner (Appeals) Order 26–40 19-08-2026 Uploaded 3 Grounds of First Appeal 41–48 19-08-2026 Uploaded 4 Appeal Fee 49 19-08-2026 Verified 5 Rule 13 Certificate 50 19-08-2026 Uploaded
This would effectively replace the physical paper-book index with a searchable electronic document index.
Original Order and Certified Documents The requirement in Rule 12 to provide the original order should not simply disappear because of e-filing. Instead, the electronic rule should distinguish between:
Documents capable of electronic verification which may be uploaded electronically where they are available through IRIS, the Tribunal's system or another authenticated government database.
Documents requiring original/certified production, where the Tribunal considers the original or certified copy necessary, the appellant may subsequently be directed to produce it physically.
The important point is that production of the original at a later stage should not invalidate the original electronic filing or constitute a fresh filing, provided the appeal was electronically filed and acknowledged in accordance with Rule 8.
Date of Communication of Impugned Order The certificate under Rule 12(2) is particularly important and should be retained in the electronic system. The portal should either:
(a) allow the appellant to enter the date of communication and upload the supporting certificate; or
(b) where the order is available through IRIS or another integrated system, retrieve the date automatically.
The system could then automatically calculate the last date for filing the appeal, subject to the applicable limitation and any condonation provisions. This would provide an important safeguard against errors in calculation of limitation.
Scrutiny of Documents under Rule 12 The electronic filing system should perform an initial document completeness check before submission. For example:
Mandatory documents missing → System warning → Appellant uploads document → Checklist complete → Submission enabled
However, this should not prevent the Tribunal from exercising the discretion presently available under Rule 12(3) to accept an appeal notwithstanding missing documents. Therefore, the system should distinguish between: “System deficiency” and “Legal rejection.”
A missing document should generate a deficiency notification; it should not automatically result in rejection of the appeal unless the Rules or an order of the Tribunal provides.
Rule 13 — Intimation of Filing of Appeal or Application to Respondents Rule 13 presently requires the appellant/applicant, before filing an appeal or application, to send a copy of the memorandum and grounds of appeal/application to the respondent through:
• registered post acknowledgment due; or • courier service.
A certificate confirming such service must then be appended to the appeal/application. This provision creates a separate pre-filing service process which is largely manual and requires:
Preparation → Printing → Dispatch → Postal/Courier Receipt → Delivery → Certificate → Attachment with Appeal
This is an area where substantial administrative efficiency can be achieved through electronic integration.
Proposed Electronic Mechanism under Rule 13 Where the appeal is filed electronically, the filing system should be capable of simultaneously serving the memorandum and grounds upon the relevant respondent. The proposed workflow would therefore be:
Appeal Filed → System Identifies Respondent → Electronic Copy Generated → Documents Made Available to Respondent/CIR Legal → Electronic Notification → Acknowledgment/Timestamp → Service Record Automatically Attached to Appeal
This would eliminate the need for the appellant to separately print and courier the same documents to the respondent where electronic service is available.
Automatic Identification of the Respondent For appeals involving Inland Revenue authorities, the system should preferably identify the appropriate respondent from the order being challenged. For example:
IRIS Order → Jurisdiction/Officer Identified → Relevant Commissioner Inland Revenue → Designated Legal Officer → Electronic Service
This would reduce the possibility of an appellant sending the appeal to an incorrect office or officer. It would also permit the Tribunal to maintain a centralized record of appeals filed against particular orders or jurisdictions.
Electronic Certificate of Service The existing Rule 13 requires the appellant to append a certificate confirming that the memorandum and grounds were sent to the respondent. Under electronic filing, this certificate could be generated automatically. The system-generated certificate could record:
• Appeal/Diary Number; • name of appellant; • name of respondent; • date and time of filing; • date and time of electronic service; • documents served; • email/portal account of recipient; • electronic acknowledgment; and • status of delivery.
The electronic certificate could then automatically become part of the Tribunal's digital case file.
Electronic Service Where Respondent Has Not Accessed the System An important issue is that delivery and actual access are not necessarily the same thing. Therefore, the rule should preferably recognize the point at which electronic service is legally complete. For example, when the documents are successfully transmitted to the designated official's electronic account or made available in the official portal and the system generates the prescribed acknowledgment. This avoids uncertainty over whether the respondent actually opened the document. Where electronic service fails, the existing registered post/courier mechanism should continue to operate as a fallback. Thus:
Electronic service successful → Electronic certificate Electronic service unsuccessful → Registered post/courier → Existing certificate
Parallel Operation of Physical and Electronic Systems Since the intention is that both systems should operate in parallel, Rules 12 and 13 should not abolish the existing procedure. The framework should therefore be:
Physical Appeal Paper memorandum → Triplicate → Physical documents → Paper index → Registered post/courier service → Certificate → Filing
Electronic Appeal Electronic Form A → Digital memorandum → Electronic documents → Electronic index → Electronic service → System-generated acknowledgment → Filing
Both should have equal legal effect.
Proposed Electronic Workflow for Rules 12–13 The integrated process could therefore be:
Login → Form A → Memorandum of Appeal → Upload Impugned Order → Upload Commissioner (Appeals) Order → Grounds → Fee → Rule 13 Certificate/Service → Electronic Index → Submit → Diary No. → Automatic Service on Respondent → Service Acknowledgment → Scrutiny → Deficiency Notice → Rectification → Registration
Key Amendments Required to Rules 12–13 In practical terms, I would recommend that the amendments expressly address the following:
Rule 12 1. Recognize electronic submission of all prescribed documents. 2. Exempt electronic appeals from the requirement of three physical copies. 3. Replace the physical paper-book index with an electronic index. 4. Permit original/certified documents to be produced subsequently where required. 5. Recognize electronically generated documents and acknowledgments. 6. Permit electronic rectification of deficiencies. 7. Preserve the Tribunal's existing discretion to accept an appeal despite incomplete documentation. 8. Ensure that subsequent physical production of an original does not constitute a fresh filing.
Rule 13 1. Recognize electronic service as an alternative to registered post/courier. 2. Permit simultaneous filing and electronic service through the Tribunal's system. 3. Provide for automatic identification of the relevant respondent/CIR Legal Officer. 4. Generate an electronic certificate of service. 5. Define the legal point at which electronic service is deemed complete. 6. Preserve registered post/courier as a fallback where electronic service fails. 7. Maintain the electronic service record as part of the Tribunal's digital case file.
3. Rules 16–17 — Defective Appeals, Automated Scrutiny and Limitation Rules 16 and 17 deal with two important preliminary stages in the processing of an appeal: rectification of defects and determination of delay/limitation. These provisions provide significant scope for digitization and automated scrutiny, although the system should assist the Registrar/authorized officer and the Tribunal rather than replace the discretion vested in them under the Rules.
Rule 16 — Defective Appeals Rule 16 provides that where a memorandum of appeal has not been filed in the manner specified in the Rules, the Registrar or the officer authorized under Rule 8 may require the appellant or his authorized representative to bring the appeal into conformity with the Rules within such time as may be specified, not exceeding fifteen days. Where the appellant or authorized representative fails to comply with the requirement, Rule 16(2) provides that the Registrar or authorized officer shall place the matter before the Bench for such orders as the Bench may deem fit.
Accordingly, the electronic filing system should incorporate an initial automated completeness and conformity check immediately upon submission.
The proposed workflow may be: Electronic Submission → Automated Validation → Deficiency Identified → Electronic Deficiency Notice → Rectification within up to 15 Days → Re-submission → Scrutiny Clearance → Registration
The system could automatically check, to the extent technically possible:
• whether the prescribed Form “A” has been completed; • whether the appeal has been filed under the appropriate category; • whether mandatory fields have been completed; • whether the prescribed documents under Rule 12 have been uploaded; • whether the memorandum and grounds are attached; • whether the relevant impugned order has been uploaded; • whether proof of payment of appeal fee has been provided; • whether the Rule 13 certificate/service requirement has been addressed; • whether the electronic index of documents has been completed; and • whether the uploaded documents are technically accessible and readable.
Electronic Deficiency Notice Where a deficiency is identified, the system should generate an electronic deficiency notice specifying:
1. the particular defect; 2. the Rule/provision involved, where applicable; 3. the document or information required; 4. the date on which the deficiency was communicated; 5. the deadline for rectification, subject to the maximum period of fifteen days prescribed under Rule 16; and 6. the method through which the appellant may rectify the defect electronically.
The system should maintain an electronic record of the entire deficiency cycle: Deficiency Raised → Date of Communication → Rectification Submitted → Date of Compliance → Scrutiny Outcome
This would provide a complete audit trail and eliminate uncertainty regarding when the fifteen-day period commenced and whether the appellant complied within the prescribed period.
Important Legal Limitation on Automation The system should not automatically reject an appeal merely because a defect has been identified. Rule 16(2) expressly provides that where the appellant or authorized representative fails to meet the requirement under sub-rule (1), the matter is to be placed before the Bench for such orders as it may deem fit.
Therefore, the appropriate electronic model is: Automated identification of defect → Opportunity for rectification → Non-compliance recorded → Matter electronically placed before Bench
rather than: Automated defect → Automatic rejection
This distinction is important because the Rule vests the ultimate decision in the Bench.
Rule 17 — Appellant to Explain Delay Rule 17 deals specifically with the examination of whether an appeal or application has been presented within the period prescribed by the relevant law. Under Rule 17(1), upon presentation of a memorandum of appeal or application, the Registrar or authorized officer is required to examine the copy of the order appealed against and ascertain whether, after allowing the time prescribed by the relevant law, the memorandum of appeal or application has been presented within time.
Rule 17(2) further provides that where the memorandum of appeal or application appears to have been presented after the prescribed period, a note to that effect shall be recorded by the Registrar or authorized officer. Rule 17(3) deals with the situation where the appellant/applicant has not submitted an explanation in writing setting out the reasons for delay. In such circumstances, the Tribunal may allow the appellant/applicant to submit a written explanation and, upon sufficient cause having been shown, may admit the appeal or application for hearing.
Accordingly, the electronic system can provide substantial assistance in determining limitation, but it should not itself determine whether “sufficient cause” exists. That remains a matter for the Tribunal.
Automated Limitation Calculation The electronic filing system should preferably retrieve the relevant order and its date of communication from the available electronic record, where technically possible.
It could then calculate: Date of Communication → Statutory Limitation Period → Last Date for Filing → Actual Date of Presentation → Delay, if any
The system could automatically flag: Appeal within time Filed within prescribed limitation → No delay flag or Appeal apparently time-barred Filed after prescribed limitation → Delay Flag → Rule 17 Process Initiated
This would provide an immediate preliminary determination for scrutiny.
Electronic Delay Explanation Where the system identifies that an appeal appears to have been filed after the prescribed period, the appellant should be prompted to provide the written explanation contemplated by Rule 17(3).
The electronic workflow could therefore be: Limitation Check → Delay Identified → Delay Explanation Required → Written Explanation Uploaded → Supporting Documents Uploaded → Scrutiny → Placed Before Tribunal, where required
The system should allow the appellant to provide:
• reasons for delay; • period of delay; • supporting documents; • affidavit, where required; • any other material relied upon to demonstrate sufficient cause.
The system should then associate the explanation with the appeal record.
Role of the Registrar and the Bench A crucial distinction should be maintained between automated calculation and judicial determination.
The system can objectively calculate and flag: “The appeal appears to have been filed after the prescribed period.”
However, it should not make the final determination: “The delay is not condonable.”
Similarly, the system can identify that an explanation for delay has not been submitted, but it should not itself determine whether the explanation constitutes sufficient cause.
The final decision under Rule 17(3) should remain with the Tribunal/Bench.
Integrated Rule 16–17 Workflow Rules 16 and 17 can therefore be integrated into the electronic filing process as follows: Electronic Filing → Form/Document Validation → Deficiency Check → Rule 16 Deficiency Notice → Up to 15 Days for Rectification → Compliance Check → Limitation Calculation → Date of Communication Verified → Limitation Expiry Calculated → Delay Flag, if applicable → Written Explanation for Delay → Supporting Documents → Registrar's Scrutiny → Bench, where required → Registration/Admission Process
Potential Dashboard for Registrar The electronic system could also provide the Registrar/authorized officer with a dashboard showing:
Scrutiny Item System Status Form “A” complete ✓ / Deficient Mandatory documents ✓ / Deficient Appeal fee ✓ / Pending Rule 13 service ✓ / Pending Date of communication Verified / Required Limitation Within time / Delay Delay explanation Filed / Required Rule 16 deficiency Complied / Pending Fifteen-day period Running / Expired Action required Registration / Deficiency / Bench
This would allow the Registrar or authorized officer to identify the appropriate procedural action without manually checking every document and date.
Legal/Procedural Safeguard The automation under Rules 16–17 should therefore be designed as a decision-support and case-management mechanism, not as an automated adjudication mechanism. The system may:
• identify defects; • calculate deadlines; • generate notices;
• monitor the fifteen-day rectification period; • calculate apparent delay; • request an explanation; • maintain the electronic record; and • place matters before the appropriate authority.
But it should not: • automatically reject a defective appeal where Rule 16 requires the matter to be placed before the Bench; • automatically reject a time-barred appeal; • determine whether sufficient cause exists under Rule 17(3); or • substitute an automated decision for the discretion of the Tribunal.
Proposed Digital Model The overall Rule 16–17 process may therefore be represented as:
E-Filing → Automated Scrutiny → Deficiency Identification → Rule 16 Notice → Rectification ≤ 15 Days → Compliance Check → Limitation Verification → Delay Calculation → Explanation of Delay, if required → Registrar's Note → Bench, where required → Further Order/Registration
This approach preserves the existing legal structure of Rules 16 and 17, while introducing automation for the mechanical aspects of scrutiny, deadline calculation, deficiency management and case routing.
4. RULES 19–20 — HEARING OF APPEALS, ELECTRONIC NOTIFICATION AND DIGITAL CAUSE LIST Rule 19 — Date and Place of Hearing Rule 19 presently provides that the Tribunal shall notify the parties of the date and place of hearing of an appeal or application in the form prescribed as Form “C”. The prescribed Form “C” contains, among other things:
• Name and address of the appellant/applicant; • Appeal/Application Number; • Title of the case; • Name of the appellant/applicant and respondent; • Section under which the appeal/application arises; • Order against which the appeal has been filed; • Number and date of the relevant order;
• Tax/Assessment Year; • Date fixed for hearing; • Time of hearing; • Place of hearing; • Information regarding appearance in person or through an authorized person; and • Consequences of default, including hearing ex parte/dismissal in default.
Accordingly, the electronic system should digitize the existing Form “C” rather than replace the statutory notice contemplated by Rule 19. Once a hearing date is fixed by the Tribunal, the system should automatically generate the prescribed Form “C” using the information already available in the electronic case record.
The proposed workflow may therefore be: Bench/Tribunal Fixes Hearing → System Generates Form “C” → Hearing Date/Time/Venue Recorded → Notice Generated → Electronic Service to Parties → Email/SMS/Portal Notification → Acknowledgment/Delivery Record → Hearing
The system should preferably populate the information in Form “C” automatically from the appeal record, thereby avoiding repeated manual entry of information already available in the Tribunal's system.
Electronic Notification The electronic system may additionally notify the parties through:
• electronic portal notification; • registered email address; • SMS; • mobile application notification, where available; and/or • any other officially recognized electronic communication channel.
However, such electronic notifications should initially operate as a supplementary digital facility unless the Rules expressly recognize electronic service as a legally sufficient mode of service.
The system should maintain an electronic record showing: Notice Generated → Date/Time of Dispatch → Recipient → Mode of Service → Delivery Status → Acknowledgment, where available
This would provide a reliable audit trail concerning notification of the hearing.
Rule 20 — Preparation of Cause List Rule 20 presently provides for the preparation and display of a daily cause list. Under sub- rule (1), for every working day, a daily cause list mentioning the appeals or applications is required to be prepared in the form prescribed as Form “B”. Sub-rule (2) provides that the cause list for the day is to be prepared by the Bench Clerk and displayed on the notice board by 2:00 p.m. on the day preceding the date of hearing. Sub-rule (3) further requires separate cause lists for each Bench and for each Member where an appeal is to be heard by a Single Member.
The prescribed Form “B” contains, among other particulars:
• Appeal Number; • Assessment Year; • Title of the case; • Hearing/Adjournment/Transferred status; • Total cases fixed; • Transfer/adjournment information; and • identification of the relevant Bench/Member.
Accordingly, Rule 20 provides a particularly suitable basis for digital generation and publication of cause lists.
Automated Cause List Generation Once the Tribunal fixes or modifies hearing dates, the electronic system should automatically update the relevant cause-list database.
The process could be: Hearing Fixed/Adjourned/Transferred → Case Status Updated → Bench Identified → Cause List Automatically Updated → Form “B” Generated → Cause List Published/Displayed → Parties Notified
The system should generate separate electronic cause lists for:
• each Division Bench; • each Single Member Bench; and
• any other Bench configuration recognized by the Tribunal.
This would correspond directly with the existing requirement under Rule 20(3).
Digital Form “B” The existing Form “B” should preferably be converted into an electronic cause-list template rather than creating a completely separate digital format. The system could automatically populate:
Existing Form “B” Information Electronic Source Appeal No. Appeal Registration Record Assessment Year Form “A” / Case Record Title of Case Appellant & Respondent Record Hearing Date Bench Calendar Hearing / Adjourned / Transferred Case Status Bench/Member Bench Allocation Total Cases Fixed Automated Count
This would substantially reduce the administrative work involved in manually preparing daily cause lists.
Publication and Display of Cause List The existing Rule 20 specifically requires the cause list to be displayed on the notice board by 2:00 p.m. on the day preceding the hearing. Therefore, if the intention is to retain the physical system in parallel, the electronic system should not initially replace the physical notice-board requirement. Instead, the system should provide:
Existing process Form “B” → Printed Cause List → Notice Board
Additional electronic process Form “B” → Digital Cause List → Tribunal Website/Portal → Email/SMS/Portal Notification
This would ensure that digital publication is an enhancement to, rather than an unintended replacement of, the existing statutory process.
Automated Changes to Cause List One major advantage of digitization would be the ability to automatically update the cause list where a matter is:
• adjourned; • transferred; • fixed before another Bench; • heard by a Single Member; • taken up by a Division Bench; or • otherwise altered in accordance with an order of the Tribunal.
Instead of requiring repeated manual preparation of the cause list, the case-management system could automatically update the status.
For example: Case Fixed → Hearing Date 25 August → Listed in Form “B”
If adjourned: Adjourned → New Hearing Date → Existing Entry Updated → New Cause List Generated
If transferred: Transferred → New Bench Identified → Cause List Automatically Reallocated
Email and SMS Notifications The electronic system could additionally provide automated notifications to the appellant, respondent and authorized representative. For example: “Appeal No. XXXX has been fixed for hearing before Bench ___ on ___ at ___.”
Similarly, an automated notification could be generated where:
• a case is adjourned; • the Bench is changed; • the hearing venue is changed; • the matter is transferred; • the matter is removed from the cause list; or • a revised cause list is issued.
The notification mechanism would therefore provide an additional layer of communication without disturbing the existing requirements of Rules 19 and 20.
Integration with Bench Calendar A further enhancement would be integration of the cause-list system with an electronic Bench Calendar.
The system could display: Bench → Working Day → Available Hearing Slots → Cases Fixed → Adjourned Matters → Remaining Capacity
This could assist the Tribunal administration in avoiding:
• duplicate listing; • over-listing; • incorrect Bench allocation; • omission of cases; • incorrect hearing dates; and • unnecessary manual preparation of revised cause lists.
Any actual fixing or alteration of a hearing date, however, should remain under the authority of the Tribunal/Bench or authorized officer, as applicable.
Important Legal Safeguard Automation should not be confused with judicial fixing of a hearing. The system may:
• generate Form “C”; • populate hearing information; • send notifications; • prepare Form “B”; • update the cause list; • record adjournments and transfers; and • maintain an audit trail.
However, it should not independently fix, adjourn or transfer a case unless such authority is expressly delegated under the Rules or exercised through an authorized Tribunal function. The electronic system should essentially record and communicate the decision of the Tribunal/authorized officer, rather than make that decision itself.
Integrated Rules 19–20 Electronic Workflow The complete electronic process could therefore be structured as: Case Ready for Hearing → Bench Fixes Date → Electronic Case Calendar Updated → Form “C” Automatically Generated → Notice to Parties → Hearing Notification → Form “B” Cause List Generated → Bench-wise/Member-wise List → Publication/Display → Email/SMS/Portal Notification → Hearing → Outcome Recorded → Adjournment/Transfer/Next Hearing Date → Cause List Automatically Updated
Proposed Digital Model The overall model for Rules 19–20 may therefore be represented as:
Tribunal Order Fixing Hearing ↓ Electronic Case Calendar ↓ Form “C” Automatically Generated ↓ Notice to Appellant / Respondent / Representative ↓ Electronic Acknowledgment / Delivery Record ↓ Form “B” Cause List Automatically Generated ↓ Bench/Single Member-wise Cause List ↓ Publication on Portal + Existing Notice Board ↓ Email/SMS Notification ↓ Hearing ↓ Outcome / Adjournment / Transfer Recorded ↓ Next Cause List Automatically Updated
Overall Effect Rules 19 and 20 are therefore particularly suitable for digitization because the information required for Form “C” and Form “B” is already contained within the Tribunal's case record. The proposed system would not alter the substantive hearing procedure. Rather, it would:
Rule 19 → Digitize hearing notification through Form “C”. Rule 20 → Digitize preparation, management and publication of the daily cause list through Form “B”.
The physical notice board and existing statutory procedure can continue in parallel, while the electronic portal, email and SMS facilities provide a faster, traceable and more accessible means of communication. This would create a significant administrative improvement while maintaining the legal integrity of the existing Rules.
5. RULE 21 — HEARING, DISPOSAL OF APPEAL OR APPLICATION AND ORDER MONITORING Rule 21 governs the hearing and disposal of appeals or applications before the Tribunal. Unlike Rules 19 and 20, which primarily concern scheduling and notification, Rule 21 contains substantive provisions relating to the constitution of the Bench, hearing of the parties, decision where Members differ, and the timeframe for passing orders.
Rule 21(1)–(2) — Bench Decision and Difference of Opinion Rule 21(1) provides that appeals and applications shall be heard by a Bench constituted under Rule 3, and where the Members of a Bench differ in opinion on any point, that point is to be decided according to the opinion of the majority.
Rule 21(2) deals with a situation where the Members of a Bench are equally divided on a point. In such circumstances, the Members are required to state the point on which they differ, and the matter is referred by the Chairperson for consideration by one or more other Members of the Appellate Tribunal. The point is then decided according to the opinion of the majority of the Members who have heard the case, including those who first heard it.
These provisions are essentially judicial functions and should not be subjected to automated decision-making. However, the electronic case-management system can record:
• Constitution of the Bench; • Members hearing the appeal;
• Points on which a difference of opinion arises; • Reference to additional Member(s), where applicable; • Majority position; and • Final outcome.
The system can therefore provide an electronic procedural record and audit trail, without influencing or determining the judicial decision.
Rule 21(3) — Recording of Hearing and Procedural Outcome Rule 21(3) provides that on the date fixed for hearing, or on any subsequent date to which the hearing is adjourned, the appellant or applicant shall be heard in support of the appeal or application. The Tribunal shall thereafter hear the respondent against the appeal or application, where necessary, and the appellant or applicant shall have a right of reply.
The electronic system can assist in maintaining a hearing history showing: Hearing Fixed → Appellant Heard → Respondent Heard → Right of Reply → Hearing Concluded / Adjourned
Where a matter is adjourned, the system can automatically record:
• date of hearing; • parties present/represented; • stage reached; • reason/status of adjournment, where recorded; • next hearing date; and • subsequent procedural action.
Again, the system should record the Tribunal's proceedings rather than determine how the hearing is conducted.
Rule 21(4) — Monitoring of Orders Rule 21(4) is particularly suitable for an electronic case-disposal and order-monitoring dashboard. The Rule provides that the orders of the Bench may be passed within three months from the date its hearing is concluded. Where the order is not passed within that period, the reasons for delay are to be communicated to the Chairperson.
Accordingly, the electronic system should automatically commence an order-monitoring clock from the date on which the hearing is concluded, rather than from the date on which the matter was initially fixed for hearing. The proposed monitoring mechanism may be: Hearing Concluded → Order Pending → Day 30 → Day 60 → Day 75 → Day 90 → Three-Month Threshold → Delay Alert / Reasons Required → Chairperson Monitoring
Important Point The system should calculate the three-month period objectively, but it should not treat the expiry of three months as an automatic default, disposal or adverse judicial event. Its function should simply be to identify that the period contemplated by Rule 21(4) has elapsed and facilitate the procedural requirement concerning communication of reasons for delay.
Proposed Order-Monitoring Dashboard A dedicated dashboard could provide the Chairperson, Tribunal administration and relevant Bench with a real-time view of pending orders:
Case Hearing Concluded Days Elapsed Status Action Appeal No. 101 01-Aug-2026 30 Order Pending — Appeal No. 102 01-Jul-2026 61 Order Pending Review Appeal No. 103 15-Jun-2026 77 Order Pending Alert Appeal No. 104 01-May-2026 92 > 3 Months Reasons/Chairperson
The dashboard could use graduated alerts, for example: Day 30: Internal monitoring ↓ Day 60: Bench-level reminder ↓ Day 75: Priority alert ↓ Day 90: Three-month threshold alert ↓ Beyond 90 Days: Flag for reasons for delay / communication to Chairperson
The precise alert intervals would be an administrative design choice and are not themselves prescribed by Rule 21.
Electronic Recording of Reasons for Delay Where an order is not passed within the three-month period, the system may provide a dedicated field through which the relevant reasons for delay can be recorded and communicated to the Chairperson. The electronic record could contain:
• Appeal/Application Number; • Date hearing concluded; • Date three-month period expires; • Current status of order; • Reason for delay; • Date reasons were recorded; • Date communicated to Chairperson; and • Subsequent action/status.
This would create a transparent and auditable record of compliance with Rule 21(4).
Important Judicial Safeguard The automation contemplated under Rule 21 should be limited to procedural monitoring and record management. The system should not:
• draft or determine the judicial order; • influence the Members' decision; • determine the outcome of a difference of opinion; • automatically dispose of a case; • automatically treat an order as delayed misconduct; or • determine whether the reasons for delay are adequate.
The system should merely perform the administrative function of: Count → Monitor → Alert → Record → Communicate
The judicial decision remains exclusively with the Bench, while the communication of reasons for delay remains subject to the Rule.
Proposed Digital Model The overall electronic mechanism for Rule 21 may therefore be represented as: Hearing Concluded → Case Reserved for Order → Order Monitoring Clock Starts → Day 30 → Day 60 → Day 75 → Day 90 → Order Passed? YES → Upload/Record Order → Update Case Status → Close Order Monitoring NO → Three-Month Threshold Reached → Generate Alert → Record Reasons for Delay → Communicate to Chairperson → Continue Monitoring → Order Passed → Close Case
Overall Effect The proposed digitization of Rule 21 would therefore create an objective order-monitoring mechanism without interfering with judicial independence. It would ensure that the Tribunal administration has a real-time view of matters where the three-month period is approaching or has elapsed, while preserving the Bench's exclusive authority over the hearing, determination, reasoning and final disposal of the appeal or application.
6. RULE 27 — ADJOURNMENT OF HEARING AND PROPOSED E-ADJOURNMENT MODULE Rule 27 specifically deals with adjournment of the hearing of an appeal or application. Under sub-rule (1), the Tribunal may adjourn a hearing where sufficient cause is shown, upon a request made by the party or authorized representative. The Rule further provides that, where repeated requests for adjournment are made, the Bench may grant the adjournment subject to costs as it may deem fit.
Sub-rule (2) expressly provides that no request for adjournment sent through post or fax shall be entertained. Accordingly, Rule 27 provides a suitable basis for introducing an electronic adjournment facility, particularly because the existing Rule already contemplates a request-based process and expressly excludes post and fax as acceptable modes of submission.
Proposed e-Adjournment Module The electronic filing system could provide an “Apply for Adjournment” option directly within the relevant appeal/application. The request could be linked automatically to the existing electronic case record, thereby avoiding a separate correspondence process.
The proposed workflow could be: Select Appeal/Application → Adjournment Request → State Sufficient Cause → Upload Supporting Document(s), if any → Previous Adjournment History → Electronic Submission → Bench → Decision → Costs, if any → New Hearing Date → Updated Cause List → Electronic Notification
Identification of the Case The system should automatically populate the relevant:
• Appeal/Application Number; • appellant/applicant; • respondent; • Bench; • scheduled hearing date; and • authorized representative.
This would ensure that the request is directly associated with the correct case.
Reason / Sufficient Cause Since Rule 27(1) expressly requires sufficient cause, the electronic form should require the applicant to state the reason for seeking adjournment. The applicant could also be permitted to upload supporting documentation where the request relies upon documentary evidence.
Importantly, the system should not determine whether the reason constitutes “sufficient cause.” That remains a matter for the Tribunal/Bench. The system merely captures and presents the reason to the Bench.
Previous Adjournments Because Rule 27 specifically distinguishes repeated requests for adjournment, the system should automatically display the adjournment history of the case, including:
• number of previous adjournments; • date of each request; • party who requested the adjournment;
• reason stated; • whether the request was granted or refused; and • costs imposed, if any. This would allow the Bench to readily see whether the current request forms part of a pattern of repeated adjournments.
Bench Decision Once submitted, the request should be routed electronically to the relevant Bench. The Bench may then:
Grant the adjournment → Fix a new hearing date → Impose costs, if considered appropriate → Issue any further directions OR Reject the request → Existing hearing date remains unchanged → Decision is recorded electronically
The system should therefore facilitate the Bench's decision but should not automatically grant or reject an adjournment.
Costs for Repeated Adjournments This is an important feature arising directly from Rule 27(1). Where repeated adjournments have been sought, the electronic system can alert the Bench: “Previous Adjournments: 3 | Costs Previously Imposed: Rs. ___ | Current Request: 4th Adjournment.”
The Bench may then determine whether the adjournment should be granted subject to costs as it deems fit. The system should record the costs imposed and, where appropriate, link them with the relevant payment/fee record.
New Hearing Date and Cause List Where the Bench grants an adjournment, the new hearing date should automatically update the electronic case record.
The system can then automatically: Update Hearing Calendar → Update Form “B” Cause List → Remove/Update Previous Listing → Include New Hearing Date → Notify Parties
This would also integrate Rule 27 with the proposed electronic mechanisms under Rules 19 and 20 concerning hearing notices and cause lists.
Post and Fax Restriction The existing Rule 27(2) expressly states: “No request for adjournment sent through post or fax shall be entertained.” This provision should be retained. The electronic system would therefore introduce a recognized electronic submission channel without treating ordinary email, post or fax as automatically valid methods of filing an adjournment request.
If electronic filing is formally recognized through amendment, the Rule can expressly provide that an adjournment request may be submitted through the prescribed electronic filing system.
Electronic Record / Audit Trail Every request should generate a permanent electronic record containing: Case Number → Date & Time of Request → Requesting Party → Reason → Supporting Documents → Previous Adjournment History → Bench Decision → Costs → New Hearing Date → Notification
This would provide transparency and reduce disputes concerning whether an adjournment request was submitted, when it was submitted and what decision was taken.
Important Legal Safeguard The proposed automation should remain limited to submission, information management, routing and notification. The system should not:
• determine whether sufficient cause exists; • automatically grant an adjournment; • automatically reject an adjournment; • automatically impose costs; or • independently change the hearing date.
These remain matters for the Tribunal/Bench under Rule 27.
The system's role would simply be: Capture → Verify → Display History → Route to Bench → Record Decision → Update Case → Notify Parties
Overall Digital Model Accordingly, Rule 27 can be integrated into the broader electronic Tribunal architecture as follows:
Rule 19 — Hearing Notice ↓ Rule 20 — Cause List ↓ Rule 27 — e-Adjournment Request ↓ Sufficient Cause + Supporting Documents + Adjournment History ↓ Bench Decision ↓ Costs, if any ↓ New Hearing Date ↓ Updated Cause List ↓ Electronic Notification
This is particularly valuable because Rule 27 already provides the substantive framework for adjournments; the proposed amendment would simply provide a legally recognized electronic channel for submitting and managing those requests while preserving the Bench's discretion under the existing Rule.
7. RULE 32 — MISCELLANEOUS APPLICATIONS AND STAY OF DEMAND Rule 32 prescribes the procedure for filing and disposal of miscellaneous applications, including applications seeking a stay against recovery of tax or ancillary proceedings where the relevant appeal is sub judice before the Tribunal.
The Rule is particularly suitable for digitization because it already establishes a defined set of procedural and documentary requirements, especially for stay applications.
Procedure for Miscellaneous Applications Under Rule 32(1), an application for stay against recovery of demand or tax, or ancillary proceedings, where the appeal is sub judice before the Tribunal, is to be presented in the same manner as provided under Rules 8, 10, 12, 22 and 23 relating to appeals.
Accordingly, once the proposed electronic filing mechanism under Rule 8 is operational, a miscellaneous application can be integrated into the same portal rather than requiring a separate physical process.
The electronic workflow could therefore be: Login → Select Miscellaneous Application → Select Appeal → Application Type → Complete Required Particulars → Upload Application → Affidavit → Supporting Documents → Court Fee → Submit → Diary/Reference No. → Scrutiny → Hearing
Application Format and Supporting Affidavit Rule 32(2) requires every miscellaneous application to be legible and typed on one side of the paper, in Urdu or English, and to set forth concisely the grounds of the application. Rule 32(3) further requires that the contents of every miscellaneous application be supported by a duly sworn affidavit.
Under an electronic system, these requirements could be converted into digital filing requirements by providing:
• an electronic application form or upload facility; • concise grounds/reasons for the application; • electronic upload of the sworn affidavit; • supporting documents; and • electronic verification/authentication mechanisms, where legally prescribed.
The electronic system should nevertheless preserve the substantive requirement of a duly sworn affidavit and should not treat a simple electronic declaration as automatically equivalent to an affidavit unless the applicable legal framework permits such authentication.
Stay Application — Mandatory Information under Rule 32(5) Rule 32(5) specifically identifies the information that must be provided in a stay application. The electronic stay module should therefore contain mandatory fields corresponding directly to the Rule. (a) Brief Facts Regarding the Tax Demand The applicant should provide a concise description of the tax demand against which recovery is sought to be stayed.
The system could, where technically feasible, retrieve the relevant demand from the connected tax/IRIS record, while still allowing the applicant to verify or supplement the information.
(b) Remaining Amount of Tax Due The applicant should provide the remaining amount of due tax. Where the relevant tax demand is available electronically, the system may display the outstanding amount for verification, reducing manual entry and the possibility of inconsistency.
(c) Appeal Details The application must state:
• date of filing of appeal before the Tribunal; and • appeal number, where known.
The proposed portal should preferably link the stay application directly to the existing appeal record.
Accordingly: Select Appeal → Appeal Number Automatically Populated → Filing Date Retrieved → Stay Application Linked to Appeal
This would also prevent the creation of a miscellaneous application without identifying the underlying appeal, where such identification is required.
(d) Previous Stay Application The applicant must disclose whether any application for stay was previously made before:
• the revenue authorities; or • the Tribunal.
Where an earlier application exists within the electronic system, the portal should automatically display the relevant history. The applicant should then indicate:
• whether a previous stay application was filed; • date of filing; • forum; • result; and • details of the relevant order.
(e) Result and Relevant Order Where a previous stay application has been made, the system should require the applicant to provide the result of that application and a copy of the relevant order, as contemplated by Rule 32(5)(d).
Where the order already exists electronically, the system may allow it to be linked directly to the new application rather than requiring duplicate uploading.
(f) Reasons for Seeking Stay Rule 32(5)(e) requires the applicant to state the reasons in brief for seeking stay. The electronic form should therefore provide a dedicated field for the applicant to state the grounds/reasons for stay.
Again, the system should capture the reasons but should not assess their legal sufficiency.
Automated Validation The system can perform a preliminary validation before accepting the application. For example:
Rule 32 Requirement Electronic Validation Tax demand ✓ Provided / Missing Remaining tax due ✓ Provided / Missing Appeal number ✓ Linked / Missing Appeal filing date ✓ Retrieved / Missing Previous stay application Yes / No
Rule 32 Requirement Electronic Validation Result of previous application Required, where applicable Previous order Uploaded/Linked, where applicable Reasons for stay ✓ Provided / Missing Affidavit ✓ Uploaded / Missing Court fee ✓ Paid / Pending
This would directly support Rule 32(6), which provides that an application not conforming to the requirements may be summarily rejected.
However, the system should distinguish between a technical validation failure and the Tribunal's substantive power under Rule 32(6). An automated warning may identify an apparent omission, but the legal decision concerning summary rejection should remain with the authorized officer/Tribunal in accordance with the Rule.
Rule 32(6) — Defective Miscellaneous Applications Rule 32(6) provides: An application which does not conform to the requirements may be summarily rejected. This provision can therefore be linked with the scrutiny mechanism proposed under Rule 16. The electronic system could identify apparent deficiencies before submission and give the applicant an opportunity to complete mandatory information.
The workflow could be: Application → Automated Validation → Deficiency Identified → Applicant Corrects Deficiency → Submission
Where the application remains non-compliant, it can be flagged for the Registrar/authorized officer/Tribunal to take action under Rule 32(6). This would create consistency between the proposed electronic scrutiny process under Rule 16 and miscellaneous applications under Rule 32.
Rule 32(7) — Early Hearing of Stay Application Rule 32(7) provides that on receipt of a stay application, the Registrar or any other officer authorized to act on his behalf shall fix the application for hearing as early as possible. This is one of the strongest areas for automation under Rule 32.
Upon successful submission of a stay application, the system could automatically: Receive Stay Application → Generate Diary/Reference Number → Alert Registrar/Authorized Officer → Identify Available Early Hearing Slot → Fix/Record Hearing → Generate Hearing Notice → Update Cause List → Notify Parties
The system should, however, assist in scheduling rather than independently exercise the Registrar's authority to fix the hearing.
Integration with Rules 19, 20 and 27 The Rule 32 module can be integrated with the other proposed electronic mechanisms.
Stay Application Rule 32 → Application Filed → Early Hearing
Hearing Notice Rule 19 → Form “C” → Electronic Notification
Cause List Rule 20 → Form “B” → Bench-wise Cause List
Adjournment If a party subsequently seeks an adjournment: Rule 27 → e-Adjournment Request → Bench Decision → New Hearing Date → Updated Cause
List This creates a continuous digital case-management chain.
Proposed Digital Workflow for Rule 32 The complete mechanism could therefore be: Existing Appeal Selected ↓ Miscellaneous Application → Stay Application ↓ Rule 32(5) Mandatory Information ↓ Tax Demand + Remaining Amount ↓
Appeal Number + Filing Date ↓ Previous Stay Applications + Results + Orders ↓ Reasons for Stay ↓ Affidavit + Supporting Documents ↓ Court Fee ↓ Electronic Submission ↓ Automated Preliminary Scrutiny ↓ Diary/Reference Number ↓ Registrar/Authorized Officer ↓ Early Hearing under Rule 32(7) ↓ Form “C” / Hearing Notice ↓ Form “B” / Cause List ↓ Hearing → Order
Overall Position Rule 32 can therefore be converted into a dedicated e-Miscellaneous Application and e-Stay Module, while retaining the existing substantive safeguards. The system would validate, link, route, schedule, notify and maintain the record, but the determination of whether stay should actually be granted, whether sufficient grounds exist, and whether an application warrants summary rejection would remain with the competent Tribunal/authority under Rule 32.
8. RULE 36 — ARRANGEMENT OF RECORD AND ELECTRONIC CASE FILE Rule 36 provides the statutory framework for the arrangement and preservation of the record of appeals and other petitions. It is particularly significant for digitization because the Rule expressly recognizes that the term “documents” includes all forms of electronic record.
Part-A and Part-B of the Record Under Rule 36(1), the record of appeals and other petitions consists of two parts: Part-A and Part-B. Rule 36(2) provides that the documents specified in Schedule-I shall form Part-A of the record, while all other documents shall form Part-B, unless otherwise directed by the Chairperson.
Accordingly, the electronic case-management system should preserve the existing legal distinction between Part-A and Part-B, rather than merely creating a generic digital document repository.
Part-A — Core Judicial Record Schedule-I identifies the documents forming Part-A of the record, including:
1. Folder containing particulars of appeals/petitions and a brief abstract of the orders of the Bench; 2. Order sheet or chronological abstract of orders; 3. Original memorandum of appeal; 4. Original petitions; 5. Affidavits; 6. Interlocutory orders of the Benches; 7. Judgment or any other final order; 8. All notes in the handwriting of the Members; and 9. Judgments and orders of High Courts and the Supreme Court.
These categories should therefore form the core structure of the electronic Part-A record. The system could maintain each category as a separately identifiable electronic component within the case file.
For example: Part-A → Case Particulars → Order Sheet → Memorandum → Petitions → Affidavits → Interlocutory Orders → Final Judgment → Members' Notes → High Court/Supreme Court Orders
Part-B — Other Documents All documents other than those specifically identified in Schedule-I would form Part-B of the record, unless the Chairperson directs otherwise.
The electronic case file should therefore provide a separate Part-B repository for other documents forming part of the proceedings. This may include, depending upon the case:
• supporting documents; • correspondence; • applications; • written submissions; • additional documents; • evidence; • notices; • service records; • hearing-related documents; • electronic communications; and • other procedural records.
The precise classification should follow the Rules and directions of the Chairperson rather than being determined solely by the software.
Rule 36(3) — Electronic Arrangement Before Record Room Rule 36(3) requires that, before consigning the record of an appeal or other petition to the record room:
(a) the record shall be arranged into Part-A and Part-B; and
(b) every document shall be marked according to the applicable arrangement with the letter “A” or “B”.
This requirement can be directly translated into the electronic case-management architecture.
Instead of physically arranging documents into two portions of a paper file, the system could assign every electronic document a mandatory classification: Document → Part-A / Part-B → Document Category → Date → Source → Case Reference
The system should prevent the case from being marked as “Record Complete/Ready for Archiving” until the required documents have been classified appropriately.
Electronic Record Expressly Recognized The Explanation to Rule 36 is particularly important for the proposed digital transformation. It expressly provides that: “documents” includes all forms of electronic record. This gives the proposed electronic case-file architecture a significantly stronger basis than simply treating digitization as an administrative convenience.
Accordingly, the electronic case file should be capable of preserving the Tribunal's records in their electronic form, subject to applicable requirements regarding authenticity, integrity, access and preservation.
Proposed Electronic Case File Architecture The ATIR portal could therefore maintain a case-centric electronic record rather than a collection of disconnected uploaded documents.
A proposed structure would be: E-Case File Case Identification ↓ Part-A — Schedule-I Record ↓ Part-B — Other Record ↓ Procedural History ↓ Hearing History ↓ Applications ↓ Orders & Judgments ↓ Appeal/High Court/Supreme Court History
This would allow every document to remain connected to the relevant Appeal/Application Number.
Integration with Earlier Proposed Modules Rule 36 provides the opportunity to integrate all of the electronic mechanisms proposed under the preceding Rules into a single electronic case file.
For example: Rule 8 Electronic filing → Memorandum, Form “A”, Grounds and Enclosures
Rules 12–13 Documents and electronic intimation → Orders, documents, service records
Rules 16–17 Scrutiny and limitation → Deficiency notices, compliance and limitation record
Rules 19–20 Hearing and cause list → Form “C”, Form “B”, hearing notices and cause lists
Rule 21 Hearing and disposal → Hearing history, order monitoring and final order
Rule 27 Adjournments → Adjournment requests, orders and revised hearing dates
Rule 32 Miscellaneous/Stay Applications → Stay applications, affidavits, supporting documents and orders
Rule 36 Complete electronic record
Thus, Rule 36 can effectively become the document-management and archival layer sitting underneath all the preceding electronic processes.
Document Metadata and Audit Trail Each electronic document should ideally carry basic metadata, such as:
• Appeal/Application Number; • Part-A or Part-B classification; • Document category; • Date of document; • Date of filing/upload; • Filed by; • Source; • Related application/order; • Version, where applicable; • Electronic timestamp; and • Status.
This would make it possible to identify not merely what document is in the file, but also when and how it entered the electronic record.
Integrity and Preservation of Electronic Record Since Rule 36 recognizes electronic records, the electronic system should preserve the integrity of the record through appropriate technical controls.
The system should maintain:
Original Electronic Record → Immutable Record → Audit Trail → Controlled Access → Backup → Long-Term Preservation
Any subsequent amendment, replacement or addition should be recorded separately rather than silently replacing the original electronic record. This is particularly important for orders, judgments, affidavits, Members' notes and other core judicial records.
Access and Role-Based Control The electronic case file should also incorporate role-based access.
For example: User Proposed Access Appellant/Representative Filed documents and permitted case information
User Proposed Access Respondent/Representative Relevant case record Registrar Full administrative record Bench/Member Complete judicial record Record Room/Admin Archival record Technical administration without authority to alter judicial System Administrator content The system should distinguish between access to a record and authority to modify a record.
Electronic Record Room Rule 36 can also provide the foundation for replacing the traditional concept of a physical record room with an Electronic Record Room, while retaining physical records where required.
Once the proceedings are completed:
Case Concluded → Part-A/Part-B Verification → Document Classification → Record Completeness Check → Electronic Archiving → Retention/Preservation
The electronic record should remain searchable by:
• Appeal Number; • Application Number; • Appellant; • Respondent; • Tax Year; • Assessment Year; • Date; • Bench; • Order/Judgment; and • other prescribed metadata.
Proposed Digital Model The overall Rule 36 mechanism may therefore be represented as:
Electronic Case File ↓ Part-A — Schedule-I Documents ↓ Part-B — Other Documents ↓ Document Classification A/B ↓ Procedural & Judicial Metadata ↓ Audit Trail & Version Control ↓ Case Completion Verification ↓ Electronic Record Room
Overall Effect Rule 36 is particularly important because the Rules themselves already recognize that “documents” include all forms of electronic record. The proposed system therefore need not create an entirely separate concept of a digital case file; rather, it can translate the existing Part-A/Part-B record structure into an electronic, case-centric environment.
The objective would be to move from: Paper File → Part-A + Part-B → Physical Record Room to: E-Case File → Part-A + Part-B → Electronic Record Room
while preserving the existing classification, judicial record and archival requirements under Rule 36.
9. RULE 45 — COMPUTERIZATION AND AUTOMATION: THE ENABLING PROVISION Rule 45 is the principal enabling provision for the proposed digital transformation of the Appellate Tribunal Inland Revenue. Unlike the preceding Rules, which deal with specific procedural functions such as filing, scrutiny, hearings, adjournments and record management, Rule 45 provides the broader authority for implementing those functions through computerization or automation.
The Rule provides that, for the effective and smooth functioning of the Tribunal, the Chairperson may, from time to time, subject to the availability of resources, direct any Member or officer for enforcement of the Rules through computerization or automation.
Accordingly, Rule 45 can serve as the overarching enabling provision under which the individual electronic mechanisms proposed for Rules 8, 12–13, 16–17, 19–21, 27, 32 and 36 can be implemented.
Scope of Rule 45 The wording of Rule 45 is sufficiently broad to contemplate computerization and automation for the enforcement of the Rules, rather than limiting computerization to a particular procedural stage.
Accordingly, the proposed system should not be conceived merely as an e-Filing Portal. It should function as an integrated electronic case-management and appeals system, covering the lifecycle of a case from filing through disposal and preservation of the record.
A suitable designation could therefore be: ATIR e-Court / Electronic Case Management & Appeals System
Proposed Functional Architecture The system could be structured around the following principal layers:
Layer Major Functions Appeals, stay applications, condonation applications, rectification, 1. e-Filing early hearing and miscellaneous applications Completeness, limitation, prescribed documents, fee and 2. e-Scrutiny identification of defects 3. e-Case Registration, respondent details, Bench allocation, hearing dates, Management adjournments and cause lists Hearing record, attendance, submissions, evidence, orders and 4. e-Hearing case progression Part-A/Part-B electronic record, document classification, retention, 5. e-Record preservation and certified copies
Layer Major Functions 6. e- Notices, intimation, cause lists, orders and electronic notifications Communication
These functions correspond to the individual procedural mechanisms already identified in the preceding Rules.
e-Filing Layer The system should provide a common electronic gateway for filing matters before the Tribunal. The relevant application type could be selected and the system would then generate the applicable electronic requirements.
For example: Login → Select Proceedings → Form/Particulars → Grounds → Documents → Verification → Fee → Submit → Diary No.
The e-Filing layer would therefore operationalize the electronic mechanisms proposed under Rule 8 and Rule 32, while maintaining the prescribed requirements applicable to different proceedings.
e-Scrutiny Layer The system could undertake preliminary procedural validation of filings, including:
• mandatory fields; • prescribed documents; • fee; • date of communication of order; • limitation; • previous applications; • deficiencies; and • compliance with scrutiny requirements.
This would support the proposed electronic implementation of Rules 16 and 17. The important distinction is that automation should perform procedural checking, while matters requiring judicial determination should remain with the Registrar, authorized officer or Bench, as applicable.
e-Case Management Layer Once a matter is filed and registered, the system should maintain a single case record containing:
Appeal → Parties → Respondent → Bench → Hearing → Adjournment → Cause List → Applications → Orders
This would integrate the mechanisms contemplated under Rules 19, 20, 21, 27 and 32. For example, an adjournment granted under Rule 27 should automatically update the hearing date and, where applicable, the relevant cause list under Rule 20.
e-Hearing Layer The system could maintain the procedural record associated with each hearing, including:
• date of hearing; • Bench; • appearance/attendance; • submissions; • applications made during proceedings; • adjournment, if any; • directions of the Bench; • hearing conclusion; and • subsequent order.
This would create a chronological history of the proceedings rather than relying exclusively upon separate physical files. The system should remain administrative and recording in nature and should not interfere with the judicial functions of the Bench.
e-Record Layer Rule 36 provides an important foundation for this layer because it divides the record into Part-A and Part-B and expressly recognizes that “documents” include all forms of electronic record. Accordingly, the system should maintain: Part-A → Schedule-I Record and Part-B → Other Documents within a single electronic case file.
The record could then be preserved through an electronic record room with appropriate classification, audit trail and retention controls.
e-Communication Layer The system could also provide controlled electronic communication for:
• filing acknowledgments; • deficiency notices; • hearing notices; • cause-list notifications; • adjournment decisions; • stay hearing notifications; • orders; and • other procedural communications.
Email, SMS and portal notifications could therefore operate as communication mechanisms linked to the official electronic case record, rather than as independent substitutes for the statutory documents or notices prescribed by the Rules.
Integration with FBR / IRIS A further opportunity would be controlled integration between the proposed ATIR e-Court system and FBR/IRIS, subject to appropriate legal, security, access-control and data- sharing arrangements.
Where technically and legally feasible, relevant information could be retrieved rather than repeatedly entered manually, for example:
Taxpayer NTN/CNIC → Assessment Order → Commissioner (Appeals) Order → Demand → Tax Year/Period → Jurisdiction → Relevant CIR → Departmental Representative
This could substantially reduce:
• duplicate data entry; • transcription errors; • incorrect taxpayer identification; • incorrect order particulars; and • unnecessary manual exchange of documents.
However, such integration would require appropriate authorization, interoperability arrangements, data-security controls and access permissions. Rule 45 itself, as provided, does not specifically prescribe an IRIS integration mechanism; that would therefore be an implementation layer rather than an express requirement of the Rule.
Rule 45 as the Umbrella Provision The relationship between Rule 45 and the proposed amendments can therefore be represented as:
RULE 45 — COMPUTERIZATION & AUTOMATION ↓ Rule 8 — e-Filing ↓ Rules 12–13 — e-Documents & e-Intimation ↓ Rules 16–17 — e-Scrutiny & Limitation ↓ Rules 19–20 — e-Hearing & Cause List ↓ Rule 21 — Order Monitoring ↓ Rule 27 — e-Adjournment ↓ Rule 32 — e-Miscellaneous / e-Stay ↓ Rule 36 — e-Record
Overall Legal/Administrative Position Rule 45 should consequently be positioned at the centre of the proposed reform. The preceding Rules identify individual procedural requirements; Rule 45 provides the mechanism through which those requirements may be implemented and enforced through computerization or automation, subject to the availability of resources and directions of the Chairperson.
The proposed system should therefore be designed not merely to digitize paper filing, but to establish a complete electronic lifecycle of an appeal: e-Filing → e-Scrutiny → Registration → Case Management → Hearing → Adjournment/Applications → Order → e-Record → Electronic Archiving
while ensuring that automation supports the Tribunal's procedural and administrative functions without replacing the judicial discretion vested in the Tribunal, Bench, Registrar or authorized officers under the respective Rules.
Conclusion The proposed ATIR digital transformation should therefore be regarded as an institutional reform of the administration of tax justice, rather than merely an IT project.
The existing Rules already provide the procedural architecture, while Rule 45 provides the enabling basis for computerization and automation. The proposed system would simply translate the existing paper-based processes into an integrated, traceable and secure electronic environment.
Most importantly, the physical and electronic systems can initially operate in parallel. This would allow ATIR to introduce e-filing and electronic case management progressively without disrupting existing litigants or procedures.
The ultimate objective should be: “Faster justice, better case management, greater transparency, reduced administrative burden and improved revenue realization—without compromising the independence, discretion or judicial authority of the Appellate Tribunal.”
This approach would allow ATIR to match the pace of digital transformation already taking place within FBR while preserving the essential character of ATIR as an independent quasi- judicial institution.
Mr. Muhammad Ashraf is a CEO of GNTC, an ACCA Qualified, ex advisor to KCCI, ex-assessor of ACCA Tax Paper while Mr. Yousha is assisting him and can be accessed at taxonomy@gcctaxconsultant.com
