Ethiopia’se-invoicingdirective,explainedforpeoplewhohavetoimplementit
Directive 1142/2026 explained: IRN and QR clearance, accredited suppliers, offline rules and penalties - for Ethiopian businesses running an ERP or POS.
Directive No. 1142/2026 requires taxpayers who keep books of accounts to issue invoices through an approved electronic system connected to the Ministry of Revenues. A valid invoice must carry an Invoice Registration Number, a Receipt Registration Number and a QR code, obtained before the invoice is valid. Suppliers of the software must themselves be accredited.
Last reviewed
What changed, in one section
Ethiopia has replaced a two-article rule with a thirty-one-article one. Directive No. 1142/2026 repeals Articles 8 and 23 of the Tax Invoice Utilization and Administration Directive No. 149/2018 and puts a full electronic invoicing regime in their place.
The practical shift is from reporting after the fact to clearing in near-real time. Previously a business issued invoices and reported periodically. Now the invoice itself is not valid until the Ministry’s central system has issued identifiers for it. That turns invoicing from an accounting task into an integration problem.
If your ERP, POS or billing system cannot transmit to the Ministry’s system and print an IRN and QR code, it cannot issue a valid invoice. That is a software dependency with a regulatory deadline attached, and it usually sits with whoever supplied or maintains the system rather than with the accountant.
What a valid invoice must now carry
Article 4(1)(c) sets out three clearance elements that must be obtained before an invoice is valid:
- An Invoice Registration Number (IRN), issued by the Ministry’s central system
- A Receipt Registration Number (RRN), also Ministry-issued
- A QR code linked to the cleared transaction data
Minimum invoice content is specified separately, in Regulation No. 570/2026, which the directive references rather than restates. If you are scoping an implementation, treat that regulation as a required input - the directive alone will not tell you every field you need to print.
Who needs accreditation - four different categories
This is the part most summaries flatten, and getting it wrong changes who is responsible for what. The directive accredits four distinct kinds of actor separately.
| Category | Article | Who this is |
|---|---|---|
| Sales registration system suppliers | Article 7 | Companies that supply POS or invoicing systems to other businesses |
| Software-as-a-Service providers | Articles 5 and 14 | Cloud billing or ERP platforms serving Ethiopian taxpayers |
| E-commerce and marketplace operators | Article 6 | Platforms hosting multiple sellers |
| Taxpayers building software for their own exclusive use | Article 8 | A business whose in-house system issues its own invoices |
Article 8 catches more businesses than expected: an in-house billing system built years ago by a contractor still puts the taxpayer in an accreditation category.
Article 4 sets a prescriptive technical checklist that an accredited system has to meet:
- Real-time transmission to the Ministry’s system
- Capability to issue IRNs and QR codes
- Role-based access control
- Audit logging
- INSA security clearance
- Geo-fencing, for mobile point-of-sale systems
Certification is decided by a Technical Team and an Accreditation Board (Articles 9–10 and 18), with a two-thirds vote required. Article 14(6) additionally requires tiered bank or insurance-backed performance guarantees, running from roughly USD 10,000 for a small supplier base up to USD 250,000 for the largest, with staffing minimums scaled to user base or aggregate annual sales. Suppliers have to monitor their own tier and notify the Authority when they cross a threshold.
What happens when the connection drops
A real-time clearance requirement in a country with intermittent connectivity needs fallbacks, and the directive provides three. If you are implementing, these are the paths your system has to support - not edge cases to handle later.
- Mandatory offline mode for listed sectorsAnnex 2 enumerates 26 high-volume retail, hospitality, healthcare and transport sectors that must support offline operation. If you are in one of them, offline capability is not optional.
- The Authority’s own cloud systemAn Authority-operated Cloud Sales Registration System serves new entrants, suspended taxpayers, and sectors with no compliant commercial option available yet.
- Manual QR invoices, as a last resortPaper invoices remain possible in extremity, but must be reconciled into the electronic system within 72 hours of connectivity being restored. That reconciliation is itself a feature someone has to build.
Article 20 carves out summary reporting for banks, securities markets, payment processors and telecom operators, which may report invoice data in periodic summaries rather than transaction by transaction. B2B invoices used for input-tax purposes still have to be cleared individually, so the exemption is narrower than it first appears.
What non-compliance costs
- Taxpayers face administrative and potential criminal liability under Proclamation 983/2016 for tampering or failing to register invoices.
- Suppliers face civil and criminal liability and forfeiture of their performance guarantee where a discrepancy is traced to a defect in their system (Articles 25–28).
- For marketplaces, Article 6 requires each seller to invoice under its own TIN, name and address, and the Authority may suspend individual sellers without disabling the platform.
Article 29 sets a transition period, and it matters most if your current system was certified only under the now-repealed 2018 provisions. That certification does not carry over on its own.
We are not quoting a transition deadline here because the published legal analyses reference Article 29 without stating the date, and we are not going to print a deadline we cannot source. Confirm it against the directive text or Ministry guidance before you plan around it.
What to do now, in order
A sensible sequence, whether you work with us or with anyone else:
- Establish which category you are inAre you a taxpayer using a supplied system, a taxpayer running in-house software under Article 8, a supplier, or a marketplace? This determines whose accreditation obligation it is.
- Ask your current supplier for their accreditation position in writingIf they supply your POS or billing system, they need accreditation under Article 7 or 14. A vague answer now is a compliance failure later, and the liability under Articles 25–28 attaches to defects in their system.
- Check whether you are in an Annex 2 sectorIf you are, offline capability is mandatory and materially changes the implementation scope.
- Read Regulation No. 570/2026 for the field-level invoice requirementsThe directive tells you clearance is required; the regulation tells you what has to be printed.
- Scope the integration honestlyReal-time transmission, RBAC, audit logging and a 72-hour reconciliation path are not small additions to a system that was not designed for them. Some systems are cheaper to replace than to retrofit.
- Confirm the Article 29 transition date against primary sourcesThen work backwards from it. Do not plan against a date you read in a summary, including this one.
We build and integrate ERP, billing, and accounting systems to comply with Ministry of Revenues real-time invoice transmission protocols, automated IRN generation, and secure QR code validation.
Our engineering team handles API integrations, security logging, cryptographic validation, and automated reconciliation for Ethiopian enterprises.
Sources
This page summarises published analyses of the directive rather than the directive text itself. Where they are silent - the Article 29 date, retention periods, exact penalty amounts - this page is silent too. Verify against the directive and Ministry guidance before acting:
- Kiya & Associates Law Office - legal analysis of Directive No. 1142/2026, article by article
- PKF Ethiopia (Feysel and Associates) - introduction to the electronic invoicing directive
- Eagle Advocates - Electronic Invoicing System Ethiopia: Directive 1142 guide
- Regulation No. 570/2026 - minimum invoice content (referenced by the directive)
- Proclamation 983/2016 - the penalty regime the directive applies
Questions people ask
Find out what your system actually needs
Send us what you are running - the ERP, POS or billing system, and roughly how many invoices a month go through it. We will tell you what the directive requires of it and whether retrofitting or replacing is the cheaper path.