AFIP/ARCA and Odoo in Argentina: monotributo 2026 and electronic invoicing

What changed with AFIP/ARCA and why it matters in 2026

Argentina has spent three years rewriting its tax rules. AFIP became ARCA, electronic invoicing fell under RG 5616/2024, and the monotributo scale is reindexed every four months. If your Odoo still thinks it's talking to AFIP, you already have at least three problems — and one of them is costing you money right now.

On January 1, 2026, ARCA (the former AFIP) rolled out the new monotributo scale with a 14.3% indexation. The year's first recategorization runs January 20 through February 20. And Resolución General 5616/2024 tightened pre-CAE validation: ARCA itself now rejects your invoice before issuing the Electronic Authorization Code if your ERP picked the wrong invoice type (A/B/C/M/T) for the receiver's tax status.

Layer in 16-25% annual inflation, and any contract without native multi-currency support quietly loses 1.3% of margin per month. All of this converges between March and August 2026: either your Odoo is configured for it, or month-end close stretches to 15 business days and ARCA fines start landing at 50-300% of mismatched withholdings.

What follows is the operator's version — not the awareness piece. Concrete numbers, real dates, modules by name, documented error codes. For broader regulatory context, see our Argentina country page.

#1. AFIP no longer exists — but the endpoints do

On October 21, 2024, the Milei government signed Decree 953/2024, dissolving the Administración Federal de Ingresos Públicos (AFIP), the agency in place since 1997. In its place, the Agencia de Recaudación y Control Aduanero (ARCA) took over, with headcount cut by roughly 31% and a stated mandate of digital modernization.

Legally, AFIP is gone. Operationally:

• Old domains (afip.gob.ar) redirect to arca.gob.ar, but the web services kept their endpoints and SOAP signatures — full migration is scheduled through the end of 2026.
• Forms F.572, F.931, and F.961 changed their branding, not their fields or codes.
• The SIAp desktop app still works; new builds ship with the ARCA logo.
• X.509 certificates issued by AFIP remain valid through their expiration date.

For your business, back-end integrations using wsfev1, wsfexv1, and ws_sr_constancia_inscripcion keep working without code changes. What needs to change is anything customer-facing: invoice templates, PDF headers, the customer portal, every screen still reading "AFIP." Half of SMBs skip this, and six months later their clients ask: "why does your invoice still say AFIP?"

Monotributo 2026: the new scale that kicked in on January 1

The Resolución General published in December 2025 updated all monotributo parameters. The structure stayed the same — 8 categories A→H for services, plus I/J/K for goods. The ceilings and components changed. Before drilling into the operational details, here's the reference table for 2026 (rounded; exact figures live on the ARCA portal and the official calculator).

Two recategorization windows apply in 2026:

• First window: January 20 — February 20, 2026
• Second window: July 20 — August 20, 2026

If one of your monotributista suppliers jumps from category E to F between windows, their VAT and Income Tax withholdings shift — and your AP system has to catch it. Otherwise you over-withhold (cash flow gone) or under-withhold (fine plus compensatory interest). For a calculator view, see our monotributo 2026 calculator, and for the recategorization deep-dive, monotributo recategorization in Argentina.

#1. Monotributo Unificado CABA: the pilot

From January 2026, monotributo residents in CABA pay in a single transaction the national component (ARCA) plus provincial gross-receipts tax (AGIP CABA). The pilot launched in CABA only, but Buenos Aires and Córdoba provinces have already announced rollouts for Q3 2026.

Out of the box, Odoo's l10n_ar does not handle this — the module doesn't distinguish unified from split-payment monotributo. Customization: 12-20 hours of development, done once.

#2. Who falls out and must register

If you cross the H cap (ARS 41.7M for services, ARS 82M for goods), registering as a responsable inscripto becomes mandatory. ARCA cross-checks against income-tax prepayments automatically and recategorizes ex officio when it sees a mismatch — with retroactive fines. Have that conversation with your accountant before January 20, not after.

RG 5616/2024: the pre-CAE check that rejects your invoice

Resolución General 5616/2024, signed on December 18, 2024 and in force throughout 2026, introduced three meaningful changes:

1. Expanded mandatory fields for Factura E (export) — added the DUS reference, transport mode, and validation of the receiver's tax ID against the OECD CRS registry.
2. Pre-CAE validation on the ARCA side — the system now checks whether the invoice type (A/B/C/M/T) matches the receiver's VAT status before issuing the code. If your Odoo sends a Factura A to A client who moved to monotributo, the CAE comes back rejected with error 10093 ("Receiver inconsistent with invoice type").
3. Purchases Reporting Regime — for responsables inscriptos with annual turnover above ARS 200M: near-real-time monthly transaction reporting from July 2026.

