Odoo in Peru 2026: SUNAT, l10n_pe, and SMB rollout tiers

Odoo in Peru in 2026: what changes and why your current ERP can't keep up

Rolling out Odoo in Peru in 2026 is a story about SUNAT, not about software. Three regulatory windows close in parallel by July: SIRE for large taxpayers, new CPE validations, and mandatory electronic GRE. If "change the ERP or not?" is on the table, this article covers exactly what most teams miss.

A concrete example. Monday, 9:14 a.m. Your accountant calls: SUNAT flagged a SIRE mismatch for March, and you have 5 business days to respond. Inside the Odoo your previous partner configured in 2022, nobody on the team knows where the gap is, because a year of manual corrections sits between the l10n_pe setup and the real purchase ledger. This isn't a rare situation. It's the standard 2026 scenario.

What follows: what changed, what that demands of Odoo, and where the line runs between "an upgrade is enough" and "rebuild from scratch."

One-minute summary

• SUNAT is tightening three fronts at once in 2026: SIRE is mandatory for large taxpayers from January, new CPE validations from February, electronic GRE mandatory from June 30. Odoo configurations built in 2020–2022 almost never survive without intervention.
• l10n_pe in the Community edition covers electronic invoicing, electronic boleta, and basic PLE — but it does not cover real-time SIRE integration or the GRE detail. You need an OCA stack, a commercial extension, or custom work.
• Pricing reality in Lima: SUNAT audit — S/ 9,500 flat; rescue of a dead instance — from S/ 22,000; greenfield rollout — from S/ 38,000; BI layer on top of a running Odoo — from S/ 25,000.
• Only 4 Odoo Gold Partners in Peru in the official directory. Local SEO is nearly empty, but the real Odoo competitors in the SMB segment are Defontana, Siigo, ContaSIS, and SAP Business One.
• If you have between 50 and 500 employees and S/ 5–100M in annual revenue, Odoo Enterprise in 2026 almost always wins on TCO against SAP B1. It doesn't beat Siigo if you only need accounting plus an invoicer.

Why 2026: three parallel SUNAT requirements

Three regulatory storylines unfold in Peru in 2026 at the same time. Each one changes ERP requirements. All three land in the same six-month window: January through June.

SIRE (Sistema Integrado de Registros Electrónicos). Starting January 1, 2026, the RVIE (Electronic Sales and Income Register) and RCE (Electronic Purchase Register) are mandatory for all large taxpayers (PRICO). SIRE replaces the old PLE on the sales and purchase side: data flows through the SUNAT portal in near-real time instead of periodic.txt uploads. For medium and small businesses the deadlines are staggered, but if revenue crosses the threshold, 2026 is the year.

New CPE validations starting February 2026. SUNAT updated the XML validation rules for electronic invoices and boletas. Behavior changes around the sustento fields, document type, recipient RUC validation, and tax regimes. An l10n_pe setup that worked fine through 2024–2025 starts returning errors in April.

Mandatory electronic GRE — extension to June 30, 2026. The electronic transport waybill (GRE) was mandatory for most taxpayers from late 2024, but SUNAT extended physical-waybill use for several categories through June 30, 2026. Translation: the first half of 2026 is the last transition window. Starting July 1, no more physical waybills.

When a Peruvian SMB actually needs Odoo

Not every business needs Odoo. If you have 8 employees, an outsourced accountant, and under S/ 1.5M in revenue, Siigo or Alegra is probably enough. Odoo's real zone in Peru is the pequeña / mediana band per INEI: companies with revenue between 150 and 2,300 UIT (~USD 200k–3M). According to OECD and Statista data, that's about 3% of formal companies — roughly 50,000 firms nationwide, 45% of them in Lima. Out of that slice, Odoo solves one of five scenarios:

