A successful Odoo Accounting setup gives the finance team a system it can explain and reconcile. Before go-live, the team should know where each opening balance came from, how documents move through the system, and who can review or change them.
This is a software-readiness checklist based on Odoo 19 documentation, checked on 10 November 2026. Your finance lead or accountant should approve accounting policies, account mapping and local requirements. Run the exercises in a test database before making changes to production.
Confirm the company and localization first
Record the legal entity, operating country, reporting currency and installed Odoo version. Check which localization modules support that entity’s requirements and identify any additional configuration, certificates or integrations that need validation.
Odoo’s fiscal-localization documentation explains that packages require configuration beyond installation. It also states that another package can only be selected before an entry has been posted. Resolve uncertainty before the first posting in a new production company; an existing database needs a separately reviewed change plan. A package appearing in the country list does not establish that your configured workflow meets every obligation.
Give finance ownership of account mapping
Ask the finance lead to review the proposed chart of accounts against the existing reporting structure. For each source account, document the proposed destination, purpose and reviewer. Investigate accounts with no clear match rather than choosing the closest-looking name.
Odoo’s Accounting implementation guide treats the chart of accounts as foundational data. Use the approved mapping to guide later preparation of customer and supplier records, opening documents and balances.
The implementation team can prepare the mapping and demonstrate its effects. Finance should decide whether the resulting classifications and reports represent the business correctly. Record unresolved decisions with an owner and a date, so they do not become invisible assumptions.
Review journals, bank records and periods
Prepare an inventory of bank accounts, cash handling and document flows. Odoo supports different journal types, including sales, purchase, bank and cash, and allows multiple journals of one type. Its journal documentation also explains that payment entries depend on outstanding-account configuration. Do not assume every payment registration has the same accounting effect in every setup.
Confirm the intended fiscal-year end and reporting calendar. Odoo documents fiscal-period settings in its year-end guide. Review these settings with finance in the test environment; this checklist does not prescribe year-end entries or changes to lock dates.
| Area | Decision to record | Evidence before release |
|---|---|---|
| Accounts | Who approves source-to-destination mapping? | Reviewed mapping with unresolved items closed |
| Journals and banks | Which record represents each document flow or bank account? | Sample transactions traced to the intended journal |
| Periods | Which reporting dates and cut-off apply? | Finance-approved calendar and test dates |
| Access | Who prepares, reviews, posts and changes setup? | Each role tested using its intended user account |
| Opening data | Who owns each source total? | Reconciled source and destination results |
Reconcile opening data at one cut-off
Agree a single cut-off and retain the source reports used for the migration. Prepare open customer invoices and credits, supplier bills and credits, bank information and the approved opening trial balance. Keep document references and counterparties traceable. The migration checklist covers the wider file-preparation process.
Finance should reconcile the customer and supplier detail to the corresponding control balances and confirm that the trial balance balances. Pay particular attention to double counting: importing individual open documents and their balances requires a coordinated opening-entry method. Have finance approve that method and compare the resulting totals after the trial import.
Check counts as well as amounts. Two errors can offset numerically, leaving a convincing total while the wrong customer owes the wrong amount. Inspect a sample by document, counterparty, currency and due date.
Follow documents through a complete test
Test the expected lifecycle from document preparation and review through posting, payment handling and reconciliation. Include corrections and partial payments. Odoo’s bank-reconciliation guide describes matching bank transactions with items related to invoices, bills and payments. Review the actual matches in your configured setup rather than assuming a suggested match is appropriate.
Fictional example: Cedar Office Supplies has two open customer invoices of 600 and 400 in the same currency at cut-off. Finance expects customer detail totalling 1,000 after migration. In a test, a subsequent receipt of 250 is allocated to the first invoice. The expected remaining customer total is 750, provided there are no other movements. The reviewer checks the individual invoice balances and transaction trail, not just the total. This illustrates a test condition, not a recommended accounting entry.
Agree the acceptance tests and release owner
- Opening data: reconcile approved totals and sampled documents to the source cut-off.
- Customer flow: trace a test invoice, partial receipt and remaining balance.
- Supplier flow: trace a test bill, payment handling and reconciliation.
- Correction: demonstrate the finance-approved correction process and inspect its history.
- Access: confirm intended users can perform their duties and cannot perform actions outside their approved roles.
Record expected and actual results, the reviewer and unresolved differences. Release only after finance accepts the results and a named owner is ready to handle issues. For help defining the software scope, explore Lava’s Odoo services or contact us with your current system, entities and main reconciliation concerns.