Electronic Invoicing Compliance in Nigeria: What Every Business Must Know Before Going Live

The mandate is not a software installation. It changes how invoicing works, daily, and most of what goes wrong is settled before go-live or not at all.

There is a specific moment that catches Nigerian finance teams, and it is worth describing precisely because it is avoidable.

It is late afternoon on the last working day of the month. A significant invoice needs to go out today for it to land in this period. The integration is live, it has been working for weeks, and clearance is now failing validation on a customer record that has been in the system since 2019.

Under the old arrangement, you would have issued the invoice and fixed the data later. Under clearance, you cannot. The document is not a valid invoice until the Nigeria Revenue Service returns an Invoice Reference Number, and NRS will not return one for a document it cannot validate.

Nobody discovers that in a demonstration. They discover it in week four.

This article is about what to settle before that week. Not the law, which we have covered separately, and not the procurement. This is the operational readiness piece: what changes when clearance goes live, what has to be true before it does, and the decisions that are cheap now and expensive later.

First, what NRS actually counts as compliance

Start here, because a great many companies believe they are compliant and are not.

In July 2026, NRS set out five tests. You are compliant when you have:

1. Completed onboarding on the Merchant Buyer Solution
2. Successfully integrated your systems through approved Access Point Providers or System Integrators
3. Completed all mandatory validation and testing activities
4. Actively transmitted invoices in line with approved standards
5. Ensured that only compliant e-invoices bearing a valid IRN are received from your suppliers

Test four is why registration is not compliance. A company can be onboarded, integrated and tested, and still be non-compliant because no live invoice has ever gone through. Integration is an event. Compliance is a state you have to keep being in.

Test five is why this is not solely your project. It reaches into your supply chain, and no amount of internal readiness fixes a supplier who is not transmitting.

Everything below is organised around getting genuinely past all five.

Gate one: your master data

If you read nothing else here, read this. Master data is the reason integrations fail, and it is the one workstream no provider can do for you.

Clearance is a validation engine. It rejects documents that do not conform, and it does not care that the customer record has been fine for six years.

What has to be right:

Customer tax identification numbers. Every business customer needs a valid TIN in your system, in the correct format. For most Nigerian companies with any history, this is where the real work is. Records captured before TINs mattered do not have them, and nobody can invent them. Collecting them is a customer-contact exercise with a lead time measured in weeks, not a data cleanse you run over a weekend.

Addresses that resolve to valid codes. States and local government areas use structured subdivision codes rather than free text. An address field containing "Victoria Island, Lagos" typed by a salesperson in 2021 is not a state code and a local government area code.

Product and service classification. Line items need classification codes, and somebody has to decide what your catalogue maps to. This is a judgement exercise, not a lookup, and it needs finance and tax input rather than being left to whoever runs the integration.

Tax treatment per line. Standard-rated, zero-rated, exempt. Get this wrong and you are not just failing validation, you are misreporting VAT. Note in particular that zero-rated is not exempt. Exports, basic food, medical goods and education are zero-rated, which means they are taxable supplies that go through the system. Genuinely exempt supplies are declared inside the invoice with an exemption code rather than left out.

Start this before you choose a provider. The work is provider-independent, it is the longest pole, and every week you spend on it early is a week removed from the critical path later.

A blunt readiness test: pull a random sample of one hundred active customer records and check how many have a valid TIN, a resolvable state and local government code, and a classification for what you sell them. Whatever percentage comes back is roughly your go-live readiness, and it is usually lower than the finance team expects.

Gate two: every document type, not just the sales invoice

Projects scope the standard sales invoice and then meet reality.

Enumerate every document your business issues that carries VAT, and check each against the schema and against your provider's coverage:

• Standard sales invoices
• Credit notes and debit notes
• Foreign currency transactions
• Documents mixing standard-rated, zero-rated and exempt lines
• Self-billing arrangements, if you use them
• Recurring and milestone billing
• Intercompany invoices, if group entities transact
• Proforma documents, and what they become

Credit notes deserve particular attention because they are how you correct things, and how corrections work under clearance is a policy question rather than a technical one. Which brings us to the next gate.

Gate three: how you will fix mistakes

Under the old model, an incorrect invoice was a printing problem. Under clearance, a cleared invoice is a document the tax authority already holds.

NRS provides a correction window. Its published position is that e-invoices can be rejected or cancelled within 72 hours, with corrections resubmitted as needed.

Seventy-two hours is workable, but it is a real constraint and it has consequences you should think through before go-live rather than during an incident:

Who is allowed to cancel? If cancellation authority sits with whoever is nearest the system, you have created a control weakness. If it sits too high, you will miss the window over a weekend.

How do you find out something is wrong inside 72 hours? Most invoicing errors surface when a customer complains, and customers do not reliably complain within three days. That argues for stronger controls before clearance rather than reliance on correction after it.

What happens after 72 hours? Then you are in credit note territory rather than cancellation, with the original document permanently on record. Your finance team needs to know the difference and when each applies.

