Argentina Makes Recipient VAT Status Mandatory in Electronic Invoices

Summary

Argentina’s tax authority has published Version 4.8 of the WSFEv1 Electronic Invoice Web Service Developer Manual. From 1 December 2026, electronic invoices within the relevant service must include the recipient’s VAT status in the CondicionIVAReceptorId field, reflecting the effective date established under General Resolution No. 5616. [afip.gob.ar]
Recipient VAT status information could previously be submitted on an optional basis. Once the requirement becomes mandatory, invoices lacking the field may fail validation or be rejected. The manual also provides a service for retrieving reference values corresponding to the available recipient VAT conditions, supporting consistent system mapping. [afip.gob.ar]
Businesses should update customer master data and electronic invoicing interfaces before December. Readiness work should include obtaining recipient VAT classifications, mapping valid identifiers, testing CAE and CAEA scenarios, and defining controls for missing or contradictory information. Customer onboarding processes should also capture the mandatory status for future electronic invoice issuance. [afip.gob.ar]

Article

Argentina’s Revenue and Customs Control Agency, or ARCA, has published Version 4.8 of the Developer Manual for the WSFEv1 Electronic Invoice Web Service governed by General Resolution No. 4291.

The manual confirms that the recipient’s VAT status becomes mandatory from 1 December 2026. The relevant value must be reported through the CondicionIVAReceptorId field when requesting authorisation for an electronic invoice. [afip.gob.ar]

The recipient VAT condition was introduced earlier as an optional field. Version 4.0 of the manual indicated that it could be submitted optionally from 6 April 2025 until the mandatory requirement under General Resolution No. 5616 entered into force. Version 4.8 now identifies 1 December 2026 as the date on which the field becomes compulsory. [afip.gob.ar]

The web service includes the FEParamGetCondicionIvaReceptor method, which allows systems to retrieve reference values for the VAT status codes available for recipients. Businesses should use the official reference values rather than creating local classifications that cannot be translated reliably into the required identifier. [afip.gob.ar]

The change creates a significant master-data dependency. An invoice may contain correct commercial amounts and tax calculations but still fail authorisation if the recipient’s VAT classification is missing or invalid.

Businesses should therefore identify customers whose VAT status has not been captured, validate existing classifications and establish a process for resolving inconsistent information. Controls should apply to both new-customer onboarding and updates to existing customer records.

ERP and invoicing teams should map the local customer tax status to the appropriate ARCA code and ensure that the value is transmitted in every relevant WSFEv1 request. Testing should cover different invoice types, CAE and CAEA processing, recipients with different VAT conditions, and error handling where the field is absent.

Customer-facing teams may need to request updated tax information before go-live. Businesses should also determine whether invoices blocked because of incomplete data will be held, corrected automatically or routed for manual review.

Given the risk of invoice rejection and delayed billing, production deployment should be completed in advance of 1 December 2026.

Source Links