Odoo Accounting is the financial backbone of any Odoo implementation. It integrates directly with Sales (customer invoices), Purchase (vendor bills), Inventory (stock valuation), Expenses and Payroll. This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise. One part concerns Italian companies (e-invoicing through the SdI, the Italian invoice exchange system) and is marked as such.
When an implementation is healthy
A finance implementation works when four conditions hold:
- every financial flow starts from source documents (orders, receipts, expense reports) and not from manual journal entries;
- bank reconciliation is done at least weekly and the suspense account is clear;
- tax compliance is automated (e-invoicing, VAT return, fiscal positions);
- financial reports come straight from Odoo, with no reworking in Excel.
The financial side of Odoo comprises two distinct modules: Accounting (full double entry, multi-currency, tax reports) and Invoicing (simplified receivables and payables, without full accounting). Most SMEs need the full Accounting module.
Module basics for people working in accounting
Every Odoo record can be reached from the menu and navigated with breadcrumbs. The views used most are these.
| View | Use in accounting |
|---|---|
| List | Review open invoices, vendor bills, journal entries |
| Form | Open a single invoice, bill or journal entry |
| Pivot | Revenue by month, by journal, by analytic account |
| Graph | Receivables ageing, cash flow trends |
| Kanban | Invoice stages (draft, posted, paid) |
The search bar of every list accepts free text (customer name, invoice number, amount), predefined filters ("overdue", "this month", "draft", "not reconciled"), groupings (by customer, journal, salesperson, due date) and favourites, which are filter and grouping combinations saved as a personal or shared view. Finance teams use them to build daily dashboards, for example "open invoices due this week, by customer".
Every invoice, vendor bill and journal entry has a chatter: the internal note, visible only to internal users, with @name to notify a colleague; the message, which sends an email to the customer or vendor and logs the thread on the document; the activity, a follow-up action (call, document upload, reminder) tied to the document, which appears in the activity bell and in the calendar. An example: on an overdue invoice the accountant notes "@sales_manager The customer confirmed payment by Friday, I will check again Monday" and schedules a "Phone Call" activity for Monday.
Export from any list (Action, Export) produces CSV or XLSX, and sets of columns can be saved as favourites. Import is available for contacts, products, journal entries (opening balances) and the chart of accounts through the Upload button. A finance department that leans too heavily on exporting to Excel for reporting sends a warning sign, as seen below.
Five principles
1. Source document first. Every entry should come from a business event and not from manual accounting. The sales cycle runs sales order, invoice, payment, bank statement with reconciliation. The purchase cycle runs purchase order, receipt, vendor bill, payment, bank statement. For expenses: expense report, expense, journal entry, payment. If manual entries exceed five per cent of the total posted, there is a process problem upstream: missing source documents, unconfirmed orders, bypassed workflows.
2. One source of truth for reporting. Financial reports must come straight from Odoo. When they are assembled in Excel from exports, the implementation has failed its main promise. This calls for a chart of accounts structured to produce readable profit and loss and balance sheet natively, analytic accounts set up for management reporting (cost centres, projects) and lock dates that stop closed periods being changed by mistake.
3. Taxes automatic at line level. Taxes are determined automatically, by product, fiscal position and customer and vendor configuration, and are not chosen by hand on every line. Manual choice is the cause of most compliance errors. An example: customer in France (EU), the "Intra-EU B2B" fiscal position applies by itself, 22 per cent VAT is remapped to 0 per cent with nature code N3.2 and the correct e-invoice XML is generated.
4. Reconciliation is not a month-end task. It is a daily or weekly operational job. Treating it as a closing step creates a blind spot on the cash position and delays finding differences.
5. Lock dates protect integrity. There are two: the tax return lock prevents changes to entries before the last filed VAT return, and the fiscal year lock prevents changes before the year-end closing. They have to be set right after each period is closed. Without them, an entry backdated by mistake silently corrupts financial statements that have already been signed.
Chart of accounts and journals
Chart of accounts. The principle is that accounts must map directly onto report lines. Too many accounts produce unreadable reports, too few take away the detail management needs. In the Italian chart the key types are: receivable (1501 Trade receivables, used automatically on invoices), payable (2501 Trade payables, used automatically on vendor bills), bank (1001, one account for every physical bank account), income (31xx Sales revenue, one per revenue stream and not per product) and expenses (6xxx, one per cost category and not per supplier). The account type drives behaviour: setting the wrong type (for example a bank account as "current assets" instead of "bank and cash") breaks reconciliation.
Journals. One journal is used for each physical flow, with a name that allows traceability: VEN for sales (customer invoices and credit notes), ACQ for purchases (vendor bills and credit notes), BNK1 and BNK2 one for each bank account (Banca Intesa, Banca Unicredit), CSH for the cash box, MISC for manual entries and adjustments. A single bank journal is never used for several bank accounts: reconciliation becomes impossible.
Fiscal positions and taxes
Fiscal positions remap taxes according to the fiscal status of customer and vendor. In the Italian case: domestic B2B customer (default) with VAT at 22, 10 and 4 per cent; intra-EU B2B at 0 per cent with nature code N2.1 (not taxable); extra-EU export at 0 per cent with nature code N3.1; public administration with split payment; reverse charge with document type TD16; minimum regime at 0 per cent with VAT excluded.
They apply by themselves based on the customer's country and the presence of a VAT number. They are never to be set by hand on every invoice: manual application is a configuration failure.
In Odoo 20 duplicate taxes are not needed for tax-included or tax-excluded prices: leave Included in Price on Default and use the Tax Excl. / Tax Incl. toggle on the single quotation, order or invoice. A tax explicitly set as included or excluded ignores the toggle.
Italian companies: e-invoicing and modules
To make the SdI work, the company needs a VAT number, tax code, tax regime (for example RF01 ordinary) and a full legal address. Each B2B customer needs a VAT number and the recipient code (seven characters, the SdI routing key) or a certified email (PEC) address.
Odoo generates these document types automatically: TD01 standard invoice, TD04 credit note, TD05 debit note, TD07 simplified invoice (up to 400 euros, with an incomplete address), TD16 internal reverse charge (vendor bill with a reverse-charge tax), TD17 purchase of services from abroad (EU and non-EU), TD18 purchase of goods from the EU (intra-EU acquisitions), TD19 purchase of goods from a VAT warehouse.
The modules of the Italian localisation are: l10n_it (base chart of accounts, taxes, localisation), l10n_it_edi (SdI e-invoicing, mandatory for all B2B and B2G), l10n_it_edi_doi (declaration of intent for regular exporters), l10n_it_edi_withholding (withholding tax on professional fees), l10n_it_riba (batch collections with Ri.Ba., the Italian bank receipts) and l10n_it_reports (Italian statutory reports).
The flows: customer invoice, vendor bill, reconciliation
Customer invoice. Draft, then Post: the invoice is legally registered. Then sending to the SdI: sent, delivered, accepted by the SdI, or rejected (to be corrected and resent). Then Register Payment, in payment, bank reconciliation, paid. The constraints: a posted invoice cannot be changed, it is reversed with a credit note; sequential numbering with no gaps is a legal requirement in Italy; the SdI transmission status has to be monitored, because a "rejected" invoice remains legally unregistered.
Vendor bill. The PDF is received, digitised or uploaded, the draft is created, three-way matching with order and receipt is done, it is posted, paid (payment registration, SEPA batch or Ri.Ba.) and reconciled with the bank. In three-way matching the price and quantity tolerances are configurable and differences block posting until resolved.
Bank reconciliation. The bank statement is imported (CSV, OFX, CAMT.053 or bank synchronisation by API) and each line is matched with an outstanding payment (issued from a vendor bill), an outstanding receipt (registered from a customer invoice) or a new transaction (bank charges and interest, created automatically by the reconciliation model). When all lines are matched the statement is reconciled and the suspense account is at zero. Reconciliation models match recurring patterns by themselves: bank fees go to the "Bank charges" account, interest income to "Interest income", a customer reference in the statement is matched to the open invoice.
What changes with Odoo 20
Odoo 20 Enterprise is the baseline. Before classifying a need as development (Studio or custom), it is worth testing it against these features.
- Tax excluded or included toggle on quotations, sales orders, purchase orders and invoices: for that document only it changes the behaviour of taxes with Included in Price on Default. A single tax serves both tax-inclusive and net-price situations, with no duplicates.
- Inter-company clearing. When one company of the database collects the payment of an invoice issued by another company of the same database, Odoo reconciles the open invoice in the issuing company and creates the balancing intercompany entries (Intercompany Clearing settings in Accounting).
- SEPA Direct Debit mandates. They are created automatically as drafts for sales orders paid online with the SDD method; the mandate is validated when the initial payment (wire transfer) is received and matched with the bank transaction.
- Bulk self-bills. They are sent from the list of the self-billing journal (reached from the Accounting dashboard), with the sending method following each vendor's preferences.
- Assets. Fixed assets and Non-current assets are separate account types; depreciation parameters (model, computation, prorata date) are set directly on the asset form after choosing a model; models and assets can be imported; an optional Recovery Account records the reversal of excess depreciation when statutory depreciation catches up or on disposal.
- Inventory valuation (anglo-saxon). Odoo 20 no longer uses stock input and output accounts: any balance on Stock Interim accounts must be cleared (a server action and an Accounting, Review, Inventory Valuation step per company). The step is mandatory when upgrading from Odoo 19 to 20 and automatic from 18. It has to be flagged in every migration plan.
- Purchase order matching from the vendor bill: auto-complete from the order, or PO Matching line by line.
- Bank Reconciliation Summary report: a point-in-time trail of reconciled and unreconciled items as of a chosen end date.
- Analytics. Plan applicability rules, percentage distribution per plan and bulk editing of analytic distribution on several entries.
- Invoicing. A consolidated invoice for several sales orders of the same customer; default terms and conditions as a note or PDF attachment; the account Currency restricts journal items and flags the account for unrealised exchange differences. In custom reports, expressions have a Date Scope field.
- International e-invoicing. Peppol registration has been reworked (identifier, access-point migration, sending only or sending and receiving, receiving as vendor bills or as documents, demo or production); Denmark has been added (NemHandel and Peppol, registered digital bookkeeping system); the French e-invoicing pilot phase has been withdrawn. Localisations documented or updated include Mexico, India, the United States, Kenya, Vietnam, Brazil, Georgia, Denmark and, new, China and South Korea.
For development requests the guidance is this: management reporting in Excel, manual reconciliation, manual coding of taxes and accounts, duplicated taxes for tax-inclusive and tax-exclusive prices, manual intercompany settlements and invoice and payment chasing are first tested against Odoo 20 standard and configuration, before recommending customisation.
The rationalisations you hear
| In the company they say | What it really is |
|---|---|
| "We do bank reconciliation at month end" | The cash position is unknown for weeks. Differences surface when they can no longer be corrected. |
| "We export to Excel for the real reports" | The structure of the chart of accounts or analytics is wrong. Fix the cause, not the symptom. |
| "We set the tax by hand on every invoice" | Tax becomes a human decision. One slip is a wrong VAT return and a compliance risk. |
| "We use a single bank journal for all accounts" | Reconciliation is physically impossible when statement lines cannot be matched to a single account. |
| "We do not use lock dates, we trust the team" | An entry backdated on a signed balance sheet cannot be found without lock dates. |
| "We make a journal entry to fix things" | A manual entry correcting another means a source document was wrong. Fix the source, not the ledger. |
| "We do not need analytic accounts yet" | Management reporting will live in Excel for ever. Analytics set up at go-live cost nothing extra. |
| "SdI errors are few, we handle them by hand" | Every rejected invoice is legally unregistered. Manual handling at scale builds a compliance backlog. |
Warning signs
- Manual entries above five per cent of the total posted.
- Bank reconciliation less often than weekly.
- Suspense account with unreconciled items older than thirty days.
- No lock date set on any closed period.
- Invoices at the SdI in "rejected" or "error" state with no resolution.
- Tax chosen by hand on invoice lines instead of by fiscal position.
- A single bank journal for several physical bank accounts.
- Chart of accounts with more than 500 accounts: too granular, unreadable reports.
- Financial reports (profit and loss, balance sheet) assembled in Excel from Odoo exports.
- Vendor bills entered with no reference to a purchase order, so no three-way matching.
- Withholding tax calculated outside Odoo.
- Recipient code missing on B2B customers: the SdI does not know where to route invoices.
- Fiscal positions not configured: taxes on international invoices set by hand.
How to verify a configuration
After configuring or assessing accounting, verification goes through these checks:
- the chart of accounts produces a readable profit and loss and balance sheet without reworking in Excel;
- there is one journal for each physical bank account and the short codes match the account names;
- fiscal positions are configured for all relevant categories of customers and vendors and applied automatically;
- the Italian company has VAT number, tax code, tax regime and full address;
- all B2B customers have a recipient code or PEC and the SdI transmission queue has no errors;
- 0 per cent taxes have the nature code set (required for the e-invoice XML);
- bank reconciliation is done at least weekly and the suspense account balance is explained;
- lock dates are set for all closed periods (tax return and fiscal year);
- manual entries are below five per cent of the total;
- analytic plans are configured for at least one management dimension (department, project or product line);
- reports (profit and loss, balance sheet, aged receivable) come straight from Odoo;
- three-way matching is active between purchase orders, receipts and vendor bills.
Standard, configuration, integration or custom development
To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: full double-entry accounting with multi-currency and multi-company consolidation; inter-company clearing when one company collects another's invoice; automatic customer invoicing from sales orders or deliveries; vendor bill processing with three-way matching; bank reconciliation with CSV, OFX, CAMT import and automatic matching rules; Italian e-invoicing (SdI) with l10n_it_edi, B2B and public administration; VAT returns, Intrastat and Italian statutory reports natively; analytic accounting for cost centres, projects and product lines; SEPA batch payments and Ri.Ba. collections; SEPA Direct Debit mandates created from online payments.
Six questions help classify each gap before asking for development:
- How long does the monthly close take? What are the steps, who is involved, what blocks it? A close longer than five working days is usually a process and configuration problem, not a missing feature.
- How are customer invoices generated today? By hand from scratch, from sales orders, by export and import? Who triggers them? Invoices created by hand outside ERP data are a configuration gap, solved with Odoo's invoicing policy.
- How is the bank reconciled? Daily, weekly or monthly? With what tool? Are there unreconciled items older than thirty days? Manual monthly reconciliation is a process and configuration gap. Non-standard bank formats are an integration.
- How are taxes handled on invoices? By hand line by line or automatically? Who checks compliance? Taxes chosen by hand are a configuration gap, solved by fiscal positions. SdI rejections point to configuration gaps.
- Which financial reports does management really use? How are they produced (Odoo, Excel, BI tool), how often? Reworking Odoo exports in Excel is a configuration gap (wrong chart of accounts or missing analytics), not a development need.
- How is vendor bill approval handled? Who approves, at what amount threshold, through which channel? Approvals by email or chat are solved with the Purchase approval rules and the bill approval policy.
The typical classification of the commonest cases is this:
| Common gap | Typical path | Signals that push towards custom |
|---|---|---|
| Invoices created by hand | Configuration (invoicing policy) | Multi-step billing logic tied to project milestones |
| Monthly bank reconciliation | Process change and configuration | Non-standard bank file format not supported by Odoo's importers |
| Manual tax selection | Configuration (fiscal positions) | Tax rules that change dynamically by product, customer and date combinations |
| Profit and loss assembled in Excel | Configuration (restructure the chart of accounts) | Management requires consolidated multi-entity reporting not native to Odoo |
| No lock dates on closed periods | Process change | None |
| Duplicate taxes for tax-inclusive and tax-exclusive prices | Configuration (tax excluded or included toggle) | None |
| Manual intercompany settlement of payments collected by another group company | Configuration (inter-company clearing) | Group structure spread across separate databases |
| SdI e-invoicing not yet active | Configuration | Custom nature codes or non-standard document types |
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-financeGuide to designing and assessing the Odoo 20 Enterprise Accounting module: source document first, chart of accounts, journals, fiscal positions and automatic taxes, bank reconciliation, lock dates, Italian e-invoicing (SdI). It includes warning signs, the rationalisations heard in companies and the questions that decide between standard, configuration, integration and custom development. Use it when setting up or checking accounting in Odoo, with or without interviews with finance managers and controllers.