Skip to main content
iVentureTeam
Odoo Accounting & Tax

Odoo Argentina Localization: ARCA E-Invoicing, ARBA and Withholdings

Odoo Argentina localization for Odoo 19 and 20: l10n_ar_edi ARCA e-invoicing, ARBA retenciones, IIBB percepciones, setup steps and the padron gap.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 15, 202611 min read4 views
Odoo Argentina Localization: ARCA E-Invoicing, ARBA and Withholdings cover

Most guides on Odoo for Argentina stop at "install the module". The real work is ARCA certificates, document types, journals per point of sale and keeping ARBA rates current every month. Our Odoo implementation services plan all of that as one project.

Related service: Odoo for finance teams — accounting, tax and reporting automation.

This guide is for CFOs, controllers and IT leads in Argentina, or foreign groups opening an Argentine entity, who run or plan to run Odoo 19 or 20. For the wider picture of what country packages leave out, see our guide to Odoo localization gaps by country.

What does the Odoo Argentina localization include?

The Odoo Argentina localization is a set of modules that add ARCA rules, taxes, document types, e-invoicing and withholdings to Odoo Accounting.

ModuleTechnical nameWhat it doesWhere it lives
Argentina - Accountingl10n_arCharts of accounts, taxes, document types, ARCA responsibility typesCommunity source
Argentinean Electronic Invoicingl10n_ar_ediE-invoices through ARCA web services, CAE, vendor bill checksNot in the public source, so an Enterprise module
Argentinean Accounting Reportsl10n_ar_reportsVAT book and VAT summary reportsNot in the public source, so an Enterprise module
Argentina - Payment Withholdingsl10n_ar_withholdingEarnings and IIBB withholdings on vendor paymentsCommunity source
Point of Sale with AR Docl10n_ar_posArgentine fiscal fields in the POSCommunity source, auto-installs
Argentinean - Stockl10n_ar_stockDelivery guides (remitos) with CAI dataCommunity source, auto-installs
Argentinean eCommercel10n_ar_website_saleIdentification type and ARCA responsibility at checkoutCommunity source, auto-installs

The Odoo 20 Argentina documentation lists three charts of accounts: Monotributista (227 accounts), Exento (290) and Responsable Inscripto (298). The Responsable Inscripto package creates 73 taxes.

Is AFIP now ARCA, and does Odoo support the change?

Yes, AFIP was dissolved and replaced by ARCA (Agencia de Recaudación y Control Aduanero), and Odoo's Argentina localization now uses ARCA in its fields and menus. The web services and CAE logic carried over.

ARCA's own site states that Decree 953/2024 dissolved AFIP. Odoo's Latin America team posted on the Odoo forum on 24 October 2024 that the decree kept the current e-invoicing functions and standards until new rules were published.

Odoo 19 and 20 now show labels such as ARCA Responsibility Type and ARCA POS System, though some error texts still say AFIP.

How do you set up Odoo for Argentina step by step?

Set up the company's ARCA data first, then the chart, journals, certificate and contacts, and test everything in ARCA's testing environment before production.

  1. Company: enter the CUIT and set the ARCA Responsibility Type (Responsable Inscripto, Exento or Monotributo).
  2. Chart of accounts: pick the package that matches that responsibility type in Accounting settings; Odoo does not install one by default.
  3. ARCA portal: enable the right web service, for example "RECE para aplicativo y WebServices" for a Responsable Inscripto.
  4. Certificate: click Generate Renewal Request in Odoo, use the .csr file in ARCA to get the certificate, then upload it with the private key.
  5. Environment: choose Testing (Prueba) first; testing and production certificates are not interchangeable.
  6. Sales journals: tick Use Documents, set the ARCA POS System, ARCA POS Number and POS address for each point of sale.
  7. Contacts: set identification type, CUIT and ARCA Responsibility Type on every customer and vendor.
  8. Withholdings: install l10n_ar_withholding, set outstanding accounts on every bank payment method and review each withholding tax.
  9. Go live: switch to Production, post a first invoice and let Odoo sync the last sequence used in ARCA.

How does ARCA e-invoicing work in Odoo (l10n_ar_edi)?

When you post an invoice, l10n_ar_edi sends it to ARCA's web service, receives a CAE authorization code and prints it with a QR code on the PDF. If ARCA rejects it, the invoice stays in draft with the error and a suggested fix.

Odoo picks the document letter from the two parties' ARCA responsibility types: A for a Responsable Inscripto customer, B for end consumers and E for exports. You can change the suggested type before posting.

The journal's ARCA POS System decides which web service is used:

  • wsfev1: standard electronic invoice for A, B, C and M documents, without item detail.
  • wsbfev1: electronic fiscal bond for companies invoicing capital goods.
  • wsfexv1: export invoices, document type E, with the Incoterm filled in.

For services, ARCA needs service start and end dates; blank dates default to the invoice month.

