In Argentina, the e-invoice is authorized with the AFIP (now ARCA) through its web services, which return the CAE (Electronic Authorization Code) that gives the receipt validity. Doing it manually in the portal is slow; doing it via API, embedded in your workflows, makes every sale authorize itself. This guide reviews what you need and how to automate it with Floogos.
Note: this article is a general technical guide, not tax advice. Always validate the current requirements with the AFIP/ARCA or your accountant.
- Authority
- ARCA
- CAE
- 75123456789012
- Tax
- IVA 21%
- Delivery
- XML + PDF
Key concepts in 30 seconds
Gather what you need
Before issuing via API, have your certificate and data in order:
- Issuer CUIT and tax data
- Digital certificate and its private key to authenticate
- A point of sale enabled for web services
- The receipt types you'll issue (A, B, C...)
💡 Tip: start in the AFIP's homologation environment. You request test CAEs before issuing in production.
Authenticate (WSAA → token)
Access to the web services requires a session token:
- You sign the request with your certificate
- The WSAA returns a token and an access signature
- That token authorizes the calls to the WSFE
- It expires; renew it when it does
💡 Tip: reuse the token while it's still valid instead of requesting a new one per invoice; it's more efficient.
Build the receipt
With the sale's data, the authorization request is prepared:
- Issuer, receiver and amount detail
- VAT (21% or other rates) and totals
- Point of sale, receipt type and consecutive numbering
- Data per type (A, B, C) and the receiver's condition
💡 Tip: respect the consecutive numbering per point of sale and type. A gap or repeat causes rejection.
Request the CAE (WSFE)
Here's where authorization happens: the AFIP validates and responds:
- You send the request to the WSFE with the access token
- The AFIP validates and returns the CAE and its expiry date
- With the CAE, the receipt is now valid
- If there are observations or rejection, the reason is returned
💡 Tip: keep the CAE and its expiry with the receipt. They're data that must appear on the invoice.
Delivery and notes
You close the cycle by delivering the invoice and handling adjustments:
- Generate the representation (PDF) with the CAE and the barcode/QR
- Send it to the customer and archive it
- Credit note for returns/voids; debit note for charges
- Notes also request their own CAE
💡 Tip: the printed representation must include the CAE, its expiry and the QR. Automating its generation avoids errors.
How you automate it with Floogos
In Floogos, the whole flow fits into a workflow. The Argentina invoicing node handles authentication, building and the CAE request; you connect the trigger and the data:
- 1A trigger starts the process (a sale, a form, an order in your ERP)
- 2The workflow builds the receipt with the VAT and totals
- 3The Argentina node authenticates (WSAA) and requests the CAE (WSFE)
- 4It receives the CAE and another node generates and delivers the PDF to the customer
- 5The receipt is archived with its CAE, with traces and insights per run
💡 The credential (certificate) is configured once and reused. As a workflow, you can issue in batches, retry rejections and notify errors automatically.
Frequently asked questions
What is the CAE?
The Electronic Authorization Code returned by the AFIP that gives the invoice validity. Floogos requests it automatically within the workflow and archives it with the receipt.
What do I need to issue via API?
Your CUIT and tax data, a digital certificate with its private key, a point of sale enabled for web services, and the receipt types to issue. With that, the Argentina node can already request the CAE.
Can I test before issuing real invoices?
Yes. The AFIP offers a homologation environment where you request test CAEs to validate your integration before production.
How do I void or correct an invoice?
With credit notes (for returns or voids) or debit notes (for charges), which also request their own CAE from the AFIP.
E-invoicing in Argentina doesn't have to depend on the portal and manual work. With the CAE request via API embedded in your processes, every sale authorizes, is delivered and archived, with full traceability. Floogos turns authentication and authorization into a node in your workflow; you focus on selling.
Official sources
General technical guide, not tax advice. Requirements verified against official sources; always check the current regulations with ARCA (formerly AFIP) or your accountant.