Country deep dive
Peru's rollout followed the classic Latin American pattern — largest taxpayers first, then a steady widening until essentially the entire economy was covered.
SUNAT starts requiring the largest businesses to issue Comprobantes de Pago Electrónicos, establishing the clearance infrastructure the rest of the economy would later join.
Earlier UBL 2.0 documents are no longer accepted — every CPE from this date must be structured according to UBL 2.1.
Large taxpayers with automated billing must use an authorised Electronic Services Operator (OSE) for validation, rather than relying on SUNAT's own free tools.
Peru operates one of Latin America's most mature e-invoicing systems. Electronic Payment Receipts (CPE) must be issued in UBL 2.1 XML, digitally signed, and validated by SUNAT or an authorised Electronic Services Operator (OSE) before they are legally valid.
Superintendency Resolution No. 000033-2026/SUNAT introduces a digital reporting system for commercial airlines providing scheduled passenger transport, replacing the older PDT No. 3540-based model with one aligned to the standard e-invoicing infrastructure.
CPE is a broad umbrella term — Peru covers far more document types under this single framework than most countries in this tracker.
Article 2 of the implementing regulation is explicit: only documents meeting all these technical characteristics simultaneously are legally valid — partial compliance doesn't count.
Vendor pages commonly say an INDECOPI-accredited certificate is required. INDECOPI accredits the certification entities behind Peru's signature framework, but we found nothing in SUNAT's own rules making that accreditation a condition of issuing.
SUNAT's own PDF of RS 097-2012 is a scanned image with no machine-readable text, so these rows rest on the Reglamento de Comprobantes de Pago and SUNAT's UBL guides rather than on the electronic-issuance resolution itself.
The exact retention obligation varies slightly by taxpayer regime — confirm your specific rule rather than assuming a flat 5-year figure applies uniformly.
Choosing the right CPE type matters — the wrong one can cost a deduction or a tax credit, not just cause paperwork. So does the label: these are formal document names fixed in regulation, not descriptions you may paraphrase.
Peru's model has a genuinely distinctive feature: OSEs aren't mere intermediaries — they carry the same legal validation authority as SUNAT itself.
This is worth internalising: an OSE's validation is legally equivalent to SUNAT validating it directly. But an OSE cannot validate delivery/transport documents — that distinction matters for logistics-heavy businesses.
Match your tier to your actual transaction volume and technical capacity — over-engineering a low-volume business onto a full OSE integration wastes effort that a free SOL portal account would have covered.
Just because the regulation permits sending an invoice before validation completes doesn't make it good practice — a subsequently rejected document creates real reconciliation problems for both parties.
The CDR (Constancia de Recepción) is Peru's equivalent of a clearance receipt — it's what confirms the document has full legal and tax validity, similar in function to Poland's UPO or Italy's Ricevuta di Consegna.
Verifying your provider's authorisation status matters more here than in most countries — unauthorised PSE/OSE providers issue documents with no legal validity at all.
Your Registro Único de Contribuyentes number and electronic-issuer registration with SUNAT are the prerequisites for everything that follows.
SEE-SOL for low volume, PSE for medium volume with external help, OSE for high volume with your own ERP, or SEE Facturador if you lack in-house development capacity.
This is what authenticates and signs every CPE you issue.
Check cpe.sunat.gob.pe before contracting — an unauthorised provider's output carries no legal tax validity, regardless of how correct the XML looks.
Confirm your system produces conformant output before your first production submission.
Every issued CPE needs its corresponding CDR retained alongside it — treat the pair as a single compliance record, not two separate files.
Wait for SUNAT/OSE validation before delivering to the buyer, even though the regulation technically permits sending first.
Peru's e-invoicing and e-reporting framework is described by practitioners as comprehensive and technologically advanced — the practical risk is invalidity, not just fines.
Other countries in the same region, ordered by their next dated milestone. Each links to a full briefing.