FIRS E-INVOICING NIGERIA | SERPA | ODOO ERP FOR AFRICA

A finance team closes the month, sends its usual PDF invoices and expects the tax file to follow. Then the compliance review asks a different question: did each taxable supply pass through the Electronic Fiscal System and reach the Nigeria Revenue Service in real time?

That is the operational issue behind FIRS e-invoicing Nigeria searches in 2026. FIRS is the name many teams still use, but the federal authority is now the Nigeria Revenue Service, or NRS. For companies running Odoo across Nigerian entities, the work sits at the intersection of invoice controls, tax data, approved integration and auditable transaction records.

Our Odoo African tax localisation (SARS, FIRS, OHADA) work starts with that distinction. An Odoo Nigeria fiscal localisation helps structure accounting and tax operations. It does not, by itself, establish an NRS-certified Electronic Fiscal System connection.

What changed in Nigeria’s e-invoicing programme

Nigeria’s national e-invoicing regime uses the Electronic Fiscal System, or EFS, with the Merchant-Buyer Solution. Under section 23 of the Nigeria Tax Administration Act 2025, where the NRS deploys an EFS, a person making a taxable supply must use it to record and report supplies and retain accurate EFS transaction records.

The legal test matters because an emailed invoice or a PDF generated from Odoo is not evidence that the supply was processed through the EFS. The requirement concerns the transaction path, including validation and reporting, rather than the visual format of the document sent to a customer.

The first mandatory phase targeted large taxpayers with annual turnover of ₦5 billion or more. The original launch date was 1 August 2025, followed by an extension to 1 November 2025. A July 2026 NRS notice reportedly set 31 July 2026 for full large-taxpayer compliance, including onboarding, approved access-point integration, testing and invoice transmission. That reported date should be confirmed against the current NRS instruction and the taxpayer’s transition notice before the Board relies on it.

Change log for finance and IT teams

| Date | Change | Practical impact in Odoo | | 1 August 2025 | Original first-phase start for taxpayers with annual turnover of ₦5 billion or more. | Large taxpayers needed an e-invoicing delivery plan, not just a tax configuration review. | | 1 November 2025 | FIRS extension date for the large-taxpayer phase. | Teams that treated the extension as a permanent exemption accumulated integration risk. | | 1 January 2026 | The Nigeria Revenue Service replaced FIRS under the tax-law reforms. The Nigeria Tax Administration Act 2025 took effect. | Update governance papers, vendor documentation and compliance ownership to refer to NRS. | | 31 July 2026 | Reported NRS full-compliance date for large taxpayers, covering onboarding, approved integration, testing and transmission. | Confirm current status with NRS, then retain evidence of each test and production transmission. |   The NRS e-invoice portal now operates under the NRS domain. Older FIRS documents and references remain useful for the programme history, but they should not be treated as the current federal authority reference without the NRS update.

What Odoo users must separate

A sound implementation separates three workstreams. Combining them into one vendor question, such as “does Odoo do FIRS e-invoicing?”, usually produces an incomplete answer.

Nigeria fiscal localisation

Odoo’s official documentation lists Nigeria among its fiscal-localisation countries. This supports the finance configuration layer: taxes, accounts and the accounting treatment needed for Nigerian operations.

That work should include a review of tax settings, invoice sequences, customer master data and entity-level controls. Multi-entity groups need particular discipline. A tax position, invoice numbering rule or customer record that works in one legal entity can produce incorrect transaction data when copied into another.

EFS and access-point integration

Odoo’s country-specific e-invoicing documentation does not list Nigeria as a documented country-specific electronic invoicing integration. That means an Odoo Nigeria localisation must not be represented as a native NRS or FIRS connector without checking the current approved-software or access-point list.

The implementation question is therefore specific: which approved integration path will receive the Odoo invoice data, validate it and transmit it to the EFS in real time? The answer needs documentary proof from the relevant programme process, not a sales assurance.

Data governance and exception handling

The EFS connection will only be as reliable as the data arriving at it. Finance and IT should define which Odoo fields are mandatory before an invoice can be posted, who may amend customer tax data, and what happens when a transmission is rejected.

The step organisations skip is deciding whether an invoice can be released before EFS confirmation. That is a control decision for the CFO, tax lead and operations owner. It should not be left to a default setting in an integration project.

The penalty exposure deserves Board attention

The Nigeria Tax Administration Act 2025 sets material consequences for failing to process a taxable supply through the fiscalisation system. The exposure is ₦200,000 plus 100% of the tax due and interest at the Central Bank of Nigeria monetary policy rate.

Refusing access for deployment technology after 30 days of notice can attract ₦1 million plus 10% of the tax due and interest. These provisions change the economics of delay. The cost is not limited to an integration project or an invoice correction. It can include a statutory penalty, tax exposure and interest.

