Ethiopia: E-Invoicing and E-Reporting Framework

Current-status date: 2 October 2026

Important status qualification

Ethiopia has enacted a detailed legal and operational framework for clearance-based electronic invoicing through Electronic Invoicing System Administration Directive No. 1142/2026, dated 9 June 2026. However, the framework is not yet a universal nationwide mandate with a published taxpayer rollout date. The directive is legally in force, but the Ministry of Revenues has not published the implementation schedule identifying which taxpayers must migrate and by when. Therefore, statements that Ethiopia already has a fully operational nationwide B2B and B2C mandate should be treated cautiously. [vatcalc.com]

Ethiopian legislation often displays both Ethiopian-calendar and Gregorian-calendar years. Directive No. 1142/2018 in the Ethiopian calendar is generally referenced internationally as Directive No. 1142/2026. Similarly, VAT Proclamation No. 1341/2016 in the Ethiopian calendar is the Gregorian-calendar VAT Proclamation No. 1341/2024, published on 21 August 2024.

1. Introduction and Country Context

1.1 Tax-digitalization journey

Ethiopia has used fiscal sales-register machines for nearly two decades. Council of Ministers Regulations No. 139/2007 established an accredited sales-register-machine framework for taxpayers designated by the tax administration. That framework focused mainly on recording sales through fiscal devices rather than centrally clearing individual invoices.

The modernization journey accelerated through:

• Federal Tax Administration Proclamation No. 983/2016, which established the general taxpayer-record, invoice, enforcement and information-management framework.
• Tax Invoice Utilization and Administration Directive No. 149/2018, which contained Ethiopia’s earlier, limited electronic-invoicing provisions.
• VAT Proclamation No. 1341/2024, which modernized VAT rules and expressly responded to electronic transactions and the digital economy.
• VAT Regulation No. 570/2025, which implements the 2024 VAT Proclamation and contains detailed VAT and invoice rules.
• Electronic Invoicing System Administration Directive No. 1142/2026, which replaces the earlier two-article e-invoicing framework with a standalone 31-article regime.
• Tax Administration Amendment Proclamation No. 1434/2026, which strengthened the statutory basis and penalties supporting electronic invoicing. [justice.gov.et], [justice.gov.et], [justice.gov.et], [kiyalaw.com]

1.2 Policy objectives

The Ethiopian framework is intended to:

• provide real-time visibility of taxable sales;
• reduce omitted sales, duplicate invoices, false invoices and manipulated transaction values;
• standardize sales-registration and invoicing software;
• improve the reliability of VAT declarations and audit data;
• regulate software developers, cloud providers, marketplaces and service providers supporting invoicing;
• move tax control from retrospective physical inspection toward automated transaction-level supervision; and
• support the government’s broader objective of building a modern tax administration by 2030. [mor.gov.et], [feyselanda…ciates.com]

1.3 Regional and international position

Ethiopia is adopting a centralized clearance or pre-validation model, comparable in principle to continuous transaction control systems used elsewhere in Africa, Latin America and parts of Asia. It is not adopting the European decentralized Peppol model or an EU-style post-transaction Digital Reporting Requirement. [kiyalaw.com]

The available legislation does not formally state that the design follows an OECD CTC specification, OECD SAF-T, Peppol BIS, EN 16931 or UN/CEFACT standards. Any comparison with those standards is presently analytical rather than a statement of legal alignment.

1.4 Supranational authorization

• Ethiopia is not an EU Member State and therefore does not require a derogation from Articles 218 or 232 of the EU VAT Directive.
• No WTO notification, regional treaty authorization or other supranational approval specific to the mandate was identified.
• No published link has been identified between Ethiopia’s system and the African Continental Free Trade Area or another regional invoice-exchange mechanism.

2. Regulatory Framework

2.1 Primary legislation

VAT Proclamation No. 1341/2024

The Value Added Tax Proclamation No. 1341/2024, dated 21 August 2024, replaced VAT Proclamation No. 285/2002. It applies VAT to domestic taxable supplies, imports, reverse-charged supplies and specified remote or electronically supplied services. It also provides the statutory basis for tax invoices, debit notes, credit notes and adjustments. [ethiodata.et], [a-tla.org]

The official text is available through the [Ethiopian Ministry of Justice].

Federal Tax Administration Proclamation No. 983/2016

This proclamation provides the general rules for:

• taxpayer registration and TINs;
• record keeping;
• use of invoices;
• administrative penalties;
• criminal invoice offences;
• audits and access to records; and
• the Ministry’s authority to regulate electronic tax systems. [justice.gov.et], [justice.gov.et]

The official text is available through the Ethiopian Ministry of Justice.

Tax Administration Amendment Proclamation No. 1434/2026

