Nigeria Payroll (PAYE, Pension, NHF)

Name: Nigeria Payroll (PAYE, Pension, NHF)
Brand: ECOSIRE
SKU: odoo-nigeria-payroll

Recursos Principais

PAYE progressive tax computed across the statutory income bands as Odoo salary rules, with the consolidated relief allowance (CRA) applied before taxable income is derived

Employee and employer pension contributions calculated on the pensionable base, posted as separate deduction and employer-cost lines on the payslip

National Housing Fund (NHF) deduction computed on basic salary with configurable eligibility per employee or contract

NSITF and ITF employer levy handling, modelled as employer-side contributions that never reduce employee net pay but feed cost reporting

NGN salary structures and structure types with reusable Nigeria salary categories (basic, housing, transport, allowances) so contracts assemble from standard building blocks

New fields added to hr.employee and hr.contract via models.Model — TIN, pension PIN, NHF number, pension administrator (PFA) — with @api.depends compute for taxable and pensionable bases

Statutory schedules and remittance summaries rendered as QWeb reports (PAYE schedule, pension schedule, NHF schedule) ready for FIRS/PenCom/FMBN submission

Per-employee and per-run payslips as branded QWeb PDF, showing gross, each statutory deduction, and net pay in NGN with correct rounding

Security enforced with ir.model.access.csv plus record rules so payroll officers see only their company's employees under Odoo multi-company

Automated actions for recurring payroll tasks — scheduled payslip email dispatch and monthly remittance-schedule generation

Accounting integration that posts payroll journals to your NGN chart of accounts, keeping salary, PAYE, pension and NHF liabilities cleanly separated

Configurable rule parameters (band thresholds, rates, contribution percentages) exposed as data records so Finance Act or PenCom rate changes are updated without code edits

XML-RPC / JSON-RPC compatible — payroll figures are standard Odoo records, so external HR portals or reporting tools can read and write them

Full parallel-run validation harness: we reproduce your most recent payroll inside Odoo and reconcile line-by-line before go-live

Built cleanly for Odoo 17, 18 and 19 on Community or Enterprise, with an upgrade path so you are not locked to one version

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu Odoo.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

Odoo core HR Payroll ships no Nigerian salary rules — no PAYE bands, no consolidated relief allowance, no pension or NHF logic. Teams end up running payroll in spreadsheets alongside Odoo, or paying for a generic apps.odoo.com module that doesn't match Finance Act treatment or FIRS/PenCom expectations.

Nigeria Payroll (PAYE, Pension, NHF) is a build-to-order Odoo localization that ECOSIRE designs, builds, installs and supports specifically for your company. This is not an instant download — after purchase our Odoo engineers scope your exact salary components, entities and reporting needs, then deliver a production-ready module for Odoo 17, 18 or 19 (Community or Enterprise) within a typical 2–4 week lead time.

The module extends hr.payroll with NGN salary structures and Nigeria-specific rules encoded as Odoo salary rules and Python compute logic: PAYE progressive tax across the statutory bands, the consolidated relief allowance, employee and employer pension contributions, National Housing Fund (NHF) deductions, and handling for NSITF and ITF employer levies. Every rule is a real Odoo object — new fields on hr.employee/hr.contract via models.Model, computed amounts using @api.depends, access controlled through ir.model.access.csv and record rules, and results rendered on QWeb payslip reports and statutory schedules.

Because it is built for your books, the numbers reconcile with your chart of accounts, your pay frequency and your reporting entities. We ground the build in your real data, validate a full parallel run against your last payroll, and hand over documentation, training and a support window. Where you need automation — monthly remittance schedules, payslip email dispatch, or pushing net-pay journals — we wire Odoo automated actions and (optionally) XML-RPC/JSON-RPC endpoints so the payroll talks to the rest of your stack.

O que você ganha

Production-ready Odoo module (custom addon) with a proper __manifest__.py, models, views, security and QWeb reports, delivered to a Git repository you own

Configured NGN salary structures, salary rules and rule parameters mapped to your actual pay components and entities

Security configuration: ir.model.access.csv and record rules scoped to your payroll roles and multi-company setup

QWeb payslip and statutory schedule templates (PAYE, pension, NHF) branded for your organization

A documented, reconciled parallel-run report comparing Odoo output against your last live payroll run

Administrator and payroll-officer documentation plus a recorded/live training session for your HR team

Deployment and installation on your Odoo instance (self-hosted, Odoo.sh, or ECOSIRE-managed hosting), with go-live support

