Ethiopia e-Invoicing Guide

Ethiopia has a complete e-invoicing rulebook and not a single taxpayer with a deadline. The Electronic Invoicing System Administration Directive No. 1142/2026 , 31 articles and two annexes signed by Minister Aynalem Nigussie Ali, was published on the Ministry of Revenues website on 1 July 2026 and took effect on publication under Article 31. It sets out how invoices are registered, how software is accredited, what an exempt sector may do instead and what happens when the connection drops. Article 29 (1) then makes a compliant sales register system mandatory for every taxpayer obliged to keep books of accounts, and immediately hands the timing to someone else: implementation "shall be carried out in accordance with the schedule issued by the Authority".

That schedule does not exist. No phase, no threshold, no sector order and no start date has been published, and the Ministry has issued nothing on the subject since. So the regime is legally in force and practically dormant. Ethiopia is not a country where you have missed a deadline; it is a country where the obligation is written, the technical bar is high and the clock has not been started. The directive is nonetheless drafted for a staged start. Article 18 (6) (k) makes issuing the implementation schedule a duty of the Accreditation Board it establishes, and Article 29 (2) tells taxpayers already using sales register software to migrate on that same schedule.

One trap catches almost everyone reading Ethiopian tax law for the first time, and it is worth clearing up before any of the numbers below make sense. Ethiopian legislation is numbered by the Ethiopian calendar, which runs seven to eight years behind the Gregorian one. The directive is cited on its own cover as both 1142/2018 and 1142/2026, because 2018 in the Ethiopian calendar is 2026. The VAT proclamation everyone writes as 1341/2016 is Proclamation No. 1341/2024 , published on 21 August 2024. A reference to "the 2016 VAT proclamation" in an Ethiopian source is almost always the 2024 law, not the 2016 one, and trackers that copy the Ethiopian year across as though it were Gregorian date this reform eight years too early.

Ethiopia has policed sales electronically for nearly twenty years, just not with invoices. Council of Ministers Regulations No. 139/2007 , published in Federal Negarit Gazeta No. 48 on 26 January 2007, made accredited sales register machines obligatory for taxpayers named in ministerial directives and prescribed what every machine-generated receipt must show. That fiscal device regime, backed by cash register machines and fiscal memory, is what Ethiopian businesses have actually operated ever since. Regulation No. 139/2007 has not been repealed; what Directive 1142/2026 does is require that estate to connect and register each document rather than merely record it.

The statutory scaffolding arrived in two pieces, nearly a decade apart. Federal Tax Administration Proclamation No. 983/2016 of 20 August 2016 supplied the record-keeping duties, the invoice offences and, in Article 19 (4), the power the Ministry later used to issue the directive. Proclamation No. 1341/2024 of 21 August 2024 then replaced the 2002 VAT law and set the tax invoice, debit note and credit note rules the directive builds on, including the Article 3 test that decides which transactions it reaches at all.

The last month of activity is the important one. The directive appeared on 1 July 2026. Four weeks later Proclamation No. 1434/2026 , carried in Federal Negarit Gazette No. 48 of 30 July 2026 and effective on publication, amended the 2016 proclamation to give the directive a firmer statutory footing and to sharpen the penalty behind it. Nothing has been published since. Anyone tracking Ethiopia should watch the Ministry of Revenues directives register for one document: the implementation schedule that Article 18 (6) (k) makes the Accreditation Board's job to issue. It is the single thing standing between this framework and a live obligation.

Scope is set by what you are, not by whom you sell to. Article 3 of the directive applies it to taxpayers that issue invoices under the tax law, to sales registration system suppliers, to taxpayers running software for their own exclusive use, to software-as-a-service providers and to e-commerce and digital marketplace operators. Article 3 (2) then limits it to transactions on which VAT is chargeable under Article 3 of Proclamation No. 1341/2024. Article 29 (1) fixes the population that will eventually be called up: every taxpayer obliged to maintain books of accounts. Taxpayers already required to use sales register software under Directive No. 149/2018 must move to a compliant system on the same schedule.

The directive draws no line between business, government and consumer sales, so Ethiopia has no separate B2G regime, no procurement-specific format and no public sector timetable. A supply to a ministry and a B2C sale over a shop counter are caught on exactly the same terms. Where the directive does discriminate is between B2B and everything else. Article 20 (5) singles out invoices between registered taxpayers that are intended for tax reporting: those must be registered through a direct connection to the Electronic Invoice Registration System, and Article 20 (6) keeps them out of the summarised report that some sectors are allowed to file instead.

The reliefs are sectoral and conditional rather than size-based, and there is no turnover threshold anywhere in the directive. Article 20 (1) lets the Authority release taxpayers in banking, securities markets, digital payment processing and telecommunications from the direct connection for consumer transactions, on the ground that their operations generate high invoice volumes and are already open to audit. They report summarised sales instead, on a daily, weekly or monthly cycle the Authority sets by sector, and every invoice must still carry a unique number and a QR code. Article 20 (2) lets the Ministry extend that approach to other sectors.

Annex 2 works the other way round and is easy to misread as a let-off. Article 19 (3) provides that a sales register system used in a listed sector must mandatorily function in offline mode, so for retail sale of food, beverages, tobacco, fuel, clothing and pharmaceutical goods, passenger rail and urban transport, postal services, short-term accommodation and restaurants, offline business continuity is a required capability of the software rather than an exemption from using it. Article 19 (4) lets the Tax Authority revise that list, and Article 19 (2) leaves voluntary adoption open to any other taxpayer with a compatible system. Records must be kept for five years from the date the relevant tax declaration was filed, or the Commercial Code period if longer, in Amharic or English and inside Ethiopia, under Article 17 of Proclamation No. 983/2016.

