Argentina Electronic Invoicing: A Guide to Factura Electrónica

An invoice issued in Argentina has legal validity only if it comes through a channel the tax authority controls: an electronic invoice (factura electrónica) authorized before it is delivered, or a ticket from a homologated fiscal controller (controlador fiscal) at the point of sale. Electronic invoicing is the main channel, and it is not a post-hoc reporting requirement. Argentina operates a pre-clearance model where the tax authority validates each invoice in real time and assigns a CAE (Código de Autorización Electrónico) before the document can be delivered to the buyer. Without a CAE, an electronic invoice has no fiscal standing. From 1 November 2026, General Resolution 5893/2026 makes one of the two channels compulsory for the domestic sales of almost every taxpayer, and paper invoice books survive only as a fallback for outages. Mexico's CFDI framework is the nearest large comparison in the region: it also clears every invoice before it gains fiscal validity, but routes it through certified intermediaries (PACs) rather than straight to the tax authority.

The authority behind this system is ARCA (Agencia de Recaudación y Control Aduanero), which replaced the former AFIP (Administración Federal de Ingresos Públicos) in October 2024 under Decree 953/2024. ARCA inherited AFIP's entire electronic invoicing infrastructure: technical specifications, web services, and taxpayer obligations carried over without interruption. Legacy documentation and technical guides still reference AFIP; prior AFIP resolutions remain in force unless explicitly superseded by new ARCA resolutions. The broader trajectory of Argentine tax modernization reinforces this direction: the World Bank's 2025 announcement of a US$300 million tax modernization project for Argentina targets enhanced tax administration through ARCA, including simplified procedures and pre-filled digital tax forms.

Argentina's electronic invoicing system revolves around several core components:

• Lettered invoice types (A, B, C, T, E) determined by the tax registration status of both the issuer and the recipient. The correct letter is not optional: it fixes how VAT is shown and whether the buyer can claim it as a credit, and ARCA's web service checks it against the recipient's declared VAT condition.
• XML-based web service requests submitted to ARCA for authorization. Each approved submission returns a CAE and an expiration date, which must appear on the printed or PDF version of the invoice.
• Mandatory QR codes on electronic invoices since 24 December 2020 (web-service issuers were phased in between March and June 2021), encoding key invoice data in a standardized format that anyone can check against ARCA's records.
• Integration with VAT reporting through IVA Simple and the Libro IVA Digital: the invoices ARCA authorizes are pre-loaded into the taxpayer's VAT records, so the monthly return starts from invoice data the taxpayer validates rather than retypes.

---

Invoice Types A, B, C, M, T, and E Explained

The first decision in issuing an Argentine invoice is selecting the correct letter type. Each invoice carries a letter designation (A, B, C, T, or E, plus M until November 2025) that controls how VAT is treated on the document, what withholding obligations apply, and which data fields are mandatory. The letter is determined by two factors: the tax registration status of the issuer and the tax registration status of the recipient.

Before using the decision matrix below, you need to understand two foundational tax categories in Argentina's system:

Responsable Inscripto refers to a taxpayer registered in the general VAT regime. These businesses charge VAT on their sales, claim input VAT credits on their purchases, and file monthly VAT returns. Most medium and large businesses fall into this category.

Monotributista refers to a taxpayer enrolled in the Monotributo (simplified tax regime), which bundles income tax, VAT, and social security into a single fixed monthly payment based on revenue brackets. Monotributistas do not itemize VAT on their invoices and cannot claim VAT input credits. This regime is designed for small businesses, freelancers, and sole proprietors below certain revenue thresholds.

Invoice Type Decision Matrix

What Each Type Means in Practice

Types A, B, and C cover the standard domestic scenarios. Type A is the B2B invoice between two Responsable Inscripto entities, with VAT itemized so the recipient can claim input credits. Since 1 July 2021 (General Resolution 5003/2021) it is also the invoice a Responsable Inscripto issues to a Monotributista, carrying a legend that the VAT shown may be used only for the purposes of the small-taxpayer regime of Ley 27.618, not as an ordinary VAT credit. Type B applies when the recipient is a final consumer, VAT-exempt or not categorized, embedding tax in the price; under the consumer fiscal transparency regime of Ley 27.743, the invoice still shows the VAT that price contains. Type C is issued by Monotributistas and VAT-exempt taxpayers to any domestic recipient, with no VAT itemization permitted. The fields and limits specific to a Monotributista's invoices are set out in the guide to what a Monotributo invoice (Factura C) must show.