A post-delivery support window for fixes, questions and statutory rate adjustments, with terms agreed at scoping

Para quem é isso

Payroll Officer at a Nigerian SME

Runs monthly payroll and needs PAYE, pension and NHF to compute correctly inside Odoo instead of maintaining a fragile parallel spreadsheet. Wants payslips, deductions and net pay to reconcile every month without manual recalculation.

HR Manager scaling headcount

Manages growing staff across roles and allowances and needs standardized NGN salary structures, clean role-based access, and reliable statutory schedules to hand to Finance and to regulators on time.

Finance Controller / Accountant

Owns the numbers and cares that PAYE, pension, NHF, NSITF and ITF post as distinct liabilities to the NGN chart of accounts, reconcile to bank remittances, and survive audit — with clear reporting rather than opaque black-box calculations.

Como Nigeria Payroll (PAYE, Pension, NHF) se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Nigeria PAYE, pension & NHF rules out of the box	Built to Nigerian statutory rules and your pay components	Only if you build every rule yourself	Sometimes, but often generic or outdated
Fits your exact salary structures & entities	Scoped and configured to your real data	Yes, but you carry all the design work	Rarely — you adapt to the module's assumptions
Parallel-run reconciliation before go-live	Included — line-by-line against your last payroll	Only if you plan and run it yourself	Not provided; you validate alone
Statutory QWeb reports (PAYE / pension / NHF)	Delivered as branded QWeb templates	Must be designed and built from scratch	Partial or generic layouts
Updates for rate / Finance Act changes	Editable rule parameters + support window	You maintain it yourself indefinitely	Depends on vendor's release cadence
Code ownership & Odoo 17/18/19 support	You own the addon; built for your version & edition	You own it; version support is on you	Vendor-licensed; upgrade timing not yours
Named support & training for your team	Docs, live training and a post-go-live window	Internal knowledge only	Ticket-based, generic support

Perguntas frequentes sobre Nigeria Payroll (PAYE, Pension, NHF)

How long until the module is delivered, and is this an instant download?

This is a build-to-order module, not an instant apps.odoo.com download. After purchase, ECOSIRE scopes your salary components, entities and reporting needs, then builds, tests and installs the module. Typical lead time is 2–4 weeks depending on complexity, the number of pay components and how many entities are in scope. You get a confirmed timeline at the end of the scoping call.

What support and updates are included after delivery?

Delivery includes a post-go-live support window (agreed during scoping) covering bug fixes, configuration questions and help during your first live payroll runs. Because statutory rates and thresholds (PAYE bands, pension and NHF rates, Finance Act changes) evolve, rule parameters are exposed as data records so most rate changes are configuration, not code. We also offer ongoing support and update retainers for teams that want ECOSIRE to maintain the module across Odoo version upgrades.

Which Odoo versions and editions does this support?

We build for Odoo 17, 18 and 19, on both Community and Enterprise. We confirm your exact version and edition at scoping and deliver a module aligned to it, with a documented upgrade path so a future Odoo version bump does not strand your payroll.

Will the calculations actually match my current payroll?

Yes — that is the point of the parallel run. Before go-live we reproduce your most recent payroll inside Odoo and reconcile it line-by-line against your existing figures. We resolve any differences (rounding, relief treatment, allowance handling) with you until the numbers agree, so you switch over with confidence rather than hope.

How is PAYE, pension and NHF actually computed inside Odoo?

Each is a real Odoo salary rule with Python compute logic. PAYE applies the consolidated relief allowance and then the progressive tax bands to derive tax; pension is calculated on the pensionable base as separate employee and employer lines; NHF is computed on basic salary. Employer levies like NSITF and ITF are modelled as employer-side costs that do not reduce net pay. Band thresholds and rates live in editable rule parameters so they can be updated as regulations change.

Can it handle multiple companies, allowances and integrate with accounting?

Yes. Salary structures are built from reusable NGN salary categories so different roles and allowance packages assemble cleanly, record rules enforce per-company visibility under Odoo multi-company, and payroll journals post to your NGN chart of accounts with PAYE, pension and NHF kept as distinct liabilities. Since everything is standard Odoo data, it is also reachable via XML-RPC/JSON-RPC for external tools.

Do we own the code, and can we customize it later?

You own the module — it is delivered to a Git repository under your control as a standard Odoo addon with a documented __manifest__.py, models, views and security files. Your own developers, or ECOSIRE, can extend it later. Nothing is obfuscated or license-locked to us.