The amendment entered into force on 30 July 2026. It strengthened the legal basis for rules covering electronic tax systems, QR-coded invoices and electronic commerce. It also increased the administrative penalty for failure to issue a required tax invoice to ETB 100,000 per invoice. [justice.gov.et]

2.2 Implementing regulations and directives

VAT Regulation No. 570/2025

Council of Ministers VAT Regulation No. 570/2025 implements Article 72(1) of VAT Proclamation No. 1341/2024. It contains detailed rules relevant to VAT registration, invoices, adjustments and VAT administration. The Federal Negarit Gazette publication is dated 17 March 2025, although the Ministry of Justice catalogue displays 26 January 2026 on the landing page. Businesses should therefore retain the Gazette version as the controlling publication record. [justice.gov.et], [justice.gov.et]

Electronic Invoicing System Administration Directive No. 1142/2026

The directive:

• establishes the Electronic Invoice Registration System;
• defines when an electronic invoice becomes valid;
• regulates approved sales-registration systems;
• introduces accreditation for software suppliers and service providers;
• regulates cloud solutions, marketplaces and internally developed systems;
• prescribes real-time registration, IRNs, RRNs and QR codes;
• provides outage procedures;
• regulates cancellations and adjustments;
• establishes a Technical Team and Accreditation Board; and
• delegates the rollout timetable to the tax authority. [kiyalaw.com]

The directive repeals Articles 8 and 23 of Tax Invoice Utilization and Administration Directive No. 149/2018 but does not repeal the broader fiscal-device regime. [360ground.com], [kiyalaw.com]

2.3 Circulars, guidance and FAQs

The Ministry of Justice catalogue lists an official Explanatory Note on the Electronic Invoicing System Administration Directive, dated 9 June 2026. However, no comprehensive public English-language implementation manual, API guide, onboarding FAQ, validation-rule catalogue or taxpayer rollout schedule was located as of 2 October 2026. [justice.gov.et], [justice.gov.et]

The Ministry of Revenues provides an eTax portal, legal-publication pages, forms, FAQs and a QR-verification facility. These portals should be monitored for the implementation schedule and technical releases. [mor.gov.et], [etax.mor.gov.et]

2.4 International legal basis

No EU, Peppol, OECD or other international legal instrument forms part of the direct legal basis. The mandate is based on Ethiopian domestic tax-administration and executive-powers legislation. [kiyalaw.com]

3. Scope of the Mandate

3.1 Transactions in scope

The directive ultimately targets transactions for which Ethiopian tax law requires the issuance of an invoice and, more specifically, transactions on which VAT is chargeable under Article 3 of VAT Proclamation No. 1341/2024. The activation date for individual taxpayer categories remains subject to a future schedule. [vatcalc.com]

Domestic B2B

• Domestic B2B transactions between registered taxpayers are a central part of the framework.
• Article 20 distinguishes invoices between registered taxpayers that are intended for tax reporting. These invoices must be registered through a direct connection and cannot be included only in a sectoral summarized-sales report.
• Once a taxpayer is activated, a paper or ordinary PDF without system registration, IRN/RRN and QR authentication will not constitute the compliant invoice for an in-scope transaction. [360ground.com]

Domestic B2C

• The directive does not generally exclude B2C transactions.
• Retail, hospitality, transport, fuel, pharmaceuticals and similar high-volume activities are expressly contemplated.
• Certain high-volume sectors may receive permission to submit summarized consumer-sales data daily, weekly or monthly instead of connecting each consumer transaction directly, but invoices must still carry a unique number and QR code.
• The reporting frequency will be determined by the tax authority by sector.

Domestic B2G

• No separate procurement-specific B2G invoice format or independent B2G timeline has been published.
• Supplies to government bodies appear to follow the ordinary transaction rules.
• Government budget institutions must use the electronic registration system when issuing withholding-tax receipts for domestic purchases of goods and services. [vatcalc.com], [vatupdate.com]

Intra-EU acquisitions and supplies

• Not applicable. Ethiopia is not part of the European Union VAT territory.
• Ethiopia has no EU-style intra-Community acquisition, intra-Community supply or triangulation simplification.

Imports

• Customs import declarations and supporting commercial invoices remain the principal documents for import VAT.
• No rule has been identified requiring a foreign supplier’s import invoice to be cleared through the Ethiopian system merely because the goods are imported.
• Imports are nevertheless within the substantive scope of Ethiopian VAT under VAT Proclamation No. 1341/2024. [ethiodata.et], [ysalawoffice.com]

Exports

• Exports that qualify as zero-rated supplies remain subject to the VAT law’s documentary and invoice requirements.
• Where an Ethiopian taxpayer required to use the system issues an export invoice, the broad wording suggests that the invoice may need to be registered electronically. However, no export-specific technical code, workflow or formal exclusion has yet been published.

Other cross-border B2B transactions