Type M was a monitoring mechanism for newly registered Responsable Inscripto taxpayers or those flagged by the tax authority for compliance risk. It worked like a Type A invoice but carried a legend requiring the buyer to withhold VAT and remit it directly to the tax authority. General Resolution 5762/2025 abolished Type M from 1 December 2025. Where M used to apply, ARCA now authorizes a Type A invoice with the legend "OPERACIÓN SUJETA A RETENCIÓN", on which a VAT-registered buyer withholds 100% of the VAT and 6% income tax on the net amount when it pays. How withholding at payment is calculated and certified is covered in the guide to Argentina's percepciones and retenciones. Issuers who fail only ARCA's solvency test can opt instead for Type A with the legend "PAGO EN CBU INFORMADA": no withholding, but the buyer must pay into the bank account (CBU) the issuer has declared. ARCA re-evaluates who falls into these regimes every four months.

Type T serves a narrow purpose: refunding VAT on accommodation to foreign tourists. VAT-registered hotels, hostels, apart-hotels, campsites and authorized travel agencies issue it for lodging (and breakfast included in the room price) supplied to non-residents who pay with a foreign-issued card or a transfer from abroad. The refund happens on the invoice itself: the Type T invoice shows a refund equal to the VAT, and the hotel reports that VAT in its own return under the "TurIVA" regime (Joint General Resolution 3971/2016). It is unrelated to the refund visitors can claim at airports and ports, which covers purchases of goods, uses ordinary invoices and runs under a separate regime (General Resolution 5843/2026).

Type E is the export invoice, used for exports of goods and services whether the issuer is a Responsable Inscripto, a Monotributista or an exempt taxpayer. These invoices carry zero-rated VAT, consistent with the destination principle applied in international trade, and they are authorized through a separate web service, WSFEX, rather than the WSFEv1 service used for domestic invoices. Type E invoices have their own required fields, including the destination country and the customs documentation reference where applicable.

---

CAE Authorization: How Real-Time Invoice Clearance Works

An Argentine electronic invoice without a CAE (or, in a contingency, a CAEA) is not a legal document. The CAE (Código de Autorización Electrónico) is what transforms a draft invoice into a fiscal document recognized by ARCA and enforceable under Argentine tax law.

The authorization workflow operates as a real-time clearance model. The issuing party submits structured invoice data to ARCA's web services, ARCA validates the submission against its rules, and if everything checks out, it returns a unique CAE along with an expiration date. The entire exchange happens programmatically, typically completing in seconds.

The Technical Workflow

The process follows a defined sequence:

1. Authentication. The issuer authenticates against ARCA's authentication service (WSAA) using a digital certificate (certificado digital). The certificate is obtained with the taxpayer's Clave Fiscal, linked to the taxpayer's CUIT (Clave Única de Identificación Tributaria) and associated with the electronic invoicing web service. Authentication produces an access ticket, a token and sign valid for 12 hours, that authorizes subsequent requests.

2. Invoice data submission. The issuer sends the invoice data in XML format to ARCA's electronic invoicing web service, known as WSFE (Web Service de Facturación Electrónica) or its current version WSFEv1. The XML payload includes the invoice type, point of sale number, the recipient's document type and number (the CUIT for businesses), the recipient's VAT condition, taxable amounts, VAT breakdowns, and any applicable perceptions or withholdings.

3. Validation and response. ARCA validates the submitted data against multiple criteria: sequential numbering for the point of sale, correct tax categorization of both parties, mathematical consistency of amounts and tax calculations, and the issuer's authorization to emit that invoice type. If validation passes, ARCA returns the CAE and its expiration date. If it fails, the response includes error codes identifying which fields or rules were violated.

4. Invoice completion. The issuer incorporates the CAE and its expiration date into the final invoice document before delivering it to the recipient. An invoice transmitted to a customer without a valid CAE is not a legal fiscal document.

XML Format Requirements