If your SMB sits below ARS 200M, point 3 doesn't apply yet. Points 1 and 2 hit everyone without exception. For a deeper walk-through of invoice types and CAE flow, see the guide to electronic invoicing in Argentina with Odoo.

Configuring Odoo for ARCA: modules, certificates, multi-currency

In Odoo 17 and 18, the Argentine localization is a family of l10n_ar* modules — about 12 official ones plus OCA extensions. The minimum base stack for an SMB that invoices, withholds, and reports:

OCA adds specific extensions: l10n_ar_edi_export (Factura E), l10n_ar_iibb_arba (Buenos Aires IIBB), l10n_ar_monotributo_validator, and a handful of others actively maintained. Without the OCA stack, reaching middle-market compliance gets expensive: either pay for Enterprise Studio to script around it, or write the modules yourself.

#1. Connecting to ARCA web services

ARCA inherited the AFIP endpoints for backward compatibility. Configure them in Odoo under Settings → Accounting → Argentina → AFIP/ARCA Web Services:

1. X.509 certificate — generated at arca.gob.ar/IG_PaginaPrincipal (Digital Certificate Administration).
2. CUIT + company name — declared on ARCA when the certificate is created.
3. Enabled services — activated on ARCA via delegation:
   • wsfev1 — Electronic Invoice v1 (A/B/C/M)
   • wsfexv1 — Factura E (export)
   • wsbfev1 — Fiscal bonds
   • wscdc — Inbound invoice verification
   • ws_sr_constancia_inscripcion — CUIT and monotributo category verification

Odoo testing still hits wswhomo.afip.gov.ar (homologation) — the domain remains on AFIP for now, with ARCA migration planned for Q4 2026.

#2. Multi-currency: the danger zone

This is where 70% of SMBs misconfigure and bleed margin. Argentina runs five operative currencies/rates in parallel:

• ARS — Argentine peso, local operations.
• USD official — for statutory reporting (BCRA Communication A 7340).
• USD MEP — the real rate for most export operations via MAE.
• USD CCL — contado con liquidación, used for capital movements.
• UVA — purchasing-power unit, used in indexed contracts.

Odoo supports multi-currency, but defaults to one rate per day. For Argentina:

1. Enable currency_rate_live with a custom connector to BCRA Communication A 3500 for the official USD rate.
2. Add a separate connector for MEP/CCL (via the Ámbito Financiero API or Rava).
3. Configure a fiscal position per currency — that's what decides which rate converts the tax base at invoice issuance.

Without this, a Factura E export goes out at the official rate (say, 1,050 ARS/USD), but you collect at MEP (1,380 ARS/USD) — losing 24% of margin per transaction. A year of that, and you owe 30-50% of annual revenue in cash you don't have.

#3. Multi-jurisdiction IIBB

Argentina has 24 provinces plus CABA, each with its own gross-receipts tax (IIBB) and its own withholding and perception rates. If you sell in three jurisdictions, that's three monthly filings.

In Odoo, l10n_ar_account_withholding supports the Convenio Multilateral simplified regime. For the general regime, configuration is manual:

• Fiscal position per province (minimum: CABA, Buenos Aires, Córdoba, Santa Fe, Mendoza).
• Tax groups for withholding and perception (tax_iibb_caba_2026, tax_iibb_bsas_2026, etc).
• On the partner record, set primary_jurisdiction and convenio_multilateral_coef.
• At sale time, Odoo picks the correct withholding via a jurisdiction × activity × operation-type matrix.

Get this wrong and one of two things happens: you over-pay IIBB across every jurisdiction (cash flow gone), or you under-pay and get a fine plus 1.2% monthly compensatory interest.

#4. Automated monotributo supplier validation

The most common SMB-Odoo bug: a monotributista supplier recategorizes, but Odoo still has them logged as "Category E, VAT perception 0%." On the next purchase, you either skip the withholding or apply the wrong rate.

The fix — a cron job that calls ws_sr_constancia_inscripcion every two weeks for all active partners flagged "Monotributista" and updates l10n_ar_afip_responsibility_type_id plus the category. Four to six hours of one-time development, and the problem disappears. If you'd rather not write it yourself, see Odoo implementation.

5 typical mistakes when rolling out Odoo in Argentina

Across the 60 LATAM projects we have audited, the following five show up in nearly every misconfigured Argentine Odoo. Each one has a preventive fix.

#1. Mixing up invoice types A vs B vs C

The most expensive mistake. The logic:

• Factura A — between responsables inscriptos (VAT broken out).
• Factura B — from RI to final consumer, monotributista, or exempt (VAT included, not separated).
• Factura C — issued by a monotributista or a VAT-exempt RI.
• Factura M — for new responsables inscriptos under a conditional regime.
• Factura T — tourist recipient (tax refund).

