Odoo L10n Compliance

Odoo Localization & Compliance (l10n)

Overview

Odoo provides localization modules (l10n_*) for 80+ countries that configure the correct chart of accounts, tax types, and fiscal reporting. This skill helps you install and configure the right localization, set up country-specific e-invoicing (Mexico CFDI, Italy FatturaPA, Poland SAF-T), and ensure fiscal compliance.

When to Use This Skill

• Setting up Odoo for a company in a specific country (Mexico, Italy, Spain, US, etc.).
• Configuring country-required e-invoicing (electronic invoice submission to tax authorities).
• Setting up VAT/GST/IVA tax rules with correct fiscal positions.
• Generating required fiscal reports (VAT return, SAF-T, DIAN report).

How It Works

1. Activate: Mention @odoo-l10n-compliance and specify your country and Odoo version.
2. Install: Get the exact localization module and configuration steps.
3. Configure: Receive tax code setup, fiscal position rules, and reporting guidance.

Country Localization Modules

Examples

Example 1: Configure Mexico CFDI 4.0

Step 1: Install module
  Apps → Search "Mexico" → Install "Mexico - Accounting"
  Also install: "Mexico - Electronic Invoicing" (l10n_mx_edi)

Step 2: Configure Company
  Settings → Company → [Your Company]
  Country: Mexico
  RFC: Your RFC number (tax ID)
  Company Type: Moral Person or Physical Person

Step 3: Upload SAT Certificates
  Accounting → Configuration → Certificates → New
  CSD Certificate (.cer file from SAT)
  Private Key (.key file from SAT)
  Password: Your FIEL password

Step 4: Issue a CFDI Invoice
  Create invoice → Confirm → CFDI XML generated automatically
  Sent to SAT → Receive UUID (folio fiscal)
  PDF includes QR code + UUID for buyer verification

Example 2: EU Intra-Community VAT Setup (Any EU Country)

Menu: Accounting → Configuration → Taxes → New

Tax Name: EU Intra-Community Sales (0%)
Tax Type: Sales
Tax Scope: Services or Goods
Tax Computation: Fixed
Amount: 0%
Tax Group: Intra-Community

Label on Invoice: "Intra-Community Supply - VAT Exempt per Art. 138 VAT Directive"

Fiscal Position (created separately):
  Name: EU B2B Intra-Community
  Auto-detect: Country Group = Europe + VAT Required = YES
  Tax Mapping: Standard VAT Rate → 0% Intra-Community

Example 3: Install and Validate a Localization

# Install via CLI (if module not in Apps)
./odoo-bin -d mydb --stop-after-init -i l10n_mx_edi

# Verify in Odoo:
# Apps → Installed → Search "l10n_mx" → Should show as Installed

Best Practices

• ✅ Do: Install the localization module before creating any accounting entries — it sets up the correct accounts.
• ✅ Do: Use Fiscal Positions to automate tax switching for international customers (B2B vs B2C, domestic vs export).
• ✅ Do: Test e-invoicing in the SAT/tax authority test environment before going live.
• ❌ Don't: Manually create a chart of accounts if a localization module exists for your country.
• ❌ Don't: Mix localization tax accounts with custom accounts — it breaks fiscal reports.

AGI Framework Integration

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

Memory-First Protocol

Cache compliance check results to avoid re-running expensive AWS API calls. Retrieve prior audit findings to track remediation progress across sessions.

# Check for prior security context before starting
python3 execution/memory_manager.py auto --query "prior security audit results for Odoo L10N Compliance"

Storing Results

After completing work, store security decisions for future sessions:

python3 execution/memory_manager.py store \
  --content "Audit findings: 3 critical IAM misconfigurations found and remediated" \
  --type technical --project <project> \
  --tags odoo-l10n-compliance security

Multi-Agent Collaboration

Share security findings with other agents so they avoid introducing vulnerabilities in their code changes.

python3 execution/cross_agent_context.py store \
  --agent "<your-agent>" \
  --action "Completed security audit — 3 critical findings fixed, compliance score 94%" \
  --project <project>

Signed Audit Trail

All security findings are cryptographically signed with the agent's Ed25519 identity, providing tamper-proof audit logs for compliance reporting.

Semantic Cache for Compliance

Cache compliance check results (semantic_cache.py) to avoid redundant AWS API calls. Cache hit at similarity >0.92 returns prior results instantly.