• Remote services, electronically supplied services and reverse-charged supplies are addressed by the VAT Proclamation.
• No evidence was found that a non-established foreign supplier must connect to the domestic invoice-clearance system solely because it is registered under a simplified remote-services arrangement.
• No detailed e-reporting schema for inbound reverse-charge invoices has been published. [ethiodata.et], [ysalawoffice.com]

3.2 Special transactions

Self-billing

The current public directive and available official summaries do not expressly establish a dedicated self-billing workflow, buyer-issued invoice flag or special platform authorization. Self-billing should therefore not be assumed to be operationally supported without written confirmation from the Ministry of Revenues.

Triangulation and chain transactions

There is no EU-style triangulation simplification. In multi-party chains, each Ethiopian-taxable supply must be analyzed separately. An invoice issued by an activated Ethiopian taxpayer for a domestically taxable leg would be expected to follow the electronic-invoice requirements, but no dedicated chain-transaction reporting fields have been published.

Special VAT regimes

No detailed electronic-invoicing rules were found for:

• travel-agent margin schemes;
• second-hand-goods margins;
• investment gold;
• flat-rate farmers;
• consignment stock;
• call-off stock; or
• sector-specific margin calculations.

Where a transaction is taxable and an invoice is legally required, the default assumption should be that the electronic-invoicing framework applies once the taxpayer is activated, unless a future schedule or directive provides otherwise.

3.3 Exclusions and special reporting relief

Direct-connection relief may be granted for consumer transactions in:

• banking;
• securities markets;
• digital-payment processing; and
• telecommunications.

The Ministry may extend the summarized-reporting model to other high-volume sectors. This is not a full exemption from invoice controls. The affected invoices must retain unique identifiers and QR codes, and registered-taxpayer B2B invoices remain subject to direct registration.

4. Taxable Persons in Scope

4.1 Established entities

Article 29 of the directive provides that taxpayers required to maintain books of account will ultimately be required to use a compliant electronic sales-registration system according to the schedule issued by the Authority. This potentially includes companies, partnerships, sole traders and other persons falling within the relevant accounting category. [360ground.com]

The directive itself does not contain a separate turnover threshold. The VAT-registration threshold and the e-invoicing population are therefore not necessarily identical. VAT sources report a general compulsory VAT-registration threshold of ETB 2 million annual taxable turnover, but a person can potentially be subject to accounting or invoice obligations for reasons other than VAT registration. [ysalawoffice.com], [apexhab.com]

4.2 Non-established entities

• Foreign entity with an Ethiopian fixed establishment: likely treated as an established taxpayer for local taxable transactions if it is registered and required to keep Ethiopian books.
• Foreign entity VAT-registered without a fixed establishment: no specific inclusion or exclusion has been published.
• Foreign remote-services supplier using simplified registration: no technical rule currently confirms a requirement to issue invoices through the domestic clearance platform.
• Foreign entity without Ethiopian registration: no general platform obligation was identified.

These conclusions remain provisional until the taxpayer-designation schedule and onboarding guidance are published.

4.3 Voluntary participation

Article 19 permits voluntary adoption by taxpayers not yet compulsorily activated if they use a compatible approved system. Details of the application, acceptance criteria and any lock-in consequences have not yet been published.

4.4 Sector-specific rules

The directive regulates or specifically contemplates:

• banks and financial institutions;
• securities markets;
• digital-payment processors;
• telecommunications operators;
• e-commerce and digital marketplaces;
• retail;
• fuel;
• restaurants and accommodation;
• transport and postal services;
• pharmaceutical and healthcare-related sales; and
• government budget institutions. [kiyalaw.com]

No general exemption for SMEs, micro-enterprises, financial services, healthcare or public bodies has been published.

5. Implementation Timeline

5.1 Legislative history

• 26 January 2007: fiscal sales-register-machine regime established under Council of Ministers Regulations No. 139/2007.
• 20 August 2016: Federal Tax Administration Proclamation No. 983/2016 enacted.
• 2018: Tax Invoice Utilization and Administration Directive No. 149/2018 introduced limited electronic-invoice provisions.
• 21 August 2024: VAT Proclamation No. 1341/2024 published.
• 17 March 2025: VAT Regulation No. 570/2025 published in Federal Negarit Gazette No. 31.
• 9 June 2026: Electronic Invoicing System Administration Directive No. 1142/2026 dated and registered.
• 1 July 2026: specialist sources report publication on the Ministry of Revenues website and entry into force under Article 31.
• 30 July 2026: Tax Administration Amendment Proclamation No. 1434/2026 entered into force. [justice.gov.et], [justice.gov.et]

5.2 Pilot or voluntary phase

The directive permits voluntary use of a compatible system, but no formal pilot population, pilot start date or incentive package has been publicly identified.

5.3 Mandatory go-live

As of 2 October 2026:

• no nationwide go-live date has been published;
• no taxpayer threshold or first-wave list has been issued;
• no separate B2B, B2C or B2G date has been announced;
• no date for mandatory receipt of electronic invoices has been announced; and
• no SME phase has been announced. [vatcalc.com], [vatupdate.com]

5.4 Grace periods

No official penalty-free period, soft-landing period or transitional acceptance of PDF invoices has been announced. Existing invoicing and fiscal-device rules remain relevant until each taxpayer is required to migrate.

5.5 Pre-mandate milestones

Expected milestones include:

• publication of the taxpayer implementation schedule;
• availability of definitive schemas and API documentation;
• launch or confirmation of test and production environments;
• publication of accredited system and provider lists;
• issuance of digital certificates;
• taxpayer portal registration; and
• issuance of System Numbers, API Keys and Client Secrets. [360ground.com]

5.6 Postponements

No postponement can currently be identified because no binding nationwide start date has yet been announced.

6. Operating Model

6.1 Model classification

Ethiopia’s intended model is a centralized, real-time clearance model:

1. The seller’s approved system prepares the transaction.
2. Transaction data is transmitted to the Electronic Invoice Registration System.
3. The Ministry’s system validates the submission.
4. The system returns an Invoice Registration Number or Receipt Reference Number and a QR code.
5. The invoice or receipt is issued only after confirmation. [360ground.com], [kiyalaw.com]

This combines invoice clearance with transaction-level e-reporting. Separate summarized reporting may be permitted for designated high-volume consumer sectors.

6.2 Invoice lifecycle

Step 1: Creation

The taxpayer generates the invoice using:

• approved software;
• an approved SaaS or cloud solution;
• an approved electronic-invoicing service provider; or
• an internally developed system authorized by the tax authority. [vatcalc.com], [vatupdate.com]

Step 2: Submission

The system transmits transaction data in real time to the centralized registration system.

Step 3: Validation

The transaction is checked for required data and system validity. Public sources do not yet provide a complete catalogue of business-rule validations or error codes.

Step 4: Clearance

The platform returns:

• an IRN for an invoice;
• an RRN for a receipt; and
• a QR code.

The document is not considered valid until this response has been received. [360ground.com]

Step 5: Delivery

The approved system must support delivery to the purchaser by printing, email, SMS or another authorized electronic method. [360ground.com]

Step 6: Buyer retrieval

Detailed buyer-portal and API-retrieval functions have not yet been publicly documented. The QR code allows authentication or verification through the Ministry’s QR-verification facility. [mor.gov.et]

Step 7: Archiving

The taxpayer remains responsible for retention. Central registration should not be treated as replacing the taxpayer’s statutory record-retention obligation.

6.3 Authentication and access

Taxpayer onboarding is expected to require:

• registration through the Taxpayer Portal;
• a System Number;
• an API Key;
• a Client Secret; and
• a digital-signature certificate issued by the Information Network Security Administration or another authorized body. [360ground.com]

The detailed rules for authorizing accountants, fiscal representatives, self-billing customers or other third parties have not been published.

6.4 Offline and contingency mode

Manual QR-coded invoices are permitted when:

• the Authority announces a system outage;
• a supplier cannot remedy a system defect within two hours; or
• widespread network or power disruption affects taxpayers.

Transactions issued under the contingency process must be registered within 72 hours after connectivity is restored, with reference to the manual invoice number. Twenty-six sectors listed in Annex 2 must have software capable of offline operation. [inventory.et]

6.5 Buyer acceptance

No evidence was identified that affirmative buyer acceptance is a condition for legal validity. Validity appears to depend principally on registration and assignment of the required platform identifiers.

6.6 QR code

A QR code is mandatory on a registered invoice or receipt. Public material confirms that it supports authentication, but the complete encoded dataset and formal QR specification have not been publicly identified. [vatcalc.com], [feyselanda…ciates.com]

7. Acceptable E-Invoice Formats

7.1 Mandatory format

No publicly available legal text prescribes UBL, CII, Peppol BIS, EN 16931, XML or another internationally standardized syntax. The directive refers to a compliant electronic sales-registration system and includes a sample invoice in Annex 1, but it does not publicly establish a complete machine-readable semantic or syntactic standard.

Accordingly:

• a structured system-to-platform message is operationally required;
• PDF alone is not the clearance payload;
• paper or PDF may serve as a human-readable representation;
• the legally authenticated invoice requires system registration, relevant registration number and QR code; and
• taxpayers should not build integrations around a vendor-specific XML format until official technical specifications are obtained.

7.2 International standards

No official alignment has been identified with:

• EN 16931;
• Peppol BIS Billing 3.0;
• UBL 2.1;
• UN/CEFACT CII;
• Factur-X or ZUGFeRD; or
• OECD SAF-T.

7.3 Transitional formats

