Odoo fiscal localization for your operation in Brazil.
We don't depend on Avalara. We don't charge per issued document. We have co-maintained OCA l10n-brazil since 2012, with +60 modules covering NF-e, NFC-e, CT-e, MDF-e, NFS-e, SPED, ECD, ECF, eSocial and Reinf.
When SEFAZ publishes a technical note, the fix lands on GitHub in days - not on a vendor's closed roadmap.
What Brazilian fiscal localization is
The set of modules that adapts Odoo to every Brazilian tax and fiscal obligation - document issuance, tax computation, SPED bookkeeping, eSocial, bank integration and more.
Electronic Fiscal Documents
NF-e (model 55), NFC-e (65), CT-e (57), MDF-e (58), NFS-e across hundreds of municipalities, BP-e, SAT-CF-e. Direct issuance to SEFAZ/city hall using your own A1 certificate.
Full tax engine
ICMS, ICMS-ST, DIFAL, FCP, IPI, PIS, COFINS, ISS, withholdings (IRRF, INSS, ISS, PIS/COFINS) computed by CFOP, CST/CSOSN, NCM, CEST and tax regime. No external gateway dependency.
SPED + ECD + ECF + DCTFWeb
EFD ICMS/IPI (layout 20/2026), EFD Contribuições (PIS/COFINS), ECD (digital accounting), ECF (fiscal bookkeeping), bases for DCTFWeb. KMEE maintains +20,000 lines of EFD PIS/COFINS in the OCA, running in production.
eSocial + Reinf
S-1000/1010/1020 (registries), S-1200 (compensation), S-2200/2206/2230/2299 (worker events). KMEE-authored module, validated through years of production use at a public-sector client, now migrated to Odoo 16+ on OCA.
Banks and payment methods
CNAB 240/400 across +6 banks, hybrid boleto with Pix QR Code, Pix Automático, DDA, direct API integration with 10 Brazilian banks. No per-document fees.
ICP-Brasil digital certificate
A1 certificate (PFX) management with encryption via the `l10n_br_fiscal_certificate` module. Optional external vault (HashiCorp, AWS, Azure, GCP). Audit trail for every call.
OCA l10n-brazil vs Odoo SA Enterprise
Odoo SA's official localization (via Avalara) covers the bare minimum. OCA l10n-brazil covers the full fiscal ecosystem - with no per-document fees.
| Feature | Odoo + OCA l10n-brazil (KMEE) | Odoo SA Enterprise |
|---|---|---|
| NF-e model 55 | Yes, native | via Avalara (per-document fee) |
| NFC-e model 65 (retail POS) | Yes, native | via Avalara |
| CT-e (transportation) | Yes, native | No, not covered |
| MDF-e (manifest) | Yes, native | No, not covered |
| NFS-e (hundreds of cities) | Yes, native | via Avalara (limited) |
| EFD ICMS/IPI | Yes, native | No |
| EFD Contribuições (PIS/COFINS) | Yes, native | No |
| ECD | Yes, native | No |
| ECF | Yes, native | No |
| Full eSocial | Yes, native | No |
| EFD-Reinf | Yes, native | No |
| DCTFWeb | Yes, native | No |
| CNAB / Pix / boleto | Yes, native | via paid gateway |
| Recipient acknowledgment (DF-e) | Yes, native | No |
| Cost per issued document | R$ 0 | Avalara charges per NF-e/NFS-e |
| Access to fiscal source code | Yes, AGPL/LGPL | No, closed |
Avalara/AvaTax charges per issued document (NF-e/NFS-e/NFC-e). OCA l10n-brazil issues directly to SEFAZ/city hall using your own A1 certificate - zero cost per transaction.
How KMEE shows up on OCA l10n-brazil
We don't just consume OCA - we are active co-maintainers. We invest engineering effort in large PRs that unlock fiscal compliance for the entire Brazilian ecosystem.
- EFD PIS/COFINS - module in production in the OCA, +20,000 lines:
l10n_br_sped_efd_pis_cofinsmodule. - Payroll + eSocial - KMEE-authored module, validated through years of production use at a client, migrated from Odoo 8.0 to Odoo 16+ and donated in full to the OCA.
- Bank integration - 10 banks via direct API, hybrid boleto, Pix Automático, DDA. See the dedicated page.
- PR review - KMEE engineers actively review code from the OCA community, keeping the technical bar of l10n-brazil high.
Who this is for (and who it isn't)
Honesty is worth more than the wrong client.
Green light
Makes sense if your company:
- Brazilian company with +50 NF-e/month or multiple fiscal documents (CT-e, MDF-e, NFC-e)
- Multiple state registrations (IE) or multi-company setup
- Tax team feeling pain with SPED, ECD, EFD or eSocial
- Migrating away from TOTVS, SAP B1, Sankhya or Senior due to cost or lock-in
- Foreign company opening a Brazilian subsidiary
- Distributor, manufacturer, carrier or e-commerce with volume
Yellow light
May not be ideal if your company:
- MEI or Simples Nacional company with up to 30 NF-e/month - Omie/ContaAzul may be enough
- No IT team and no appetite for a customized Odoo SLA
Frequently asked questions
The most common questions we hear during the fiscal diagnosis.
What is Brazilian fiscal localization in Odoo?
It is the set of modules that adapts Odoo to Brazil's tax and fiscal obligations: issuing NF-e/NFC-e/CT-e/MDF-e/NFS-e, computing ICMS/IPI/PIS/COFINS/ISS, withholdings, SPED bookkeeping (EFD ICMS/IPI, EFD Contribuições, ECD, ECF), eSocial and Reinf, and CNAB/Pix bank integration. These modules are maintained by the OCA (Odoo Community Association) community in the l10n-brazil repository.
Is OCA l10n-brazil the same as the official Odoo SA localization?
No. Odoo SA ships a minimal Brazilian localization in the Enterprise edition that only covers NF-e, NFC-e and NFS-e via Avalara/AvaTax - you pay per issued document. It does not cover CT-e, MDF-e, EFD, ECD, ECF, eSocial or Reinf. OCA l10n-brazil is the real, complete localization, maintained by the open-source community with KMEE among the lead maintainers, open under AGPL/LGPL, with no per-transaction fees.
Which Odoo version is the localization stable on today?
As of May 2026, the stable, production-ready version is Odoo 16 + OCA l10n-brazil 16.0 (62 modules covering the full fiscal ecosystem). Odoo 14 is end-of-life - we don't recommend it for new deployments. Versions 17 and 18 still have gaps in the Brazilian account, sale and purchase modules.
Do I need to buy Odoo Enterprise to use OCA l10n-brazil?
No. OCA l10n-brazil works on both Odoo Community (free) and Enterprise. Brazilian companies served by KMEE use both models, depending on their need for Enterprise-only features (such as Studio or IoT Box).
How much does the implementation cost?
There is no per-user or per-document license. You pay for implementation (scope defined after diagnosis), ongoing monthly support, and infrastructure (cloud or self-hosted). Pix/boleto fees are whatever your bank charges - we don't take a cut of the transaction.
How do you contribute to OCA?
KMEE is one of the main maintainers of l10n-brazil since 2012. We invest community engineering effort in EFD PIS/COFINS (+20,000 lines in production), payroll + eSocial (KMEE-authored module, migrated to Odoo 16+) and ongoing PR review across the ecosystem. You can follow our contributions on GitHub at OCA/l10n-brazil.
Will it work with Brazil's 2026 Tax Reform?
OCA maintains IBS, CBS and IS in the open fiscal codebase, tracking the regulation as it evolves. Because the code is open, adjustments to SEFAZ/Receita technical notes land on GitHub in days, not on a closed vendor roadmap. KMEE guides every client through the transition; the detail for your scenario is best covered in a conversation.
Can I migrate from TOTVS/SAP/Omie to Odoo+OCA and keep my fiscal history?
Yes. KMEE has a migration methodology that imports master data (CNPJ, IE, NCM, CFOP), accounting balances, inventory movement history and issued NF-e XMLs. SPED filings from prior periods stay preserved for tax inspection.
Free fiscal diagnosis
In 30 minutes we map your scenario (NF-e volume, tax regime, relevant SPED modules, current ERP) and walk out with a realistic migration or implementation plan.
Request your diagnosis
Tell us a bit about your fiscal scenario (regime, volume, current ERP). We respond within one business day.
No spam, no list selling. LGPD-compliant. Privacy Policy.