Factura de Crédito Electrónica (FCE MiPyME)

Odoo supports FCE documents such as types 201, 202 and 206, with a default transmission option of SCA or ADC. Odoo's docs state a CBU bank account on the issuer and an amount over ARS 100,000; check ARCA's current FCE threshold before you rely on that figure.

Checking vendor bills against ARCA

You can make Odoo verify vendor bill numbers in ARCA: Not available, Available (warn) or Required (block posting). Required suits strict purchase controls, the buying side of "odoo afip facturacion electronica".

How does Odoo handle ARBA retenciones and other withholdings?

The l10n_ar_withholding module computes withholdings when you register a vendor payment, using taxes assigned to each vendor with optional date ranges. For ARBA retenciones, Odoo ships an "IIBB WTH PBA 0%" tax that you configure.

The module supports four withholding types, per the withholding section of Odoo's Argentina docs:

TypeHow Odoo calculates itWhat you maintain
EarningsPercentage of the payment, with non-taxable amount and minimumRate, thresholds and ARCA regime code
Earnings ScaleBrackets from the Earnings Scale table, cumulative in the monthThe scale brackets
IIBB Total AmountPercentage of the total payment for a provinceThe province rate
IIBB UntaxedPercentage per province, no threshold or minimumThe province rate

Each vendor's Accounting tab holds a Purchase Withholdings table with From Date and To Date, and Odoo applies those taxes on every payment.

In the Odoo 20 source, the default earnings scale still starts with an ARS 8,000 bracket, so check it against ARCA's current table. A developer note says accumulation supports one earnings regime per vendor at a time.

How are IIBB percepciones recorded in Odoo?

On sales, Odoo has 0% perception taxes per jurisdiction that you set per customer; on purchases, you add the perception suffered to a bill line and type the real amount. The tax groups cover CABA and all 23 provinces.

On vendor bills the perception default is 0.10; click the pencil icon and type the supplier's figure. On sales, "P. IIBB PBA 0%" is the Buenos Aires starting point, and each customer's rate comes from the ARBA padron.

What does standard Odoo not cover for ARBA and AGIP?

Odoo Argentina localization: What standard Odoo leaves to you

Standard Odoo 19 and 20 do not import the ARBA or AGIP padron and do not issue the ARBA A-122R certificate; Odoo's docs say provincial rates "must be manually updated". This is the biggest gap buyers miss.

ARBA's Resolución Normativa 36/2025 says collection rates are published in padrones on ARBA's site. ARBA RN 22/2025 made A-122R, issued in ARBA's own web app, the only valid withholding certificate, and RN 27/2025 moved its start to 1 March 2026.

RequirementStandard Odoo 19/20What you add
ARBA rate per CUIT (padron)Not imported; rates typed per taxMonthly import script or partner module
AGIP padron for CABANot imported in standardSame routine as ARBA, own file format
A-122R withholding certificateNot generated or sent to ARBABatch file export or certificate step in ARBA's app
Province rate changesManual edit of each tax recordOwner, calendar reminder and test payment
Multi-regime earnings per vendorOne regime at a time per vendorReview vendors with mixed concepts
Other provincial agent regimesIIBB reports by jurisdiction onlyExport layouts per province, scoped per project

Argentine partners sell modules for these tasks. Treat them as custom code: check version support and who maintains them. We have not tested them all, so we name none.

What changed between Odoo 19 and Odoo 20 for Argentina?

Functionally little, but the withholding module was rebuilt on Odoo's shared withholding tax engine in Odoo 20. The 19.0 and 20.0 Argentina documentation pages are identical, so the user flows stay the same.

In the 20.0 source, l10n_ar_withholding depends on the generic l10n_account_withholding_tax module and its type field was renamed, so custom withholding code needs changes. Test payments on a copy first; our Odoo 20 accounting upgrade checklist lists the wider tax tests.

What are the common Odoo Argentina errors and how do you fix them?

Most Odoo Argentina e-invoicing errors come from sequence mismatches with ARCA, expired certificates or missing contact data.

  • Error 10016: ARCA says the number or date is not the next to authorize; a user on Odoo 18 Enterprise hit error 10016 on an ARCA invoice. Use Consult Invoice in ARCA, Get Last Invoice, then resequence.
  • Expired certificates: an Odoo forum answer on expired ARCA certificates says to unlink the old certificate, create and link a new one, and check the web service is active.
  • Wrong document letter: usually a missing ARCA Responsibility Type on the contact.
  • Withholding with no journal entry: outstanding accounts are missing on a bank payment method.
  • FCE rejected: no CBU bank account on the issuer, or the amount is under the threshold.

Odoo Argentina localization by industry

