Electronic invoicing that never stops your till.
Kubrik POS talks directly to ARCA's web services, with no middleman. Every sale gets its CAE in seconds. If ARCA goes down, the till switches to CAEA contingency on its own, keeps selling and reports later. A voucher is never issued twice.
One sale, from the till to ARCA, in six steps.
This is what happens every time the cashier presses F9. It runs on its own, in seconds, and every step leaves a trace. Click a step to see it, or let it play.
The log data is an example. The calls and service names are ARCA's real ones.
An outage never ends in a duplicated invoice.
The risky moment is when ARCA doesn't answer: it may have authorized, or not. Kubrik never resends blindly. It asks first.
ARCA doesn't answer in time
Each call gets 12 seconds. If it times out, the voucher is left "pending" and recovery looks up that exact number at ARCA. If it was authorized, it checks amount, date and processing time before claiming it.
Two tills on the same point of sale
If two tills ask for the same number at once, ARCA answers 10016 or 502. Kubrik discards its attempt, asks for the last number again and resends once.
ARCA rejects the voucher
The cashier sees ARCA's code with a clear message and the number is released. If the point of sale isn't enabled at ARCA, the message says what to do. Data errors are stopped before sending.
Automatic recovery
Every 2 minutes a job reviews pending vouchers and settles them against ARCA. It spaces attempts by age, from 2 to 60 minutes, so it never floods ARCA.
And when a person is needed
The manager has a recovery screen: retry, reconcile by typing the real CAE, void, or reopen the sale. Reopening is only allowed when there is proof ARCA authorized nothing.
ARCA goes down. Your till keeps selling.
CAEA is a code ARCA grants per fortnight to issue vouchers offline. Kubrik requests it, enters contingency, returns from it and reports what was issued, all on its own. Try it: cut ARCA off and see what the cashier sees.
If there's no valid CAEA or the branch has no contingency point of sale, the till doesn't improvise: it blocks and tells the cashier why.
The right letter, without the cashier thinking about it.
The letter follows from your VAT status and the customer's. Pick a combination.
Customer ID (RG 5616)
Every voucher declares the receiver's VAT status. CUIT and CUIL are checked with their check digit and DNI by length. From the threshold the rule sets, configurable and $10,000,000 by default, a final consumer must be identified, and the till asks before charging.
VAT and other taxes
Rates of 0%, 2.5%, 5%, 10.5%, 21% and 27%. Exempt and non-taxed go in their own boxes. Discounts are spread across rates. IIBB, VAT and municipal withholdings, plus the CABA IIBB regime per branch.
A voucher that complies
VAT status legends, start of activities, the VAT-content block of Law 27,743 and the Monotributo legend. Credit notes cite their invoice. In homologation the voucher says it isn't valid, so nobody gets confused.
The QR ARCA requires, built from what was declared.
The QR is never recalculated: it comes from what was sent to ARCA. If a field is missing, the voucher says "No verification code" instead of printing a wrong QR.
"E" means online CAE. In contingency the same QR carries "A" and the CAEA code.
From CUIT to first invoice, without leaving Kubrik.
Everything is set up from the POS "Fiscal configuration" screen. The only things done on ARCA's website are uploading the certificate request and enabling the points of sale.
Company tax data
CUIT with check digit, VAT status, gross income tax and start of activities. Kubrik won't issue if anything is missing.
Certificate request generated by Kubrik
Kubrik generates the key and the request (CSR). The private key never leaves the server and is encrypted with AES-256-GCM. You only handle public files.
You upload the request to ARCA
At ARCA you link it to the electronic invoicing service (wsfe) and download the signed certificate.
You load the signed certificate
Kubrik pairs it with its key and rejects it if it doesn't match. The screen shows how many days are left before it expires. There's one certificate per environment.
CAE and contingency points of sale
You add the online point of sale and the CAEA contingency one. The "Verify" button asks ARCA whether they're enabled, before you sell.
You test in homologation, then go live
One button issues a $1,000 test invoice against ARCA's test environment, and the till shows a "HOMOLOGATION" band. When you're ready, you promote to production. The environment can't be switched while tills are open.
For your accountant and your tech team.
| Voucher | ARCA code |
|---|---|
| Invoice A | 1 |
| Invoice B | 6 |
| Invoice C | 11 |
| Credit note A | 3 |
| Credit note B | 8 |
| Credit note C | 13 |
| What | Value |
|---|---|
| Wait per call to ARCA | 12 s |
| WSAA access ticket | about 12 h, encrypted cache |
| Entering contingency | 3 failures over 5+ min |
| Checking ARCA is back | every 2 min |
| Pending recovery | every 2 min, spaced up to 60 min |
| CAEA request | automatic, from 5 days before |
| CAEA report | daily, 6 am–10 pm, batches of 250 |
| Email delivery | queue with up to 6 attempts |
| WSAA | loginCms |
| Online CAE | FECAESolicitar · FECompUltimoAutorizado · FECompConsultar |
| CAEA | FECAEASolicitar · FECAEAConsultar · FECAEARegInformativo |
| Availability and points of sale | FEDummy · FEParamGetPtosVenta |
10016 · 502two tills at once: retries once
10004 · 10005 · 11000 · 11002point of sale not enabled
15006 · 15008CAEA window and CAEA already granted
703gap or duplicate in the report
TAlive WSAA ticket lost: explained without blaming the certificate
Invoice with ARCA from day one.
Kubrik POS ships with the ARCA integration ready. See how it charges with Mercado Pago too, or go back to everything the POS does.