The practical answer for most businesses is to move validation earlier. Catching a bad customer record at order entry is cheap. Catching it at clearance is disruptive. Catching it after 72 hours is a reconciliation exercise.

Gate four: the buyer side

Half of the compliance definition concerns invoices you receive, and this is the most commonly under-scoped part of an entire project.

You are required to ensure that the invoices your suppliers send you carry valid Invoice Reference Numbers. That is an accounts payable process change, not a sending-side integration.

Settle these before go-live:

How do you check? Manually, by someone eyeballing a QR code, or automatically through validation in your AP workflow? At any volume, manual checking is not a control, it is a hope.

What happens when an invoice fails? Do you reject it, hold it, pay it and flag it? Who decides? This needs to be a written policy, because the first time it happens the answer will otherwise be improvised by whoever is on duty.

What do you tell suppliers? Most Nigerian businesses will need a supplier communication programme. Your smaller suppliers may be in a phase that does not require them to transmit yet, and you may be required to receive only compliant invoices. That tension is real and it resolves commercially, through your onboarding terms and your purchase order conditions, rather than through your software.

Start the supplier conversation early. It has a longer lead time than anything technical.

Gate five: B2C, if it applies to you

If you sell to consumers, the model is different. B2C transactions are not cleared in advance. They are reported afterwards, within 24 hours.

NRS illustrates the pattern with a retailer running 200 stores and 1,200 cash registers: each register issues a simplified tax invoice carrying a QR code, receipts flow to a central system, and the company must report all issued invoices within 24 hours.

Two decisions follow. First, you elect between real-time and near real-time submission, and that choice should be driven by your point of sale architecture rather than taken by default. Second, your reporting is only as good as the central collection path, so the store-to-centre link becomes a compliance dependency rather than an operational convenience.

If you run both B2B and B2C, confirm your provider handles both models. Not all coverage is symmetrical.

Gate six: archiving and where data lives

Two separate questions, and the second has a clear answer.

Where the data lives is settled by regulation. The NITDA guideline requires that all electronic data, including user records, access codes, logs and invoice data, be encrypted and stored or backed up on servers or data centres in Nigeria. If your provider or your own architecture stores invoice data exclusively offshore, that does not meet the guideline. For multinationals running consolidated regional systems, this is often the most disruptive single requirement, and it is better raised in design than in an audit.

How long you must keep records is set by statute, and the figure that circulates in vendor material is broadly right but imprecisely stated.

Section 31 of the Nigeria Tax Administration Act 2025, headed "Books of Account", requires that "every person, including a company granted exemption from incorporation, shall, whether or not the person is liable to pay tax, maintain books or records of accounts." Subsection (5) sets the period:

"Any book or record required to be kept under this section shall be kept for a period not less than six years after the year of assessment in which the income relates."

Three details matter, and the shorthand "six-year archiving" loses all of them.

It is a minimum, not a period. The Act says "not less than six years."

It runs from the year of assessment, not from the invoice date. An invoice raised early in a financial year is held longer in practice than a six-year clock started on its own date would suggest. If you are configuring an automated purge, this is the detail that gets it wrong.

Six years is not an absolute ceiling on your exposure. Section 55 gives the tax authority a six-year assessment window, but subsection (2) allows an audit that commenced before expiry to continue past it, and subsection (4) provides that where there is a deliberate misstatement, the authority may assess "at any time and as often as may be necessary." Section 68(6) carries a similar carve-out for records found to be untrue. Destroying records at exactly six years is compliant. It is not always prudent.

The NITDA e-invoicing guideline does not impose its own retention period, but it does require that the e-invoicing platform "provide data retrieval, archiving and transfer modalities for safekeeping and business continuity to ensure continuous availability."

Whatever the period, settle these contractually: who holds the archive, in what format you can extract it, how long extraction takes, what it costs, and what happens to it if you change provider. That conversation is straightforward before signing and difficult afterwards.

Testing, and then actually going live

NRS operates separate staging and production environments with distinct credentials. You work through validation and testing in staging before production access means anything.

Two things to plan around.

Test with your real data, not clean samples. The failures that matter are data failures. An integration that works perfectly against three tidy test records tells you nothing about a customer master with fifteen years of accumulated variation. Run volume, run your worst records deliberately, and run the document types you nearly forgot.

Go-live is not the finish. NRS's compliance definition requires active transmission. Plan the operational handover: who watches the queue, who clears exceptions, what the escalation path is, and what the first month-end looks like. A company that integrates beautifully and then transmits nothing has not complied.

What actually changes on day one

This is the part that rarely appears in a project plan and always appears in the first month.

Invoicing becomes real-time. Whatever used to happen in a batch at the end of the day now happens transactionally, with an external dependency in the middle. That is a different operating rhythm.

Exceptions need a daily owner. Not a project team, a named person in the business. Cleared, failed, pending, cancelled: someone has to look every day and act. Organisations that leave this to the integration partner discover the gap at month end.