1. Outgrew Excel + an invoicer. The accountant builds manual summaries, no sync runs between ContaSIS / Concar and the invoicer API, and warehouse lives on its own. Numbers don't match once a month.
2. SAP Business One on the books. Licenses, local partner, add-ons — S/ 200,000–600,000 a year. The math in Excel is already done: Odoo Enterprise is at least 2.5× cheaper. Migration fear is the only thing stopping you.
3. Odoo is already running, but someone else configured it 2–4 years ago. SIRE returns errors. The accountant patches by hand every month. Nobody on the team knows whether the module or the configuration is broken.
4. Need analytics on top of Odoo. Out-of-the-box reports don't deliver what's needed: real-time margin by SKU, cohort customer analysis, cash forecasting. A BI layer is required — ClickHouse, Metabase, Superset, or Power BI over ODBC.
5. Need a second opinion on the current partner. Suspicion of overpricing or that the setup won't survive an audit. A paid audit is the way to get an independent technical assessment.

The engagement format differs by scenario. Details below.

Odoo localization for Peru: what l10n_pe covers and what it doesn't

The l10n_pe localization module ships the baseline without which an ERP doesn't run in Peru. Here is the 2026 picture.

Out-of-the-box coverage:

• Peruvian chart of accounts (l10n_pe.chart_template), aligned with the PCGE (Plan Contable General Empresarial).
• Document types: electronic invoice, electronic boleta, credit note, debit note, fee receipt.
• RUC handling, RUC format validation, tax-regime types.
• IGV 18% calculation, withholdings, and detractions (basic scenarios).
• .txt file export for PLE (Programa de Libros Electrónicos).
• Through l10n_pe_edi: electronic exchange with SUNAT and the PSE (Electronic Service Provider).

Not covered out of the box (requires OCA, commercial extension, or custom development):

• Near-real-time SIRE integration. Base l10n_pe emits.txt for PLE; the new SIRE demands direct API integration with the SUNAT portal. That's the OCA l10n_pe_sire module (if it exists when you read this), a commercial partner layer, or in-house work.
• GRE (electronic transport waybill). From July 2026 the GRE is the only valid transport document. You need PSE integration or direct SUNAT API, generating XML per the GRE specification.
• SIRE-RCE reconciliation. To avoid mismatches between the SIRE purchase ledger and Odoo's, a cross-check mechanism is required. Community doesn't have one.
• February 2026 CPE validations. l10n_pe updates land first on Odoo 17 and 18. On Odoo 15 and 16: late and incomplete. On Odoo 13–14: not at all. If you're on an old version, that's the first risk.
• Detractions and percepciones automation by operation type. The baseline is configured by hand through taxes; automation is custom.

Minimum production-ready stack for Peru in 2026: Odoo Enterprise 17 (or Community 17 + OCA), l10n_pe as the base, l10n_pe_edi for electronic exchange, plus a SIRE connector, a GRE connector, and a BI layer (Metabase or ClickHouse + Superset).

Odoo version matters. If you're on Odoo 13 or 14 today, that's the first risk to close — before SUNAT problems even surface.

Odoo vs alternatives in Peru: an honest comparison

In the Peruvian SMB segment Odoo's real competitors aren't other international ERPs — they're local and regional products:

Key insight: Odoo wins on TCO from ~30 employees up when accounting, warehouse, sales, CRM, HR, and projects are needed together. Siigo wins if only accounting and an invoicer are needed. SAP B1 wins in exactly one scenario: when the parent company abroad mandates SAP as a group standard.

Service tiers and pricing in S/

Four fixed tiers, real ranges from the last 12 months. The audit is flat-fee; the rest follows diagnosis.

#1. Odoo SUNAT audit — S/ 9,500 flat, 2 weeks

A 40-page report: module inventory, inconsistencies, SUNAT risks against a 47-point checklist, step-by-step remediation plan. If you move to a paid engagement, the S/ 9,500 are credited.

#2. Odoo rescue — from S/ 22,000, 4–8 weeks