WSFEv1 is a SOAP web service, and invoice data submitted to it must conform to ARCA's published schema. Key structural elements include the FECAESolicitar method call, which wraps the header data (point of sale, invoice type, quantity of records) and one or more detail records containing the commercial and tax data for each invoice. Amounts are sent as decimal numbers with up to two decimal places (a VAT amount of 26.25 is sent as 26.25), and ARCA checks the totals for consistency within defined rounding tolerances. Date fields follow the YYYYMMDD format without separators.

Version 4 of ARCA's developer manual added two fields. CondicionIVAReceptorId carries the recipient's VAT condition, which General Resolution 5616/2024 made part of every electronic invoice; the manual warns that requests without it will be rejected once it becomes mandatory, so a system that still omits it should add it now. CanMisMonExt flags an invoice that will be settled in the same foreign currency it is issued in, in which case the exchange rate sent must match the rate ARCA publishes for the previous business day exactly.

Error handling requires parsing the response XML for both the Resultado field (A for approved, R for rejected, or P for a batch only partly approved) and any Observaciones or Errors nodes that provide specific rejection codes. Common rejection causes include duplicate invoice numbers, mismatched tax categories between issuer and recipient, and amounts that fail internal consistency checks.

QR Code Requirements

Since 24 December 2020 (General Resolution 4892/2020), electronic invoices must include a QR code that encodes verification data in a standardized format. Issuers using the web service were phased in between 1 March and 1 June 2021, and on invoices made in ARCA's own Comprobantes en Línea and Facturador Móvil tools, ARCA adds the code itself. The QR contains a URL pointing to ARCA's verification service, with parameters that include the version of the QR data format, date of issue, CUIT of the issuer, point of sale number, invoice type and number, the total amount, currency and exchange rate, the recipient's document type and number, whether the authorization is a CAE or a CAEA, and the authorization code itself. This allows any recipient or auditor to scan the code and verify the invoice's authenticity directly against ARCA's records. The QR does not replace any of the printed data the invoice must carry.

The data encoded in the QR is Base64-encoded JSON appended as the p parameter to ARCA's verification URL (https://www.arca.gob.ar/fe/qr/). Generating this correctly requires attention to the exact field names and data types in ARCA's QR specification: the QR's date, for instance, is written YYYY-MM-DD, unlike the web service's YYYYMMDD.

ARCA maintains separate homologación (testing) and production environments for web service integration. Each requires its own authentication certificate, and CAE codes issued in testing have no legal effect.

---

CAEA: The Anticipated Authorization Code and Its 2026 Transition

The CAEA (Código de Autorización Electrónico Anticipado) is an advance authorization mechanism that works on a fundamentally different model than real-time CAE clearance. Rather than submitting each invoice individually for approval, the taxpayer requests a single CAEA code covering a half-month period, either the 1st through the 15th or the 16th through the end of the month, from up to five days before the period starts. Invoices issued under it carry that code without any real-time web service call to ARCA at the moment of issuance, and they are reported to ARCA afterwards, by the 8th calendar day after the period ends.

This model was designed for high-volume operations where constant connectivity to ARCA's servers was impractical or unreliable. Logistics companies issuing thousands of freight invoices daily, fuel distributors processing transactions at remote stations, and large retail chains generating high volumes of receipts across distributed locations all gravitated toward CAEA. The mechanism gave these businesses the flexibility to continue issuing valid electronic invoices even when network conditions or transaction speed requirements made real-time authorization unfeasible.

That arrangement has ended. General Resolution 5782/2025, with its companion RG 5785/2025, replaced the old optional CAEA regime with an exceptional, contingency-only procedure. Both were due to take effect on 1 June 2026; General Resolution 5852/2026 postponed them to 1 August 2026 after business chambers reported they could not finish their system changes in time. ARCA has accepted no new adhesions to CAEA as a main issuing mode since 1 June 2026, and since 1 August 2026 CAEA is the first contingency option for web-service issuers rather than a routine one. Every CAEA point of sale is now a contingency point of sale tied to the same address as the issuer's normal one, and ARCA may refuse the contingency CAEA to taxpayers who do not report their CAEA invoices or do not file their monthly VAT returns.