Manual QR-coded invoices are allowed only under prescribed contingency circumstances. No general dual-format PDF/XML arrangement or permanent hybrid-invoice option has been published.

7.4 Attachments

No official rule was identified governing embedded attachments, external file references, purchase orders, delivery notes or supporting PDFs within the electronic-invoice message.

8. Technical and Functional Requirements

8.1 Invoice data

Based on the VAT framework, the Directive and available descriptions, the invoice dataset is expected to cover:

• supplier legal identity, address and TIN;
• buyer identity and TIN where applicable;
• invoice or receipt number;
• issue date and time;
• transaction and item descriptions;
• quantities and units;
• unit prices;
• discounts or price adjustments;
• taxable amount;
• tax category and rate;
• VAT, excise or withholding amounts where applicable;
• total consideration;
• payment information where required;
• IRN or RRN;
• QR code; and
• references to earlier invoices for debit notes, credit notes or cancellations. [justice.gov.et], [360ground.com], [kiyalaw.com]

A definitive field-by-field data dictionary and coded-list catalogue has not been publicly identified.

8.2 E-reporting

Two e-reporting mechanisms are contemplated:

• Real-time transaction registration for ordinary in-scope invoices, particularly invoices between registered taxpayers.
• Periodic summarized sales reporting for approved high-volume consumer sectors, potentially daily, weekly or monthly as determined by the Authority.

Ethiopia has not announced a VAT SAF-T, JPK, SII-type ledger file or a separate standardized invoice-data report comparable to EU digital reporting.

8.3 Digital signature and integrity

Digital certificates are part of taxpayer and system authentication. Approved systems must protect data from unauthorized alteration, maintain audit trails and meet security-certification requirements. Platform clearance, registration numbers, QR codes and controlled system access collectively support invoice authenticity and integrity. [360ground.com]

8.4 Real-time processing

The primary model is real-time clearance. Public legislation does not provide contractual uptime percentages, maximum response times or service-level commitments.

9. Corrections

9.1 Invoice corrections

The directive regulates:

• cancellation;
• debit notes;
• credit notes;
• price changes; and
• transaction adjustments. [vatcalc.com], [vatupdate.com]

A cancellation request must be submitted electronically to the Authority. If the Authority requests supporting evidence, the taxpayer has 48 hours to respond. Cancellation becomes effective only after approval and registration through the system.

The safer operational approach is:

• do not overwrite or delete a cleared invoice;
• issue a registered credit note, debit note or corrective document;
• reference the original IRN and invoice number;
• state the reason for the adjustment;
• include the corrected taxable amount and VAT;
• retain the full audit trail; and
• ensure the correction is reflected in the relevant VAT return.

9.2 E-reporting corrections

No separate corrective-file schema or published deadline exists for correcting summarized sector reports. Errors affecting a VAT return should be corrected under the VAT and Tax Administration rules, potentially through an amended declaration and payment of additional tax, interest and any applicable penalty.

No dedicated public form for correcting an electronic-invoice report was identified.

10. Transmission and Workflow

10.1 Central platform

The platform is referred to as the Electronic Invoice Registration System or, in some advisory material, the Electronic Invoice Management System. It is operated for the Ministry of Revenues. The Information Network Security Administration has a supporting role in system security and digital certification. [dddinvoices.com]

10.2 Transmission channels

Permitted models include:

• direct integration by an approved taxpayer system;
• approved locally installed invoicing software;
• an approved SaaS or cloud platform;
• an accredited electronic-invoicing service provider;
• an approved e-commerce or digital-marketplace system;
• a self-developed system authorized for exclusive use; and
• an Authority-provided Cloud Sales Registration System where applicable. [vatcalc.com], [kiyalaw.com]

Peppol is not listed as a transmission channel.

10.3 Accredited providers

Accreditation tracks apply separately to:

• sales-registration-system suppliers;
• SaaS providers;
• e-commerce and marketplace operators; and
• taxpayers developing systems for their exclusive use.

Security guarantees start at different levels, including USD 30,000 for system suppliers, USD 50,000 for SaaS providers, USD 25,000 for marketplace operators and USD 15,000 for exclusive-use systems. Higher guarantees of up to USD 250,000 can apply depending on user numbers or transaction values.

No authoritative public register of accredited providers was located.

10.4 Hosting and interoperability

Hosting for regulated systems must be located in Ethiopia and meet Tier III or equivalent Level 3 data-centre standards, with registered public IP addresses and required security assurance. Cross-border cloud hosting should therefore not be assumed to be permissible for the regulated platform component.

No Peppol, EN 16931 or foreign-platform interoperability framework has been announced.

10.5 Deadlines

• Normal invoice registration: real time.
• Contingency invoices: upload within 72 hours after restoration.
• Summarized sector reporting: daily, weekly or monthly, as set by the Authority.
• VAT accounting: monthly under the VAT Proclamation.
• VAT return/payment: advisory sources report filing by the last day of the following month, but businesses should verify this against the applicable official VAT provisions and their taxpayer status. [metaappz.com], [apexhab.com]

