
Directive No. 1142/2026: What Businesses Must Know
INTRODUCTION
The Ministry of Revenue has issued Directive No. 1142/2026 (the “Electronic Invoicing System Administration Directive”), establishing a comprehensive legal framework for the use, licensing, operation, and administration of the Electronic Sales Register System (ESRS) and the Electronic Invoice Registration System (EIRS) in Ethiopia. Effective upon registration with the Ministry of Justice and publication on the Ministry of Revenue’s official website, the Directive marks a significant step toward a real-time, technology-driven tax administration regime. It replaces the fragmented e-invoicing provisions of Tax Invoice Utilization and Administration Directive No. 149/2018 and introduces a comprehensive, standalone regime with five core pillars: Mandatory real-time integration, Tiered licensing and accreditation, Scalable financial guarantees, Sector-specific offline mandates, and Strict liability and enforcement.
This piece provides a comprehensive regulatory analysis of the applicable legal framework, key regulatory instruments, principal developments, taxpayer obligations, system inspection and licensing process, institutional structure for accreditation, and liability framework, issues warranting close attention, and practical compliance considerations for businesses and advisors.
LEGAL FRAMEWORK & AUTHORITY
The Directive is issued pursuant to:
- Article 19(4) of the Definition of Powers and Duties of the Executive Organs Proclamation No. 1263/2021 empowers the Ministry of Revenue to issue Directives necessary for the discharge of the powers, duties, and responsibilities vested in it under applicable laws.
- Article 19(4) of the Federal Tax Administration Proclamation No. 983/2016, which empowers the Ministry to issue directives to specify how taxpayers shall manage invoicing and record-keeping obligations.
It operates within the broader normative ecosystem of:
- Federal Tax Administration Proclamation No. 983/2016: Provides the overarching framework for tax compliance, penalties, and administrative enforcement, which this Directive directly invokes for liability purposes under Articles 27 and 28.
- VAT Proclamation No. 1341/2024 and VAT Regulation No. 570/2025: The Directive directly cross-references these instruments for the minimum content requirements of electronic invoices and for rules governing Tax Debit & Credit Notes (Article 20 & 21 of the VAT Regulation; Articles 43 & 44 of the VAT Proclamation).
- Income Tax Proclamation No. 979/2016 (as amended by Proclamation No. 1395/2024): The concept of “Permanent Establishment” referenced in Article 2(23) of the Directive carries the meaning given under the federal income tax framework, which matters for determining when a foreign-developed sales register system developer is required to hold a local supplier license.
- Tax Invoice Utilization and Administration Directive No. 149/2018: Partially repealed by this Directive, specifically Articles 8 & 23 pertaining to electronic invoices. Taxpayers previously governed by that Directive’s e-invoicing provisions must now migrate under Article 29 of this Electronic Invoicing System Administration Directive.
KEY INSTRUMENTS & CONCEPTS INTRODUCED
The Directive introduces and formally defines a layered ecosystem of instruments and actors:
Core Technological Infrastructure
| Instrument | Description |
|---|---|
| Electronic Invoice Registration System (EIRS) | A Ministry-developed central platform for registering, verifying, and processing invoice data in real time. All compliant sales register software must integrate with the EIRS. |
| Electronic Invoice (E-Invoice) | A digital transaction document issued using Ministry-accredited Sales Registration Software, transmitted to & registered by the EIRS. |
| Registered Electronic Invoice | An e-invoice that has been assigned both an Invoice Registration Number (IRN) and a QR Code by the EIRS, these are the legally valid outputs. |
| Cloud Sales Register System | An Authority-operated fallback system available for transitional use, newly registered taxpayers, and scenarios where an accredited system is unavailable. |
| Offline Business Continuity System | A defined contingency mechanism allowing transactions to continue for a limited period when real-time EIRS connectivity is lost, with mandatory catch-up registration within 72 hours. |
| Manual Invoice with QR Code | A paper-based fallback authorized only under specific, enumerated conditions such as EIRS downtime or taxpayer system failure exceeding two hours. |
Invoice Types Governed
The Directive covers the following invoice and receipt types, all of which must be processed through the ESRS:
- Cash Sales Invoice (VAT receipt, Excise Tax receipt, or exempt sale receipt)
- Credit Sales Invoice
- Cash Receipt (for advance payments, loan receipts, credit settlements, not for sale of goods/services)
- Withholding Tax Receipt
- Purchase Voucher (for tax-authority-recognized transactions where a standard receipt cannot be issued)
- Receipt for VAT Withheld by the Buyer
- Tax Debit Note / Tax Credit Note (for VAT adjustments under Articles 43 – 44 of Proclamation No. 1341/2024)
- E-Commerce / Digital Marketplace Receipt
Categories of Authorized System Providers
| Category | Description & Performance Guarantee Required at Entry Level |
|---|---|
| Sales Registration System Supplier | Sells accredited ESRS software to taxpayers. Entry guarantee: USD 30,000. Minimum 4 qualified professionals at application. |
| Sales Registration System Service Provider (SaaS) | Provides ESRS on a subscription basis. Entry guarantee: USD 50,000. Minimum 6 qualified professionals. Must maintain Tier III data centre in Ethiopia. |
| E-Commerce / Digital Marketplace Operator | Operates a digital platform connecting buyers and sellers. Entry guarantee: USD 25,000. Must separately register and issue invoices per seller TIN. |
| Taxpayer Using Own Exclusive System | Develops or purchases a system solely for own use where accredited market solutions are inadequate. Entry guarantee: USD 15,000. Must have a distinct ownership/management structure. |
WHAT THE DIRECTIVE DOES – NEW SYSTEM ARCHITECTURE
Before this Directive, e-invoicing in Ethiopia was governed by fragmented provisions of Directive No. 149/2018. The new Directive replaces those provisions with a comprehensive, standalone regime. Key structural changes include:
Mandatory Real-Time Integration
Every licensed ESRS must transmit transaction data to the EIRS in real time as the transaction occurs. An invoice may only be generated after the EIRS has validated the data and issued an IRN & QR Code. This creates a closed-loop system where no valid invoice can exist outside EIRS knowledge.
Tiered Licensing Regime
The Directive establishes a two-tier licensing structure. First, a system license granted to the software itself following inspection by the Technical Team. Second, a supplier/provider accreditation license is granted to the entity selling or providing the system. Both must be maintained with biennial renewals. A licensed system operated by an unlicensed entity is non-compliant, and vice versa.
Scalable Guarantee and Staffing Requirements
Rather than a flat guarantee, the Directive introduces a ten-tier scaling table (Article 14(6)(a)) that increases both the performance guarantee amount and the mandatory number of qualified professionals as the provider’s taxpayer base or aggregated annual sales volume grows. The maximum tier (Level 10: above 40,000 taxpayers or above ETB 1 trillion in annual sales) requires USD 250,000 in guarantees and 8 professionals, in addition to the base entry requirements.
Sector-Specific Offline Mandate
Annex Two of the Directive lists 26 business sectors for which offline-capable ESRS is mandatory. These span retail trade, transport, hospitality, healthcare, personal services, and entertainment, sectors where connectivity interruptions are common & transaction continuity is critical. The Tax Authority retains the power to amend this list.
Exemptions for High-Volume Issuers
Banks, securities markets, digital payment processors, and telecom service providers may, with Ministry authorization, issue invoices without direct EIRS integration for consumer transactions, instead submitting summarized sales data at daily, weekly, or monthly intervals. However, B2B transactions involving registered taxpayers must still be registered individually through the EIRS.
Cloud Sales Register System
The Authority provides a Cloud Sales Register System as a backup for taxpayers unable to reach approved systems. Newly registered taxpayers may use this for up to 2 months from acquiring a business license till an approved system is implemented, where the Authority validates the taxpayer lacks capacity to utilize an authorized system, where the Tax Authority demands or authorizes use based on transaction nature or business sector, where flaws are identified in the taxpayer’s system until corrections are made, or where the system or provider is suspended till the taxpayer can utilize another system.
- SYSTEM INSPECTION AND LICENSING PROCESS
- Preconditions for Testing
Any ESRS submitted for testing must:
- Undergo and pass verification tests on the testing system to demonstrate capability to provide required services.
- Submit the system identification number used for inspection, the time of testing, and the completed checklist.
- Submit supporting documents including detailed service descriptions, software design, technology list, system version and last update date, integration documentation, and types of invoices included.
- Clearly disclose any third-party intellectual property rights or open-source components.
Inspection Process
The inspection procedure requires that:
- Documents required for inspection must be fully completed and submitted to the inspection team.
- The inspection team may request incomplete or additional explanatory documents.
- The supplier must provide a sample computer or device with the system installed.
- No modifications may be made to a system once inspection has commenced.
- If defects are identified, they must be rectified and the inspection restarted.
- A system found defective may be re-inspected after rectification for a maximum of three times within six months.
Licensing
Licensing is granted upon full compliance with all technical requirements under the Directive. For offline systems, additional requirements must be fulfilled. For mobile systems, additional requirements must be fulfilled.
License Renewal and Revocation
Licenses must be renewed every two years. Upon renewal, the following must be submitted:
- A software security certificate from INSA not more than one month old
- Verification confirming that modifications issued by the Authority have been implemented within the specified timeframe
- A registered system checksum to verify no unauthorized modifications have been made
If the renewal period expires and ten days elapse, the system is suspended from the market. If the period exceeds three months, the license is revoked. Additional grounds for license revocation include:
- Failure to implement modifications issued by the Authority within the specified timeframe
- When the security certificate is revoked or expires
- When defects found in the system are not rectified within the specified timeframe
- When unauthorized modifications are found in operation
- When transaction data has been shared with a third party outside legal authorization
MAJOR TAXPAYER OBLIGATIONS
Every taxpayer required to maintain books of account under Ethiopian tax law is subject to this Directive. The major taxpayer obligations include:
Issuance and Registration Obligations
- Issue a registered electronic invoice for every sale. The law has provided no exceptions outside the enumerated fallback scenarios.
- Register for the EIRS through the Tax Authority’s Taxpayer Portal, obtain a System Number, API Key, Client Secret, and a Digital Signature Certificate from INSA or an authorized body.
- Where offline mode is used, transmit all offline transaction data within 72 hours of EIRS connectivity being restored.
Inspection and Cooperation Obligations
- Cooperate fully with Tax Authority inspections of the ESRS at any time, including granting system access to Authority employees.
- Provide appropriate information during inspections and cooperate in the process.
Buyer Information Obligations
- Record buyer identity details (TIN, ID, or phone number) on the invoice when the buyer requests it.
- Where the buyer’s TIN or identification is recorded, ensure notifications regarding invoice cancellation requests and approvals are delivered to the buyer through digital means.
System Integrity Obligations
- Refrain from making any software changes or modifications to the accredited ESRS without Authority approval.
- When using an exclusively licensed system, do not transfer or make available the system to any third party.
Invoice Cancellation Obligations
- Submit invoice cancellation requests electronically immediately upon discovering an error.
- Respond to Authority evidence requests within 48 hours.
- Cancellation is valid only upon approval by the Authority and registration in the EIRS.
Withholding Tax and Purchase Voucher Obligations
- Taxpayers making payments subject to withholding tax must issue withholding tax receipts through the electronic system.
- Where standard receipts cannot be provided, purchase vouchers may be used as evidence of expense, but these must be prepared by the buyer and comply with all applicable requirements.
SUPPLIER OBLIGATIONS
Suppliers have specific ongoing obligations:
- Implement system updates within specified timeframes whenever the Authority introduces modifications.
- Provide updates, security patches, and fundamental modifications to user taxpayers within specified timeframes.
- Notify the Authority before making modifications to accredited systems.
- Cooperate with the Authority’s monitoring and supervision activities and provide requested information and reports promptly.
- Extract and provide customer lists and transaction data during investigations.
- Do not collect data beyond operational requirements or transfer taxpayer data to other systems without a legally valid special agreement.
- Provide standardized maintenance and support through Service Level Agreements.
- Notify the Tax Authority when user taxpayers commence or terminate the system
SANCTIONS & LIABILITY FRAMEWORK
The Directive imposes a dual-track liability regime:
Taxpayer Liability (Article 27)
A taxpayer is subject to administrative penalties and potential criminal liability under the Federal Tax Administration Proclamation No. 983/2016 for:
- Failure to register an issued e-invoice (or manual QR invoice) with the EIRS.
- Altering invoice data or deleting system data without Authority authorization.
- Discrepancies between the registered invoice data and information provided to the buyer.
- Unauthorized transfer of an exclusively licensed ESRS to a third party.
- Any other violation of the Directive’s obligations.
Provider Liability (Article 28)
Sales Register Software providers, SaaS providers, and e-commerce platform operators face:
- Criminal and civil liability under relevant laws for failure to discharge Directive obligations.
- Forfeiture of the deposited performance guarantee bond.
Attribution of liability where a discrepancy between EIRS data and taxpayer sales records is proven to result from the provider’s system defect.
- ISSUES WARRANTING CLOSE ATTENTION
- Permanent Establishment & the Supplier License Obligation
Under Article 24, where a taxpayer purchases or licenses a sales register system from a developer that is either (a) based in Ethiopia or (b) constitutes a permanent establishment in Ethiopia (within the meaning of the Income Tax Proclamation No. 979/2016, as amended), that developer is required to hold a formal supplier license. This creates a compliance obligation not just for the taxpayer but for the system developer and should be scrutinized in commercial contracts for ERP or POS system integration.
E-Commerce Platforms – Multi-Party Invoice Obligation
Where a single transaction on an e-commerce or digital marketplace involves multiple sellers or the platform operator itself, each seller must issue a separate invoice using their own TIN, name, and address. Platform operators must build systems capable of this disaggregation. Combined printing for convenience is permissible only where individual invoice content remains clearly visible.
Data Residency Requirement for SaaS Providers
Article 14(3)(g) mandates that the infrastructure through which SaaS sales register services are provided must be physically located within Ethiopia, meeting at least Tier III data center design standards. Foreign-based cloud providers cannot serve this market without establishing qualifying in-country infrastructure.
System Modification Controls
Once an ESRS is licensed, any modification must be pre-notified to the Authority. Modifications affecting security, tax calculation, messaging, or core invoice issuance require a full regression test under Articles 9 and 10. Unauthorized modifications may result in license revocation under Article 13(5). This applies equally to taxpayers using exclusively licensed systems.
Exit and Transition Management
Providers terminating services must give 6 months’ advance notice to both the Authority and user taxpayers, submit and receive approval for an exit strategy, and ensure all taxpayer data is transferred within 6 months of service termination. Failure to comply exposes the provider to civil and criminal liability and forfeiture of the performance bond.
Transitional Compliance Timeline
The Directive does not set a single migration deadline. Instead, mandatory adoption is phased in accordance with an implementation schedule to be issued by the Authority. Taxpayers currently using sales register software under Directive No. 149/2018 must migrate to EIRS-compliant systems per that schedule. Newly licensed taxpayers have up to 2 months to implement an accredited system, during which the Authority’s Cloud system may be used.
WHAT BUSINESSES & ADVISORS SHOULD DO NOW
- Audit your current invoicing infrastructure: Determine whether your existing POS, ERP, or billing system is among the accredited ESRS or is capable of EIRS integration. Assess whether it meets all technical requirements, including real-time transmission, QR code generation, audit logging, and security certification.
- Engage accredited suppliers early: The Authority’s implementation schedule will impose firm deadlines. Early engagement avoids last-minute compliance failures and associated penalties. Verify that your supplier holds valid accreditation and has deposited the required performance guarantee.
- Review commercial contracts: Agreements with software vendors, ERP integrators, and cloud service providers should be reviewed for compliance with the Directive’s accreditation, data residency, and supplier license requirements. Ensure contracts address liability allocation for system defects.
- Train operational staff: Cashiers, finance personnel, and system administrators must understand the fallback protocols for system downtime and the 72-hour registration obligation. Staff must also understand the invoice cancellation procedures.
- For SaaS or e-commerce operators: Begin infrastructure planning to ensure compliance with Tier III data centre, data isolation, and professional staffing requirements. Assess your current and projected taxpayer base against the scaling table to determine your guarantee and staffing obligations.
- For system developers with local clients: Assess whether your development activity triggers the mandatory supplier license obligation under Article 24 of the directive. If you have a permanent establishment in Ethiopia or are locally based, you must obtain accreditation.
- Learn about the cancellation procedures: Be familiar with the steps for cancelling an invoice, such as receiving immediate notification and responding to Authority evidence requests within 48 hours. Keep in mind that the Authority may have restrictions on cancellation frequency and timing.
- Get ready for system changes: Establish internal protocols for reporting any changes to your ESRS to the Authority.
- Apply proper regression analysis to any changes in security, tax calculation, or the allocation of core invoices.
- Establish contingency plans that address system failures, such as comprehending manual QR-code invoice fallback procedures and the Cloud Sales Register System.
CONCLUSION
Directive No. 1142/2026 is not merely a technical update to Ethiopia’s invoicing rules; it is a structural transformation of how tax compliance is monitored and enforced. By anchoring every sale to a real-time, centrally registered digital record, the Ministry of Revenue is effectively closing the gap between declared income and actual transactions.
For taxpayers, the message is clear: the era of paper-based and self-managed invoicing is ending. Compliance now requires not just issuing the right invoice but issuing it through an accredited system that speaks directly to the EIRS in real time, every time.
For businesses operating e-commerce platforms, SaaS systems, or ERP-integrated environments, the obligations go deeper: data residency, provider accreditation, performance guarantees, and professional staffing requirements must all be in place before users can legally transact through your platform. For system developers, a direct compliance obligation exists where the developer is locally based or has a permanent establishment in Ethiopia. This has significant implications for commercial contracts and system integration projects.
The transitional window is an opportunity, not a grace period. The implementation schedule to be issued by the Authority will set firm timelines, and the penalty framework under Proclamation No. 983/2016 leaves little room for late movers. Businesses that begin their compliance assessment, system migration, and staff training now will be far better positioned than those who wait for enforcement to begin. The question is not whether to comply, but how quickly and effectively your business can adapt to the new reality.
This article is general information and not legal advice. Contact us about your specific situation.



