ARCA e-invoicing: what your management system needs

If your business invoices in Argentina, at some point your system needs to talk to ARCA (formerly AFIP). It isn't optional, and getting it wrong causes real problems: rejected vouchers, customers with badly issued invoices, or worse, a system that goes down right when ARCA is having a slowdown.

Here's what we've found needs to be solved, after integrating it into several real systems — Narella, La Fiat de San Justo and Bookear, among others.

Voucher types matter from the design stage

Invoicing as a registered taxpayer (Invoice A/B) isn't the same as invoicing as a monotributista (Invoice C), and you need to add credit and debit notes for when something gets canceled or adjusted. The system needs to know, based on who the customer is and what tax regime the business operates under, which voucher type applies — automatically, not as a manual decision someone might get wrong.

The CAE isn't a technical detail, it's what makes the invoice valid

The CAE (Electronic Authorization Code) is what makes an invoice legally valid. It's requested from ARCA at the moment the voucher is issued, and if that request fails — say, if ARCA's service is slow or down — the system needs to handle that error gracefully, not break in the middle of a sale.

At a counter point of sale (like the one we built for La Fiat de San Justo), this is critical: if invoicing gets stuck because ARCA isn't responding, the entire sale stalls. A good system has a contingency plan for that moment.

The QR code is mandatory, and it has a specific format

For a while now, every tax voucher in Argentina needs a QR code with specific data about the issuer and the voucher. It's not enough to "put any QR code" — it has to follow the format the tax authority requires, or the voucher gets flagged.

Multi-warehouse, multi-branch: invoicing needs to know where each sale comes from

If your business has more than one point of sale or warehouse, voucher numbering and invoicing logic need to respect that structure. It's a detail that, if not thought through from the system's design, is painful to fix later.

What a well-integrated system should give you without asking

• Automatic issuance of the correct voucher type based on the customer
• CAE and QR generated with no manual intervention
• Error handling that doesn't stop the sale if ARCA has a brief slowdown
• Reports that make tax filing easier afterward, not a separate spreadsheet you have to build by hand

If you already have a system but invoicing is still manual

It's one of the automations that pays for itself the fastest: eliminating manual invoice entry reduces errors and frees up time at the counter. If your current system doesn't have ARCA integrated, it's a good candidate for a first project — starting small, with something specific, is exactly what we recommend instead of tackling everything at once.

Does your current system invoice by hand, or is ARCA badly integrated? Tell us about your case and we'll size the real work involved.