FIRS e-invoicing guide for Nigerian retailers (Large Taxpayer compliance)
Last reviewed 2026-05-27 · by the RetailPOS team
Nigeria's Federal Inland Revenue Service (FIRS) has progressively rolled out e-invoicing mandates for Large Taxpayers since 2022, following a similar architectural pattern to GST e-invoicing in India and FBR e-invoicing in Pakistan. Affected businesses must submit each B2B invoice to FIRS' e-invoicing platform in real- time, receive a unique Invoice Reference Number (IRN), and carry a QR code on the printed/digital invoice that decodes to invoice details verifiable on the FIRS portal.
For a covered retailer running RetailPOS, the integration is live before the first invoice goes out — no manual upload, no end-of- day batch, no spreadsheet workaround. This guide covers what FIRS e-invoicing actually requires, which businesses qualify as Large Taxpayers under current rules, what the POS-to-FIRS integration architecture looks like, the penalty schedule, the integration partner landscape, and how RetailPOS' FIRS connector ships.
FIRS e-invoicing is implementing FIRS guidance and pronouncements that continue to evolve. Confirm current threshold + roll-out schedule applicable to your business sector + revenue tier with your tax advisor; this guide reflects the public guidance as of the document date.
Large Taxpayer threshold + scope
FIRS' Large Taxpayer Office (LTO) administers tax matters for businesses meeting the Large Taxpayer threshold. The e-invoicing mandate has rolled out progressively, starting with the largest taxpayers and expanding the threshold over time. As of 2026, the threshold has been progressively tightening; check current FIRS notification for your sector.
Common factors driving Large Taxpayer classification:
- Annual revenue threshold (the headline number that has been progressively lowered)
- Sector-specific application (oil, telecommunications, financial services, manufacturing have had earlier mandates)
- Voluntary registration (businesses can opt in below the threshold)
- FIRS-issued notification to specific taxpayers
For retail businesses, the practical question is: are you currently being assessed at the FIRS Large Taxpayer Office? Your FIRS-assigned tax officer or accountant can confirm. Beyond LTO assignment, FIRS continues to add e-invoicing requirements at the medium-taxpayer tier; the direction is toward universal B2B coverage.
What FIRS e-invoicing actually requires
Every B2B invoice generated by your POS must:
- Be submitted to the FIRS e-invoicing endpoint in real-time
- Receive an Invoice Reference Number (IRN) uniquely identifying the invoice
- Carry a QR code on the invoice that decodes to invoice details verifiable on the FIRS portal
- Include the buyer's TIN (Tax Identification Number) — mandatory for B2B; B2C handled separately
- Include line-item detail with applicable VAT (7.5% standard, zero-rated, exempt as classified)
- Be retained electronically for the audit retention period (FIRS specifies; consult current guidance)
The buyer-side experience: customers scanning the QR or entering the IRN on the FIRS portal verify the invoice was reported to FIRS. This supports the buyer's input-VAT credit claim — wrong or unreported invoices fail the buyer's VAT return reconciliation. The real-time integration is the primary defence against input-credit mismatches.
POS-to-FIRS integration architecture
When a covered retailer rings a B2B sale on RetailPOS:
- Cashier rings the sale, captures buyer TIN (one-tap toggle on the till); standard checkout flow completes locally
- On payment confirmation, POS commits the sale locally + emits an outbox event
- The FIRS e-invoicing connector picks up the event; formats per FIRS schema; signs with the registered API credentials
- Connector posts to the FIRS e-invoicing endpoint; FIRS responds with the IRN + QR-encoded payload
- Connector writes the IRN + QR back to the sale record; receipt printer prints the customer copy with IRN + QR
Total elapsed time from payment confirmation to printed receipt: typically 2-5 seconds with healthy connectivity. The POS doesn't block on FIRS response — if FIRS is slow or briefly unreachable, the local sale completes on time and the connector retries in the background.
For sustained outages, the connector queues invoices locally and submits in order when connectivity returns. The local queue + retry policy reflects FIRS' guidance on permissible-queuing-window without penalty.
Registration + API credential provisioning
Registration flow:
- Apply for FIRS e-invoicing registration via the FIRS taxpayer portal
- Submit your Large Taxpayer status documentation + the POS vendor identity
- Generate API credentials for production use; sandbox credentials for testing
- Configure the credentials into the POS during onboarding; validate against sandbox first
- Move to production endpoint after validation; first live B2B sale generates the first IRN
For multi-branch retailers, each branch typically operates under the same FIRS taxpayer identity (TIN); the e-invoicing credentials apply across all branches. RetailPOS' per- location TIN configuration handles routing correctly.
For RetailPOS customers, the onboarding includes the FIRS credential setup; subsequent new branches self-serve via the back-office configuration screen.
Penalty schedule + audit-defensibility
FIRS penalty schedule for e-invoicing non-compliance has been tightening. General direction:
- Issuing invoice without obtaining IRN when required: monetary penalty + risk of tax-credit denial to buyer
- Issuing non-compliant invoice (missing QR, wrong format): per-invoice penalty
- Failing to file VAT returns reconciled with FIRS-recorded invoices: penalty + interest on underpaid VAT
- Repeated non-compliance triggers FIRS audit + risk of TIN suspension
Specific penalty amounts and enforcement specifics update via FIRS notification; consult your tax advisor for current schedule. The general direction is tightening enforcement.
The tax-credit-denial-to-buyer impact is often more painful than direct penalty — losing B2B customers because your invoices don't support their input-VAT-credit claims compounds over time. The real-time e-invoicing integration is the primary safeguard.
VAT reconciliation + monthly returns
E-invoicing data feeds the monthly VAT return (Form VAT Returns) auto-prep. At month-end:
- FIRS' VAT return auto-draft pre-populated from your e-invoices submitted during the month
- You (or accountant) verify the auto-draft against your POS records; the POS exports the period's sales as a CSV for cross-check
- Any non-e-invoiced transactions (B2C below threshold, exempt supplies) add to the auto-draft manually
- File monthly VAT return + remit VAT due by FIRS due-date
The data-export endpoint produces clean CSVs + per-invoice PDFs on demand for FIRS audit visits. The full audit trail per invoice (POS-side sale record + FIRS-side IRN + interaction history with timestamps) supports defending any FIRS query.
Integration partner landscape
FIRS' e-invoicing API may be accessed directly or via licensed integration partners (similar to GSP/ASP architecture in India). The licensed-partner ecosystem in Nigeria continues to develop.
For a retailer running an international POS without native Nigeria e-invoicing support, the path is via an integration partner — adds latency, a service fee per invoice, and additional integration failure points.
For a retailer running RetailPOS, the FIRS e-invoicing connector ships as part of the platform. We hold (or partner with the holding entity for) the licensed-integrator relationship; the connector is part of the standard sign-up flow for covered retailers; no separate contract, no per- invoice fee beyond the platform subscription.
Frequently asked
- My business isn't in the LTO — does e-invoicing apply?
- Probably not yet for B2B e-invoicing, but the FIRS mandate continues to expand. The direction is toward universal B2B coverage; medium-taxpayer tiers progressively added. Check current FIRS notification for your sector + revenue tier; your tax advisor can confirm.
- Does RetailPOS' FIRS integration cost extra?
- For standard retail categories, the connector ships as part of the platform — no separate per-invoice fee, no separate integration partner relationship. Specialised categories may have category-specific arrangements; confirm at sign-up.
- How long does FIRS API credential provisioning take?
- Typically 5-15 business days from FIRS portal application to credential issuance. RetailPOS' onboarding handles the technical steps; you provide the documentation.
- What happens if FIRS endpoint is down during a sale?
- The local sale completes on time; the connector queues the submission and retries when the endpoint recovers. The retry policy reflects FIRS-guidance on permissible-queuing-window. Sustained outages surface via the manager dashboard.
- Can I issue a B2B invoice without buyer TIN?
- For covered businesses with B2B transactions: TIN mandatory for e-invoicing eligibility + buyer input-VAT-credit claim. For B2C: e-invoicing scope handled separately per FIRS guidance.
- Do I need a separate FIRS integration partner relationship?
- For standard retail categories on RetailPOS — no. The platform holds (or partners with the holding entity for) the licensed-integrator relationship; the connector is native. For specialised categories or volume tiers outside standard, confirm at sign-up.
Open your shop in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.