NRS e-invoicing: a Nigerian operator's survival guide

If you run a Nigerian business and issue B2B invoices, the Nigeria Revenue Service now requires you to electronically register every one of them before sending it to your buyer.

Not file a report at year-end. Not submit a batch at month-end. Register each invoice, individually, at the point of issue, and receive a government-issued reference number before that invoice is legally valid.

This is the NRS Mandatory Billing System, and for most Nigerian operators it represents the biggest change to invoicing practice in a generation. This guide explains what it actually requires, what the consequences of non-compliance are, and the fastest practical path to getting it right.

What the NRS MBS actually is

The Mandatory Billing System is Nigeria's real-time e-invoicing infrastructure. It is operated by the Nigeria Revenue Service and built on the international UBL (Universal Business Language) standard, the same technical foundation used by Saudi Arabia's ZATCA system and the European Peppol network.

The model is a clearance system. This means your invoice does not legally exist until the NRS has seen it, validated it, and signed it. The process:

You generate the invoice in your accounting or ERP system. Your system submits the invoice data to the NRS API. The NRS validates the payload: buyer and seller TINs, line items, tax amounts, required fields. If validation passes, the NRS signs the invoice and returns two things: an Invoice Reference Number (IRN) and a Cryptographic Stamp Identifier (CSID). Your system generates a QR code from the signing data. The IRN, CSID, and QR code are printed on the invoice you send to your buyer.

That sequence happens in seconds. For a business with integrated software, it is invisible to the user. For a business still issuing invoices manually in Word or sending PDFs from Excel, it requires a significant change in how invoices are produced.

The IRN: what it is and where it comes from

The Invoice Reference Number is the most important output of the NRS submission process. Without it, your invoice is not a valid fiscal document.

The IRN follows a specific format generated by your system, not by the NRS:

Invoice number (alphanumeric characters only, hyphens and slashes stripped) + Service ID (8 characters, assigned when you register on the NRS portal) + Date (YYYYMMDD format using the invoice posting date)

For example: SINV202600001-B0B17AB7-20260601

The NRS validates this IRN during the submission process and confirms it is unique. If it has already been used for another invoice, submission fails. If the format is wrong, submission fails.

The Service ID is assigned once, when your business completes the enablement process on the NRS e-Invoice portal. It is specific to your business and should be treated like a credential.

Who needs to comply and when

The NRS MBS mandate is being rolled out in phases based on business size, measured by annual turnover. The NRS publishes updated thresholds on the NRS e-Invoice portal. The direction of travel is clear: the threshold is lowering progressively, and the mandate will eventually cover all businesses that issue B2B invoices, regardless of size.

If your annual turnover is above the current threshold, you are already required to comply. If you are below the threshold today, you will be covered within the rollout period.

The safest assumption for any Nigerian business issuing B2B invoices is that compliance is required now or will be required within the next operating year. Building toward it immediately is always better than scrambling to meet a deadline that has already passed.

For B2C transactions at the point of sale, the requirement is different. POS receipts are covered by the ATRS (Automated Tax Remittance System), which uses a separate OAuth-based flow and generates a payment code for each transaction rather than an IRN. If you operate a retail or hospitality business with significant cash or card transactions, ATRS is your compliance path for those transactions.

What the penalties actually are

The Nigeria Tax Act 2025 gives the NRS broad enforcement powers for e-invoice non-compliance. The practical consequences operate at several levels.

The invoice is not valid. A buyer who receives an invoice without an IRN and QR code is receiving a document that does not meet NRS requirements. Sophisticated buyers, especially larger corporates and government entities, are already rejecting non-compliant invoices. If your buyer's finance team flags your invoice and sends it back, you have a cash flow problem, not just a compliance problem.

Audit exposure. The NRS has access to the e-invoice registry. During a tax audit, the auditor can compare your filed VAT returns to the invoices registered in the system. Any invoices that appear in your records but not in the NRS registry are immediately suspect. The audit exposure extends beyond e-invoice compliance to the underlying VAT position.

Administrative penalties. The NTA 2025 provides for financial penalties for non-compliance with e-invoicing requirements. The specific penalty structure is detailed in the Act and accompanying regulations. The pattern established by other markets that have introduced similar mandates suggests that penalties apply per non-compliant invoice, and that they scale with business size and the duration of non-compliance.

The honest summary: the cost of non-compliance is not just the penalty. It is the rejected invoices, the delayed payments, the audit risk, and the credibility cost with buyers who are themselves trying to maintain compliant supply chains.

The five things you need to get compliant

1. Register on the NRS e-Invoice portal

Go to the NRS e-Invoice portal and complete the business enablement process. You will need your company's TIN, CAC registration number, and contact details. Once approved, you will receive your Business ID and Service ID. These are the credentials your software uses to authenticate every API call.

2. Get your API credentials

After enablement, you will be issued an API key and API secret. These are permanent credentials (not session tokens) that are included in the header of every request to the NRS API. They should be stored securely and treated with the same care as a password.

3. Connect your invoicing system