The practical impact falls hardest on businesses that built their invoicing infrastructure around the batch model. Systems designed to request codes in advance and assign them offline have had to be re-architected to support real-time web service calls for every invoice: reliable connectivity to ARCA's servers, handling of synchronous responses including rejections, and fallback procedures for the contingency path. ARCA also watches how often that path is used. Contingency use stops counting as exceptional when, in two consecutive or three alternate months of a calendar year, contingency invoices reach 5% or more of a branch's monthly total, or CAEA contingency time exceeds 5% of ARCA's monthly service availability for that branch (outages attributable to ARCA excluded).

---

Mandatory Invoice Fields After April 2025

Argentina's tax authority requires a defined set of data elements on every electronic invoice, regardless of taxpayer size. Two changes in April 2025 added consumer tax-transparency and recipient fields, and a July 2026 change reset the rules for identifying final consumers, so practitioners should audit their invoicing systems against the complete requirements below.

Issuer Information

Every electronic invoice must identify the issuer with the following fields:

• CUIT (Clave Única de Identificación Tributaria), the 11-digit tax identification number
• Ingresos Brutos registration number, reflecting the issuer's provincial gross income tax enrollment, or a statement that the issuer is not liable for it (how that provincial tax is apportioned across jurisdictions is explained in the guide to Argentina's Ingresos Brutos and Convenio Multilateral)
• VAT registration status (Responsable Inscripto, Monotributista, Exento, etc.)
• Legal business name (razón social) or registered trade name
• Registered commercial address (domicilio comercial)
• Start-of-activities date (inicio de actividades)

Recipient Information

• CUIT, name or business name, and commercial address for business recipients
• The recipient's VAT condition, which every electronic invoice must identify since General Resolution 5616/2024
• For final consumers, the legend "A CONSUMIDOR FINAL". Since 1 July 2026 (General Resolution 5866/2026), identification by DNI (Documento Nacional de Identidad), CUIL or CDI is required only when the operation reaches ARS 10,000,000, or by CUIT whenever the buyer asks to be identified in order to deduct the expense for income tax

Invoice Identifiers

• Date of issue (fecha de emisión)
• Sequential invoice number of up to eight digits, which must follow an unbroken numeric sequence per point of sale and invoice type
• Point-of-sale code (punto de venta), a number of up to five digits assigned to each billing location or electronic billing system. Since July 2026 a point of sale can optionally be linked to a declared economic activity, and a closed point of sale can never be reused
• Invoice type letter (A, B, C, T, or E), determining the tax treatment and permitted issuer-recipient combination, plus the legend on either legended variant of Type A

Line Item Detail

• Description of the goods or services
• Quantity
• Unit price
• Net amount per line item

Tax Totals and Breakdown

This is where the 2025 changes landed. Type A invoices have always itemized VAT by rate so the buyer can claim the credit; what changed in 2025 is the consumer side. General Resolution 5614/2024 implemented the consumer fiscal transparency regime of Ley 27.743: invoices to final consumers and to exempt and non-taxed recipients must show the VAT contained in the price, under the heading "Régimen de Transparencia Fiscal al Consumidor (Ley 27.743)" with the lines "IVA Contenido" and "Otros Impuestos Nacionales Indirectos". Large companies had to comply from 1 January 2025 and every other taxpayer from 1 April 2025.

General Resolution 5616/2024 is a separate change, covering foreign-currency invoices and the recipient's VAT condition, which web-service billing systems had to apply from 15 April 2025. The mandatory tax fields now include:

• VAT amounts broken out by each applicable rate: 21% general, 10.5% reduced, 27% for gas, electricity, metered water and certain telecom services supplied to businesses rather than homes, plus special rates of 5% and 2.5%, or exempt
• Other national, provincial, or municipal indirect taxes, each itemized separately
• On consumer-facing invoices, the VAT contained and other national indirect taxes, shown under the transparency heading
• Currency code and exchange rate for any transaction denominated in foreign currency, on types A, B, C, E and T. When the invoice is settled in the same foreign currency, the rate is Banco de la Nación's selling rate at the close of the previous business day, which ARCA's systems fill in automatically

The phasing still matters when auditing 2025 records: a taxpayer outside the large-company category that did not update its invoice templates until April 2025 issued compliant invoices between January and March 2025 without the transparency disclosure. From April 2025 onward, no taxpayer is exempt from it. For comparison, Brazil's ICMS state tax rules on invoices impose their own detailed tax field mandates on every nota fiscal.

