Odoo Accounting Setup

Odoo Accounting Setup

Overview

This skill guides functional consultants and business owners through setting up Odoo Accounting correctly from scratch. It covers chart of accounts configuration, journal setup, tax rules, fiscal positions, payment terms, and the bank statement reconciliation workflow.

When to Use This Skill

• Setting up a new Odoo instance for a company for the first time.
• Configuring multi-currency or multi-company accounting.
• Troubleshooting tax calculation or fiscal position mapping errors.
• Creating payment terms for installment billing (e.g., Net 30, 50% upfront).

How It Works

1. Activate: Mention @odoo-accounting-setup and describe your accounting scenario.
2. Configure: Receive step-by-step Odoo menu navigation with exact field values.
3. Validate: Get a checklist to verify your setup is complete and correct.

Examples

Example 1: Create a Payment Term (Net 30 with 2% Early Pay Discount)

Menu: Accounting → Configuration → Payment Terms → New

Name: Net 30 / 2% Early Pay Discount
Company: [Your Company]

Lines:
  Line 1:
    - Due Type: Percent
    - Value: 100%
    - Due: 30 days (full balance due in 30 days)

Early Payment Discount (Odoo 16+):
  Discount %: 2
  Discount Days: 10
  Balance Sheet Accounts:
    - Gain: 4900 Early Payment Discounts Granted
    - Loss: 5900 Early Payment Discounts Received

Note (v16+): Use the built-in Early Payment Discount field instead of the old split-line workaround. Odoo now posts the discount automatically when the customer pays within the discount window and generates correct accounting entries.

Example 2: Fiscal Position for EU VAT (B2B Intra-Community)

Menu: Accounting → Configuration → Fiscal Positions → New

Name: EU Intra-Community B2B
Auto-detection: ON
  - Country Group: Europe
  - VAT Required: YES (customer must have EU VAT number)

Tax Mapping:
  Tax on Sales (21% VAT) → 0% Intra-Community VAT
  Tax on Purchases      → 0% Reverse Charge

Account Mapping:
  (Leave empty unless your localization requires account remapping)

Example 3: Reconciliation Model for Bank Fees

Menu: Accounting → Configuration → Reconciliation Models → New

Name: Bank Fee Auto-Match
Type: Write-off
Matching Order: 1

Conditions:
  - Label Contains: "BANK FEE" OR "SERVICE CHARGE"
  - Amount Type: Amount is lower than: $50.00

Action:
  - Account: 6200 Bank Charges
  - Tax: None
  - Analytic: Administrative

Best Practices

• ✅ Do: Install your country's localization module first (l10n_us, l10n_mx, etc.) before manually creating accounts — it sets up the correct chart of accounts.
• ✅ Do: Use Fiscal Positions to automate B2B vs B2C tax switching — never change taxes manually on individual invoices.
• ✅ Do: Lock accounting periods (Accounting → Actions → Lock Dates) after month-end closing to prevent retroactive edits.
• ✅ Do: Use the Early Payment Discount feature (v16+) instead of splitting payment term lines for discount modelling.
• ❌ Don't: Delete journal entries — always reverse them with a credit note or the built-in reversal function.
• ❌ Don't: Mix personal and business transactions in the same journal.
• ❌ Don't: Create manual journal entries to fix bank reconciliation mismatches — use the reconciliation model workflow instead.

Limitations

• Does not cover multi-currency revaluation or foreign exchange gain/loss accounting in depth.
• Country-specific e-invoicing (CFDI, FatturaPA, SAF-T) requires additional localization modules — use @odoo-l10n-compliance for those.
• Payroll accounting integration (salary journals, deduction accounts) is not covered here — use @odoo-hr-payroll-setup.
• Odoo Community Edition does not include the full lock dates feature; some controls are Enterprise-only.

AGI Framework Integration

Adapted for @techwavedev/agi-agent-kit Original source: antigravity-awesome-skills

Memory-First Protocol

Retrieve prior design decisions (color palettes, typography, spacing scales) to maintain visual consistency across sessions. Cache generated design tokens.

# Check for prior frontend/design context before starting
python3 execution/memory_manager.py auto --query "design system decisions and component patterns for Odoo Accounting Setup"

Storing Results

After completing work, store frontend/design decisions for future sessions:

python3 execution/memory_manager.py store \
  --content "Design system: adopted 8px grid, Inter font family, HSL color tokens with dark mode support" \
  --type decision --project <project> \
  --tags odoo-accounting-setup frontend

Multi-Agent Collaboration

Share design decisions with backend agents (API contract changes) and QA agents (visual regression baselines).

python3 execution/cross_agent_context.py store \
  --agent "<your-agent>" \
  --action "Implemented UI components — new design system with accessibility compliance (WCAG 2.1 AA)" \
  --project <project>

Design Memory Persistence

Store design system tokens and component decisions in Qdrant so any agent on any platform (Claude, Gemini, Cursor) can retrieve and apply consistent styling.