Odoo Updates · Odoo 20
Odoo 20 for finance teams: what changes in accounting, payroll and reporting
Odoo 20 changes how bills get coded, how bank entries get posted, what "Paid" means, and how US sales tax and payroll run. Here is each change a controller or CFO should know: who it affects, what to check before the upgrade, and which edition it needs.
Key takeaways
- Every entry on a bank account must now start from a bank transaction, so manual bank entries need a new routine.
- Payment statuses shift: In Process becomes Paid, and Paid becomes Reconciled. Filters, exports and training need updating.
- Parent accounts replace account groups, account codes become optional, and depreciation models replace asset models.
- US companies get Avalara Included, a redesigned sales tax report, New York City and Yonkers payroll taxes and eleven more states.
- Payroll drops work entries, so run a full pay period on an upgraded copy before you trust it.
Our Odoo 20 overview gave accounting one paragraph. This is the long version, for the controller or CFO who signs off on the upgrade, drawn from Odoo's release notes, the 20.0 documentation and, where the documentation lags, the 20.0 source code.
Two cautions. On September 30, 2026, several 20.0 documentation pages still showed version 19 screens, such as account groups and payroll work entries, so train your team on an upgraded test database. Most of this is Enterprise: Odoo's editions page lists full Accounting, with bank reconciliation, consolidation and reports, and Payroll as Enterprise-only, while Invoicing and Expenses are in both editions. The table near the end gives the edition for each change. The new Accounting AI agent runs on paid credits like every AI feature in 20; our AI agents deep dive covers it.
Payables: bill line prediction and purchase order matching
Bill line prediction is what AP clerks will notice first. On a new or imported bill, Odoo proposes the product, account, tax, analytic distribution and vehicle for each line from the label and your bill history, without overwriting values entered by hand. Purchase order matching was reworked too: Auto-Complete checks for matching bill lines before adding new ones, a summary shows what matched, price and quantity differences raise a warning, and a bill can be unmatched.
Prediction learns from your history, so if last year's bills went to a catch-all account, it will suggest the same. Clean up the coding on recent bills from your top vendors first, and agree who clears a price or quantity warning. Both features are part of full Accounting. The payment wizard now also deducts payments already recorded but not yet cleared from the amount due, which should cut double payments. Paying bills from Odoo through a payment initiation provider is new as well, but the notes name no banks or countries, so US teams should keep NACHA files and check printing in the plan.
Receivables: customer invoice reminders
Invoice reminders can now be sent by hand from the invoice list or an invoice's Send button, and automatic reminders are switched on in the Accounting settings. It matters most where small balances pile up, as in clinic groups: our clinic billing client cut the time from visit to invoice from 14 days to 2 on Odoo and recovered $380K in its first year, and Odoo for healthcare billing explains that setup.
Reconcile the bank before switching automatic reminders on: Odoo's follow-up documentation warns that unreconciled transactions trigger reminders for invoices customers have already paid. Decide how reminders sit beside your current follow-up levels, and test the templates on a copy so no customer gets two emails. Treat reminders as Enterprise: follow-ups are not in Odoo's Community source.
Chart of accounts: parent accounts and optional codes
Account groups are gone. You now structure the chart with parent accounts, one account sitting under another rather than grouped by code prefix, and account codes become optional. The 20.0 source confirms it: the account group model is removed and accounts have a parent field. Allow Reconciliation is renamed Payment Reconciliation, and manual reconciliation now works on any account.
This affects any report, export or BI tool that reads groups or looks accounts up by code. List those before the upgrade, then compare the trial balance by section against 19 on a test upgrade, to the cent. Keep codes if auditors or integrations rely on them. Optional codes do help newcomers: many QuickBooks files run without account numbers, and NetSuite subaccounts map naturally onto parent accounts, as our QuickBooks to Odoo and NetSuite to Odoo guides discuss. This change is in the shared accounting module, so Community databases get it too.
Fixed assets: depreciation models
Asset models become depreciation models that hold only the calculation, while asset settings and automation move onto the asset accounts. Depreciation can use rates and decimal values, and in the US localization each preconfigured model gets its own depreciation and expense accounts. After a test upgrade, compare the depreciation boards of a few assets per old model with 19, review the settings now on your asset accounts, and map the new US accounts to your chart. Assets are part of full Accounting.
Bank entries must come from bank transactions
This change alters daily habits most. Every journal entry that touches a bank account must now originate from a bank transaction, which the notes say prevents "manual journal mismatches". A bookkeeper who used to post a bank fee, interest, a loan repayment or a transfer by hand straight to the bank account now starts from the transaction, imported or entered manually, and reconciles it, with reconciliation models handling the repeats. The bank journal becomes a mirror of the bank, which is good for control and audit and removes a common reason bank balances never tie out.
Before the upgrade, pull a year of manual entries on your bank and cash accounts: that is your retraining list and your backlog of reconciliation models. Confirm every account has a feed or import, and agree how opening balances and historic adjustments will be handled, because the notes do not cover migration. Alongside come a bank reconciliation summary report at a period end date, a button to rerun automatic reconciliation, easier splitting of one transaction across accounts, and wire transfer payments confirmed from bank transactions. Bank reconciliation is part of full Accounting.
Renamed payment statuses
On payment records, In Process becomes Paid and Paid becomes Reconciled, and the Mark as Reconciled button moves into the action menu. The stored values changed as well as the labels: a payment's state is paid or reconciled in 20.0, where 19.0 used in_process and paid, so "paid" means something different in each version.
Before the upgrade, search filters, spreadsheets, exports, automations, custom modules and integrations for the payment state. Then brief the team: the invoice's own status keeps In Payment and Paid, so an invoice showing In Payment has a payment marked Paid, and an invoice marked Paid has a payment marked Reconciled. This change is in the shared accounting module, so Community databases see it too.
Reconciliation, tax, multi-currency and consolidation
Taxes must now belong to the invoice's fiscal position: a default tax outside it is removed, even when there is no replacement. If you use fiscal positions for exempt customers or out-of-state sales, test invoices for each one, because a tax that quietly disappears is worse than an error. New matching rules set a payment tolerance and order for automatic reconciliation.
In multi-currency, exchange differences collapse into one expandable line per invoice, rates show when you register a foreign-currency payment, and a Cumulative Translation Adjustment line on the balance sheet, trial balance and general ledger absorbs differences between historical and closing rates. For consolidation, multi-ledger setups now list the journals to include instead of those to exclude. That flips an existing setup's logic, so rebuild the consolidated statements on a test upgrade and compare. With perpetual valuation, accruals can be posted from the inventory valuation closing report; our inventory and manufacturing deep dive covers the stock side.
US localization: sales tax and payroll
Avalara Included and the new sales tax report
Odoo's Avalara documentation describes Avalara Included, a second way to connect AvaTax for US and Canadian companies. It is paid in in-app credits, one per invoice or credit note posted with an AvaTax fiscal position, Odoo gives first-level support, and it is capped at 5,000 transactions a year; above that you need Avalara Direct, the contract route. Filing and remittance are add-ons under both. Each company needs its own account, and activation must be done on the production database, since a test database without a valid Enterprise contract returns an error. The release notes add automatic Avalara tax parameters for state-specific rules and a redesigned US Sales Tax Report with jurisdiction breakdowns, state summaries and better handling of exemptions.
Before switching, count last year's posted invoices and credit notes per company, check exemption certificates and fiscal positions, and tie the new report to a return already filed.
New York City, Yonkers and eleven more states
US payroll adds New York City and Yonkers local taxes, plus Georgia, Iowa, Kansas, Kentucky, Michigan, Mississippi, Missouri, New Jersey, South Carolina, Tennessee and Utah, with state, county and city rules. The list grew after launch, from five states in our September 27 copy of the notes to eleven on September 30, so check the current notes. The qualified overtime deduction under the "One Big Beautiful Bill" is marked available from 19.0. Per the US payroll documentation, the state in the employee's work address decides which rules apply, so check addresses, then run a pay period in parallel with your current provider and compare gross, each tax, net and employer cost. Payroll is Enterprise-only.
Payroll: a warnings dashboard, and work entries removed
The Payroll dashboard is rebuilt around warnings for setup and day-to-day control; the US documentation's example is an employee without a trusted bank account, which raises a warning and blocks the pay run. Pay runs get a step-by-step flow and a test print, payslips can go out on confirmation, on payment or by hand, and you can simulate pay from a target net amount. Contract dates that affect existing payslips can no longer be edited until those payslips are reverted.
The structural change is the removal of work entries and of the Planning and Payroll integration, with work entry types and time off types merged; in the 20.0 source, Time Off now extends the work entry type model, labeled Time Type. The notes do not say how hours from Attendances or Planning now reach an hourly payslip, and the 20.0 payroll pages still describe work entries, so this is the highest-risk item if you pay hourly staff. Resolve open conflicts in 19, list every report, export and module that reads work entries or time off types, and run a full pay period on an upgraded copy against 19.
Expenses: draft bills, limits and payroll
The Employee Expenses menu in Accounting is gone: approved expenses now create draft bills in the default expense journal, for accountants to post with other vendor receipts. Managers can cap claims at a limit per job position, and expense products can carry a salary rule so reimbursements land on the right payslip line. Decide who posts those bills, and map taxable and non-taxable reimbursements to the right rules. Expenses is in both editions; reimbursement in payslips is Enterprise.
Change, who it affects, what to do before upgrading
| Change | Who it affects | What to do before upgrading | Edition |
|---|---|---|---|
| Bill line prediction | AP, controller | Clean coding on recent bills | Enterprise |
| Purchase order matching | AP, purchasing | Agree who clears price and quantity warnings | Enterprise |
| Invoice reminders | Collections | Reconcile the bank; test templates | Enterprise |
| Parent accounts, optional codes | Reporting, integrations | List what reads groups or codes; compare the trial balance | Both |
| Depreciation models | Asset register | Compare sample depreciation boards | Enterprise |
| Bank transaction rule | Bookkeepers, auditors | List a year of manual bank entries | Enterprise |
| Payment statuses | AP, AR, integrations | Search filters and code for payment state; retrain | Both |
| Taxes limited to fiscal positions | Tax, billing | Test invoices per fiscal position | Both |
| Consolidation journals | Group controller | Rebuild and compare consolidated statements | Enterprise |
| Avalara Included, sales tax report | US tax | Count yearly transactions; tie to a filed return | Enterprise, plus credits |
| NYC, Yonkers, eleven states | US payroll | Parallel pay run | Enterprise |
| Work entries removed | Payroll, hourly staff | Full pay period on an upgraded copy | Enterprise |
| Expenses as draft bills | AP, payroll | Assign posting; map salary rules | Both |
When to move your finance team to 20
For most databases, land on 19 first and move to 20 once the first rounds of fixes are in, unless a version 20 feature is critical to you, such as Avalara Included, a newly covered payroll state or the bank control. Odoo Online databases on a 19.x online version are upgraded on Odoo's schedule, so request an upgraded test database early. Cut over after a month-end close, never across a year-end.
Our Odoo upgrade and migration engagements run these checks on an upgraded copy, at a fixed price agreed before kickoff, with 30 days of hypercare. Starting fresh? Choose the version during Odoo implementation scoping. The developer changes deep dive covers the code side.
Frequently asked questions
Is Odoo 20 accounting available in Community?
Partly. Invoicing is in both editions, but Odoo's editions page lists full Accounting, including bank reconciliation, consolidation and reports, and Payroll as Enterprise-only. The renamed payment statuses and parent accounts sit in the shared accounting module, so Community databases get those two changes as well.
What is Avalara Included in Odoo 20?
It is a second way to connect AvaTax for companies in the United States and Canada, paid with in-app purchase credits instead of a contract. Odoo's documentation says one credit is used per posted invoice or credit note with an AvaTax fiscal position, and businesses above 5,000 transactions a year need Avalara Direct.
Which US payroll taxes and states did Odoo 20 add?
Local taxes for New York City and Yonkers, plus Georgia, Iowa, Kansas, Kentucky, Michigan, Mississippi, Missouri, New Jersey, South Carolina, Tennessee and Utah, according to the release notes as read on September 30, 2026. The list has grown since launch, so check the current notes.
Will our finance reports and exports still work after the upgrade?
Not without testing. Payment statuses change their stored values, account groups become parent accounts and payroll work entries are removed, so filters, exports, spreadsheets and integrations built on them can break or quietly return different numbers. Run each one on an upgraded copy and compare it with 19.
Moving finance to Odoo 20?
Bring your chart, bank feeds and payroll setup, and in 30 minutes we will tell you what the upgrade touches.
Book a discovery callKeep going
Related services and articles
Plan your finance team's move to 20
Upgraded copy first, reports and payroll compared with 19, and a fixed price before kickoff.
Odoo upgrade and migration services$380K recovered in the first year
A four-branch clinic group cut the time from visit to invoice from 14 days to 2 on Odoo.
Healthcare billing case study Odoo UpdatesOdoo 20 is here: what's new and what it means for your business
What changed across accounting, inventory, manufacturing, POS, eCommerce and AI, the price changes, and when to move.
ImplementationMigrating from QuickBooks to Odoo: the complete 2026 guide
What transfers cleanly, what to clean first, and a four-phase method for a clean go-live.
Find out what Odoo 20 changes for your finance team
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751