By Musskart Technology Editorial Team Published: Updated: Reviewed by Musskart Senior Engineers

Your Invoicing Software Just Got a New Job

If you are VAT-registered and raise invoices from an ERP, a POS terminal, an accounting package or software your own team built, that software now carries a new responsibility. Every invoice must be transmitted to the tax authority's platform, checked against a published rule set, and returned carrying an official Invoice Reference Number (IRN) and a QR code — before it reaches your customer. That is what Nigeria's national e-invoicing programme, delivered through the FIRS e-Invoice service on the Merchant Buyer Solution (MBS) platform, requires.

The rollout is phased by annual turnover. Large taxpayers (over ₦5 billion) went live in November 2025, and the tax authority set 31 July 2026 for all of them to be fully on the system. Medium taxpayers (₦1 billion to ₦5 billion) went live on 1 July 2026, with penalties enforced from January–March 2027. Emerging taxpayers (below ₦1 billion) go live on 1 July 2027, with enforcement from January–March 2028. You will also see two names for one authority: under Nigeria's 2025 tax reform legislation, including the Nigeria Tax Administration Act 2025 and the Nigeria Revenue Service (Establishment) Act 2025, the Federal Inland Revenue Service becomes the Nigeria Revenue Service (NRS).

Taxpayer group (annual turnover)Go-livePenalties enforced from
Large (over ₦5bn)November 2025 (full adoption due 31 July 2026)April 2026
Medium (₦1bn–₦5bn)1 July 2026January–March 2027
Emerging (below ₦1bn)1 July 2027January–March 2028

Source: Nigeria Revenue Service public notice of 17 February 2026, as summarised by KPMG and Sovos; large-taxpayer deadline reported by Nairametrics (19 July 2026). Each phase starts with engagement and a pilot; penalties under the Nigeria Tax Administration Act apply only from the enforcement phase.

This page is about the engineering, not the tax. Musskart Technology Limited is a registered Nigerian software company. We connect the system you already run to the platform, map your invoice data to the required fields, and handle the validation responses and the failure cases — so the till still works when the network does not.

250+

Projects Delivered Since 2020

HQ Asaba

Delta State, Plus An Abuja Office

Registered

A Registered Nigerian Company

Jan 2027

Penalties Begin for Medium Taxpayers

We reply on WhatsApp within minutes.

What the MBS Mandate Requires

Strip away the acronyms and the obligation is short: before an invoice is a valid invoice, it must be submitted, validated and stamped. Four things follow.

Near-real-time validation

Your invoice is no longer a private document between you and your customer. It is submitted as it is raised and checked against the platform's rules — supplier and buyer identification, mandatory fields, tax treatment, arithmetic. Batch-uploading last month's sales is not the model.

IRN, cryptographic stamp and QR

A successful submission returns an Invoice Reference Number, a cryptographic stamp identifier and a QR code. These must be stored against the invoice and printed on your customer's copy, so it can be verified independently.

Who is in scope

VAT-registered businesses invoicing business-to-business, business-to-government and business-to-consumer. Waves are set by turnover band. Confirm your own with the tax authority or your tax adviser.

More than sales invoices

Credit notes, debit notes and amendments are in scope too, and must reference the original document. This is where half-finished integrations fall over: they submit the sale and forget the refund.

How the Integration Actually Works

Nigeria's platform follows the international four-corner model, using a standards-based invoice format rather than a bespoke file layout, and invoices commonly travel through an access point provider accredited by the tax authority rather than straight from your server. Here is the path an invoice takes once we are finished.

Step 1 — Your system raises the invoice as normal

Nothing about your staff's day changes. Compliance that forces people to type things twice does not survive a busy shop floor, so we hook into the workflow you already have.

Step 2 — We map your data to the required structure

Your record becomes the structured format the platform expects: supplier and buyer tax identification numbers, invoice type code, currency, issue date, line-level descriptions and codes, quantity, unit price, discounts, VAT rate and amount per line, tax-exclusive and tax-inclusive totals, payment terms, and a reference to the original for a credit or debit note.

Step 3 — Authenticated submission over the API

The document is signed with your credentials and transmitted, either directly against the published API or through the accredited access point provider you appoint. That route stays in configuration, not hard-coded, so changing provider later is a settings change.