11. Self-Billing

• No dedicated self-billing provisions were identified in the published electronic-invoicing materials.
• No self-billing code, invoice flag or buyer-authentication process has been published.
• No explicit rule confirms whether a foreign customer may connect and issue an Ethiopian supplier’s invoice.
• No platform-specific buyer approval or deemed-acceptance process has been published.
• Businesses should not assume that an existing contractual self-billing arrangement automatically satisfies the electronic-invoicing rules.
• A written ruling or clarification should be obtained before implementing self-billing after the relevant taxpayer is activated.

12. Triangulation and Special Scenarios

12.1 Triangulation

EU triangulation is not applicable. Each Ethiopian leg must be classified under domestic place-of-supply, import, export and reverse-charge rules.

12.2 Chain transactions

No specialized chain-transaction fields or reporting simplifications have been published. Each supplier in a chain should determine separately whether it makes a taxable supply in Ethiopia and whether it must issue a registered invoice.

12.3 Reverse charge

The VAT Proclamation recognizes reverse-charged supplies, including relevant services received from non-residents. No evidence was found that a foreign supplier’s invoice must itself be cleared through Ethiopia’s platform. The Ethiopian recipient must account for VAT according to the substantive reverse-charge rules. [ethiodata.et], [ysalawoffice.com]

12.4 Zero-rated and exempt supplies

• Qualifying exports may be zero-rated.
• Exempt activities remain governed by the VAT Proclamation and schedules.
• No comprehensive electronic coding list for exemptions and zero rates has been published.
• Systems should support tax-category codes, exemption reasons and documentary references once the technical specifications are issued.

12.5 Local nuances

Important Ethiopian features include:

• withholding-tax receipts issued by government budget institutions;
• fiscal-device and sales-register continuity;
• QR-based invoice verification;
• direct B2B registration despite possible B2C summarized reporting;
• mandatory offline resilience for designated sectors;
• mobile-device location controls and approved geofencing; and
• domestic hosting and INSA security certification. [vatcalc.com], [360ground.com]

13. Archiving and Retention

13.1 Central storage

The registration system receives transaction data centrally. The legislation reviewed does not state that central storage relieves taxpayers of their own record-keeping obligations.

13.2 Required format

Taxpayers should retain:

• the original structured submission;
• the platform response;
• IRN or RRN;
• QR code;
• human-readable representation;
• status and rejection messages;
• cancellations and corrective documents;
• manual contingency invoices; and
• evidence of subsequent upload.

No rule was identified requiring both XML and PDF because the final mandatory syntax has not been published.

13.3 Retention period

Federal Tax Administration Proclamation No. 983/2016 requires relevant records to be retained for five years from the date the corresponding tax declaration is filed, or longer where the Commercial Code requires a longer period.

A secondary technology source states ten years, but this conflicts with the more detailed legal analysis based on Article 17 of Proclamation No. 983/2016. Until official clarification is obtained, businesses should apply the longer internal retention period where practical, while recognizing that the specifically identified tax-law minimum is five years. [dddinvoices.com]

13.4 Storage location

Tax records must be maintained in Ethiopia and in Amharic or English. Regulated service-provider hosting must also be located in Ethiopia. Offshore-only archiving should not be adopted without confirming that immediate local access and required domestic copies are maintained.

13.5 Integrity and readability

Integrity should be maintained through:

• digital signatures and certificates;
• role-based access;
• tamper-resistant audit trails;
• retention of original platform responses;
• secure backup;
• prevention of unauthorized transaction deletion; and
• preservation of readable invoice representations. [360ground.com]

13.6 Audit access

Records must be made available to the tax authority. The real-time registration system gives the authority transaction data at issuance, but taxpayers must still preserve supporting commercial, accounting and correction records.

14. Penalties and Enforcement

14.1 Transitional enforcement

No general grace period has been published. Until the implementation schedule is issued, the new framework should not be described as universally activated. Existing invoice, tax-return and record-keeping penalties continue to apply.

14.2 Administrative penalties

Under the 2026 amendment, failure to issue a tax invoice when required attracts an administrative penalty of ETB 100,000 for each invoice not issued to the buyer. The Authority may not waive that penalty. [justice.gov.et]

14.3 Criminal invoice offences

The updated framework provides severe criminal exposure:

• understating the sales price or issuing invoices showing inconsistent or understated prices can attract an ETB 100,000 fine and rigorous imprisonment of five to seven years;
• where the actual transaction price exceeds ETB 100,000, the fine may equal the highest price and imprisonment may run from seven to ten years;
• producing, distributing or using fraudulent invoices can attract an ETB 100,000 fine and seven to ten years’ imprisonment;
• where the fraudulent benefit exceeds ETB 100,000, the fine may equal the benefit and imprisonment may run from ten to fifteen years; and
• criminal liability for simple failure to issue an invoice generally follows two prior administrative penalties for the same act within one tax period.

