Electronic invoicing in Argentina with Odoo: AFIP, ARCA and monotributo

AFIP vs ARCA — what changed in 2026

The government dissolved AFIP in July 2024 and created ARCA  (Agencia de Recaudación y Control Aduanero) as its successor. Only the name changed — CUITs and fiscal keys stayed the same. What did change: tighter control over monotributistas invoicing VAT-registered companies, and bank integration to detect discrepancies in monthly CAEA.

What stays the same from Odoo's technical perspective:

• The wsaa  (authentication) and wsfe  (e-invoicing) webservices keep the same URLs and SOAP envelopes — only the branding in the documentation changed.
• The digital certificate is still managed from the fiscal key via the Administrador de Relaciones service.
• CAE (Electronic Authorization Code) and CAEA (Anticipated Electronic Authorization Code) keep their 14-digit formats.

What did change and forces you to revisit setup:

1. ARCA-Monotributo cross-check: if you issue a C invoice to a VAT-registered client and they claim it as credit, ARCA automatically flags the operation. If you exceed 30% of your monthly invoicing with a single client, it triggers a disguised-employment alert.
2. RG 5616/2024: new VAT withholding regime for B2B digital services. Applies if you invoice a foreign provider for hosting, SaaS, online advertising — the 21% withholding must be filed via Odoo as an internal debit note.
3. Cross-border TIN validation: E invoices (export) now require validating the buyer's TIN against fiscal records in the destination country. Without this, ARCA defers exporter VAT refunds for up to 90 days.

Comprobante types (A/B/C/E) and which one each client generates

The golden rule: the comprobante type depends on the receiver's VAT status, not the issuer's.

Odoo determines the type automatically if the partner has the L10n AR AFIP Responsibility Type field set correctly. The most common mistake: marking the client as Responsable Inscripto when they're actually Monotributista  — Odoo generates a type-A invoice, AFIP rejects it with code 10052.

Sub-types that matter

• Type-A invoice with "Operación sujeta a percepción" notation  — if you sell to a perception agent, you must itemize IIBB and VAT perceptions (RG 2408) as separate lines.
• Type-M invoice  — a variant of A for when the buyer's CUIT isn't yet validated. Issued with full VAT withholding. Almost nobody uses it because the operation is cumbersome, but it's valid.
• Electronic C receipt  — mandatory since 2023 for monotributistas who collect upfront, often forgotten.

Configuring l10n_ar in Odoo (CAE, CAEA, FACE)

The l10n_ar  (Argentina) module ships officially with Odoo 17+ and keeps compatibility with 16. The electronic connector is called l10n_ar_edi  (Electronic Data Interchange) and brings:

• WSAA + WSFE (traditional A/B/C invoice, CAE per document)
• WSFEXv1 (E invoice for export)
• WSFEv1 (legacy version, still supported)

What it does not bring officially:

• CAEA  (anticipated authorization, for high-volume invoicing in offline zones) — requires Adhoc's module ( l10n_ar_edi_caea ) or custom development.
• FACE  (SME Electronic Credit Invoice) — separate module, essential if your clients are large enterprises and you want your invoice to be tradable on capital markets.
• T comprobantes  (tourism) — niche, requires custom development.

#1. Company setup

In Settings → Companies → Your company:

• CUIT in the VAT field (format XX-XXXXXXXX-X), Odoo validates the check digit automatically.
• AFIP Responsibility Type: Responsable Inscripto, Monotributo, Exento, Consumidor Final.
• Province  — affects IIBB and Convenio Multilateral jurisdiction.
• AFIP activities  (CLAE) — a client can have several, one primary.

#2. Digital certificate

Generate the CSR (Certificate Signing Request) from Odoo (the Generate CSR button), upload it to AFIP/ARCA via the Administrador de Certificados Digitales service, download the signed.crt, and load it back into Odoo together with the private key. Validity: 2 years. Automatic reminder: set up a recurring activity 30 days before expiration.

