Automation · e-invoicing · 2026
The invoice issues itself.
The customer pays with Mercado Pago and, seconds later, has their Argentine electronic invoice (ARCA) in their inbox, with its authorization code (CAE) and QR. Nobody logs into the tax site or retypes an amount. This is how it works in Alhia, the management platform I built.
- 0
- invoices typed by hand
- 1
- CAE per payment, even if the connection drops
- A · B · C
- by the customer’s VAT status
From payment to invoice, in seconds
01
Payment
The customer pays with Mercado Pago: link, QR or card.
02
Verified notice
Mercado Pago reports the payment. The signature, the amount against the sale and the approved status are checked.
03
A single claim
The payment is recorded only once, even if Mercado Pago repeats the notice.
04
ARCA authorization
The invoice is requested via web service (WSFEv1), with the right type and letter.
05
PDF with QR
The invoice is built with the ARCA QR and emailed to the customer.
The problem
A business that gets paid through Mercado Pago has to invoice every payment: log into ARCA, pick the invoice type, copy the amount and customer data, and send the PDF. With dozens of payments a day it falls behind, uses the wrong letter or invoices the same payment twice.
What I built
The payment triggers the invoice. Mercado Pago reports the payment, the system verifies it, requests the CAE from ARCA with the business and customer data, and delivers the PDF. Everything is logged: what was paid, what was invoiced and with which CAE.
What cannot go wrong
Never two CAEs for one payment
The request to ARCA is logged before it goes out. If the connection drops halfway, the system asks ARCA whether the invoice already exists before requesting another.
The amount comes from the sale, not the notice
The amount and customer are taken from what was sold; a notice with a different amount or from another account is held for review instead of invoiced.
Approved payments only
A pending payment is not invoiced; once it is approved, it is, exactly once.
The right letter
Invoice A, B or C according to the VAT status of the issuer and the customer, including invoice A to small taxpayers.
Deposit and balance
If the customer paid a deposit and then the balance, each part is invoiced separately and the second does not repeat the first.
The counter by shift
QR payments at the counter are grouped into one invoice per cash shift, one line per shift.
The PDF is not stored
It is regenerated from the invoice data every time it is requested: no files with tax data lying around.
One ARCA per business
Each business delegates invoicing under its own tax ID and point of sale; the system never invoices with someone else’s data.
Built with
- Node.js
- PostgreSQL
- Mercado Pago webhooks
- ARCA · WSAA + WSFEv1
- PDF with QR
- Transactional email
Need it for your business?
It fits wherever you get paid with Mercado Pago: your online store (Tiendanube, WooCommerce or your own), payment links or the in-store QR. If you already invoice in ARCA, it connects to your same point of sale.
Tell me about your case