EazLink guide

What do IRN, RRN and QR code mean in Ethiopia e-invoicing?

A plain explanation of the invoice and receipt references, QR verification data, and what an ERP or POS should retain after registration.

Short answer

IRN is commonly used for the invoice registration reference, RRN for the receipt reference, and the QR code for document verification. The exact field names and when each value is returned must come from the current Ethiopian technical specification. Your ERP or POS should keep every official value beside its own invoice number so staff can reconcile the business record with the registered document.

Evidence checked: [1] Registered Directives · [2] Electronic Invoice Management System announcement

Prepared and reviewed by the EazLink compliance engineering team at Xiamen DataMega Technology Co., Ltd.

Quick decision guide

Best for	Finance teams, ERP owners, POS developers, cashiers, support teams, auditors, and implementation partners
Main question	What do IRN, RRN and QR code mean in Ethiopia e-invoicing?
Before implementation	Confirm the current taxpayer scope, rollout notice, and technical specification with the relevant Ethiopian authority.

What to remember

Keep the ERP invoice number and official registration references together.
Generate or display QR data only from the confirmed authority response.
A printed receipt is not proof of registration unless its status and references can be verified.

The identifiers answer different questions

The business invoice number answers, 'Which sale is this in our system?' The registration reference answers, 'Which document did the government service register?' A receipt reference may identify the customer-facing receipt or acknowledgement. The QR code gives a machine-readable route to verification data.

Do not replace the ERP's internal number with an external reference. Store both and keep the relationship stable through corrections and reprints.

What the ERP or POS should store

Keep the original document ID, request ID, official references, QR payload or verification URL, submission time, response time, current status, and response code. Store enough history to show whether a retry returned the first result or created a new document.

Source invoice or receipt number
IRN and RRN when applicable
QR or verification data
Accepted, rejected, pending, cancelled, or corrected status
Full response history and timestamps

Check the printed and digital result

A cashier needs a clear result, not a log file. Test the paper receipt, PDF, email, and any customer verification link. Make sure long references fit, Amharic characters render, ETB amounts use the agreed precision, and a reprint does not look like a new sale.

Invoice proof test

Confirm the official field definitions.
Map source and government identifiers separately.
Test QR scanning from paper and screen.
Reprint an accepted invoice and compare it with the original.
Trace one correction from the ERP to the final registered state.

Quick questions

Is an IRN the same as my ERP invoice number?

No. Treat the ERP number as the source business identifier and the IRN as an official registration reference unless the current specification states otherwise.

Can the POS create its own QR code?

It can render QR data supplied or defined by the approved process. It should not invent verification content.

What happens when a reference is missing?

Keep the document in a visible pending or failed state and reconcile it. Do not print an accepted status without confirmed registration evidence.

Sources

Registered Directives · Ethiopian Ministry of Justice
Electronic Invoice Management System announcement · INSA

Sources are used for regulatory and technical context only.