SIFEN 2026 in Paraguay: when your SME falls under the mandate

One-minute summary

On January 2, 2026, DNIT switched SIFEN on for every contractor that bills the Paraguayan state. Group 15 went live on March 2; group 18 lands on December 1. If you still don't know which group you're in, that's not a process — it's a problem. Electronic timbrado registration takes 5-10 business days, and DNIT fines for issuing a paper invoice in violation of the mandate reach PYG 30M+ for systemic breaches (≈ USD 4,700 at the April 2026 exchange rate). In 15 minutes we settle whether your SME is in scope and what to do next.

• Effective January 2, 2026, SIFEN is mandatory for every state supplier — DNIT General Resolution N.° 41/2025.
• Groups 15-18 cover March through December 2026: four compliance-panic windows in a single calendar year.
• Paraguay runs on two platforms: e-Kuatia (mid-to-large, custom integration) versus e-Kuatia'i (micro-issuer via the DNIT portal).
• Technical minimum: digitally signed XML + 44-digit CDC + asynchronous validation through DNIT.
• Electronic timbrado registration = 5-10 business days. Miss it — invoicing is fully blocked.
• The OCA l10n_py module covers the chart of accounts, but not SIFEN XML, KuDE, or CDC — you need a PSP or a custom module. Set against the broader Odoo-in-Paraguay picture, this is the piece that eats the most time.

Where SIFEN comes from and why 2026 is the hinge year

SIFEN — Sistema Integrado de Facturación Electrónica Nacional — is Paraguay's electronic-tax backbone. The framework is set by Decree N.° 7,795/2017; the operator is DNIT (Dirección Nacional de Ingresos Tributarios), formed in 2024 by merging SET and Aduanas.

Since 2019 the rollout has been phased: groups 1-14 closed by year-end 2025. In 2026 the final mass deployment arrives, with four hard dates:

• Group 15 — March 2, 2026
• Group 16 — June 1, 2026
• Group 17 — September 1, 2026
• Group 18 — December 1, 2026

In parallel, a separate rule took effect: General Resolution N.° 41/2025. Starting January 2, 2026, SIFEN applies to every state supplier — regardless of size, revenue, or assigned group. The overlap stings: if you hold a contract with any public body, the cutoff is January 2, not your scheduled group date.

The macro backdrop adds pressure: the Central Bank projects 4.2% growth for 2026, the economy is expanding, and the share of SMEs supplying the state is rising with it. If you want a regional comparison, see DIAN 2026 (Colombia) or SII 2026 (Chile) — the compliance load is in the same ballpark.

SIFEN Groups Finder: identify your group in 15 minutes

