The Nigeria Revenue Service launched its Merchant Buyer Solution in 2025, and as of 2026, compliance is no longer optional. If your business is VAT-registered in Nigeria and you are still generating invoices manually or through disconnected software, you are already at risk. This guide covers everything you need: what NRS MBS actually requires, who it applies to, what happens if you ignore it, and how to get compliant without disrupting your operations.

This is not a theoretical overview. It is based on what we have seen working with dozens of Nigerian businesses through the compliance process, from initial registration to live invoice submission.

What is the NRS Merchant Buyer Solution?

The Merchant Buyer Solution (MBS) is the Nigeria Revenue Service’s real-time electronic invoicing infrastructure. It requires businesses to submit structured invoice data to NRS servers at the point of transaction, receive a cryptographic stamp and unique invoice reference number, and display a verifiable QR code on every invoice issued to customers.

The system works in two modes:

Online mode: Invoice data is transmitted to the NRS gateway in real time. The gateway validates the data, applies a digital signature, returns a stamped invoice reference number (IRN), and the transaction is recorded in the NRS system.
Offline mode: For businesses in areas with unreliable connectivity, a limited offline mode allows invoice generation with local cryptographic signing. These invoices must be uploaded to the NRS gateway within 24 hours.

The NRS MBS is modeled on similar systems in Saudi Arabia (ZATCA), India (IRN), and the broader OECD push toward continuous transaction controls (CTC). Nigeria’s implementation follows the same core principle: tax authorities want to see transactions as they happen, not six months later during an audit.

Who Does NRS MBS Apply To?

The obligation binds any person making a taxable supply once the NRS switches its Electronic Fiscal System on for them, and the NRS is rolling it out in phases by annual turnover:

Large taxpayers (₦5bn+ turnover) — live since 1 November 2025, with enforcement from April 2026.
Medium taxpayers (₦1bn–₦5bn turnover) — go-live 1 July 2026, with enforcement from January 2027.
Small / emerging taxpayers (below ₦1bn turnover) — go-live 1 July 2027, with enforcement from January 2028.

So for most businesses the question is not if but when: your bracket sets your go-live date, and setting up early means you clear invoices while everyone else scrambles at the deadline. (Note: the ₦50 million figure that circulates online is the Nigeria Tax Act’s small-company VAT threshold — a different rule — not an e-invoicing exemption, and it does not apply to professional-services businesses.)

What the MBS Requires Technically

Understanding the technical requirements is critical for evaluating whether your current software can meet them. Here is what every MBS-compliant invoice must include.

Mandatory Invoice Fields

Seller TIN (Tax Identification Number) and VAT registration number
Buyer TIN (for B2B transactions above NGN 500,000)
Invoice number in NRS-specified sequential format
Invoice date and time (with timezone)
Line-item description, quantity, unit price, and applicable VAT rate for each item
VAT amount per line item and total VAT for the invoice
Invoice total (exclusive and inclusive of VAT)
Currency code and exchange rate (for foreign currency invoices)
Supply type code (standard-rated, zero-rated, exempt, or out-of-scope)
NRS Invoice Reference Number (IRN) returned by the gateway after validation
Cryptographic hash of the invoice data
QR code encoding key invoice fields and the IRN

Submission Requirements

Invoices must be submitted to the NRS MBS gateway in XML format following the NRS e-invoice schema (based on the UBL 2.1 standard with NRS-specific extensions). The API uses OAuth 2.0 for authentication. Responses are returned synchronously for online submissions; businesses must handle both success responses (with IRN) and rejection responses (with error codes).

Credit notes and debit notes must also be submitted through the gateway and linked to the original invoice IRN.

QR Code Requirements

The QR code must be generated after the IRN is received and must encode: the seller’s TIN, invoice date, total excluding VAT, VAT total, and the IRN. The QR code must be printable at a minimum size of 20mm x 20mm and must be scannable by the NRS Verify mobile application.

Penalties for Non-Compliance

The penalties are set by the Nigeria Tax Administration Act 2025, and two distinct sections are routinely confused — so here is the precise position:

Failing to fiscalise a taxable sale (Section 104): ₦200,000 plus 100% of the tax due on that sale, plus interest at the prevailing CBN Monetary Policy Rate, per year. This is the e-invoicing penalty — it applies to every taxable sale that skips the system.
Refusing to let the NRS deploy its technology within 30 days of notice (Section 103): ₦1,000,000 for the first day of default, plus ₦10,000 for each subsequent day. Note this is the technology-deployment-refusal penalty — not the per-invoice penalty, though many articles quote it as if it were.

Beyond the direct financial penalties, non-compliant businesses face VAT input credit disallowance. If your supplier issues you an invoice without a valid IRN, you cannot claim the VAT as input credit, even if you paid the VAT. This creates downstream risk: your suppliers’ non-compliance becomes your tax problem.

The Practical Compliance Checklist

Getting to compliance requires work across three areas: registration, systems, and processes.

Registration

Confirm your business is enrolled in the NRS taxpayer portal and your TIN is active
Register for MBS access through the NRS Business Portal
Obtain your MBS API credentials (client ID and client secret)
Configure your certificate for cryptographic signing
Run test submissions in the NRS sandbox environment before going live

Systems

The choices are:

Option A: Direct API integration. Your accounting or billing software connects directly to the NRS MBS gateway. This requires your software to support the NRS UBL XML schema, handle OAuth token management, process IRN responses, generate QR codes, and manage submission retries. This is the most reliable approach if your software supports it natively.

Option B: Middleware or connector. A third-party middleware layer sits between your existing software and the NRS gateway. This works as a stopgap but introduces an additional failure point and typically requires manual reconciliation between systems.

Option C: Manual submission portal. The NRS provides a web portal for manual invoice entry. This is only viable for very low transaction volumes (under 10 invoices per day). For any business with meaningful transaction volume, manual submission is operationally unsustainable and error-prone.

Processes

Update invoice templates to include the IRN and QR code fields
Train your accounts receivable team on the new workflow: invoices cannot be issued to customers until the IRN is received
Establish a process for handling gateway downtime: the NRS offline mode procedure must be documented and tested
Update your purchase verification process to check that supplier invoices carry valid IRNs

How an Integrated ERP Handles NRS Compliance

With an ERP that has a native NRS MBS connector, the process is invisible to the user. The invoice is created in the ERP. On submission, the ERP automatically formats the invoice data to the NRS UBL XML schema, submits it to the MBS gateway, receives the IRN, embeds the IRN and QR code into the invoice PDF, and marks the transaction as NRS-compliant. The entire round-trip takes under two seconds for online submissions.

The ERP also handles edge cases: gateway timeouts with automatic retry logic, offline mode fallback with 24-hour upload queue, rejection responses with error codes surfaced to the user for correction, and a compliance audit log that stores every submission, response, and IRN against each invoice record.

When evaluating an ERP for NRS compliance, ask:

Is the NRS MBS connector native to the ERP or a bolt-on integration from a third party?
Does the ERP handle IRN storage and QR code generation automatically?
How does the ERP handle gateway downtime and offline mode?
Is the NRS schema kept current as NRS publishes schema updates?
What happens to historical invoices during a compliance audit?

Getting Started

Zinye includes a fully managed NRS MBS connector on every plan. There is no additional module to purchase. When a sales invoice is submitted in Zinye, the NRS MBS integration fires automatically: the invoice data is validated, submitted to the MBS gateway, the returned IRN is stored against the invoice record, and the customer-facing PDF includes the QR code and IRN.

Zinye also handles the credential management and certificate rotation that NRS requires periodically. As NRS publishes schema updates, Zinye pushes connector updates to all customers without requiring manual upgrades.

If your business is VAT-registered in Nigeria and you are not yet submitting invoices through the NRS MBS, the time to act is now. Zinye offers a free 14-day trial with full NRS MBS functionality. You can test your first compliant invoice submissions in the sandbox and go live without operational disruption, starting at $19 per seat per month.

Book a compliance consultation with our Nigeria team at zinye.com/contact, or start your trial today.

NRS e-invoicing compliance guide for Nigeria (2026)