NRS Merchant Buyer Solution Explained

The Merchant Buyer Solution is the part of NRS e-invoicing that most directly affects how your invoices are processed day to day. This guide explains what it is, how an invoice moves through it, what IRNs and clearance marks are for, and what to review before you integrate.

Regulatory information is provided for general guidance and may change. Businesses should confirm current requirements with the Nigeria Revenue Service and their professional tax advisers. Nigeria Revenue Service.

Merchant Buyer Solution Explained

The Merchant Buyer Solution, commonly referred to as MBS, is the NRS e-invoicing environment used to support electronic invoice processes between merchants, buyers and the revenue authority. Your commercial systems continue to create invoices; MBS is where the structured invoice information is processed and given a status.

For a business preparing to take part, three things matter: how access and registration are handled, what has to be present in the invoice data, and how the response is consumed by your own systems and people.

How an Invoice Moves Through the Process

The operational flow is short enough to hold in your head:

01Invoice Created
02Data Validated
03Submitted
04Response Received
05Status Recorded

This simplified flow is an operational summary for planning purposes. It is not the complete official technical specification, and it should not be used as a substitute for current NRS documentation.

The two points where businesses lose control are the first and the last. If validation happens only after submission, your customers feel the delay. If statuses are not written back into the systems finance actually uses, nobody can answer "what happened to that invoice?" without opening a separate tool.

What Are IRNs and Clearance Marks?

An Invoice Reference Number, or IRN, is a unique reference associated with an invoice processed through the relevant e-invoicing workflow. A clearance mark - often presented as a QR code on the invoice document - is a machine-readable indication that an invoice has been through that processing and can be checked.

The exact technical, formatting and validation requirements for references and clearance marks should follow current NRS specifications. From a business design perspective, plan for three things: storing the reference against the invoice record, presenting it on the document your customer receives, and being able to retrieve it later during a query or an audit.

What Businesses Should Review Before Integration

Invoice inventory. Every system and process that issues an invoice, including departmental tools and manual billing.
Invoice types. Standard invoices, credit and debit notes, proforma documents, intercompany charges, foreign-currency invoices and exempt or zero-rated supplies.
Data completeness. Whether the required identifiers, classifications and tax treatment already exist in the source data.
Volume and timing. Peak daily volume, month-end concentration, and whether invoices must be issued in real time.
Ownership. Named owners for data quality, monitoring, exceptions and credentials.

Portal, API and Service-Provider Approaches

Portal entry needs no integration work and suits very low volumes or a fallback path, but it is manual and offers little control or audit depth. A configured API integration puts validation and submission inside your own process, which scales and gives you visibility, at the cost of a build and a defined support model. A service-provider approach shifts part of that build and monitoring effort, and should be assessed on control, auditability and data handling rather than convenience alone.

Most organisations with meaningful volume end up with an integration for their main systems and a controlled manual path for edge cases. Our integration guide compares those routes in detail.

Common Implementation Problems

Missing or inconsistent buyer tax identifiers in master data
Free-text line descriptions where a classification is expected
Totals that do not reconcile after rounding or discount logic
Credit notes that do not reference the original invoice
Responses collected but never reviewed, so rejections age silently
No named owner for exceptions, so corrections depend on individuals

None of these are exotic. They are the reason a technical readiness review usually starts with a sample of your real invoice data rather than a system diagram.

Frequently Asked Questions

Is the Merchant Buyer Solution the same thing as an ERP?

No. Your ERP or accounting platform creates the invoice. The Merchant Buyer Solution is the NRS e-invoicing environment that supports the electronic invoice process between merchants, buyers and the revenue authority.

Do we submit invoices one at a time?

That depends on the integration method and the volumes involved. A configured integration can prepare and submit invoice data continuously, while portal entry is inherently one invoice at a time.

What should we record for audit purposes?

Keep the submitted payload, the processing response, the resulting status and the identity of whoever corrected an exception. Retaining only the final invoice makes later questions difficult to answer.

Can we test before going live?

Plan for a test cycle using realistic invoice sets, including credit notes, exempt lines, foreign currency and deliberately faulty records, so exception handling is proven before the first live invoice.

Request a Technical Readiness Demonstration

In a technical readiness demonstration we walk through invoice preparation, validation rules, submission, response handling and exception management against your own invoice shapes. You can start with the two-minute readiness check or read the NRS e-invoicing business guide first.

Requirements should always be confirmed at source with the Nigeria Revenue Service.

What Is the NRS Merchant Buyer Solution?

Planning an MBS integration?