Step 4 — Validation and error handling

On success you get the reference number, stamp identifier and QR payload. On failure you get error codes — a TIN that does not resolve, an empty mandatory field, totals that do not reconcile, an invalid tax category. We translate those into plain English, because "ERR-0042" helps nobody.

Step 5 — Stamp, store, queue and reconcile

The reference number and QR are written back onto the invoice record and the printed or emailed copy, in a layout that survives a 58mm thermal printer as well as an A4 PDF. Full request and response payloads are retained, anything untransmitted sits on a durable queue for automatic retry, and a reconciliation view lists every invoice still waiting for a reference number.

The Systems We Integrate

We do not sell you a replacement platform. Your existing software keeps its job and gains one new capability.

Odoo modules ERPNext apps Laravel & Node services POS queue & receipt stamps Middleware for legacy systems Sandbox test harness Reconciliation dashboard Credit & debit notes Multi-branch rollout Multi-entity groups

Data Mapping and VAT — Where the Time Goes

Clients expect the API work to be the hard part. It rarely is. What consumes the schedule is your existing data, because an electronic invoice demands a completeness a PDF never did.

Tax identification numbers

Business customers need a valid TIN on record. Most companies discover on first submission that a meaningful share of their customer file has a blank, a phone number in the wrong field, or a transposed digit. We run a clean-up pass before go-live rather than letting rejections teach you one customer at a time.

VAT treatment per line, not per invoice

Standard-rated at 7.5%, zero-rated, exempt and out-of-scope items behave differently, and the format expects the treatment declared at line level with the arithmetic reconciling exactly. Businesses that applied VAT at invoice level get caught here. We map each product category to a tax category, with your accountant confirming the classification.

Descriptions, rounding and credit notes

"Item", "Misc" and "Sundry" do not survive; line descriptions and codes must be meaningful. Discrepancies of one kobo fail validation, so rounding rules are settled once — per line, per tax subtotal, per invoice. And every refund or correction must reference the original stamped invoice, so we build those paths from the start.

What Happens When the Network Fails

This is the section other integrators skip, and the one that decides whether your compliance holds up in real Nigerian trading conditions. Fibre gets cut, bundles finish, remote platforms have maintenance windows — and you still have to sell.

What e-Invoicing Integration Costs in Nigeria

We quote fixed prices in Naira against a written scope, after a short discovery call. Most integrations land between ₦500,000 and ₦5,000,000, depending on how many systems are involved, how clean your data is, and whether you need credit notes, branches and multiple legal entities on day one.

Single System

₦500,000 – ₦1,200,000

One system, one entity, one tax profile. Field mapping, API integration, sandbox testing, IRN and QR on your invoice template, queue and retry, go-live support.

Multi-Branch

₦1,200,000 – ₦3,000,000

Custom or legacy software, credit and debit notes, several branches or POS terminals, offline queuing, review queue, reconciliation dashboard, data clean-up, staff training.

Group / Middleware

₦3,000,000 – ₦5,000,000

Multiple entities and source systems on one shared middleware service, high volume, monitoring and alerting, role-based access, documentation and handover.

After go-live we quote a support and compliance-change retainer, typically ₦120,000 to ₦450,000 per month, depending on volume and response time. It covers monitoring, clearing stuck submissions, and updating the integration when the platform's specification changes. Everything is invoiced in Naira by Musskart Technology Limited.

Timeline: Sandbox First, Then a Calm Go-Live

Nobody should meet a validation rule for the first time on a real customer's invoice. A single-system integration runs three to five weeks; a multi-system or multi-entity rollout runs six to twelve weeks.

Week 1 — Discovery and field mapping

We review your system, invoice templates, tax profile and a sample of live data, then hand you a field-mapping document and a fixed price before anyone writes code.

Weeks 2–3 — Build and sandbox testing

We register your test credentials and replay a slice of your real invoice history through the platform's sandbox — your product mix, your customer types, your awkward edge cases — until submissions pass cleanly and every error path is understood.

Week 4 — Data clean-up and parallel run

Customer TINs validated and corrected, tax categories confirmed with your accountant, and invoices transmitted in parallel with your normal process while we compare totals daily — the cheapest place to find a mapping mistake.

Week 5 — Go-live, training and handover