If you are responsable inscripto and issue a Factura A to A monotributista, ARCA rejects the CAE with error 10093. Each rejection stalls the transaction for 30-120 minutes (resubmission via wsfev1 after the fix). Inside an automated e-commerce flow, checkout sits halted.

Prevention: automate invoice type selection in Odoo via the partner's fiscal position plus a pre-issue call to ws_sr_constancia_inscripcion. The standard l10n_ar_edi handles this — but only if the partner record is filled in correctly.

#2. Not tracking monotributo recategorizations

If your Odoo caches the partner's monotributo category, after 4-8 months the local data drifts from ARCA. Result:

• AP under-withholds VAT → 50% fine on the missed amount plus interest.
• AR over-withholds on sales → cash flow gone (refund requested via DDJJ, 3-6 months).

Prevention: cron plus ws_sr_constancia_inscripcion (see above).

#3. ARS-only contracts with no indexation clause

If you have a long-running ARS contract with no UVA or CPI clause, 16-25% annual inflation eats roughly 1.3% of margin per month. On a 100M ARS yearly contract, that's 16M lost outright. Not an ARCA fine — just the reality of the peso.

Prevention: wire the indexation clause to the sales order via a custom field plus an automation that recalculates the balance against UVA every month. Implementation: 16-24 hours.

#4. Ignoring IIBB Convenio Multilateral

If you sell in 3 or more jurisdictions but file IIBB only in one (Simplified regime when General applies), ARBA, AGIP, and Córdoba Rentas cross-check through ARCA with a 6-18 month lag. Fine: 100-300% of the missed amount plus interest.

Prevention: determine the correct regime (Simplified up to 7.2M ARS, General above) and set Odoo for multi-jurisdiction withholding.

#5. One X.509 certificate across multiple systems

Many SMBs share a single production AFIP/ARCA certificate across Odoo, a legacy Tango install, and a separate web invoicer. When two systems lose sync on the punto-de-venta sequence number, ARCA rejects the CAE with error 10016 ("Invoice already authorized").

Prevention: one punto de venta, one system. Mid-migration, activate separate puntos de venta for Tango and Odoo via ARCA delegation, then deprecate the old one.

Anonymous case: 280-headcount SMB, Buenos Aires + Rosario

Anonymized. Segment: processing and distribution. Annualized revenue around USD 8M, 280 employees, 4 locations (HQ Buenos Aires, Rosario plant, two warehouses).

Before: Calipso for AR localization, separate legacy AFIP-web invoicer, Excel for multi-jurisdiction IIBB, external accountant for month-end close. CAE rejection rate: 11% (1 out of 9 invoices resubmitted), month-end close: 12 business days, IIBB filings done by hand. EUR contracts with the EU had no indexation to ARS — inflation was eating margin.

What we executed:

1. Audit of the existing Odoo install (a pilot had been abandoned two years prior). Cost: USD 3,200 fixed, 2 weeks.
2. Migration Calipso → Odoo 17 Enterprise with l10n_ar, l10n_ar_edi, l10n_ar_account_withholding, l10n_ar_reports, plus OCA l10n_ar_iibb_arba_consolidated.
3. Custom build: monotributo supplier cron + multi-currency with two rates (official + MEP) + IIBB config across 4 jurisdictions (CABA, Buenos Aires, Santa Fe, Córdoba).
4. 14 months of historical data migration + a wave-based go-live (admin → plant → warehouse → finance).

Measured at 9 months post go-live:

• CAE rejections: 11% → 0.6% (the 0.6% are real data errors, not system errors).
• Month-end close: 12 days → 3 days.
• IIBB filings: from 4 manual Excel files to a 1-day pre-filled flow out of Odoo.
• Multi-currency margin erosion: roughly 22% on export operations dropped below 2%.
• License cost: SAP B1 quote (rejected alternative) at USD 16,400/year vs Odoo Enterprise at USD 4,100/year plus hosting.
• Project investment: USD 48,000 year one, USD 22,000 maintenance year two.

"The biggest shift wasn't the license cost — it was no longer improvising the close every month."

This SMB is the typical middle-tier ICP. Smaller companies (under 50 people) pay less. Larger ones (above 500) pay more. The pattern holds. If you want to talk through a similar setup, start with an Odoo audit.

Monotributo 2026 checklist — free download

We packaged a 28-page PDF with the full ARCA compliance map for 2026: all 8 monotributo categories with exact ceilings and components, a 44-point pre-recategorization checklist for AP and AR, an Excel template for mass-validating monotributo suppliers, the ARCA web-services endpoint map with SOAP envelope examples, and the 12 most common CAE failures with their error codes.

Grab the monotributo 2026 checklist (PDF, 28 pages). Leave your email and it arrives in under 5 minutes.

FAQ