14.4 Provider liability

Under Article 28 of Directive No. 1142/2026, software suppliers, service providers and marketplace operators may face:

• forfeiture of their security guarantee;
• suspension or revocation of accreditation;
• civil liability;
• criminal liability; and
• liability for discrepancies attributable to their system or technical defect.

No separate e-reporting late-filing penalty schedule specific to summarized electronic reports was identified. General tax-administration penalties would apply.

15. Pre-Filled VAT Returns

• Ethiopia does not currently have a publicly documented system of fully pre-filled periodic VAT returns generated from cleared invoice data.
• Existing VAT returns remain taxpayer-filed monthly declarations.
• No official implementation date for pre-filled VAT returns has been announced.
• The clearance database could technically support future pre-population of output VAT and, where buyer matching is available, input VAT.
• It is not yet known whether tax, taxable-base, credit-note or import fields will be pre-filled.
• No link exists to EU ViDA pre-filled-return provisions because Ethiopia is outside the EU framework.

16. Readiness for ViDA and International Digital Reporting

16.1 Position relative to ViDA

ViDA is not legally applicable to Ethiopia. Ethiopia is nevertheless moving ahead of many jurisdictions in establishing a transaction-level clearance architecture, although its taxpayer rollout has not yet commenced nationally.

16.2 Technical alignment

Potential areas of alignment include:

• structured transaction data;
• rapid reporting;
• unique transaction identifiers;
• automated validation;
• digital authenticity; and
• system-to-system integration.

Important gaps compared with ViDA, EN 16931 and Peppol include:

• no published semantic data standard;
• no confirmed UBL or CII syntax;
• no decentralized multi-provider interoperability model;
• no EU-compatible cross-border reporting dataset;
• no published buyer-delivery standard; and
• no stated international identifier or code-list alignment.

16.3 Cross-border digital reporting

No mechanism exists for transmitting Ethiopian invoice data to an EU VAT Information Exchange System or another supranational platform.

16.4 Business implications

Multinationals should design the Ethiopian solution as a country-specific clearance connector while preserving a global canonical invoice model. Mapping should be capable of supporting future Ethiopian fields without embedding local logic directly into core ERP billing processes.

17. Impact on SMEs and Startups

17.1 Phased onboarding

No SME-specific timeline has been published. The future schedule may phase taxpayers by accounting category, sector, turnover or technical readiness, but no criteria have yet been confirmed. [vatcalc.com], [vatupdate.com]

17.2 Government tools and support

The framework contemplates an Authority-operated Cloud Sales Registration System, which could reduce entry costs for smaller taxpayers. The Ministry also maintains the eTax portal, QR verification, forms, FAQs and a toll-free support line. Detailed SME onboarding manuals and training schedules have not yet been located. [mor.gov.et]

17.3 Simplifications

Potential simplifications include:

• summarized B2C reporting for approved high-volume sectors;
• voluntary early participation;
• an Authority cloud solution; and
• manual QR invoices during qualifying outages.

No general SME turnover exemption from the directive has been identified.

17.4 Subsidies

No dedicated grant, tax credit, software subsidy or reimbursement programme for e-invoicing implementation was identified.

17.5 Compliance costs

Likely one-time costs include:

• ERP or POS modification;
• API development;
• master-data cleansing;
• digital certificates;
• local hosting;
• testing and accreditation;
• offline transaction queues;
• QR generation;
• staff training; and
• migration from fiscal devices.

Ongoing costs may include provider fees, certificate renewal, software maintenance, data-centre services and regulatory updates.

17.6 Cash-flow and operational effects

Potential benefits include:

• earlier error detection;
• better sales and VAT reconciliation;
• reduced paper handling;
• automated customer posting;
• improved audit trails; and
• potentially faster future VAT verification.

No official commitment to faster VAT refunds based on e-invoice participation has been published.

17.7 Burden versus simplification

The initial burden may be material for smaller firms because of connectivity constraints, local hosting and certification requirements. Longer-term benefits will depend on whether the Authority’s cloud system is affordable, whether APIs are stable and whether invoice data can be reused for accounting and VAT returns.

17.8 Market impact

The accreditation and security-guarantee requirements may favor larger or well-capitalized technology providers. At the same time, the framework creates opportunities for local ERP, POS, cloud and integration firms. Offline resilience will be a critical competitive feature in the Ethiopian market. [inventory.et]

17.9 SME readiness assessment

No official national SME-readiness assessment, cost-benefit study or quantified digital-capability survey specific to Directive No. 1142/2026 was identified.

18. Official References and Sources

