SUNAT is changing the XML almost monthly, so there are many new SAP notes on Peru electronic invoice to implement to keep your solution updated.
It is known that SUNAT have determined the mandatory use of the new UBL 2.1 version in electronic invoice from September 2019, but this is just an example.
What is the UBL Format? the UBL (Universal Business Language) format is intended to simplify the automation of financial information exchange using XML.
The types of documents that must have this new UBL 2.1 format are invoices, Boletas, credit and debit notes. This change will improve the quality of information and have a better order in the market.
These are some examples of the corrections and enhancements released by SAP in the last two years just for Peru electronic invoice – Document Compliance solution:
- Filling billing document reference in Boletas Summary.
- Withholding and collection tax certificate AIF mapping corrections.
- Change for UBL 2.1 Payment Terms.
- Proxy changes to enable Invoice solution for UBL 2.1.
- UBL 2.1 mapping corrections for eDocuments.
- Reading incorrect reference date for FI void documents.
- Full screen XML display in eDocument Cockpit.
- eInvoice and Boletas Summary Exception Handling
Also, now customers are using online boletas, summarized are also supported but people do not like it because the error handling in the summary is very difficult.
The latest XLS from SUNAT with requirements and validations is here (June 2021):
For LATAM companies running SAP ECC or S/4HANA, Origen’s Document Compliance offering can help to use a single SAP Platform for LATAM for e-invoicing and other electronic documents like withholding certificate, delivery note, payment complement, etc.
Know more about Peru electronic invoice: click here.
