Odoo Accounting Consultant, Nigeria

Completing the fiscal setup when the package is thin

Odoo ships fiscal localizations that install a chart of accounts, taxes and sometimes report formats for a country. Coverage varies by country and version, so the first step for a Nigerian company is to install the package in a test database for the exact version you plan to run and list what it gives you. Do not assume a localization exists, or that it matches how your accountant reports, until you have seen it.

Where the package is missing or thin, I build the foundation with your accountant:

• Chart of accounts structured for your statutory statements and management reporting, with account groups that make the balance sheet readable without exporting it.
• Taxes and tax groups for standard, exempt and zero-rated VAT, and for withholding categories, each with the correct accounts for the tax and its base.
• Tax report lines, so the built-in tax report produces the totals your accountant transfers to the return, rather than a generic list.
• Fiscal positions that switch taxes automatically for exempt customers or foreign buyers, as your advisor defines them.

Each element is tested with a batch of real invoices and bills before go-live. Tax treatments are your advisor's decisions, and current rules should be checked with them because Nigerian tax administration has been changing. My role is to make Odoo record those decisions the same way every time.

Withholding on payments and receipts in Odoo

Withholding is where Nigerian Odoo setups most often fail quietly. On the payables side, your company deducts tax from certain supplier payments and remits it. On the receivables side, customers deduct tax from what they pay you and send evidence later. Odoo's standard tax engine is built around invoices, so withholding at payment time needs a deliberate approach.

The options depend on version and localization: dedicated withholding taxes applied on payments where available, a maintained module, or reconciliation models that split a payment into its settled and withheld parts. I choose with your accountant after testing, then design the full trail:

• Supplier side. The bill is settled in full, the deduction posts to a withholding payable account, and remittance to the tax authority clears it with the receipt attached.
• Customer side. A short payment is matched to the invoice with the withheld part posted to a withholding receivable account, not left as an open balance.
• Evidence matching. When the customer's credit evidence arrives, it is recorded against the receivable, and an aged report shows which evidence is still outstanding.
• Reporting. Balances on both accounts reconcile to supporting lists at each month end.

The Odoo consultant Nigeria page covers the wider platform decisions; this flow is where the accounting detail lives.

Intercompany between related Nigerian companies

Many Nigerian groups run more than one company: a manufacturing entity, a trading or distribution entity, perhaps a logistics or services company, sometimes with a related company abroad. Goods, services, staff costs and cash move between them, and at year end someone has to prove that every intercompany balance agrees on both sides.

A single Odoo database can run several legal entities side by side, keeping separate ledgers, taxes, currencies and journals for each. The design work is in how they interact:

• Intercompany rules that create the mirrored purchase document on the buying side whenever one entity bills a sister entity, so both sides record the same amount on the same date.
• Dedicated intercompany accounts per counterparty, kept separate from external receivables and payables.
• Recharges for shared staff, rent or services documented as a process: who raises them, on what basis and how often.
• Cash movements such as loans and funding recorded with matching entries in both companies.
• A monthly agreement check listing intercompany balances side by side, investigated before the close is signed.

Consolidation and eliminations remain with your accountant, whether in Odoo's reporting or outside it. The design simply makes their job mechanical rather than investigative. My multi-company ERP page discusses group structures more generally.

Community or Enterprise from the finance team's view

The Community versus Enterprise decision is usually argued on licensing cost and operational apps. Finance should have its own say, because the difference is significant for accounting. In Enterprise, the full Accounting app brings the reconciliation interface, financial reports, asset management, deferred revenue and expenses, budgets and customer follow-up tools. Community provides invoicing and core journals, with many of these accounting features supplied by third-party or community modules when needed.

From the finance view, the questions I work through with you are:

• Close effort. How many bank lines, payments and journals your team handles each month, and how much the reconciliation tools save.
• Reporting. Whether your accountant can produce the statements they need from Odoo, or will export everything.
• Fixed assets. Whether depreciation schedules live in Odoo or a separate register.
• Module ownership. Who maintains any community accounting modules through upgrades, and what happens if their author stops.
• Localization fit. Whether anything in the fiscal package or e-invoicing work depends on Enterprise.

Features move between editions over time, so I verify them in the version you plan to use. Subscription cost is a cost driver to weigh against maintenance risk, not a figure I quote. The global Odoo Accounting page covers the editions in general terms.

Bank imports, e-invoicing questions and the close

Odoo offers online bank synchronization in some editions and regions, but coverage for Nigerian banks should be checked rather than assumed. Statement imports in a standard file format are the dependable route. I agree a format per bank, then build reconciliation models for transfer charges, levies, recurring receipts and payment gateway settlements, so most lines are proposed automatically and the accountant reviews exceptions.

The federal tax authority is phasing in electronic invoicing; ask your tax advisor how and when it reaches your company. For Odoo, I ask your implementer or Odoo how invoices from your version and edition would be transmitted, who maintains that code, and how rejected or failed submissions appear in Accounting. Until a route has been demonstrated with your own documents, I keep invoice data clean so the eventual connector has something reliable to send.

The close then follows a fixed sequence: banks reconciled, withholding balances matched, intercompany agreed, foreign currency revalued under your accountant's method, tax report reviewed and lock dates set. Migration of opening balances follows my ERP data migration approach. Odoo Accounting is a weaker fit for a small service firm that only needs invoicing; there, lighter tools may serve. Broader context sits on my ERP consulting page for Nigeria and the Nigeria overview.