IRN & Peppol E-Invoicing Standards
How Invoice Reference Numbers, the Peppol network, UBL/XML format, and digital signatures fit together under Nigeria's e-invoicing standard — and how to avoid the validation errors that trip most businesses up.
What Is an IRN?
The Invoice Reference Number is the immutable reference every compliant invoice carries — the primary lookup key for status and dispute resolution.
Length
40 characters
Contains
Timestamp, business ID, sequence number, check digits
Mutable?
No — immutable once issued
Used for
Status tracking, audit, dispute resolution
Your internal invoice number is business-facing and follows your own convention. The IRN is a separate compliance reference generated for regulatory tracking — it can't be edited once issued, so corrections go through a credit note or debit note instead.
The Peppol Network
Peppol (Pan-European Public Procurement Online) is a global interoperability framework for exchanging standardized business documents. Nigeria's e-invoicing system is built on Peppol's 4-corner model: your business and your invoicing software (System Integrator) on one side, your buyer and their software on the other, connected through certified Access Point Providers (APPs) on each end.
The APP's job is network transport — moving your invoice securely and reliably to its destination. Your System Integrator's job is everything else: creating the invoice, validating it, generating the IRN, and managing your workflow. Most businesses need both, though a platform like ZUTAX pairs the two so there's no separate APP contract to negotiate.
UBL/XML Invoice Format
Compliant invoices aren't PDFs — they're structured UBL (Universal Business Language) XML documents, conforming to the Peppol BIS Billing 3.0 standard. UBL gives every system a consistent, machine-readable field structure, which is what makes automated validation and cross-platform exchange possible in the first place.
A PDF invoice is a presentation format — useful for a human to read, but not what gets validated or transmitted. The underlying UBL payload is what your e-invoicing software generates and what NRS actually checks. You don't need to hand-write XML: a compliant platform generates and validates UBL automatically from your invoice form or API payload.
Invoice Validation & Common Errors
Validation checks that your invoice payload meets required schema and compliance constraints before it's accepted. These four causes account for most rejections.
Invalid or unverified TIN
Supplier or buyer TIN is mistyped, inactive, or unverified. Always verify TINs before first invoice.
Missing mandatory fields
IRN, QR code, digital signature, or a required UBL field is absent from the payload.
Tax computation mismatch
VAT calculated at the wrong rate, or totals that don't reconcile with line items.
Malformed structured payload
The UBL/XML doesn't conform to the Peppol BIS Billing 3.0 schema — often from hand-built or legacy integrations.
QR Codes & Digital Signatures
Every compliant invoice carries two additional proof mechanisms: a QR code for quick, scannable verification, and an ECDSA (Elliptic Curve Digital Signature Algorithm) digital signature that cryptographically proves the invoice was issued and validated correctly. Together with the IRN, these are what make an invoice tamper-evident and independently verifiable — by a buyer, an auditor, or NRS itself — without needing to contact the issuer.
Both are generated automatically as part of the signing step; there's no manual certificate management or key handling required on your end when using a compliant platform.
Correcting Invoices: Credit & Debit Notes
Because an IRN is immutable once issued, you can't simply edit an invoice after the fact. Corrections — a return, a pricing adjustment, an undercharge — go through a credit note (reducing the original amount) or debit note (increasing it), each linked back to the original invoice's IRN so the audit trail stays intact.
See the full guide to credit and debit notes for how partial and full corrections work end to end.
IRN & Peppol Reading
What Is an Invoice Reference Number (IRN)?
The full breakdown of how IRN generation, structure, and lookup work.
What Is Peppol? A Simple Explanation
Peppol in plain language for Nigerian business owners.
Peppol Compliance Guide
Connecting to the Peppol network for international transactions.
Nigeria Joins Peppol: What It Means
NRS is now a Peppol Authority — what changed for Nigerian businesses.
Technical Guides
UBL/XML Invoice Format Guide
The Peppol BIS Billing 3.0 structure your invoices must conform to.
Invoice Validation Errors & How to Fix Them
The most common rejection causes, and how to resolve each one.
Credit Notes & Debit Notes in E-Invoicing
How corrections link back to the original IRN-tracked invoice.
Frequently Asked Questions
What is an IRN and how is it generated?
An Invoice Reference Number (IRN) is a unique 40-character identifier generated for each compliant e-invoice. It contains a timestamp, business identifier, sequential number, and check digits, and serves as the immutable reference for tracking an invoice across validation, transmission, and audit.
What is Peppol and why does Nigeria use it?
Peppol (Pan-European Public Procurement Online) is a global interoperability framework for exchanging standardized business documents. Nigeria connects to it so invoices can move between businesses and public entities through certified Access Points, using consistent document standards instead of one-off integrations.
What format do NRS-compliant invoices need to be in?
Invoices must be structured as UBL (Universal Business Language) XML, conforming to the Peppol BIS Billing 3.0 standard. A PDF alone is a presentation format, not a compliant payload — the underlying structured UBL data is what gets validated and transmitted.
What causes most invoice validation failures?
The most common causes are invalid or unverified TINs, missing mandatory fields (IRN, QR code, digital signature), tax computation mismatches, and malformed UBL/XML payloads that don't conform to the Peppol BIS Billing 3.0 schema.
What role do QR codes and digital signatures play?
Every compliant invoice carries a QR code for quick verification and an ECDSA (Elliptic Curve Digital Signature Algorithm) digital signature that cryptographically proves the invoice was issued and validated by the correct authority. Both are generated automatically by a compliant e-invoicing platform.
Is an IRN the same as my internal invoice number?
No. Your internal invoice number is business-facing and can follow your own numbering convention. The IRN is the compliance reference generated separately for regulatory workflow tracking, and it cannot be edited once issued — corrections go through a credit note or debit note instead.
IRN Generation & Peppol Dispatch, Handled
ZUTAX generates your IRN, validates UBL, signs invoices, and dispatches through a certified Access Point Provider — automatically, on every invoice.