Nigeria is moving toward a more connected digital tax and invoicing environment through the Nigeria Revenue Service (NRS) e-invoicing system, formerly associated with FIRS. The system uses the Merchant Buyer Solution (MBS) to validate and exchange electronic invoices and connect businesses with the tax authority.
For businesses operating in Nigeria, e-invoicing is not simply a matter of replacing PDF invoices with electronic documents. Your ERP, accounting system, POS, or invoicing application may need to generate structured invoice data, communicate with the NRS ecosystem, handle validation responses, and retain information such as the Invoice Reference Number (IRN) and QR code.
This guide explains Nigeria’s e-invoicing requirements, rollout timelines, the MBS workflow, ERP readiness requirements, Access Point Providers and System Integrators, and what businesses should consider when preparing their ERP.
Key Takeaways
- Nigeria’s e-invoicing framework is administered by the Nigeria Revenue Service (NRS) through its Merchant Buyer Solution (MBS).
- The rollout is being phased according to taxpayer category and annual turnover, with different go-live and enforcement periods.
- Businesses need more than a PDF invoice: ERP and invoicing systems need to support NRS’s structured invoice requirements and integration process.
- The NRS system supports structured invoice data using UBL-based XML or JSON and provides APIs for system integration.
- Before implementation, businesses should validate their taxpayer category, ERP readiness, integration route, invoice data, testing process, and applicable compliance deadline.
What Is Nigeria's E-Invoicing System?
Nigeria’s e-invoicing system is a digital invoicing framework implemented by the Nigeria Revenue Service (NRS) to electronically validate, process, and exchange invoices.
The system is built around the Merchant Buyer Solution (MBS) and is designed to connect taxpayer invoicing systems with the NRS platform. Businesses can integrate their ERP or invoicing application through the NRS-supported technical ecosystem and submit structured invoice information for validation and processing.
The framework is intended to improve invoice traceability, standardize invoice data, support tax administration, and reduce manual processes.
FIRS vs NRS: Why Do You See Both Names?
Businesses researching Nigerian e-invoicing may encounter both FIRS e-invoicing and NRS e-invoicing.
The current tax authority name used by the e-invoicing platform is Nigeria Revenue Service (NRS). Therefore, the current article should primarily use “NRS e-invoicing,” while mentioning “FIRS e-invoicing” where useful for people searching using the former terminology.
What Is MBS?
MBS stands for Merchant Buyer Solution.
The NRS MBS is the central e-invoicing environment through which businesses can register, manage e-invoicing enablement, and interact with the electronic invoicing ecosystem.
The NRS platform also provides documentation for businesses, System Integrators, and Access Point Providers.
What Is an IRN?
An Invoice Reference Number (IRN) is a unique reference associated with an electronic invoice.
The NRS invoice schema identifies IRN as a mandatory invoice field and uses it as a unique tracking number for the invoice.
What About the QR Code and Digital Security?
NRS’s e-invoicing ecosystem includes mechanisms for validating and securing invoice data. Depending on the invoice flow and implementation, the resulting invoice can include information such as an IRN, QR code, and cryptographic or digital signatures.
Businesses should therefore ensure that their ERP can store and reproduce the required information after an invoice has been processed.
Who Must Comply? Nigeria's E-Invoicing Deadlines by Turnover
The NRS rollout is being implemented in phases based on taxpayer category and annual turnover.
The February 2026 NRS rollout timeline reported by KPMG identified three broad groups: large taxpayers above ₦5 billion, medium taxpayers between ₦1 billion and ₦5 billion, and emerging taxpayers below ₦1 billion.
| Taxpayer category | Annual turnover | Go-live | Compliance enforcement* |
|---|
| Large taxpayers | Above ₦5 billion | Already commenced | See latest NRS notice |
| Medium taxpayers | ₦1 billion–₦5 billion | 1 July 2026 | January–March 2027 |
| Emerging taxpayers | Below ₦1 billion | 1 July 2027 | January–March 2028 |
Enforcement dates should be checked against the latest NRS notice before publication because the rollout has been subject to updates.
Large Taxpayers — Above ₦5 Billion
Large taxpayers were the first category included in the phased rollout.
KPMG’s February 2026 summary records the large-taxpayer go-live as already completed, following the initial rollout that began in November 2025.
For businesses in this category, the focus should now be on maintaining operational compliance, monitoring invoice transmission, resolving rejected invoices, and keeping ERP integrations aligned with the current NRS technical requirements.
Medium Taxpayers — ₦1 Billion to ₦5 Billion
Medium taxpayers are an especially important group for businesses preparing during 2026.
The published NRS rollout timeline identified:
- Go-live: 1 July 2026
- Post-go-live review: October–November 2026
- Compliance enforcement: January–March 2027
This creates an important preparation window for businesses that have not yet completed their ERP integration.
If you fall into this category, now is the time to:
- Confirm your taxpayer classification.
- Review your ERP’s invoice capabilities.
- Map required tax and customer data.
- Select your integration route.
- Test invoice transmission.
- Train finance and billing teams.
- Establish an error-handling process.
Emerging Taxpayers — Below ₦1 Billion
The rollout for emerging taxpayers is scheduled later.
The February 2026 timeline identified:
- Go-live: 1 July 2027
- Post-go-live review: October–November 2027
- Compliance enforcement: January–March 2028
A later deadline does not necessarily mean businesses should wait.
ERP changes, data cleanup, integration development, testing, and staff training can take time. Starting early allows businesses to address technical issues before the compliance deadline becomes urgent.
Important: Confirm your exact compliance category and current deadline against the latest NRS communication before taking regulatory action.
How Nigeria's E-Invoicing Works: Step by Step
The basic architecture connects your business system with the NRS e-invoicing environment through an approved integration route.
A simplified workflow is:
ERP / Accounting / POS → System Integrator or Access Point Provider → NRS MBS → Validation / Processing → Invoice Response → Customer
The exact architecture depends on your integration model.
Step 1: Generate the Invoice in Your ERP
Your ERP or accounting system creates the invoice using the underlying transaction data.
This may include:
- Seller information
- Buyer information
- TIN
- Invoice number
- Invoice date
- Items or services
- Quantities
- Prices
- Currency
- VAT
- Payment information
- Delivery references
The NRS invoice schema specifies mandatory and optional fields and supports XML and JSON structures based on UBL.
Step 2: Validate the Invoice Data
The invoice needs to conform to the NRS schema and validation requirements.
The NRS documentation provides an invoice validation API and identifies fields such as business ID, IRN, invoice date, invoice type, currency, tax totals, invoice lines, and supplier/customer information.
Step 3: Send Through the Integration Layer
Businesses can integrate their systems through the NRS ecosystem of System Integrators and Access Point Providers.
The NRS describes APPs as intermediaries that facilitate secure communication between ERP systems, businesses, trading partners, and NRS.
Step 4: NRS Processing
The invoice is processed through the NRS e-invoicing infrastructure.
Your integration should be designed to handle both successful responses and rejected invoices.
Step 5: Store the Response
Your ERP should retain the relevant response information associated with the invoice.
This is important for:
- Audit trails
- Invoice retrieval
- Customer service
- Reconciliation
- Tax records
- Error resolution
Step 6: Deliver the Validated Invoice
The resulting invoice can then be provided to the customer according to the applicable transaction workflow.
B2B and B2G E-Invoicing
Business-to-business transactions form a key use case in the NRS e-invoicing documentation.
The NRS provides a B2B example in which a supplier generates an electronic invoice through its invoicing solution, including buyer details, goods or services, total values, and VAT.
For businesses, this means the ERP needs to capture accurate customer and transaction information before the invoice is transmitted.
B2G transactions should similarly be evaluated according to the applicable NRS requirements and transaction workflow.
B2C E-Invoicing and Reporting
The NRS documentation also includes Business-to-Consumer use cases.
For example, the official documentation describes a retail scenario where point-of-sale systems generate receipts containing QR codes and report issued invoices or receipts to the company’s central repository and finance system. It also describes a requirement in that example to report issued invoices within 24 hours.
Businesses with large numbers of consumer transactions should therefore pay particular attention to:
- POS integration
- Centralized invoice storage
- Transaction volumes
- Reporting workflows
- QR code generation
- Error handling
- Connectivity and retry processes
Do not assume that a B2B workflow can simply be copied into a high-volume B2C environment.
Penalties and VAT Impact of Non-Compliance
E-invoicing compliance has both technical and tax implications, but businesses should be careful when relying on third-party summaries of penalties.
The supplied research identifies penalty provisions under the Nigeria Tax Administration Act 2025, including potential fixed penalties, tax-related amounts, interest, and penalties associated with failure to deploy approved compliance technology. However, those exact figures should be checked against the current legislation and NRS guidance before publication.
Therefore, businesses should not treat a blog article as the definitive source for penalty calculations.
Instead, the practical approach is:
- Confirm your taxpayer category.
- Confirm your applicable compliance date.
- Verify the current NRS technical requirements.
- Complete your ERP integration.
- Test invoices before enforcement.
- Keep evidence of your implementation and testing.
- Monitor NRS updates.
For tax-credit treatment and input VAT implications, obtain professional tax advice and verify the current statutory requirements before making accounting decisions.
What Your ERP Needs for E-Invoicing Compliance
E-invoicing changes the requirements placed on your ERP.
A normal invoice-generation workflow is no longer enough if your business is required to participate in the NRS e-invoicing system.
Nigeria E-Invoicing ERP Readiness Checklist
Use the following checklist during your ERP assessment:
- ERP can generate structured invoice data in the required XML or JSON format.
- Invoice structure aligns with the NRS/UBL requirements.
- Customer and supplier TIN information can be captured and validated.
- NGN and applicable tax information are mapped correctly.
- VAT and tax codes are configured correctly.
- ERP can communicate with the required integration layer.
- ERP can receive and store NRS responses.
- IRN can be stored against the invoice.
- Required QR or other invoice response information can be reproduced on the invoice.
- Rejected invoices are logged with the reason for rejection.
- Failed transmissions can be retried.
- Credit notes and related invoice references can be handled.
- Invoice audit trails are maintained.
- Validated invoice records can be archived and retrieved.
The NRS developer documentation provides an API environment, authentication requirements, testing guidance, and invoice-schema documentation for system integration.
Your ERP Should Handle More Than Invoice Generation
A compliant architecture should also consider what happens when something goes wrong.
For example:
Invoice Created → Validation Failed → Error Returned → Finance Team Corrects Data → Invoice Resubmitted → NRS Response Stored
Without a proper error-handling workflow, finance teams may end up manually recreating invoices or maintaining parallel spreadsheets.
E-Invoicing with ERPNext
ERPNext can serve as the underlying ERP platform for businesses that need structured invoicing, accounting, sales, customer, supplier, and tax workflows.
However, Nigeria’s NRS e-invoicing requirements mean that businesses should evaluate the specific integration layer and implementation approach, rather than assuming that a standard ERPNext invoice automatically satisfies every NRS requirement.
The NRS provides API documentation specifically for system integration, including authentication, invoice validation, invoice schema, IRN and QR-related functionality, testing, and production deployment.
What an ERPNext Implementation May Need to Address
Depending on the business and confirmed implementation architecture, an ERPNext e-invoicing project may involve:
- Customer and supplier TIN fields
- Nigerian tax configuration
- Invoice data mapping
- NRS-compatible invoice structure
- API integration
- IRN handling
- QR code handling
- Response storage
- Error and retry workflows
- Credit-note processing
- Invoice archiving
- Testing and go-live support
Important: Matiyas should publish only the ERPNext/NRS capabilities that its team has actually implemented or is currently able to deliver.
Access Point Providers and System Integrators: How to Choose
An important part of Nigeria’s e-invoicing architecture is understanding the role of service providers.
The NRS documentation distinguishes between System Integrators (SIs) and Access Point Providers (APPs) and provides onboarding and technical documentation for these roles.
What an Access Point Provider Does
The NRS describes APPs as intermediaries responsible for facilitating secure communication between ERP systems, trading partners, and NRS. Their responsibilities include data validation, transmission, interoperability, and integration with the NRS platform.
What to Evaluate
When selecting an APP, SI, or ERP implementation partner, ask:
- Is the provider approved or recognized within the current NRS framework?
Check the current NRS service-provider directory rather than relying on an old vendor list.
- Can it integrate with your ERP?
Your provider should understand your ERP’s APIs, data structures, authentication, and invoice workflows.
- How does it handle rejected invoices?
Ask to see the error-handling and retry process.
- How are IRNs and invoice responses stored?
The ERP should not lose the response received from the e-invoicing system.
- How is the integration tested?
The NRS provides staging/testing guidance before production deployment.
- Who maintains the integration when NRS requirements change?
E-invoicing is a regulatory integration, so ongoing maintenance matters.
Common Nigeria E-Invoicing Mistakes to Avoid
Waiting Until the Deadline
ERP integration is rarely just a configuration checkbox.
It can involve development, tax mapping, data cleanup, testing, user training, and troubleshooting.
Treating a PDF as an E-Invoice
A PDF invoice is not automatically equivalent to a structured electronic invoice.
The NRS platform supports structured invoice data based on its defined schema, including XML and JSON representations.
Incorrect TIN and Customer Data
Poor master data can lead to validation failures.
Review:
- Customer TINs
- Supplier TINs
- Legal names
- Addresses
- Tax classifications
- VAT information
Not Storing the IRN
The invoice response should be retained in your ERP or connected system so the business can retrieve the relevant information later.
Ignoring Rejected Invoices
A good integration needs an exception-management process.
Finance users should know:
- Why the invoice failed
- What needs correction
- Who should correct it
- How it should be resubmitted
Assuming a Generic Peppol Validator Is Enough
NRS’s invoice schema has Nigeria-specific fields and validation requirements.
A generic document validator should not be treated as proof that an invoice will pass NRS validation.
Failing to Test Before Go-Live
The NRS documentation explicitly provides testing and staging guidance before moving an application to production.
Get Your ERP E-Invoicing Ready
Nigeria’s e-invoicing rollout makes ERP readiness a business priority—not simply an accounting-system upgrade.
Before your deadline, review your taxpayer category, invoice data, TIN information, tax configuration, ERP capabilities, integration route, testing process, and post-validation workflow.
For medium taxpayers, the period leading into the planned 2027 enforcement window is particularly important. Rather than waiting for compliance enforcement, use the available time to integrate, test, train your finance team, and resolve invoice-validation issues.
Matiyas can help businesses assess their ERP readiness, identify integration requirements, configure or customize ERP workflows, and plan an e-invoicing implementation based on their actual technology environment.
Frequently Asked Questions
"I am quite happy with the ERP solution provided by Matiyas. Before we implemented their system, our organization was struggling with inefficient processes and fragmented data. Their customized ERP solution not only streamlined our workflows but also provided real-time insights into our operations. The customer support from Matiya's Team has been exceptional throughout the journey." 
"Matiyas offered us a functionally strong and automated solution to address the end-to-end needs of our business operation. This solutions will be able to scale and grow our business and it will surely reduce manual interventions." 
"I wanted to thank you Matiyas team to set-up the ERP system based on our business process. The assistance was invaluable in helping my company get as we requested. We sincerely appreciate your efforts and thanks again Matiyas team to provide us a best solution with the erp system." 
"The implementation of the Matiyas ERP solution has revolutionized our workflow. The automation of previously manual processes has not only saved us time but also significantly reduced errors. It’s like having an extra set of hands on our team, streamlining operations and boosting productivity" 
"Our company is very new to ERP, we tried to implement ERP by ourselves, however along the way we found struggles as we are very new. We are lucky HasanAli from Matiyas helped us in many ways, from a simple question to very complex developments and deployments. Rates are reasonable too! We are happy that Matiyas is there to help us." 
"The folks at Matiyas Software are the best. They're skilled, work quickly and professionally, and were able to tailor ERP to our exact specifications. Would use them again." 
"Very knowledgeable and prompt and professional. I highly recommend Matiyas for any ERP customizations." 