The tax setup is the same for everyone, but the pain point changes by industry.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
DistributionMany customers with ARBA perception ratesP. IIBB taxes per customer, monthly padron updateBuild and test the padron import
ManufacturingEarnings and IIBB withholdings on many suppliersl10n_ar_withholding with vendor date rangesMap regimes and scales per supplier
Retail and POSSeveral points of sale, one ARCA POS eachl10n_ar_pos and one journal per ARCA POSSet journals, test CAE per store
eCommerceFiscal data at checkout and auto invoicingl10n_ar_website_sale and Automatic InvoiceConfigure checkout and payment provider
ExportersType E invoices, Incoterms, foreign currencywsfexv1 journal and export fiscal positionTest export flows in homologation

Our Odoo ERP for retail page covers the POS side in more depth.

How much does an Odoo Argentina implementation cost?

Budget as for any Odoo rollout, plus time for ARCA certificates, homologation tests and the padron routine.

Per our Odoo implementation cost guide, small projects run $3k to $9k (4 to 8 weeks), mid-size $9k to $27k (8 to 14 weeks) and large $27k to $150k+ (12 to 24 weeks). Data migration adds $1.2k to $9k depending on the source system and years of history.

Argentina adds work per ARCA point of sale, per agent province and for any padron import. For a first number, try the Odoo implementation cost calculator. Weighing Mexico too? See Odoo implementation cost in Mexico.

How iVentureTeam helps with Odoo Argentina localization

Rolling out in Argentina? Price it first

We set up and test the Argentina localization end to end, from ARCA certificates to the monthly ARBA routine. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Fit check: which modules you need, Odoo Online, Odoo.sh or on-premise, and which gaps need custom work.
  • ARCA setup: certificates, journals per point of sale, document types and homologation tests.
  • Withholdings and percepciones: regimes, scales, vendor and customer assignments, and a tested padron import through our Odoo customization services.
  • Migration: opening balances, open invoices and contacts with ARCA data from your current system.
  • Training: accounts staff learn the daily checks, the error fixes and the monthly close.

Odoo localization case study: Fernando Tax Management

This case is not Argentine: it is a Dutch tax practice with Netherlands and Curaçao reporting, the closest match we have to localized tax work. We include it to show how we handle tax reporting fixes, and we say plainly how it differs.

Fernando Tax Management B.V. had outgrown a rigid legacy system, with duplicate records from manual entry and translation gaps in compliance reports.

We migrated the firm to Odoo 18, built custom tax compliance reports for its Dutch and Curaçao contexts, fixed a hidden journal lines issue and corrected translation defects. The project ran 10 weeks and cut manual data entry by 60%.

It involved no ARCA, ARBA or Argentine withholdings. Read the Fernando Tax Odoo accounting automation case study.

The bottom line on Odoo Argentina localization

Odoo 19 and 20 handle ARCA e-invoicing, VAT books, percepciones and withholdings well, but you must own the ARBA and AGIP rate updates and the A-122R step. Plan for that from day one.

Pick the right chart, test every document type in homologation, and name who updates provincial rates each month.

Ready to set up Odoo for ARCA and ARBA?

Plan your Argentina rollout

Get a localization plan before you buy licenses. Plan your Odoo Argentina rollout with our team, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Does Odoo support electronic invoicing in Argentina?

+

Yes. The l10n_ar_edi module sends invoices to ARCA web services, gets a CAE and prints a QR code on the PDF. It supports standard, export and fiscal bond web services, plus FCE MiPyME documents.

Is l10n_ar_edi included in Odoo Community?

+

No. The module is not in Odoo's public Community source, so it comes with Odoo Enterprise. The base l10n_ar module and l10n_ar_withholding are in Community.

Does Odoo import the ARBA padron automatically?

+

Not in the standard modules. Odoo's docs say provincial rates must be updated manually. Most companies add a monthly import script or a partner module and test it each month.

Can Odoo generate the ARBA A-122R withholding certificate?

+

Not in standard Odoo 19 or 20. Since ARBA RN 22/2025, the A-122R is issued in ARBA's own app, so you export withholdings from Odoo or use a partner module that prepares the batch.

How do I fix ARCA error 10016 in Odoo?

+

It means the number or date is not the next one ARCA expects. Use Consult Invoice in ARCA with Get Last Invoice to see ARCA's last number, then align the Odoo sequence and post again.

Which chart of accounts should I choose in Odoo Argentina?

+

Pick the one that matches your ARCA responsibility type: Responsable Inscripto, Exento or Monotributista. Odoo does not install one by default, so choose it in Accounting settings before posting.

Does Odoo 20 change Argentine withholdings?

+

User flows are the same, but l10n_ar_withholding is rebuilt on Odoo's shared withholding tax engine. Custom code on withholdings needs review, so test payments on a copy before upgrading.

Free e-invoicing and tax readiness check

Getting Odoo ready for e-invoicing?

We check your Odoo version, localization and invoice flows against e-invoicing, then send what to set up, what to test and the effort involved.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.