Blog
SIATSeptember 20, 2026· 5 min
SIAT contingency: what happens when your till loses the internet
Significant events, packages and CUFD explained without jargon, and how a well-built POS keeps selling when the SIN doesn't respond.
It’s Friday night, the store is full and the internet goes down. For many Bolivian businesses that ends with a stalled line and a cashier writing sales on paper. It doesn’t have to.
Online doesn’t mean “always connected”
Under SIAT online invoicing, each invoice is sent to the tax authority (SIN) for validation. But the regulation assumes the connection can fail, on your side or theirs. That’s what contingency is for.
The three pieces to understand
- Significant event. The formal record that something went wrong: an internet outage, an SIN service failure or a power cut, among others. It’s declared with a start and an end.
- Offline issuing. During the event you keep issuing invoices with their CUF and QR code, signed and ready. They just haven’t reached the SIN yet.
- Packages. When the connection returns, invoices issued during the event are grouped into packages and sent for validation.
What MKA does for you
- If the SIN doesn’t respond, the sale is issued in contingency and queued locally.
- The significant event is recorded with its times.
- When the connection returns, packages are built and sent in the background while the cashier keeps selling.
- You’re alerted before your CUFD or CUIS codes expire.
Try it
On the POS page you can ring up a sale, cut the internet with one button, ring up another and watch the package go out when you restore the connection.