Authorization and Verification

• CAE code, the unique authorization number returned by ARCA upon real-time clearance (or the CAEA code on an invoice issued in contingency)
• CAE expiration date (Fecha de Vto.), printed alongside the code
• QR code encoding verification data, allowing recipients and auditors to validate the invoice directly against ARCA's records by scanning the code

Digital Retention Requirement

Argentine tax law requires invoices, and the records they were entered in, to be kept until five years after the tax period they relate to has prescribed (Decreto 1397/79, article 48). By ARCA's own count that comes to about 11 years for registered taxpayers and 16 for unregistered ones. Separately, the Civil and Commercial Code requires anyone obliged to keep accounts to hold their books, records and supporting documents for 10 years (article 328). The duty applies to both issuers and recipients, since each keeps the vouchers behind its own taxable operations, and a recipient may store the electronic original on an independent medium. Practitioners should check their archival systems against the longer tax period before assuming older records can be purged.

---

Libro IVA Digital and IVA Simple: From Invoice to VAT Return

The Libro IVA Digital, or Digital VAT Ledger (General Resolution 4597/2019), was the monthly electronic record of purchases and sales through which Responsables Inscriptos reported their fiscal debits and credits to ARCA, invoice by invoice. Since the November 2025 period, Responsables Inscriptos no longer file it as a separate submission: they record their operations in the "Registración Electrónica de Operaciones" module of IVA Simple, the pre-filled VAT return described below. The Libro IVA Digital remains in use for VAT-exempt subjects.

What makes the Argentine system distinctive is how tightly e-invoicing and VAT reporting are coupled. When a taxpayer issues an invoice and receives a CAE authorization, that transaction is already in ARCA's database. It is pre-loaded into the taxpayer's VAT records as a fiscal debit, and CAE-authorized invoices received from suppliers appear as fiscal credits. The taxpayer validates the pre-loaded operations, adds what the invoice data does not cover (imports, some purchases, prorations), adjusts where needed and confirms, and the confirmed records feed the monthly VAT return. The chain from individual transaction to tax filing is digital end to end, with the taxpayer reviewing rather than transcribing. The 2026 extension of invoicing to banks, insurers and card issuers (see the timeline below) fills one of the larger remaining gaps, since their charges reach the same database as each stage takes effect.

This closed-loop model resembles what other Latin American countries are building toward. Brazil's NF-e electronic invoice system follows a similar philosophy of capturing tax-relevant data at the point of issuance, though Argentina's integration between invoice authorization and VAT returns is among the most tightly coupled implementations in the region. Uruguay provides a useful nearby contrast because its DGI-managed CFE framework pairs mandated electronic documents with explicit fallback rules, which the guide to Uruguay's CFE requirements and contingency handling explains in practical terms.

IVA Simple and Pre-Filled VAT Returns

General Resolution 5705/2025 (Official Gazette, 2 June 2025) created IVA Simple, a VAT return filed on Form F.2051 in ARCA's Portal IVA and pre-filled from ARCA's own data: issued and received invoices, withholdings and perceptions suffered, payments on account and balances carried forward. It was optional for the June to October 2025 periods and became mandatory for every Responsable Inscripto from the November 2025 period, first filed in December 2025. Rather than building VAT declarations from scratch, taxpayers receive a return that already reflects their invoiced sales and documented purchases. The obligation shifts from preparation to review: verify the pre-filled figures, add, modify or delete entries where necessary, and confirm. Pre-filling does not limit ARCA's audit powers, and skipping F.2051 filings has a cost elsewhere, since ARCA may then refuse the taxpayer the contingency CAEA.

---

2025-2027 Regulatory Timeline

Argentina's e-invoicing framework changed repeatedly across 2025 and 2026, and several 2026 resolutions set deadlines that run into 2027. The following timeline consolidates the major milestones into a single reference, with the General Resolution behind each change and what it means in practice.

January 2025: Consumer Tax Transparency for Large Companies General Resolution 5614/2024 implements the consumer fiscal transparency regime of Ley 27.743. From 1 January 2025, large companies must show the VAT contained ("IVA Contenido") and other national indirect taxes on invoices to final consumers and to exempt and non-taxed recipients.

