MakinganERPcomplywithEthiopia’se-invoicingrules
What has to change inside an ERP or POS to clear invoices under Ethiopia’s Directive 1142/2026 - and how to tell whether retrofitting or replacing is cheaper.
To comply with Directive No. 1142/2026 an ERP or POS must transmit invoices to the Ministry of Revenues in real time, obtain and print an Invoice Registration Number and QR code, enforce role-based access control, keep audit logs, and support a 72-hour offline reconciliation path. Its supplier must also hold accreditation.
Last reviewed
What to check in your current system
Work through these before commissioning anything. Most of the cost of an e-invoicing project is determined by how many of them your current system already does, and that is knowable in an afternoon.
| Capability required | Question to ask of your system | If the answer is no |
|---|---|---|
| Real-time transmission | Can it call an external API at the moment of invoice creation, and block on the response? | Significant work. Batch-oriented systems are architecturally the wrong shape for clearance. |
| IRN and QR printing | Can the invoice template carry Ministry-issued identifiers and a generated QR code? | Usually moderate - template and storage changes, plus a field to hold the identifiers. |
| Role-based access control | Are permissions per-role, or does everyone share a login? | Shared logins are common in older deployments and a genuine blocker. |
| Audit logging | Is every invoice creation, amendment and void recorded with who and when? | Retrofitting audit trails onto a system without them is invasive. |
| Offline queue and reconciliation | If the connection drops mid-sale, what happens - and can it reconcile within 72 hours? | Needs a durable local queue plus a reconciliation routine. Not a small feature. |
| Supplier accreditation | Is whoever supplies the system accredited under Article 7 or 14? | Not fixable by you. This one determines whether the system has a future at all. |
The last row is the one to establish first, because it can make the other five moot.
Retrofit or replace
The instinct is always to retrofit, because the existing system is paid for. That instinct is right about half the time. The variable that decides it is not the feature list but whether the system was built with an integration seam anywhere near invoice creation.
Retrofitting is usually the right call when:
- The system has an API or plugin architecture, and invoice creation passes through one code path
- Access control is already per-user, even if roles need tightening
- You have source access, or a supplier who will still be accredited and is willing to do the work
- Invoice volume is modest enough that the offline path can be simple
Replacing is usually cheaper when:
- Invoices can be created from several places in the system, so clearance has to be bolted onto each
- There is no source access and no accredited supplier behind it
- It is an Excel-and-templates arrangement rather than a system - very common, and much easier to replace than to make compliant
- You were already going to replace it within two years for other reasons
- It cannot support per-role access at all, which usually indicates a deeper architectural age problem
A supplier who sells ERP licences will conclude you need a new ERP. A supplier who bills hourly will conclude you need a long retrofit. Both conclusions may be honestly reached and still be wrong for you.
Get the gap analysis from someone who is not selling you the remedy, or at least ask each candidate to argue the case against their own recommendation.
A sensible implementation sequence
- Establish your accreditation categoryTaxpayer using a supplied system, taxpayer running in-house software under Article 8, supplier, or marketplace. This determines whose legal obligation the accreditation is.
- Get your supplier’s accreditation position in writingUnder Articles 25–28 the supplier carries liability for defects in their system, including forfeiture of their performance guarantee. Their status is your dependency.
- Run the gap analysis against the six capabilities aboveAnswer each with yes, no, or unknown. The unknowns are usually the expensive ones and worth resolving first.
- Read Regulation No. 570/2026 for field-level requirementsThe directive requires clearance; the regulation specifies minimum invoice content. You need both to scope the template work.
- Decide retrofit or replace, then pilot on one invoice streamNever all of them at once. One stream, cleared end to end, including a deliberate offline test with a real reconnection.
- Test the offline path properly before you rely on itPull the connection during a sale, then restore it. This is the scenario that will actually happen, and the one least likely to have been tested.
Questions people ask
Get the gap analysis done first
Tell us what you are running and roughly how many invoices a month go through it. We will work through the six capabilities with you and tell you honestly whether retrofitting or replacing is the cheaper path - including when the answer is to keep what you have.