SUNAT UBL 2.1 electronic invoice
Peru’s UBL 2.1 electronic invoice and receipt documents with digital signatures, catalogues and SUNAT/OSE responses.
Current version and implementation status
How to recognize the profile
Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.
- UBLVersionID 2.1
- CustomizationID 2.0
- SUNAT UBLExtensions
- RUC
Production validation stack
- 1UBL schema
Confirm that the document is well formed and structurally compatible with the intended SUNAT UBL 2.1 syntax.
- 2SUNAT catalogues
Apply semantic and business-rule checks rather than accepting a file merely because it parses.
- 3Digital signature
Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.
- 4CDR acceptance or rejection
Apply the national, network or authority restrictions that narrow the base syntax.
Common errors and corrective action
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.
Countries using or referencing this profile
Questions people ask
What is SUNAT UBL 2.1?
Peru’s UBL 2.1 electronic invoice and receipt documents with digital signatures, catalogues and SUNAT/OSE responses.
How is SUNAT UBL 2.1 validated?
A production check normally applies UBL schema, SUNAT catalogues, Digital signature, CDR acceptance or rejection. Local browser preflight cannot replace the official validation artefacts or authority outcome.
Which version should I use?
The current research note is: UBL 2.1 guides and current SUNAT catalogues. Confirm release notes at the official source before production deployment.
Inspect and prepare SUNAT UBL 2.1 files
Technical invoice preflight
Check parseability, core fields, identifiers and arithmetic before submission.
Invoice code-list checker
Check common currency, country, tax-category and payment-means codes.
Signature metadata inspector
Locate XML signature, certificate and digest metadata without claiming cryptographic validity.
Authority and network response decoder
Extract status, identifiers, error codes and messages from common JSON or XML invoice responses.