Peru runs one of the most mature electronic invoicing systems in Latin America, and also one of the most misunderstood by companies implementing Business Central Peru for the first time. The confusion usually starts with the acronyms: CPE, PSE, OSE, SEE. Each one refers to a different party or document in the validation chain, and missing any one of them means invoicing simply doesn't work.
How Peru's Electronic Invoicing Model Actually Works
Every electronic invoice in Peru is a Comprobante de Pago Electrónico (CPE), built as an XML file in the UBL 2.1 format under SUNAT's Sistema de Emisión Electrónica (SEE) framework. But a company doesn't send that CPE straight to SUNAT — it goes through a Proveedor de Servicios Electrónicos (PSE), which handles the technical construction and digital signature, and then an Operador de Servicios Electrónicos (OSE), which validates the document and issues a Constancia de Recepción (CDR) confirming it's legally valid.
Only once that CDR comes back is the invoice considered issued. For a Business Central environment, that means invoicing isn't a one-step process — it's a round trip through two external parties before a document is final.
The GRE and Other Document Types That Matter Beyond Invoices
Invoicing isn't the only document Peru requires electronically. Goods in transit need a Guía de Remisión Electrónica (GRE), mandatory since 2023, which follows the same OSE validation path. Credit notes, debit notes, and withholding or perception receipts each have their own structure and rules for when they're required.
PLE and the Reporting Side of Compliance
Invoicing is only one part of SUNAT compliance. Companies must also submit their accounting ledgers electronically through the Programa de Libros Electrónicos (PLE) on a monthly basis, in SUNAT's specific format. On top of that, transactions are frequently subject to detracciones, percepciones, and IGV/ISR retenciones — each with its own rules for when and how much applies, depending on the good, service, or taxpayer category involved.
What This Means for Business Central Projects
Put together, this creates a specific set of configuration and integration points for any Business Central Peru project:
- Maintaining a working PSE/OSE integration and correctly handling CDR responses
- Generating GRE documents automatically for shipments, not just sales invoices
- Exporting PLE-compliant electronic ledgers every month without manual rework
- Applying detracciones, percepciones, and IGV/ISR retenciones correctly by transaction type
- Adapting quickly whenever SUNAT updates its resolutions or document formats
Miss any one of these, and the risk isn't just a rejected document — it's a stalled shipment, a delayed collection, or a compliance gap that surfaces at audit time.
Common Challenges in Peru Implementations
Beyond the acronyms themselves, teams delivering Business Central Peru projects tend to run into the same handful of issues:
- Treating PSE/OSE integration as an afterthought instead of a day-one requirement
- Manually reconciling CDR responses instead of automating the round trip
- Missing GRE generation for transfer orders, not just sales shipments
- Calculating detracciones or retenciones with outdated rates or rules
- Falling behind on SUNAT resolution changes that alter document formats mid-year
Each of these is manageable on its own. Together, across hundreds of monthly transactions, they're exactly what turns a Business Central implementation from a straightforward rollout into an ongoing support burden.
Why the Right Localization Matters
A proper Peru localization automates the PSE/OSE round trip, generates GRE and PLE files without manual intervention, and keeps detraction and retention rules current as SUNAT adjusts them — built as an extension, with no changes to Business Central's core, so upgrades stay simple.
How LLB Solutions Supports Business Central Peru
covers SUNAT electronic invoicing, PLE electronic ledgers, detracciones, percepciones, and ISR/IGV withholdings — built as an AppSource-certified extension integrated with certified PSE/OSE providers.
Peru's three-party validation model is exactly the kind of detail that looks manageable in a requirements document and becomes a real operational challenge once transaction volumes climb. Companies that map out CPE, PSE, OSE, GRE, and PLE requirements before go-live avoid the scramble that comes from discovering them one rejected document at a time.
For Microsoft partners, understanding this model well enough to explain it clearly to a client is often what separates a smooth Business Central go-live from a project stuck fielding invoicing tickets in its first month of operation.
See how LLB Solutions' Peru Localization fits your Business Central project —