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.
With micro, small, and medium-sized enterprises now fully incorporated, both issuing and receiving CPE becomes mandatory for the entire Peruvian taxpayer base, B2B and B2G alike.
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.
Choosing the correct CPE type for your specific transaction is critical — the wrong type can undermine your ability to deduct expenses or claim tax credits, not just create a paperwork headache.
These are formal, specific document names defined in regulation — get the label as well as the content right.
The exact retention obligation varies slightly by taxpayer regime — confirm your specific rule rather than assuming a flat 5-year figure applies uniformly.
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.
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.
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.
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.