#3. Electronic point of sale

Each point of sale is an independent numbering range. In Accounting → Configuration → Journals → AFIP POS, create one per comprobante × point-of-sale combination. Typical error: using one POS for both A and B; Odoo allows it but AFIP rejects because numbering must be separate per type.

Monotributo: the 5 most common traps

Monotributo is the simplified regime for freelancers and SMBs invoicing under a certain ceiling. In Odoo it looks simple — a partner with AFIP Responsibility = Monotributista issues type-C invoices, no VAT itemized. But the operational traps:

1. Forgotten quarterly recategorization  — ARCA automatically recategorizes every January and July based on the last 12 months. If your Odoo revenue doesn't match what ARCA sees, you get bumped up a tier and your fee jumps 30–60%. Fix: monthly report cross-checking Odoo against ARCA.
2. Exclusion from exceeding the cap  — if you cross the annual cap on a single large invoice, AFIP excludes you retroactively and you must pay VAT and Income Tax from the start of the month. Set an Odoo alert when you hit 90% of the cap.
3. Type-C invoice to a company with disguised dependency relationship  — the famous "off-the-books employment". ARCA cross-references: if you invoice more than 30% per month to the same CUIT for over 12 consecutive months, an investigation triggers.
4. Late monthly fee payment  — the fee is due on the 20th of each month. Late payment → automatic block on e-invoicing. Odoo doesn't warn you, AFIP simply returns error 1014 on the next CAE attempt.
5. Manual comprobantes that don't appear in Mis Comprobantes  — if you issue by hand for contingency (preprinted invoice), you must upload it in the Comprobantes en línea service within 24h. Forgetting is the #1 cause of discrepancies in recategorization.

Anonymous case: SMB that migrated from Tango to Odoo

Digital marketing services company, 18 employees, Buenos Aires. 2025 revenue: ARS 380M (~ USD 320K at average official exchange rate). 9 years on Tango Gestión, migration to Odoo 17 executed in Q3 2025. Three reasons to migrate:

• Tango doesn't integrate well with new digital banks (Mercado Pago, Ualá, Brubank). Bank reconciliation by hand = 2 days/month of an accountant.
• No native CRM. They sold with Excel spreadsheets + WhatsApp.
• The cost of Tango Punto de Venta + Tango Gestión + Tango Sueldos exceeded USD 280/month per user for 18 people.

What went right:

1. Partner migration (1,200 active clients) in 3 days with a Python script + Odoo API.
2. Argentine chart of accounts (RG 3293) mapped from Tango's without structural changes.
3. First 50 invoices in AFIP homologation in 5 days — zero rejections.

What went wrong:

1. VAT history was not migrated line by line (a conscious decision) — the accountant had to file the last DDJJ of the fiscal year with Tango and the first with Odoo, with no overlap. 3 extra days of work.
2. Invoice numbering  — the accountant assumed AFIP allows reusing points of sale across systems. It doesn't. Each migration requires decommissioning the point of sale in AFIP and creating a new one. The first batch of invoices in Odoo was rejected until fixed.
3. Professional-fee receipts from employees (8 monotributistas billing the SRL) weren't in Tango — they were generated by hand. When moved to Odoo, 4 monotributistas surfaced out of date with missed recategorizations. Total fine: ARS 380K (~ USD 320).

"Odoo's ROI broke even at 7 months, not the 12 we'd projected. What we didn't account for: the time recovered by the accountant and me — reconciliation went from 2 days/month to 2 hours. That's 22 days a year between the two of us."

Related resources:

• Argentina country page  — l10n, AFIP/ARCA, certified partners
• Monotributo recategorization: the calendar nobody explains
• Migration service from Tango / Bejerman / Quickbooks
• AFIP/ARCA 2026 checklist (18 points)

Frequently asked questions

The questions that come in every week from Argentine SMBs evaluating Odoo + AFIP/ARCA.