Take an illustrative Nigerian distributor, which we will call Coastline Industrial Supplies. Its annual turnover is above the documented ₦5 billion first-phase threshold. The company has Odoo invoices, but its IT team plans to upload PDF invoices after month-end because the EFS connection is still being discussed.

That approach leaves each taxable supply outside the required real-time process. If the supply is not processed through the fiscalisation system, the statutory exposure starts at ₦200,000, then adds the full tax due and interest at the Central Bank of Nigeria monetary policy rate. Coastline should first confirm its NRS onboarding status, then test an approved integration path using production-like Odoo data before releasing it. The better decision would have been to run tax localisation and EFS integration as linked workstreams from the start.

Take a second illustrative business, a Nigerian services group called Meridian Projects. Its turnover is below the documented ₦5 billion first-phase threshold, and its management assumes it has no work to do. That conclusion goes too far because section 23 applies where the Service deploys an EFS and prescribes the relevant transition arrangements.

For a business in this position, we would not treat the published first-phase threshold alone as proof that an immediate production connection is required. We would still clean the Odoo customer master, tax mapping and invoice approval rules now. That reduces rework if the NRS transition scope expands, and it gives management an auditable baseline instead of a late remediation project.

An Odoo implementation plan that can be audited

The objective is not to add another invoice output. The objective is a controlled chain from sale to tax record, with evidence that can be reviewed by finance, internal audit and the NRS.

Establish scope and legal ownership

Start with the Nigerian legal entities, taxable supplies, invoice volumes and turnover classification. Identify whether each entity falls within the documented large-taxpayer cohort and record the NRS correspondence that supports the conclusion.

Do not use the former 1 August 2025 launch date as the final deadline. The extension and the reported July 2026 enforcement notice changed the implementation context.

Validate Odoo source data

Review the data that originates in Odoo before discussing interfaces. This includes customer identity and tax details, product tax treatment, invoice dates, credit-note treatment, legal-entity assignment and user permissions.

A connection cannot correct an invoice that is wrong before it leaves Odoo. This is why tax localisation belongs in the implementation plan, alongside integration design.

Confirm the approved connection model

Ask for proof that the proposed software, access point or integration route is accepted for the NRS programme. Odoo official documentation supports Nigeria fiscal localisation, but it does not publish Nigeria in its country-specific e-invoicing documentation.

That difference should be written into the project decision record. It prevents a common procurement mistake: buying a localisation configuration on the assumption that certified EFS transmission is included.

Test the full transaction lifecycle

Testing should cover more than a successful standard invoice. Include the scenarios that create accounting and tax exceptions: corrected customer data, cancelled invoices, credit notes, rejected transmissions and the reconciliation between Odoo invoice records and EFS records.

Retain the test evidence. An auditable implementation needs a clear answer to two questions: what did Odoo create, and what did the EFS accept or reject?

Put operational controls in place

Define ownership for failed transmissions, monitoring frequency, escalation and reconciliation. Finance should own tax treatment. IT should own the reliability and security of the integration. Operations should understand when an invoice may be released to a customer.

For groups using Odoo ERP across countries, keep Nigeria-specific EFS controls separate from other local rules. SARS e-invoicing considerations, Zimbabwe fiscalisation processes and OHADA accounting requirements may all need localised design. They should not be copied into a Nigerian configuration without a country-by-country compliance review.

Questions Boards should ask before approving the project

Frequently Asked Questions

Is FIRS still responsible for e-invoicing in Nigeria?

The federal authority is the Nigeria Revenue Service from 1 January 2026. FIRS remains relevant in historic programme materials and in common search language, which is why many organisations still refer to FIRS e-invoicing.

Does Odoo Nigeria fiscal localisation provide NRS e-invoicing compliance?

No conclusion should be made from localisation alone. Odoo officially lists Nigeria as a fiscal-localisation country, while its country-specific e-invoicing documentation does not list Nigeria. Confirm the approved EFS connection model separately.

Are PDF invoices sent by email enough for the EFS requirement?

A PDF or email does not by itself demonstrate EFS validation and real-time transmission. Section 23 requires use of the EFS where deployed by the Service for taxable supplies, subject to the prescribed system and transition arrangements.

What is the penalty for bypassing the fiscalisation system?

The stated penalty is ₦200,000 plus 100% of the tax due and interest at the Central Bank of Nigeria monetary policy rate. Refusing deployment access after 30 days of notice carries ₦1 million plus 10% of tax due and interest.

Sources used for this update

This update reflects the Nigeria Tax Administration Act 2025, the NRS Electronic Fiscal System portal, the original FIRS large-taxpayer advisory, and Odoo’s official fiscal localisation and electronic invoicing documentation. The reported 31 July 2026 full-compliance date remains marked for verification because it is based on a reported NRS notice.

If your Nigerian entity invoices taxable supplies from Odoo, Request a Consultation on Odoo African tax localisation (SARS, FIRS, OHADA) before approving an integration or relying on a PDF-based invoice process.