18.1 Government portals

• Ministry of Revenues
• Ministry of Revenues eTax portal
• Ministry of Revenues QR verification service
• Ministry of Justice taxation and revenue register

18.2 Legislation

• [Electronic Invoicing System Administration Directive No. 1142/2026]
• [VAT Proclamation No. 1341/2024]
• VAT Regulation No. 570/2025
• Federal Tax Administration Proclamation No. 983/2016
• Tax Administration Amendment Proclamation No. 1434/2026

18.3 Technical specifications

No complete, authoritative and publicly accessible API specification, schema package, validation-rule catalogue or sandbox documentation was identified. The directive and Annex 1 provide functional requirements and a sample invoice, but not a complete public technical implementation package.

18.4 Official guidance

• The Ministry of Justice catalogue lists an Explanatory Note on the Electronic Invoicing System Administration Directive, dated 9 June 2026.
• The Ministry of Revenues website and eTax portal remain the principal channels to monitor for schedules, FAQs and onboarding instructions. [justice.gov.et], [mor.gov.et]

18.5 Advisor and technology publications

• VATCalc: Ethiopia adopts e-invoicing framework
• VATupdate: Ethiopia establishes legal and operational framework
• Kiya and Associates: Legal analysis of Directive No. 1142/2026
• PKF Ethiopia / Feysel & Associates: Electronic Invoicing Directive
• [E-Invoice.app: Ethiopia guide and missing implementation date]
• 360Ground: Practical guide to Directive No. 1142/2026
• [Eagle Advocates: Digital shift in Ethiopian tax compliance]

18.6 Source-quality observations

• The official Ministry of Justice texts are the most authoritative sources.
• Advisory sources generally agree that the directive is in force but the taxpayer schedule is outstanding.
• Some technology websites incorrectly describe the mandate as already universally enforced.
• Some sources describe the retention period as ten years, while legal analysis citing Article 17 of Proclamation No. 983/2016 identifies five years or the longer Commercial Code period.
• Public references to Regulation No. 570 vary between 2025 and 2026. The official Gazette identifies it as Regulation No. 570/2025.

19. Summary and Key Takeaways

19.1 Scope

Ethiopia has established a broad legal framework covering taxpayers required to maintain books and issue invoices, including domestic B2B and B2C transactions, government withholding receipts, marketplaces and high-volume sectors. However, the mandatory taxpayer population will become operational only under a separate implementation schedule.

19.2 Format

A registered electronic invoice must be produced through an approved system and carry an IRN or RRN and QR code. No official UBL, CII, Peppol, EN 16931 or national XML schema has yet been publicly confirmed.

19.3 Timeline

Directive No. 1142/2026 is in force, but as of 2 October 2026 there is no nationwide go-live date, phased taxpayer timetable, SME date or announced grace period.

19.4 How it works

The intended model is real-time centralized clearance. The seller transmits the transaction, the Ministry validates it, and the system returns registration identifiers and a QR code before the invoice is issued. Approved sectoral B2C-summary reporting and a 72-hour post-outage upload process are available in defined circumstances.

19.5 Key obligations

Businesses should prepare to:

• use an approved solution;
• register through the Taxpayer Portal;
• obtain system credentials and a digital certificate;
• transmit transactions in real time;
• store IRN/RRN and QR data;
• process credit notes, debit notes and cancellations electronically;
• maintain offline capability where required; and
• retain accessible records in Ethiopia.

19.6 Main risks

Principal risks include:

• relying on an unapproved vendor;
• treating a PDF as the legal e-invoice;
• failing to capture the platform response;
• inadequate offline continuity;
• inaccurate tax coding;
• inability to link corrective documents to original invoices;
• provider or hosting non-compliance;
• loss of support for input-VAT deductions; and
• substantial administrative or criminal penalties.

19.7 SME implications

No SME exemption or special rollout date has been published. The Authority’s cloud solution may reduce entry costs, but connectivity, certification, software upgrades, digital skills and provider costs remain significant concerns.

19.8 International readiness

The move to transaction-level clearance is consistent with the international trend toward continuous transaction controls, but Ethiopia has not aligned its public specifications with Peppol, EN 16931, ViDA or OECD SAF-T.

19.9 Critical dates and next steps

The key date is not yet known. Businesses should monitor the Ministry of Revenues for the implementation schedule and should now:

• identify Ethiopian legal entities, establishments, registrations and invoicing flows;
• inventory ERP, POS, marketplace and manual-invoice processes;
• map B2B, B2C, B2G, export, import and reverse-charge scenarios;
• assess local hosting and digital-certificate requirements;
• build IRN/RRN, QR, cancellation and offline-queue capabilities;
• verify provider-accreditation status;
• preserve existing fiscal-device compliance; and
• avoid committing to a technical syntax until the Ministry releases definitive schemas and API specifications.