This is the most technically involved step. Your accounting or ERP system needs to be able to submit invoice data to the NRS API in the correct format (UBL BIS Billing 3.0 JSON), receive the IRN and CSID, generate a QR code, and print those elements on the invoice PDF.

If you use an ERP that has built-in NRS MBS integration, this is configuration, not development. If you use standalone accounting software or generate invoices manually, you either need a middleware service that sits between your system and the NRS API, or you need to move to software that handles the integration natively.

4. Classify your customers correctly

The NRS requires each invoice to be classified as B2B, B2C, or B2G. B2B classification is automatic when the buyer has a registered TIN on file. B2C is the default when no TIN is available. B2G applies to invoices issued to government entities.

The classification affects how the invoice is processed and what validation the NRS applies. Misclassification can cause submission failures or audit issues. Review your customer records and ensure TINs are recorded for all business customers.

5. Set up item classifications

Every line item on an e-invoice must carry either an HS code (for goods) or a service code (for services). These are the NRS classification codes that identify what is being sold. The NRS publishes the full list on the e-Invoice portal and provides an API endpoint to sync them into your system.

If your items are not classified with HS or service codes, the NRS validation will reject your invoice payload. This is one of the most common causes of submission failures during initial go-live.

The submission process in plain terms

When a compliant invoice is issued, the sequence from your ERP's perspective is:

The user creates and saves the invoice in the system. The system generates the IRN using the formula: stripped invoice number, Service ID, posting date. The system submits the invoice payload to the NRS validate endpoint. If validation passes, the system submits the same payload to the NRS sign endpoint. The NRS returns the CSID and QR data. The system attaches the IRN, CSID, and QR code to the invoice record. The invoice PDF, now carrying all required NRS elements, is sent to the buyer.

If the NRS API returns a validation error (wrong field, invalid TIN, missing required data), the issue must be corrected and the invoice resubmitted. If the API is temporarily unavailable, the invoice goes into a retry queue and is submitted automatically when the API recovers.

The whole process, when working normally, adds seconds to the invoice creation time and is invisible to the person creating the invoice.

What to do if you are already late

If the mandate applies to your business and you are not yet compliant, the priority is to start now rather than wait for a more convenient moment.

The NRS has not, to date, issued wide-scale penalties for businesses that can demonstrate they are actively working toward compliance. The businesses most at risk are those that are making no effort and have no plan. Being in the process of implementing compliance is a different position from ignoring the requirement entirely.

Practically, the fastest path to compliance is:

Complete the NRS portal registration this week. Identify the software solution you will use, whether that is an ERP with built-in NRS integration, a middleware service, or an API connection built by a developer. Run a test submission using the NRS sandbox environment (the sandbox URL is provided in the NRS portal documentation) before going live on the production API. Go live on the production API and submit your next B2B invoice through the new process.

For a business using modern accounting software with NRS integration already built in, steps two through four can happen in a few days after registration. For a business using older software or manual invoicing, the timeline is longer but the urgency is the same.

The two mistakes that delay most implementations

Waiting for the software to be perfect before going live. The perfect is the enemy of the compliant. If your system can submit invoices and receive IRNs, go live with that, even if the QR code printing needs to be improved later or the retry logic is not yet fully automated. An IRN on every invoice, however imperfectly produced, is compliant. A perfectly formatted invoice with no IRN is not.

Not testing on the sandbox first. The NRS provides a sandbox environment specifically for testing integrations before they connect to the live API. Every implementation should run at least twenty test invoices through the sandbox before the production API key is loaded. The most common issues: field format errors, missing required fields, and HS/service code mismatches are all caught in sandbox testing, not in production.

A note on B2C and ATRS

If your business is primarily retail or hospitality, selling directly to consumers rather than businesses, the NRS MBS IRN process applies to invoices you issue in a B2B context. Your point-of-sale transactions are covered by ATRS.

ATRS requires each POS receipt to be submitted to the NRS in real time via a separate API. The authentication is OAuth rather than API key. The response includes a payment code that is printed on the receipt. The submission happens per transaction, not per invoice.

If you operate both B2B invoicing and retail POS, you need both integrations: NRS MBS for your B2B invoices and ATRS for your retail receipts.

The bottom line

E-invoicing is not optional and is not going away. Every significant economy that has introduced a real-time invoice reporting mandate has expanded its scope rather than pulled it back. Nigeria's NRS MBS is following the same pattern.

The businesses that will find this easiest are those using integrated software where the NRS submission happens automatically and the operator does not have to think about it. The businesses that will find it hardest are those still issuing invoices manually or using disconnected systems.

If you are in the second group, the transition is a project with a finite end. Once it is done, it is done, and the compliance happens in the background with every invoice you issue.

The question is not whether to comply. It is how quickly you can get there.

Zinye ERP has NRS MBS compliance built in as a core feature, not a bolt-on. Every Sales Invoice is automatically submitted to the NRS API on posting, with retry handling, status tracking, and the IRN and QR code printed on the invoice PDF. If you want to see what compliant invoicing looks like in practice, register your interest at zinyecrm.zinye.com/partner/.