COMPLIANCE BUILDS

Get NRS-compliant invoicing without re-architecting your business.

We integrate your existing sales process — whether it lives in Excel, a POS, a custom CRM, or even WhatsApp — directly into the NRS Merchant Buyer Solution. Compliant invoices, IRNs, QR validation, audit-ready records. Two to three weeks. No staff retraining needed.

₦2M – ₦4M2–3 WEEKSINCLUDES 30-DAY POST-LAUNCH SUPPORT
SEE IT WORK

Type a sale. Watch a compliant invoice generate live.

A working model of the same pipeline we'd integrate into your sales flow. Edit the three fields on the left. The invoice on the right re-renders, the IRN regenerates, the QR re-encodes, and the validation badge re-issues — exactly the way the production system will.

SALE ENTRY · DEMOMBS · SIMULATED
ENDPOINTPOST /mbs/v1/invoices
NRS-FORMAT INVOICE (DEMO)

Invoice for sale.

Sample Vendor Ltd12 Constitution Rd, Kaduna
TIN · 21847365-0001
VAT · NG-VAT-019283
IRNIRN-00000000-000000-0000
Invoice date
Bill toMrs Adaeze Okeke
DescriptionQtyAmount
20 cartons of palm oil1₦450,000.00
Subtotal₦450,000.00
VAT · 7.5%₦33,750.00
Total due₦483,750.00
Validation hashSHA-256 · 0000…0000Illustrative — not a live NRS submission.
Demo · NRS format

Interactive demo. Invoices shown are illustrative and are not cleared with the NRS.

The integration we build for you connects to the real NRS Merchant Buyer Solution.

SCOPE

What's included in the build.

A fixed-scope, fixed-price engagement. Every build ships the same seven deliverables — the only thing that varies is which sales system we wire them into.

01

NRS Merchant Buyer Solution API integration

A working connection to the MBS endpoint, wired into the sales system you already run on. Token rotation, retry policy, and the dead-letter queue for the cases where MBS is down and yours can't be.

02

BIS 3.0 XML invoice generation

Every sale serialized to the BIS 3.0 schema with the correct UBL extensions for NRS — line items, VAT, WHT, payment terms, and the CBN-mandated NGN currency code. Validates clean against the official XSDs.

03

IRN issuance and validation

An Invoice Reference Number minted for every sale, persisted before the invoice reaches the customer. Stored against your internal order ID so a single lookup gives you both sides of the audit trail.

04

QR code attachment

The validation QR encoded against the IRN and the document hash, rendered onto both the customer-facing PDF and the printed receipt at the POS. Scans against the NRS public verifier.

05

Audit-ready transaction logs

An append-only ledger of every invoice issued — payload, response, IRN, timestamp, retries, exceptions. Exported on demand to CSV or queried directly from FIRS during an audit window.

06

Staff training session

A 2-hour walkthrough for the people closing sales and the people closing the books — what changed in their workflow, what to do when MBS rejects an invoice, and the two screens they'll actually use.

07

30-day post-launch support window

Direct line to the engineer who built it for 30 days after go-live. Schema updates, edge cases, and the inevitable "it worked yesterday" — included, no clock.

FOR THE TECHNICAL READER

We know the rules.

We work with the NRS Merchant Buyer Solution MBS using BIS 3.0 XML format. Every invoice is assigned a unique Invoice Reference Number IRN, validated via QR, and logged for audit. We handle Continuous Transaction Control CTC requirements and integrate with FIRS reporting. We build to these standards directly — they're the same ones we designed TaxJeje around.

MBS
Merchant Buyer Solution — the NRS clearance endpoint every B2B invoice transits before reaching the customer.
BIS 3.0
The PEPPOL UBL profile adopted as NRS's invoice schema. We validate against the official XSDs before submission.
IRN
Invoice Reference Number — issued by NRS, the legal anchor for the invoice. No IRN, no invoice.
CTC
Continuous Transaction Control — clearance-model invoicing, where the tax authority sees the invoice before the buyer does.
WHT
Withholding tax codes correctly applied per sector, with the right ledger postings for FIRS reconciliation.
FIRS
Federal Inland Revenue Service — the reporting endpoint downstream of NRS. Reconciliation happens nightly.
FIT

You probably need this if

  • Your turnover puts you above the 2026 NRS threshold and you have weeks, not quarters, to get compliant.
  • Your sales already run on something — a POS, an ERP, a spreadsheet, a WhatsApp group — and you'd rather integrate than replace.
  • You've looked at the off-the-shelf NRS portals and the workflow doesn't fit how your team actually books sales.
  • You want the invoicing layer owned by your business, not rented from a vendor that can change the terms next quarter.
QUESTIONS

Common questions about the NRS transition.

The four we hear on every first call. If yours isn't here, the quote conversation is the place for it.

Almost always, yes. The integration sits behind whatever your team uses today — Sage, QuickBooks, Odoo, a custom Laravel app, a POS, even a shared spreadsheet — and intercepts the moment a sale is closed. Your staff keep doing what they were doing. The MBS call happens in the background. We can integrate against any system that exposes a webhook, a database, or a file the cashier touches.
We watch the NRS bulletin and run our generator against every new XSD on the day it drops. During the 30-day support window any schema change is on us. After that we offer a yearly retainer that covers schema upgrades for a fixed annual fee — typically a tenth of the build cost. Most clients take it.
Yes — and we recommend it. The legally-binding artifact is the cleared XML with its IRN; the PDF is a courtesy for human readers. We generate the PDF from the same payload, stamp it with the IRN and QR, and route it via your existing email or WhatsApp delivery. Your customers won't notice anything has changed except that the invoice now validates.
For B2C and printed receipts, yes — the QR is what lets a customer or a tax officer verify the invoice against the NRS register without calling anyone. For B2B XML-only exchanges it's not legally required, but we include it anyway because it's the cheapest dispute-resolution tool you'll own. One scan resolves "is this real?" in under a second.
Rare, but it happens — usually because of a TIN mismatch or a sector code that needs correcting. The system flags the rejection, queues the correction, and re-submits automatically once the underlying record is fixed. The original sale isn't reversed; only the compliance record is amended. Your finance team sees a single line in the exceptions queue, not a fire drill.
START

Compliant in two to three weeks.

Send us the shape of your sales process. We'll come back inside two business days with a fixed quote, a build timeline, and the three questions that decide whether you're at the lower or upper end of the range.

Get a fixed quote