October 1 SFE Deadline: A Final Checklist for Groups 9–12

On 25 March 2026, the Servicio de Impuestos Nacionales published RND No. 102600000007, moving the compliance date for the ninth, tenth, eleventh and twelfth groups of taxpayers from 1 April to 1 October 2026. That resolution is the reason a lot of Bolivian businesses stopped thinking about this in March.

It is now ten days out, and the SIN has been clear that no further postponement is coming. From 1 October, taxpayers in these groups must issue their fiscal documents exclusively through their assigned online modality — facturación electrónica en línea, facturación computarizada en línea, or the portal web en línea. The parallel track that allowed manual or computarizada invoicing alongside the new system closed on 30 March.

If you are in scope and not yet issuing, the remaining work is not large. But it has a sequence, and several of the steps depend on the SIN responding to you, which is the part you cannot compress.

First, confirm you're actually in scope. Group assignment is per-NIT and is published by the SIN — it is not something you infer from your company's size or sector. Check your group in the Oficina Virtual before assuming either that you're covered or that you're not. Businesses have discovered in both directions late in the process.

What has to be in place

Six things, roughly in this order. The first three involve the SIN and have lead times; the last three are yours to control.

An active NIT with current dataAddress, economic activity, and legal representative all have to match reality in the padrón. Mismatches here surface later as rejected documents, and correcting them mid-process costs days you don't have.

Your digital certificateIssued by an authorised certifying entity, tied to the legal representative. Certificates are not instant — identity verification takes time, and this is the single most common reason a business misses the date.

CUIS and CUFD from SIATThe Código Único de Inicio de Sistemas is requested once; the Código Único de Facturación Diaria is requested every day and expires. Any system you use must handle CUFD renewal automatically, because a stale CUFD stops invoicing entirely.

Products mapped to SIN activity and product codesEvery item you sell needs the correct código de actividad and código de producto SIN. This is tedious, it's usually left to last, and it's where most first-attempt rejections come from.

A tested issuance flowIssue real documents in the SIAT test environment until you have a clean run across your actual transaction types — not just the simple sale, but the credit note, the exempt line, and the client without a NIT.

A contingency plan that someone has rehearsedWhen SIAT is unreachable you invoice offline under contingency and transmit within the permitted window. Deciding how that works at 11am on a Tuesday with a queue at the counter is not a plan.

The transaction types that catch people out

A business can test successfully and still fail in week one, because the test covered the easy case. Before 1 October, confirm you can correctly issue each of these:

Sales to a client without a NIT — the document type and identification fields differ, and getting this wrong is common in retail and food service.
Credit notes and annulments. An invoice issued in error has two remedies with different tax consequences. Know which one your situation calls for before you need it.
Exempt or zero-rated lines, if you sell anything in those categories — a mixed transaction is not the same as an exempt one.
Invoices issued outside business hours, where the CUFD for the day may have rolled over.
High-volume bursts, if your business has them. A flow that works at four invoices an hour may not at eighty.

What non-compliance actually costs

The penalty conversation usually focuses on fines, but for most businesses the fines are the smaller problem.

⚠️ Three separate costs of missing the date

Formal sanctions — failure to issue a valid fiscal document can carry closure of the establishment, with a first offence typically convertible to a fine calculated as a multiple of the un-invoiced amount

Your clients lose their crédito fiscal — a document that isn't validly issued under the required modality is not usable by your B2B customers, which turns a compliance problem into a commercial one

You stop being able to invoice — the practical consequence, and the expensive one. No valid invoice means no collectable receivable

That middle row is worth sitting with. If you sell to other businesses, your invoice is an input to their tax position. A corporate client that discovers your documents aren't valid doesn't file a complaint — they find a supplier whose documents are. The compliance deadline is, for B2B sellers, effectively a commercial deadline.

If you're starting from zero today: request the digital certificate first, this morning, before anything else. It is the only item on the list with a lead time you don't control, and every other step can proceed in parallel once it's in motion.

A realistic ten-day plan

Days 1–2: Confirm your group in the Oficina Virtual. Verify padrón data. Initiate the digital certificate request.
Days 2–4: Choose and configure your issuance system. Request CUIS. Confirm daily CUFD retrieval is automatic.
Days 4–7: Map every product and service to its SIN codes. This is the longest task and the one most often underestimated.
Days 7–9: Test each transaction type listed above until clean. Train whoever actually issues invoices — not just the owner.
Day 10: Rehearse contingency mode. Write the offline procedure on one page and put it where the person at the counter can reach it.

Don't wait for 1 October to go live. If your system is ready on the 26th, start issuing on the 26th. Discovering a configuration problem on a normal Saturday is inconvenient; discovering it on the first mandatory day, alongside thousands of other businesses hitting SIAT at once, is not.

After the date

Compliance on 1 October is the start of an operating routine, not the end of a project. Three things become monthly:

The RCV — your Registro de Compras y Ventas is due by the 9th of each month, and it should now reconcile automatically against what you issued.
Certificate expiry — diarise it. An expired certificate stops invoicing as completely as a missed deadline does.
Contingency events — every offline period needs its documents transmitted within the window. Track them rather than trusting memory.

Businesses that treat 1 October as a finish line tend to meet it and then drift. The ones that come through cleanly are the ones that build the monthly rhythm in the same fortnight.

How Contably helps: Contably was built for the SFE rather than adapted to it. Certificate and CUIS handling, automatic daily CUFD renewal, SIN product-code mapping, contingency issuance with transmission tracking, and RCV generation are part of the product rather than add-ons — which is why onboarding is measured in days rather than weeks.

Get SFE-compliant before October 1

Contably is built natively for Bolivia's SFE — certificate handling, CUFD management, contingency mode, and RCV all included. Try it free for 30 days.

Start Free Trial →

The October 1 SFE Deadline: A Final Checklist for Groups 9–12

What has to be in place

The transaction types that catch people out

What non-compliance actually costs

A realistic ten-day plan

After the date

Get SFE-compliant before October 1

Start Your Free 30-Day Trial

You're on the list!