This is a clearance regime, and the drafting leaves no room to read it as anything softer. Article 4 (1) (c) accredits a sales registration system only where it issues an invoice or receipt after transmitting the transaction to the Electronic Invoice Registration System, having its validity confirmed and obtaining three things back: an Invoice Reference Number, a Receipt Reference Number and a QR code. Article 4 (1) (b) requires that transmission to happen in real time as the transaction occurs. The document is not valid until the numbers come back. That is CTC in its strictest form, and it puts Ethiopia in the same bracket as Turkey and the Latin American clearance countries. Within Africa it is less of a departure than it sounds: clearance is already the second most widely used model on the continent, behind real-time reporting.

No format has been prescribed, and that gap is genuine rather than an omission in this guide. The directive names no syntax, no schema and no delivery network. Annex 1 supplies a sample receipt, and Article 4 (1) (a) sets the minimum invoice content by reference to the Value Added Tax Regulation. There is no mention of Peppol, no reference to EN 16931 or UBL, and no accredited-provider list has been published. Vendors marketing an Ethiopian offering built on any particular standard are describing a product decision, not a legal requirement.

The accreditation bar is the part that will surprise software vendors, because it is unusually heavy. Article 14 requires a performance guarantee secured by a bank or insurer and renewable every two years, entered at USD 30,000 for a system supplier, USD 50,000 for a software-as-a-service provider, USD 25,000 for an e-commerce or digital marketplace operator and USD 15,000 for a taxpayer running a system for its own exclusive use. Article 14 (6) then sets the real figure on a ten-level scale keyed to whichever of user taxpayer numbers or aggregated annual sales is reached first, from nothing at all below 500 user taxpayers or ETB 5 billion of sales up to USD 250,000 above 40,000 taxpayers or ETB 1,000 billion, with required qualified staff rising from two to eight. Hosting must sit inside Ethiopia and meet a Tier III or Level 3 data centre standard, with registered public IP addresses and a security assurance certificate. Systems are inspected before approval and may be re-inspected up to three times in six months after a failure.

Who decides is set out too, which is unusual in a directive this early. Article 18 establishes a Technical Team and an Accreditation Board appointed by the Minister for two-year terms. The Technical Team, capped at nine members and chaired from the Software Development Directorate, runs the testing and signs off results by a two-thirds majority; it also physically inspects a provider's data centre where necessary. The nine-member Accreditation Board is chaired by an official designated by the Head of the Authority and includes the directors of tax intelligence, tax filing, software development and regional support, plus two representatives of regional and city administration revenue authorities. It verifies the bank or insurance guarantee, recommends licences to the State Minister of the e-Data Division, who takes the final decision, and issues a certificate of accreditation signed jointly by the Board chair and that State Minister.

Onboarding runs through the Authority's own portal, and the mechanics are already specified even though nobody has been called up. Under Article 19 (5) a taxpayer registers for the electronic invoicing service through the Taxpayer Portal and receives a System Number, an API Key and a Client Secret, then obtains a digital signature certificate from the Information Network Security Administration or another authorised body against its name, tax identification number and registered system number. The sales register software is configured with those credentials. E-commerce and digital marketplace users follow the same route under Article 19 (6), naming the platform they trade on.

Continuity is handled explicitly, which is a sign the drafters expected connectivity problems. Article 22 permits manual invoices carrying a QR code while the Electronic Invoice Registration System is unavailable, whether because the Authority has announced an outage, because a supplier cannot fix a defect within two hours, or because a large-scale network or power interruption is affecting many taxpayers. Every transaction handled that way must be registered within 72 hours of the connection being restored, referencing each manual invoice number. Article 26 covers corrections: a cancellation request goes to the Authority through the system, the taxpayer has 48 hours to answer any request for supporting evidence, and the cancellation is valid only once approved and re-registered.

The penalty behind the regime was rewritten a month after the directive appeared, and it is now severe. Proclamation No. 1434/2026 repealed Article 108 of the 2016 proclamation, renumbered 125, and replaced it: a taxpayer that fails to issue a tax invoice when required is liable for ETB 100,000 for each invoice not issued to a buyer, double the previous ETB 50,000 and charged per invoice rather than per transaction. Sub-article (2) bars the Authority from waiving it. The same amendment inserted the provision requiring the tax authority to issue a directive on the electronic tax system, on invoices carrying a QR code and on e-commerce, which is what Directive 1142/2026 now rests on.

Criminal exposure sits alongside the administrative penalty and predates it. Article 120 (2), renumbered 137 (2), punishes understating a sales price, whether by recording different prices on identical invoices for one transaction or simply by issuing an invoice that understates the price, with a fine of ETB 100,000 and rigorous imprisonment of five to seven years; where the actual price exceeds ETB 100,000 the surviving sub-article (3) raises the fine to the highest price shown and imprisonment to seven to ten years. Article 119, renumbered 136, deals with fraudulent invoices at ETB 100,000 and seven to ten years, rising to the benefit obtained and ten to fifteen years above that threshold. A new sub-article (8) added in 2026 is the one piece of restraint: criminal liability for simply failing to issue an invoice bites only after the person has been penalised administratively twice for the same act within a single tax period.

Accredited vendors carry their own exposure, which is worth pricing into any Ethiopian go-to-market plan. Under Article 28 of the directive, suppliers, service providers and marketplace operators that fail their obligations face criminal and civil liability and forfeit the security bond they deposited. Where a discrepancy between the registration system and a taxpayer's sales records is traced to the provider or to a technical defect in its system, the provider carries the liability rather than the taxpayer. Article 13 separately allows a licence to be revoked where a security assurance certificate lapses, where defects go unrectified, or where transaction data is shared outside the system.