Live credentials, close monitoring through the first week, staff trained on the new statuses, plus documentation and a runbook for the few things that go wrong at 4pm on a Friday.

Our honest advice: start six to eight weeks before your deadline. Data clean-up expands to fill whatever time you give it.

What Musskart Is — and What We Are Not

Musskart Technology Limited is a software development and integration company. We are not a tax authority, not a regulator, not an accreditation body, and not a certified provider of any government scheme. We do not give tax advice and we do not perform audits.

In practice: you obtain any registration or clearance required from the Federal Inland Revenue Service / Nigeria Revenue Service, and where your route requires it, you appoint the accredited access point provider you transact through. We build the software that connects your system to that route. Your accountant confirms your wave, your VAT classifications and what you must declare; we make sure your software can produce and transmit it correctly.

Why Businesses Bring This to Musskart

Tell us what you run — we will tell you what it takes

Send the name of your ERP, accounting package or POS, how many invoices you raise a month, and your deadline. You will get a straight answer on approach, timeline and price range in the same conversation.

Message Us on WhatsApp

Frequently Asked Questions

The programme is rolling out in waves by annual turnover. Large taxpayers (over ₦5 billion) went live in November 2025, medium taxpayers (₦1 billion to ₦5 billion) went live on 1 July 2026 with penalties enforced from January 2027, and emerging taxpayers (below ₦1 billion) go live on 1 July 2027 with enforcement from January 2028. If you are VAT-registered and issue invoices to businesses, government or consumers, assume you are in scope. The tax authority publishes the wave list and the technical specification, and it is the authority, not your software vendor, that confirms your date. Have your accountant confirm your wave, then give us the deadline and we plan backwards from it.

It depends on the route you choose and what the tax authority currently permits for a taxpayer of your size. Nigeria's platform follows a four-corner model, in which invoices commonly travel through an access point provider accredited by the tax authority rather than straight from your server. Musskart is a software developer and integrator, not an accreditation body and not an accredited access point provider. We build the connection either directly against the published API or through whichever accredited provider you appoint, and we keep that choice in configuration so you can switch later without a rewrite.

Most projects land between ₦500,000 and ₦5,000,000. One system, one entity and a straightforward sales-invoice flow sits at roughly ₦500,000 to ₦1,200,000. Credit and debit notes, several branches, offline queuing and a reconciliation dashboard run about ₦1,200,000 to ₦3,000,000. Multi-entity groups and a shared middleware service feeding several systems reach ₦3,000,000 to ₦5,000,000. After go-live we quote a support and compliance-change retainer, usually ₦120,000 to ₦450,000 per month depending on volume and response time.

Yes. For Odoo and ERPNext we build a proper module or app so validation lives inside the invoicing workflow rather than in a spreadsheet beside it. For packaged accounting software such as QuickBooks, Sage or Zoho we work through the published API or export path, because those products are not built for Nigerian fiscal rules. For custom software in Laravel, Node, .NET, Python or PHP we integrate directly in your codebase, and for POS we add a queue so a sale never blocks at the counter. If a system has no API at all, we build middleware that reads from its database.

Your sale must never stop because a remote server is unreachable, so we design for that from day one. The invoice is written locally and placed on a durable queue with a unique idempotency key, the customer is served, and a background worker retries with exponential backoff until the platform accepts it or returns a real validation error. Anything failing repeatedly moves to a review queue that a named person clears, and a reconciliation dashboard shows every invoice still waiting for a reference number. An outage becomes a short transmission delay, not a gap in your records.

A single-system integration usually takes three to five weeks from kickoff to production, and a multi-system or multi-entity rollout takes six to twelve weeks. The engineering is rarely the slow part. Time goes into field mapping and data clean-up, because tax identification numbers, customer records, product codes and VAT treatment in your existing data are usually incomplete, and into sandbox testing where you fix rejections before they reach a real customer. Start six to eight weeks before your deadline so go-live is calm rather than a scramble.

Related Musskart Guides

Get Your Invoicing Ready Before the Deadline, Not After It

Send us your system and your deadline on WhatsApp. You will get a straight answer on approach, timeline and a fixed price in Naira — and we reply within minutes.

Chat on WhatsApp Now Get a Quote Call +234 813 168 6721 See Our Full Pricing
WhatsApp