Chart of Accounts Best Practices:
Audit-Ready Financials in Odoo 19

Account Structure, Groups, Tags, and Numbering Conventions in Odoo 19

A well-structured CoA has three layers: the account number (for sorting and identification), the account group (for sub-totals on reports), and account tags (for cross-cutting analysis like tax reporting). Odoo 19 supports all three natively.

Numbering Convention: The 4-Digit Standard

The most widely used convention for mid-market companies is a 4-digit numbering scheme with the first digit indicating the account class:

Configuring Account Groups for Report Sub-Totals

Account groups in Odoo 19 create automatic sub-totals on financial reports. Without groups, your balance sheet is a flat list of 100+ accounts with no structure. With groups, it shows hierarchical totals: Total Current Assets, Total Fixed Assets, Total Assets.

<odoo>
  <data noupdate="1">
    <!-- Top-level group: Assets -->
    <record id="group_assets" model="account.group">
      <field name="name">Assets</field>
      <field name="code_prefix_start">1000</field>
      <field name="code_prefix_end">1999</field>
    </record>

    <!-- Sub-group: Current Assets -->
    <record id="group_current_assets" model="account.group">
      <field name="name">Current Assets</field>
      <field name="code_prefix_start">1000</field>
      <field name="code_prefix_end">1499</field>
      <field name="parent_id" ref="group_assets"/>
    </record>

    <!-- Sub-group: Fixed Assets -->
    <record id="group_fixed_assets" model="account.group">
      <field name="name">Fixed Assets</field>
      <field name="code_prefix_start">1500</field>
      <field name="code_prefix_end">1999</field>
      <field name="parent_id" ref="group_assets"/>
    </record>
  </data>
</odoo>

Using Account Tags for Cross-Cutting Analysis

Account tags serve a different purpose than groups. While groups define hierarchy for financial statements, tags define categories that cut across the hierarchy. Common uses include:

• Tax reporting tags — Map accounts to specific lines on your tax return (e.g., Box 1a on a VAT return)
• Operating vs. non-operating — Tag expenses as operating or non-operating for EBITDA calculations
• Cash flow classification — Tag accounts as operating, investing, or financing for the cash flow statement
• Departmental allocation — When analytic accounts are too granular, tags provide a simpler grouping mechanism

# Via the Odoo shell or a data file:
account = env['account.account'].search([('code', '=', '6200')])
operating_tag = env['account.account.tag'].search(
    [('name', '=', 'Operating Expense')]
)
account.tag_ids = [(4, operating_tag.id)]

# To create a new tag:
env['account.account.tag'].create({
    'name': 'EBITDA - Included',
    'applicability': 'accounts',
    'color': 3,
})

Reconcilable Accounts: When and Why

The reconcile flag on an account determines whether Odoo allows you to match individual debit and credit entries against each other. This is critical for:

• Accounts Receivable / Payable — Always reconcilable. Odoo matches invoices to payments automatically.
• Bank accounts — Always reconcilable. Bank statement lines are matched to journal entries during bank reconciliation.
• Inter-company accounts — Should be reconcilable. Lets you match inter-company invoices and payments to ensure balanced positions.
• Suspense / clearing accounts — Should be reconcilable. The balance should always net to zero; reconciliation proves it.
• Expense accounts — Almost never reconcilable. There's nothing to match—expenses are one-sided entries.

Lock Dates, Access Controls, and Audit Trail Best Practices in Odoo 19

A clean CoA is useless if anyone can post back-dated entries, modify locked periods, or delete journal items. Odoo 19 provides three layers of protection: fiscal lock dates, access rights, and the immutable audit trail.

Fiscal Lock Dates

Odoo 19 supports two separate lock dates that serve different purposes:

# Set lock dates via Odoo shell or automation
company = env['res.company'].browse(1)

# Lock January 2026 for non-advisers
company.period_lock_date = '2026-01-31'

# Hard lock after audit approval
company.fiscalyear_lock_date = '2025-12-31'

# Tax lock date (prevents modifying tax entries)
company.tax_lock_date = '2025-12-31'

Month-End Lock Date Workflow

The recommended workflow for lock dates follows your close calendar:

• Day 1–5 of new month: Complete month-end adjustments (accruals, depreciation, reclassifications)
• Day 5: Set the "Non-Adviser Lock Date" to the last day of the closed month
• Day 5–10: CFO reviews and approves any final adjustments
• Day 10: Set the "All Users Lock Date" to the last day of the closed month
• After annual audit: Set the fiscal year lock date to the last day of the audited year

Access Controls for Accounting Data

Odoo 19's accounting module has three security groups that control who can do what:

<!-- Odoo's built-in accounting groups -->

<!-- 1. Invoicing (account.group_account_invoice)
   Can create/validate invoices and payments
   CANNOT access journal entries or the CoA -->

<!-- 2. Accountant (account.group_account_user)
   Full access to journal entries, bank reconciliation
   CANNOT modify lock dates or the CoA structure -->

<!-- 3. Adviser (account.group_account_manager)
   Full access including CoA modification,
   lock dates, and fiscal year operations -->

<!-- Best practice: assign roles based on responsibility -->
<!-- Sales team      → Invoicing only                    -->
<!-- Staff accountant → Accountant                       -->
<!-- Controller/CFO  → Adviser                           -->

The Immutable Audit Trail

Odoo 19 enforces an immutable audit trail by default for posted journal entries. Once a journal entry is posted, it cannot be deleted—only reversed. This is a legal requirement in many jurisdictions (France, Germany, Brazil) and a best practice everywhere else. Key rules:

• Posted entries cannot be deleted — The "Delete" button disappears once an entry is posted. To correct an error, you must create a reversal entry.
• Sequence numbers are gapless — Odoo generates sequential entry numbers with no gaps. A missing number triggers an audit flag.
• All modifications are logged — The chatter on every journal entry records who created, posted, or reversed it, and when.
• Draft entries can be deleted — Only drafts can be removed. Set a policy to post entries daily so drafts don't linger as an uncontrolled audit risk.