توطين Odoo الأرجنتين 2026: إعداد ARCA وIVA وIIBB

Argentina restructured its tax administration in 2025, dissolving AFIP (Administracion Federal de Ingresos Publicos) and establishing ARCA (Agencia de Recaudacion y Control Aduanero) as the primary tax authority effective late 2024. Despite the renaming, the underlying tax framework — IVA, Ganancias, Bienes Personales, and provincial Ingresos Brutos (IIBB) — remains intact, and the electronic invoicing system originally implemented by AFIP continues operation through ARCA. Argentina's WSFE/WSFEX/WSMTXCA web services remain the integration backbone, and Odoo's l10n_ar localization is one of Latin America's most mature implementations.

Key Takeaways

• ARCA (formerly AFIP) administers IVA (21%), Ganancias (corporate 35%), and electronic invoicing
• Mandatory electronic invoicing since 2015; covers all VAT-registered taxpayers (Responsables Inscriptos)
• Odoo l10n_ar provides robust ARCA web service integration for invoice authorization (CAE)
• Provincial Ingresos Brutos (IIBB) requires per-province tax codes; rates 1-6% on revenue
• Multiple invoice classes: A (RI to RI), B (RI to consumer), C (Monotributo), E (export) — based on issuer/receiver category
• Statutory reports include IVA Compras/Ventas, Libro IVA Digital, Mis Comprobantes
• RG 5616 introduced new "Recibos Controlados" for fund-transfer receipts in 2024-2025

Argentina Tax Framework Overview

ARCA enforces:

• IVA: 21% standard rate; 10.5% reduced (basic foods, some services); 27% increased (specific utilities); 0% exports
• Ganancias (Corporate Income Tax): Progressive 25% / 30% / 35% based on profit; 35% on dividends to non-residents
• Bienes Personales: Wealth tax on individuals
• Impuesto a los Sellos: Stamp tax on contracts (provincial)
• Ingresos Brutos (IIBB): Provincial gross revenue tax (rates 1-6%, some up to 8% for specific activities); each of 24 jurisdictions has its own regime
• Withholding (Retenciones): Federal IVA, Ganancias, Sicore; provincial IIBB and Sicoba

The fiscal categorization of taxpayers drives invoice handling:

• Responsable Inscripto (RI): VAT-registered, charges and recovers IVA
• Monotributo: Simplified small taxpayer regime, single payment instead of separate IVA/Ganancias
• Consumidor Final: End consumer, no tax registration

Required Odoo Localization Modules

The Odoo l10n_ar localization has been refined over many years through significant Argentine deployment volume. Native ARCA integration handles CAE (Codigo de Autorizacion Electronico) requests reliably.

Chart of Accounts Setup

The l10n_ar chart aligns with FACPCE (Federacion Argentina de Consejos Profesionales de Ciencias Economicas) standards. Key accounts:

• 1.1.x: Caja y bancos
• 1.2.x: Creditos
• 1.3.x: Bienes de cambio (inventory)
• 2.1.x: Deudas (including IVA debito fiscal, IVA credito fiscal, Ganancias provision)
• 3.x: Patrimonio neto
• 4.x: Ingresos
• 5.x: Costos
• 6.x-7.x: Gastos

Configure the company record with:

• CUIT (11 digits) - tax identification number
• Razon social as registered with ARCA
• Categoria fiscal (Responsable Inscripto, Monotributo, etc.)
• Provincia for IIBB calculation
• ARCA digital certificate (for WSFE authentication)

Electronic Invoicing Configuration

Argentina's electronic invoicing flow:

1. Invoice is approved in Odoo
2. l10n_ar_edi calls the appropriate ARCA web service (WSFE for domestic, WSFEX for exports, WSMTXCA for itemized) with invoice data
3. ARCA validates and returns CAE (authorization code) and CAE expiration date
4. Odoo stamps the invoice with CAE; the CAE is printed on the customer-facing PDF along with QR code
5. Invoice is finalized; subsequent operations use the CAE for reference

Invoice classes and use cases:

# Example WSFE invocation pattern
def request_cae(self, invoice):
    wsfe_client = WSFEv1Client(
        cuit=invoice.company_id.l10n_ar_cuit,
        cert=invoice.company_id.l10n_ar_certificate,
        production=invoice.company_id.l10n_ar_production_mode,
    )
    request_data = {
        'PtoVta': invoice.journal_id.l10n_ar_punto_venta,
        'CbteTipo': invoice.l10n_ar_cbte_tipo,
        'Concepto': invoice.l10n_ar_concepto,  # 1=Productos, 2=Servicios, 3=Mixto
        'DocTipo': invoice.partner_id.l10n_ar_doc_type,
        'DocNro': invoice.partner_id.l10n_ar_cuit_or_dni,
        'CbteFch': invoice.invoice_date.strftime('%Y%m%d'),
        'ImpTotal': invoice.amount_total,
        'ImpNeto': invoice.amount_untaxed,
        'ImpIVA': invoice.tax_totals['amount_tax'],
        # ... etc
    }
    response = wsfe_client.cae_solicitar(request_data)
    invoice.l10n_ar_afip_auth_code = response.cae
    invoice.l10n_ar_afip_auth_code_due = response.cae_vencimiento

IVA Configuration

Configure IVA tax records:

Ingresos Brutos (IIBB) - Provincial Tax

IIBB is a provincial gross revenue tax. Each of 24 jurisdictions (CABA + 23 provinces) operates its own:

• Convenio Multilateral allocates revenue across provinces for multi-province operations
• Rates range from 1% to 6%+ depending on province and activity
• Withholding (retenciones) and percepciones operate through registered agents
• Monthly returns per province where the company has nexus

Configure separate IIBB tax codes per province:

RG 5616 - Recibos Controlados

Resolution General 5616 (effective 2024-2025) requires "Recibos Controlados" for receipts of funds (cobros), distinct from invoices. Recibos must be issued for collections that don't directly correspond to a CAE-authorized invoice — common for advances, deposits, restitutions.

Odoo deployments must extend l10n_ar_edi to issue Recibos with their own CAE flow. This is a relatively recent requirement and may not be fully native in all Odoo versions; verify support and budget custom development if needed.

Withholding (Retenciones y Percepciones)

Argentina's withholding regimes are extensive:

• Federal Retenciones IVA: SICORE rates (3% or 6%) applied to vendor payments
• Federal Retenciones Ganancias: Variable rates per service type
• Provincial Retenciones IIBB: Each province has its own designated agents
• Percepciones IVA: Charged by registered agents (typically wholesalers) to RI buyers
• Percepciones IIBB: Provincial percepcion charges

Odoo handles these via tax codes with appropriate rates and triggers based on supplier and buyer registration status.

Payroll Considerations

Argentine payroll components:

Reporting Requirements

An Argentine Odoo deployment must produce:

• Libro IVA Digital: Monthly digital book of IVA sales and purchases (RG 4597)
• F. 2002 / F. 2017: Monthly IVA return
• F. 731 (Ganancias Mensual): Monthly Ganancias withholding
• SICORE: Federal withholding regime declaration
• CITI Ventas / CITI Compras: Information regimes for IVA
• DDJJ Ingresos Brutos: Per province monthly
• Convenio Multilateral CM05: Annual multi-province revenue allocation
• F. 1357 / F. 572: Income tax certificates

Implementation Checklist

1. Confirm CUIT, fiscal categorization, ARCA web service certificate
2. Install l10n_ar and l10n_ar_edi; configure CUIT, certificate, punto de venta
3. Configure IVA 21%, 10.5%, 27%, 0%, exempt categories
4. Configure IIBB per province of operation with proper rates
5. Set up SICORE retenciones and percepciones IVA codes
6. Test electronic invoicing in homologacion (ARCA test environment)
7. Configure RG 5616 Recibos Controlados workflow
8. Configure Ganancias withholding per service category
9. Set up payroll with current pension/health/income tax rates
10. Build Libro IVA Digital export per RG 4597 format

Common Pitfalls

Wrong invoice class: Issuing class A to a Monotributista or class B to a Responsable Inscripto causes tax discrepancies. Configure customer category checks before invoice creation.

Missing IIBB on multi-province sales: Convenio Multilateral allocates revenue across provinces. Single-province IIBB without convenio leaves the company exposed in other jurisdictions.

CAE expiry: CAE has expiration date (typically 10 days). Issuing the invoice to the customer after CAE expiry is invalid.

Punto de Venta mismatch: Each "punto de venta" (POS point) must be registered with ARCA. Using an unregistered POV causes WSFE rejection.

RG 5616 Recibos Controlados ignored: Funds receipts without an underlying CAE-stamped invoice need their own Recibo Controlado. Bypassing this is now an audit trigger.

ECOSIRE provides Odoo localization for Argentina, including ARCA electronic invoicing, IIBB multi-province handling, and RG 5616 Recibos Controlados. Contact us for implementation or explore our accounting services.

Frequently Asked Questions

How does ARCA differ from AFIP for Odoo configurations?

The renaming from AFIP to ARCA is administrative — the web services (WSFE, WSFEX, WSMTXCA), CUIT structure, certificate authentication, and invoice rules remain unchanged. Existing Odoo deployments continue working without changes. New deployments simply reference ARCA in user-facing labels but use the same technical integration.

Does Odoo support Convenio Multilateral for IIBB?

Native Odoo doesn't compute Convenio Multilateral (CM05) automatically. Multi-province companies typically use specialized accounting software for IIBB (BDO Argentina, Bejerman) and import the allocations to Odoo for journal posting. Custom Odoo modules can compute revenue percentages per province but the regulatory complexity makes external tools the practical choice.

What's the difference between Retencion and Percepcion?

Retencion is a withholding by the buyer when paying a supplier (the buyer remits to ARCA). Percepcion is an additional charge by the seller when invoicing certain buyers (the seller remits to ARCA on the buyer's behalf). Both increase or decrease the buyer's tax credit. Odoo configures each as a separate tax with the proper journal direction.

Can Odoo handle high inflation accounting (Ajuste por Inflacion)?

Argentina requires inflation adjustment under FACPCE Resolution 539 when CPI exceeds thresholds. Odoo doesn't natively perform IFRS IAS 29 / FACPCE inflation adjustment — most clients export trial balances and run inflation adjustments in specialized tools, then post adjustment journals back to Odoo. Some OCA Argentina modules add basic adjustment but verify currency and accuracy before relying on them.

How do we handle the foreign currency invoicing properly?

Argentina has parallel exchange rate dynamics (official rate, MEP, CCL, blue). Invoicing in foreign currency requires care: the official BCRA rate must be used for tax calculations, but commercial settlements may use other rates. Odoo configures multi-currency with explicit rates per invoice; the IVA base is always converted at the official BCRA rate of the invoice date.