When Odoo is already installed but the configuration is bent, or the previous partner walked away. Not a migration: a repair of the existing instance — customization cleanup, configuration normalization, SUNAT tests, documentation.

#3. Greenfield rollout — from S/ 38,000, 8–16 weeks

Process analysis, 8–12 modules, data migration from SAP B1 / NetSuite / Siigo / ContaSIS / Excel, SUNAT day 1 (SIRE + FE 2.1 + boleta + PLE), three-tier training, 60-day hypercare with <4-hour SLA during Lima business hours.

#4. Odoo + analytics layer — from S/ 25,000, 4–6 weeks

For an Odoo that's already running and needs BI: ClickHouse + Superset / Metabase, OLAP cubes, CFO dashboards, ML models (forecasting, churn, scoring) where they pay back.

These are ranges, not final quotes. The final number lands after diagnosis.

Three configuration mistakes SUNAT catches in 2026

From 2024–2025 audit work, these three repeat more than anything else.

Mistake 1: sales and purchase ledgers don't match the SUNAT portal. SIRE automatically cross-checks what PSEs send against what arrives from Odoo via PLE. Mismatches of S/ 10,000–50,000 per month is the typical picture. The cause is almost always boletas without a recipient RUC, which Odoo classifies differently than SUNAT expects. The fix is correct document-type setup and tax mapping.

Mistake 2: voucher series numbering isn't consistent between Odoo and the PSE. Particularly painful when the POS runs separately from Odoo. POS uses series B001, accounting assumes F001, both land at SUNAT — the register breaks. The fix is syncing through a single Odoo Sequence and locking out manual edits.

Mistake 3: GRE pending items on the June 30, 2026 cutover. Plenty of SMBs don't grasp that June 30 is a hard deadline. They keep moving goods on the physical waybill until the last day; on July 1 they have neither a GRE configuration nor a PSE test environment. The business stalls for 1–2 weeks until the rollout finishes. Especially painful for logistics, agribusiness, and retail with their own distribution centers.

Anonymous case: textile SMB in Lima

Context. Textile company, ~180 employees, exports to the US. SAP Business One v9.2 since 2017. Three consultancies rotated through over 6 years; each one added its own patches. By mid-2025 the picture: monthly close at 14 days, SIRE mismatched against the purchase ledger by S/ 12,000–40,000 per month, SAP B1 licenses + add-ons + local partner totaling S/ 480,000 a year.

What we did. A 2-week forensic audit (S/ 9,500). A 40-page report inventorying the mismatches. The decision: migrate to Odoo 17 Enterprise in waves, no big-bang. SAP and Odoo ran in parallel for three months; modules transitioned in phases.

Results five months after go-live (CFO numbers). Monthly close: 3 days instead of 14. License savings: S/ 280,000 a year — Odoo Enterprise plus hosting plus support costs less than SAP B1 with its partner. SIRE mismatches: zero since go-live. The accounting team shrank by 1.5 FTE, reassigned to analytics.

The biggest shift was a different one: at management meetings the conversation moved from "what do these numbers mean" to "what do we do about these numbers."

What to do next

If there's a compliance owner on the team, send them the SUNAT 2026 pillar — a detailed timeline by resolution. If you're a CFO who thinks in numbers, look at the Odoo vs Excel calculator and the SMB ROI benchmark.

Service tiers on their own pages:

• Odoo audit — S/ 9,500 flat, 2 weeks, 47-point checklist.
• Odoo rescue — from S/ 22,000, repair of an existing instance.
• Odoo implementation — from S/ 38,000, greenfield.
• Odoo + Analytics — BI and ML on top of a running Odoo.

Neighboring LATAM markets: Odoo in Chile, Odoo in Colombia, Odoo in Mexico, Odoo in Argentina.

Lead magnet: free SUNAT 2026 Checklist — 47 audit items, 28-page PDF, no long forms.

If you want a 30-minute diagnostic call, book it here. Lima time zone; in Spanish, English, or Russian.

Frequently asked questions