DNIT does not publish a public registry of «company X = group Y». Group assignment is individual and lives inside Sistema Marangatu (the taxpayer's private area). Four steps, one cross-check, and you have your cutoff date.

#1. Sign in to Marangatu

Access is at marangatu.set.gov.py — the domain survived the SET → DNIT rename. Authentication: RUC + fiscal password. If you lost your password, recovery is in-person at the DNIT office in Asunción (Edificio Ñanduty, Yegros 437).

#2. Open the «Adhesión SIFEN» section

Look for the section labelled «Adhesión al SIFEN» or «Facturación electrónica». The system shows one of three states:

• Habilitado — already operating in SIFEN.
• Pendiente — on the schedule, with group and date visible.
• No designado — no group yet. Warning: if you hold a contract with a public body, Resolution 41/2025 applies anyway.

#3. Cross-check: do you have state contracts?

If you hold any contract with a public body (ministry, IPS, MOPC, municipality, ANDE, ESSAP), you are bound starting January 2, 2026 — regardless of what Marangatu says about your group. Resolution 41/2025 allows no exceptions by amount, frequency, or industry.

#4. Issuer type: e-Kuatia or e-Kuatia'i

Once your group is assigned, DNIT also sets your issuer type:

• e-Kuatia'i — for micro-issuers. Free issuance via the DNIT portal, with practical volume limits and minimal complexity. It fits operations up to ~PYG 720M of annual revenue (≈ USD 113,000).
• e-Kuatia — for mid-sized and large. Custom integration via ERP or a certified PSP, no operational ceiling.

The real boundary is not just the amount — it's complexity. If you handle more than 50 counterparties a month, B2B XML integrations, or custom DTE fields, you belong on e-Kuatia even if your revenue is below the threshold.

Mandatory electronic documents

From 2026, electronic timbrado is also enforced — series and numbering are assigned by DNIT at adhesión, ending the paper-timbrado era.

Technical requirements: what to actually implement

The compliance minimum is not negotiable. Six pieces must work:

1. Qualified digital signature — issued by Paraguayan certifying centers (Documenta, eFirma). Cost: USD 100-300 per year.
2. XML DTE generator compliant with SIFEN schema v150 (in force for 2026; details in Gosocket's reference).
3. 44-digit CDC calculation (Código de Control) per the DNIT algorithm.
4. DNIT web-service integration (sifen.set.gov.py) — XML submission and approval/rejection protocol.
5. KuDE — graphical representation of the DTE handed to the customer (PDF with QR code).
6. DTE custody for no less than 5 years.

For Odoo, the lay of the land is this: the OCA l10n_py module covers the accounting base, but leaves SIFEN itself out — no XML, no KuDE, no CDC. Most local partners run private extensions that never make it to OCA. The fast path is a PSP (Edicom, Sovos, Gosocket, Documenta): they generate the XML on their side and Odoo sends data via REST API. Typical cost: USD 0.05-0.15 per DTE. If you want to map exactly what's missing in your stack first, an Odoo audit is the cleanest starting point.

When SIFEN runs clean and when it doesn't

Not every SME will feel this the same way. Three scenarios where the rollout runs cleanly, three that require rewriting the plan, and two the standard doesn't cover.

Runs clean:

• You're an e-Kuatia'i issuer with simple operations (one location, up to 50 DTEs per month) using the DNIT portal directly — free and minimal setup.
• You run Odoo 17+ with a certified PSP integration: XML on the provider's side, Odoo pushes structured data. Fastest path for an SME with USD 100k-2M in revenue.
• One DTE type (invoice only) and a standard workflow — the base localization plus a custom module covers about 80% of the scenario in 4-6 weeks.

Rework needed:

• Complex B2B cycle (multi-site deliveries, partial deliveries, intercompany) — NRE is required, plus custom sync logic between Odoo transfers and SIFEN.
• Purchases from individuals without RUC (producers, freelancers, farmers) — electronic self-invoice (AFE) is non-standard and requires extending the base localization.
• Accounting outside Paraguay (consolidation in a RU/US/ES parent) — you need an XML bridge between the PY instance and the parent; in practice a 4-6 month project.

Standard does not cover:

• Maquila and free-zone — special DTE types with DNIT-specific validations. l10n_py does nothing here; expect a custom build (USD 15k+). The segment is growing too: the IFC Country Private Sector Diagnostic documents the expansion of Paraguay's export-oriented maquila.
• Banking, insurance, telco — distinct DTE types (sales receipt, special vouchers) with overlaps into BCP/CONACOM. Bespoke implementation, not standard.

3 typical SME mistakes when moving to SIFEN

#1. Pushing the calendar to the deadline

Most group-15 SMEs only learn about the requirement in February 2026 — and they don't make it. Timbrado registration: 5-10 business days. Test-environment QA: 2+ weeks. Production setup: 1+ week. That's one month of clean cycle minimum, 2-3 months realistically with fixes. The fallout: from the deadline forward, any invoice issued outside SIFEN is invalid, the 10% IVA is not creditable to the buyer, and the formal fine starts at PYG 2.4M (≈ USD 380), scaling with the volume of breaches.

#2. Assuming stock l10n_py is enough

The OCA module covers the chart of accounts — it does not cover SIFEN XML, KuDE, or CDC. Teams that install l10n_py and consider the problem solved find out otherwise when they issue their first invoice and DNIT rejects it. The «we have Odoo, we're localized» mindset is a myth in Paraguay — unlike Peru or Chile, where the OCA localization is much closer to actual compliance. The operational detail is laid out in LLB Solutions' SIFEN 2026 guide. Typical fallout: discovered a week before go-live, emergency PSP hunt, 2-3× overpayment for rush implementation.

#3. Ignoring Resolution 41/2025

An SME delivering a «one-off PYG 5M service» to the Asunción municipality assumes the resolution doesn't reach it. It does. The rule sets no threshold by amount, frequency, or sector — every state contractor is in scope. The fallout: the public body does not pay until it receives a validated electronic DTE. A 30-90 day cash-flow gap is fatal for an SME running on thin margins.

Anonymous case: logistics firm in Asunción, ~40 employees

December 2025. A logistics SME, MOPC contractor, USD 1.8M annual revenue. Invoicing on paper with Excel spreadsheets. The DNIT calendar assigned group 16 (June 1, 2026). Management's reasoning: «we have six months, no need to rush».

What actually happened:

1. The December 2025 audit surfaced the double-lock: an active MOPC contract → Resolution 41/2025 forced compliance from January 2, not June 1.
2. Decision: Odoo 17 + certified PSP integration.
3. Three parallel tracks: finance built the chart of accounts and tax setup; IT integrated the REST API against the PSP; operations ran KuDE training.
4. Go-live: December 28, 2025 — 5 days before the deadline.

Three-month outcome:

• The MOPC contract was not interrupted — DTEs started flowing on January 2, with no payment pause.
• Invoice issuance time: 8 minutes (manual) → 30 seconds (Odoo + PSP).
• Customer-data errors: 5% → 0.2% (RUC validated against the DNIT API).
• Operational savings: ~80 person-hours per month on invoicing and reconciliation.

Case anonymized, figures rounded. Similar scenarios for SMEs with state contracts are typical of Q1 2026.

If your SME matches this profile, it's worth front-loading the roadmap: the Odoo implementation guide spells out phases, timelines, and budget bands.

Download the SIFEN Groups Checklist 2026

We put together a 24-point checklist: how to identify your group, hit the adhesión window on time, and avoid the fine. Decision tree for e-Kuatia vs e-Kuatia'i, list of documents for adhesión, technical requirements for Odoo, and a migration cost calculator.

Download the SIFEN 2026 Checklist (PDF) — delivered to your inbox, no spam.

Frequently asked questions