Peru: Document Receipt

1. OPERATION

Document receipt flow for Peru

1. The provider has the option to issue the document in two ways:
   1. The provider manually uploads the XML through Gosocket Upload (In the section Sending Method - Manual XML Upload the conditions to be considered when sending are explained).
   2. The provider sends the XML file through the exchange mailbox (In the section Sending Method - Exchange Mailbox the conditions to be considered for sending are explained).

Note: When the document receipt channels are used, both the exchange mailbox and manual XML upload via the

Upload option, both processes run the schema, signature, and validation against the ET (Tax Authority) checks.

2. The Gosocket portal handles the download and processing of this document. When it is a tax document, it enters a validation flow.

3. First, a schema validation is performed on the document to ensure it complies with the format established by the Tax Authority. Depending on the validation performed, one of the following results can be obtained:

   1. Failed: The document does not comply with the tax format, so it will be registered in Gosocket with rejected status and the red exclamation symbol will be shown in the icons , additionally, the reason for rejection is indicated in the document's notes.
   2. Successful: The document complies with the tax format, in which case it continues with the next validation.

4. It validates the electronic signature of the document, in order to ensure that it has not been altered. Depending on the validation performed, one of the following results can be obtained:

   1. Failed: This means that the document has been altered, so it will be registered in Gosocket with rejected status and the red exclamation symbol will be shown in the icons additionally, the reason for rejection is indicated in the notes.
   2. Successful: If the digital signature validation is successful, it continues with the next validation.

5. Finally, it is verified that the document is registered with the Tax Authority. From this validation, one of the following results can be obtained:

a.   Document not found (Failed)

• Indicates that the received document is not registered with the ET.
• In Gosocket it will remain with Not Available in ET status.
• The received documents query screen (Inbox) will show the icon .

If the document is not yet registered with the ET or there is unavailability of the query service, the Automatic Retries are performed as follows:

• The system performs 30 automatic attempts every 10 minutes.
• If after the 30 attempts the document is still not found, it will remain definitively in Not Available in ET status, showing the following icon in the Inbox.
• If during these retries the document is found, its status is updated and the process continues.

Note: For each query retry with the ET, a record is generated in the Notes section.

b.  Document Rejected by the Tax Authority

If the document exists in the ET, but there is a rejection reason at the Tax Authority, its status changes to Rejected and the icon is assigned to it .

c. Document has an internal exception by Gosocket ❗

When performing the validation query with the Tax Authority for the document and Gosocket fails to connect to the ET service or there are communication errors with the service, the document changes its status to ERROR and the icon ❗ is assigned to it .

d. Document found in the ET

If the document exists in the Tax Authority, the receipt flow continues.

6. If the result of the previous validations is satisfactory, the document is registered in Gosocket with Accepted status and the symbol is shown in the icons.

a. Options Button (Manually Reprocess Document)

Additionally, in Inbox a button was implemented that allows manually reprocessing tax documents that have “ERROR” status ❗ and  “Not Available in ET” .

This button allows a reprocessing of the different validations of the receipt process, and we will find it in the following path as applicable:

• Inbox/Received/Options/Actions/Reprocess document without validating schema.
• Inbox/Received/Options/Actions/Reprocess document without validating signature.
• Inbox/Received/Options/Actions/Reprocess document.

Accompanied by a selector that, as its name indicates, will allow independently selecting one Electronic Document or a set of them.

Within this menu you will find the Reprocess document option, which will allow the user to start reprocessing documents that were left in Not Available in ET or ERROR ❗ .

Next, a pop-up window will be shown in which the user must confirm that they want to revalidate the previously selected documents.

Once the reprocessing has been generated, a record will be shown for each retry obtained from the tax authority, and its record will remain in the document preview in the notes section as we see below:

When the document changes status at the tax authority, the status icon in the received documents grid reflects this change:

---

2. SENDING METHOD

As already indicated, the solution performs the processing of documents, where once the document is received, the validation process begins.

There are two ways to carry out the document receipt process in Peru:

a. Manual XML upload through Gosocket Upload

b. Exchange mailbox

a. Manual XML upload through Gosocket Upload

Gosocket has a tool within the Inbox platform, through which the provider can upload the document's XML file.

The access path is as follows: Main menu > Upload > Manual Upload.

In this option, the user can select the XML file manually from the file browser or, if preferred, drag it directly into the Manual Upload interface.

As already indicated, the solution performs the processing of documents, where, once the document is received, the validation process begins.

Once the XML file is received through the manual upload option, the following will be identified:

1. How many XML files in total were received, how many were processed successfully, and how many have errors.

2. When clicking the “Details” button, a popup will be shown with the “Error Detail” identifying the possible errors that the XML file manually uploaded through this option may contain, and conversely, if the document has no errors, a detail will be shown indicating that it was uploaded to the Gosocket platform successfully:

3. Finally, the document will be displayed in the received tray of the inbox, with all validations performed.

i. Considerations for manual XML upload

• In a single upload, up to n XML files can be uploaded.
• The same schema, signature, availability at the Tax Authority, and certificate validations that are performed through the exchange mailbox will be carried out.
• The tax documents stipulated by the Tax Authority must be sent in XML format.

The tax documents that can be received are:

• Electronic Invoice
• Electronic Sales Receipt
• Electronic Credit Note
• Electronic Debit Note
• Sender's Dispatch Guide
• Carrier's Dispatch Guide
• Electronic Withholding
• Electronic Perception
• Electronic Fee Receipt

b. Exchange mailbox

The mailboxes that must be used are:

• Sandbox: pe_sbx@inbound.gosocket.com
• Production**:** pe@recepcionprd.gosocket.net

i. Considerations for the exchange mailbox

It is important to keep the following points in mind when sending documents, as this will prevent them from being rejected by the application.

• The tax documents stipulated by the Tax Authority must be sent in XML format.

The tax documents that can be received in Peru are:

• Electronic Invoice
• Electronic Sales Receipt
• Electronic Credit Note
• Electronic Debit Note
• Sender's Dispatch Guide
• Carrier's Dispatch Guide
• Electronic Withholding
• Electronic Perception
• Electronic Fee Receipt

1. They can be sent individually or as several XML files in the same email.
2. Several compressed XML files can be sent (.zip, .rar)
3. The XML or compressed files must be attached to the main email.
4. Attached documents can be sent, such as the invoice PDF.

The solution has the ability to process the graphic representation PDFs in case they are included, and attached documents that arrive at the email mailbox, where once received they are stored associating them with their respective document, allowing download within Inbox.

The process works as follows:

• If an XML document arrives at the mailbox along with an additional PDF file with the same name, for example: Factura12345.xml, Factura12345.pdf, it is understood that the .pdf file is the graphic representation of the DTE, so it is synchronized that way in Gosocket and is available for querying.
• If an XML document arrives at the mailbox with more than one attached file of any extension, they are associated as attached documents.

warning

Note: If there are PDF files with a different name than the XML, they will be considered as attached documents.

• For sending attachments, it is recommended to send each DTE with its attachments separately, since if more than one XML document arrives, the graphic representation will only be stored as long as the PDF file has the same name as its corresponding XML; the rest of the attached files will not be processed, since there is no way to know which document to associate them with.
• Attachments can also be associated after the XML is sent; for example, if the XML is sent without attachments, another email can be sent later with attached documents (PDF, Excel, Word, etc.) and these will be associated with the previously sent document, as long as the second email also includes the XML.

---

3. QUERYING RECEIVED DOCUMENTS FROM GOSOCKET

Once the documents have been processed by the receipt service, they can be queried from the Gosocket portal in the Inbox/Received section. **

This section shows the following screen:

1. Filters section to optimize the search result. **
2. Display order control, with which you can modify the way search results will be presented. **
3. List of options linked to the export, commercial responses, and internal movements of the Electronic Documents. **
4. Display section with the detail of the search result and representative icons of the most relevant status changes. **

warning

* For more information about these points, see the Inbox documentation.**

Once the document search is performed in the main grid, the list of received documents that met the established search criteria will be shown; in this grid, in addition to relevant document information, the document status can be observed.

1. Tax authority validation.
2. Distribution validation.
3. Smart Supply status validation.

In the status column (1), the result of the applied validations will be shown, as explained in the Operation section.

Icon	Status	Validation
	VALIDATED	Document approved by the ET
	REJECTED *	Document rejected by the ET
	Not Available in ET	Document does not exist in the ET
❗	ERROR *	Document Rejected or internal exception by Gosocket
	VOIDED	Document Voided (The document is Voided in SUNAT)

Note: Clicking on the document will open the document preview where you can review the notes related to the reason for rejection.

Note: for the case in which the document remains in “ERROR” status, the user can reprocess it through the “Reprocess document” button in order to run the schema, signature, or ET validations again. This process is explained in detail in the “Options Button (Manually Reprocess Document)” section.

Finally, if additional documents were sent in the email, these will be reflected in the “Attachments” section within the document preview.

warning

For more information about the options available in this section, see the Inbox manual.