odoo-l10n-compliance
Country-specific Odoo localization: tax configuration, e-invoicing (CFDI, FatturaPA, SAF-T), fiscal reporting, and country chart of accounts setup.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- odoo-l10n-compliance
- risk
- unknown
- source
- community
- description
- Country-specific Odoo localization: tax configuration, e-invoicing (CFDI, FatturaPA, SAF-T), fiscal reporting, and country chart of accounts setup.
03 SKILL.md 正文
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
- Activate: Mention
@odoo-l10n-complianceand specify your country and Odoo version. - Install: Get the exact localization module and configuration steps.
- Configure: Receive tax code setup, fiscal position rules, and reporting guidance.
Country Localization Modules
| Country | Module | Key Features |
|---|---|---|
| 🇺🇸 USA | l10n_us |
GAAP CoA, Payroll (ADP bridge), 1099 reporting |
| 🇲🇽 Mexico | l10n_mx_edi |
CFDI 4.0 e-invoicing, SAT integration, IEPS tax |
| 🇪🇸 Spain | l10n_es |
SII real-time VAT, Modelo 303/390, AEAT |
| 🇮🇹 Italy | l10n_it_edi |
FatturaPA XML, SDI submission, reverse charge |
| 🇵🇱 Poland | l10n_pl |
SAF-T JPK_FA, VAT-7 return |
| 🇧🇷 Brazil | l10n_br |
NF-e, NFS-e, SPED, ICMS/PIS/COFINS |
| 🇩🇪 Germany | l10n_de |
SKR03/SKR04 CoA, DATEV export, UStVA |
| 🇨🇴 Colombia | l10n_co_edi |
DIAN e-invoicing, UBL 2.1 |
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.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.