Month-end close changes shape. The cut-off is no longer when you stop raising invoices. It is when your last invoice clears. Build that into the close calendar rather than finding out.

Credit control gains a new failure mode. A customer can now dispute that they ever received a valid invoice, and the answer is verifiable rather than arguable. That works in your favour, but only if your team knows how to evidence it.

Your compliance depends on other people. Your suppliers' readiness affects your position. That is genuinely new, and it makes supplier management a compliance function as well as a commercial one.

Compliance is a state, not a milestone

One thing to build into your planning from the start: the specification moves.

NRS ships schema changes with a stated grace period. Updates are optional for three months from their release date, after which compliance is enforced. In practice that means whatever you build needs a maintenance path and someone accountable for it.

That matters more in Nigeria than in most jurisdictions, because no major ERP vendor ships a Nigeria localisation. SAP states the position for uncovered countries plainly: it "does not provide legal changes for customer local versions," and compliance maintenance "is the responsibility of the customer or their implementation partner." So when the schema changes, the update comes from your provider or from you. Establish which, in writing, before go-live rather than at the first change.

The regime itself is also still being written. The Nigeria Tax Administration Act requires the Service to issue a regulation giving effect to the fiscalisation section, and we could find no trace that it has been made. Guidance for non-resident suppliers remains unpublished. The cross-border schema is still in preparation. NRS's own resources page refers to exemption criteria that have never been released.

None of that is a reason to wait. It is a reason to have a partner who tracks it and a contract that says who is responsible when it changes.

A pre-go-live checklist

Fifteen questions. If you cannot answer them, you are not ready, whatever the integration status says.

Data

1. What percentage of active customers have a valid TIN?
2. Do our addresses resolve to valid state and local government codes?
3. Is every product and service line classified?
4. Is tax treatment correct per line, including zero-rated versus exempt?

Documents

5. Have we listed every VAT-bearing document type we issue?
6. Are credit notes and debit notes covered and tested?
7. Are foreign currency and mixed-rate documents tested?

Process

8. Who can cancel a cleared invoice, and how do we detect errors inside 72 hours?
9. Who owns exceptions daily, and what is the escalation path?
10. How does month-end cut-off change, and does the close calendar reflect it?

Buyer side

11. How do we validate IRNs on inbound supplier invoices?
12. What is our written policy when a supplier invoice has no valid IRN?
13. Have we told our suppliers, and by when do we need them ready?

Continuity

14. Who maintains our integration when the NRS schema changes, and what does the contract say?
15. Where is our archive held, in what format can we extract it, and does our retention rule run six years from the year of assessment rather than from the invoice date?

The honest summary

The businesses that struggle with this mandate are rarely the ones that chose badly. They are the ones that treated it as an IT project with a deadline rather than a change to how the business invoices.

Roughly 5,000 large taxpayers were in scope when the system went live in August 2025. Around 1,000 had onboarded within a fortnight. By mid-2026 the NRS was describing the majority as onboarded, with many transmitting, yet the compliance figure it last published stood at more than 1,000 as of the first quarter, and it has set a 31 July 2026 deadline and begun monitoring. Onboarding has moved; full compliance has lagged behind it. That gap is not a story about software procurement. It is a story about data, document types, supplier readiness and process discipline, which are the four things nobody can buy their way past.

Get those right and the integration is the easy part. Get them wrong and no provider on the register can save the go-live.

Where we fit

Doftwerks West Africa Limited holds both System Integrator and Access Point Provider accreditation, approved on 30 April 2026 and listed on the official register at mbs.gov.ng/service-providers-directory. Our MBS integration runs in the live production environment and our API documentation is published openly.

We would rather a client arrived at go-live having done the unglamorous work above than arrived on time and discovered it in week four.

Contact us: [email protected] · +234 903 981 7173 · www.doftwerks.com

Sources

The compliance definition is from the NRS statement of 19 July 2026. The 72-hour correction window, the 24-hour B2C reporting rule, the real-time and near real-time election, staging and production arrangements and the schema change grace period are from the NRS e-invoicing portal at einvoice.nrs.gov.ng, including its published resources, use cases, changelog and developer documentation. Data residency and technical obligations are from the National Regulatory Guideline for Electronic Invoicing in Nigeria 2025 issued by NITDA, in force from 1 September 2025. Statutory references are to the Nigeria Tax Administration Act 2025 and the Nigeria Tax Act 2025 as gazetted on 26 June 2025. ERP vendor positions are from each vendor's own current published documentation. Onboarding figures are from statements by the NRS e-invoicing project lead in August 2025 and NRS statements reported in July 2026. Record retention and assessment limitation provisions are quoted from sections 31, 55 and 68 of the Nigeria Tax Administration Act 2025 as gazetted, read directly from the Act rather than from commentary.

This article is provided for general information and reflects the position as at 22 July 2026. It is not legal or tax advice. Confirm your specific obligations with your tax adviser and against current NRS publications.