April 2025: Transparency for Everyone, Exchange Rates and Recipient VAT Condition The same RG 5614 obligation applies to every other taxpayer from 1 April 2025. Separately, General Resolution 5616/2024 requires foreign-currency invoices to show the exchange rate used and requires every electronic invoice to identify the recipient's VAT condition. Web-service billing systems had to apply it from 15 April 2025.

November 2025: IVA Simple (Form F.2051) Becomes Mandatory Under General Resolution 5705/2025, IVA Simple becomes mandatory for every Responsable Inscripto from the November 2025 period, replacing their separate Libro IVA Digital filing. The return is pre-filled from ARCA's invoice data, so discrepancies between issued invoices and declared VAT become immediately visible to ARCA.

December 2025: Type M Invoices Abolished General Resolution 5762/2025 abolishes class M from 1 December 2025. Taxpayers who would have issued M now issue Type A with the legend "OPERACIÓN SUJETA A RETENCIÓN", or opt for "PAGO EN CBU INFORMADA". Billing systems must remove M as a document class and map the logic that triggered it to the legended Type A variants.

April 2026: New Threshold for the Factura de Crédito Electrónica MiPyME From 14 April 2026, an SME's invoice to a large company must be issued as a Factura de Crédito Electrónica MiPyME when it reaches ARS 5,549,862. That B2B variant becomes a tradeable credit instrument once accepted and has its own acceptance and payment rules, set out in the guide to Argentina's Factura de Crédito Electrónica MiPyME.

June and August 2026: CAEA Becomes Contingency-Only From 1 June 2026, ARCA accepts no new adhesions to CAEA as a main issuing mode. From 1 August 2026, General Resolutions 5782/2025 and 5785/2025, postponed from June by RG 5852/2026, restrict CAEA to contingencies. Businesses that used CAEA for routine invoicing must authorize every invoice in real time, with CAEA available only as a connectivity fallback.

July 2026: Final-Consumer Identification Threshold From 1 July 2026, General Resolution 5866/2026 requires a final consumer's DNI, CUIL or CDI only for operations of ARS 10,000,000 or more, and a CUIT whenever the buyer asks to deduct the expense for income tax. Points of sale may now be linked to a declared economic activity.

September 2026 to March 2027: Banks, Insurers and Card Issuers Start Invoicing General Resolution 5866/2026 (Official Gazette, 29 June 2026), which replaced RG 5824/2026, ends most of the invoicing exemptions that financial institutions, insurers and card systems had. It is staged by type of operation rather than by type of entity:

• 1 September 2026: insurers, for operations with customers who are not Responsables Inscriptos or exempt.
• 1 October 2026: financial institutions, for leasing and foreign-trade operations.
• 1 December 2026: financial institutions, for loans (other than overdrafts) and for operations with customers who are not Responsables Inscriptos or exempt; financial institutions, card issuers and payment-transfer operators, for the charges included in cardholder statements.
• 1 March 2027: insurers, for co-insurance; financial institutions, card issuers and payment-transfer operators, for their periodic settlements to merchants.

These issuers, along with virtual asset service providers, prepaid health plans and private schools organized as civil associations or foundations, may invoice each operation individually or issue one monthly electronic settlement (liquidación electrónica mensual) per customer. For the businesses that pay them, bank, card and insurance charges reach ARCA's database as electronic invoices as each stage takes effect, and IVA Simple pre-loads purchases from there.

November 2026 and March 2027: E-Invoicing or a Fiscal Controller for Everyone General Resolution 5893/2026 (Official Gazette, 31 August 2026) makes electronic invoices or a new-technology fiscal controller compulsory for all domestic operations of Responsables Inscriptos, exempt taxpayers and every Monotributista, including the Monotributo Social and Monotributo Promovido categories, from 1 November 2026. Subjects outside the scope of VAT follow from 1 March 2027 and must use electronic invoices, not a fiscal controller. Monotributistas without a point of sale get one created automatically in ARCA's free Comprobantes en Línea service, and paper invoice books survive only as a contingency until their printing authorization (CAI) expires.

This timeline reflects published resolutions as of October 2026. Several of its 2026 dates were themselves postponements or re-enactments of earlier ones, and ARCA continues to issue updates, so practitioners should check the Official Gazette (Boletín Oficial) and ARCA's resolution feed before relying on a future deadline.