Peru: Document Reception (MS)

1. XML RECEPTION PROCESS

This process allows different types of documents to be received from customers and suppliers through the channels offered by Gosocket. Once received, both the issuer and the recipient can view the documents in the Inbox Received tray, along with their respective graphic representation and attached files.

Likewise, our system performs a series of automatic validations to ensure that the structure and integrity of the information strictly comply with the requirements of the tax authorities.

The following image describes, step by step, the document reception flow within the Inbox platform:

Peru reception process

1. Methods for sending the XML document in Gosocket:

The supplier has the option of sending the XML document to the Gosocket platform in three ways:

a. The supplier manually uploads the XML file using the Gosocket Upload option. The requirements and conditions for this process are detailed in the section Manual upload.

b. The supplier sends the XML document through the Gosocket exchange mailbox . The requirements and conditions for this process are detailed in the section Exchange mailbox.

c. The supplier uploads the XML document through the Reception API of Gosocket. The requirements and conditions for this process are detailed in the section Reception APIs.

info

Note: When using any of the following document reception channels:

• Exchange mailbox
• Manual XML upload (Upload option)
• Reception API

The system will automatically run the schema, signature, and corresponding validation with the Tax Authority (TA) validations.

2. Reception and validation of documents in Gosocket

The Gosocket portal downloads and processes the XML. When it is a tax document, it enters a reception validation process.

3. Document schema validation

First, a schema validation is performed on the XML document to ensure that it complies with the format established by the tax authority. Depending on the result of this validation, the process may lead to one of the following scenarios:

d. Failed: The document does not meet the fiscal format, the document reception flow will be stopped due to the schema error, it will be registered in Gosocket with the status Schema Error and the interface will display the icon and the reason for rejection will be detailed in the document notes, as follows:

Schema error icon in inbox

Document detail, Notes section - Schema Error

Detail of the XML processing for the schema error

e. Successful: If the XML schema validation is correct, the document will continue with the reception flow.

Document detail, Notes section - Successful schema validation

info

Special configuration: The XML has a schema error, but if the configuration is enabled, this option allows the reception flow to continue:

This feature can be enabled independently for each company. Its purpose is that, if a schema error is detected in the XML when the document is received in Gosocket, the specific error detail will automatically be recorded in the "Notes" section of the document.

Despite this finding, the document will continue its normal flow toward the following reception validations, such as the signature and tax authority verification.

The document will remain in Inbox as follows:

• In Gosocket, the document will remain in status Validated ET with schema error and the orange icon will be displayed, as follows:

For more details on how to configure this functionality, see the following section: XML Configuration Presents Schema Errors and Reception Flow Continues

4. Electronic signature validation of the document

Second, an electronic signature validation of the document is performed to ensure that the information has not been altered. This validation can produce one of the following results:

f. Failed: This means the document has been altered; the document reception flow will be stopped due to the signature error, so it will be registered in Gosocket with the status Signature Error, the interface will display an icon and the reason for rejection will be indicated in the preview notes, as follows:

Signature error icon in Inbox

Document detail, Notes section - Signature Error

Detail of the XML processing for the signature error

g. Successful: If the electronic signature validation of the XML is correct, the document will continue with the reception flow.

Document detail, Notes section - Successful signature validation

5.Validation of the document with the Tax Authority

Third, the query validation with the Tax Authority is performed. This validation can produce several results:

h. Document has an internal Gosocket exception ❗

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

Error icon in inbox: No communication with the TA.

Document detail, Notes section - Validation of the document with the TA with a communication error.

i. At this point in the process, when the document does exist at the tax authority, two responses may result:

• If the document exists, but has a status of Rejected (See more detail in item j)
• If the document exists, but has a status of Accepted (See more detail in item k)

j. Document Rejected by the Tax Authority

If the document exists at the TA, but there is some reason for rejection at the Tax Authority, its status will be Rejected and it will be assigned the icon .

Rejected icon in inbox: Validation of the document with the TA rejected

Document detail, Notes section - Validation of the document with the TA rejected

k. Document Accepted by the Tax Authority

If the result of the previous validations (Schema and Signature) is satisfactory and the query with the tax authority is successful, the document will be registered in Gosocket with the status Accepted. In the interface, this status will be identified with a green check icon.

Accepted icon in inbox: Successful validation of the document with the TA

Document detail, Notes section - Successful validation of the document with the TA

l. Automatic retries when the document has the status not available in the TA .

At this stage of the process, when the document does not exist at the Tax Authority, this indicates that the received document is not registered at the TA. In this scenario, the following actions are performed on the document:

• In Gosocket, the document will remain with the status Not Available in ET and will be assigned the corresponding icon .

• An automatic retry process will be triggered, which consists of performing multiple queries to the Tax Authority to check whether the document changes to a status other than Not Available in ET. If a different status is obtained during any of these retries, the document will automatically update both its status and its corresponding icon.

• If, after completing all the retries, the document is still not available at the Tax Authority, it will keep the status Not Available in ET and retain the corresponding icon .

• The current retry parameter is 30 attempts in 1 hour (the query retry is performed every 2 minutes).

When the document is received and the query retries to the TA are performed, the following message is shown in the Notes section:

and within the document detail, the “TAX-CHECK” code will indicate that validation with the TA has started:

Once the automatic retries are exhausted (approximately one hour later), the final status of the document with the TA will be displayed, as follows:

and the document detail will show the message:

“Integrated Query with the TA: Does not exist. 30 attempts were made. Manual reprocessing was performed.”

and another message will be shown on the other line: “The maximum number of retries for the status query with the TA was reached”, as follows:

and after these retries, two responses may result:

m. If after the 30 attempts the document is still not found, it will remain permanently in status Not Available in ET, showing the following icon in the Inbox.

Rejected icon in inbox: Validation of the document with the TA r

n. If during these retries the document is found at the TA, its status is updated, the process continues, and two responses may result:

• If the document exists, but has a status of Rejected (See more detail in item j)
• If the document exists, but has a status of Accepted (See more detail in item k)

6. Icons in the inbox for the reception validation results

Finally, both the issuer and the recipient can view the XML document validation results in Inbox, as follows:

No.	Status	Icon in the inbox interface
o	Document has a schema error
p	Document has a signature error
q	Communication error with the Tax Authority
r	Document was Accepted by the Tax Authority
s	Document was Rejected by the Tax Authority
t	Document not available or does not exist at the Tax Authority

---

2. MANUAL DOCUMENT REPROCESSING

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

info

Note: This option only allows reprocessing documents that were sent through the exchange mailbox, the reception API, or manual upload (upload).

This reprocessing option can be found 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 a single Electronic Document or a set of them.

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

Once the reprocessing has been generated, a banner will be displayed at the top of the page indicating that the document(s) were sent for reprocessing:

and finally, for any of the three reprocessing types generated through this option, the notes section will indicate:

• Records the email of the user who performed the document reprocessing.
• Generates a note “Document processed without schema validation” or “Document processed without signature validation”
• The document continues the reception validation flow.

This button allows reprocessing the different validations of the reception process:

2.1. Reprocess document without validating schema:

Allows the document to go through the reception validations without taking the schema validation into account; however, when the document is selected and this reprocessing without schema validation is applied, the system:

• Records the email of the user who performed the document reprocessing.
• Generates a note “Document processed without schema validation”.
• The document continues the reception validation flow.

2.2. Reprocess document without validating signature:

Allows the document to go through the reception validations without taking the signature validation into account; however, when the document is selected and this reprocessing without signature validation is applied, the system:

• Records the email of the user who performed the document reprocessing.
• Generates a note “Document processed without signature validation”.
• The document continues the reception validation flow.

2.3. Reprocess document:

Allows reprocessing the document from scratch and performs the reception validations again without omitting any of them; however, when the document is selected and this reprocessing is applied, the system:

• Records the email of the user who performed the document reprocessing.
• Performs the reception validations without omitting any of them.

---

3. METHODS FOR SENDING AN XML

Currently, there are three methods for receiving documents into the system:

• Manual upload: Import of the XML file using the Upload option in Gosocket.
• Exchange mailbox: Automated inbound flow through the exchange mailbox.
• Reception API: Connection via API for integrated processing.

3.1. Manual upload of the XML through the Upload option in Gosocket

Gosocket provides a tool within the Inbox platform that allows the supplier to directly upload the XML file of their documents.

• Access path: Main menu > Upload > Manual Upload.

From this section, the user can select the XML file from their device's file explorer or, if preferred, drag and drop it directly into the interface.

Once the document is received, the solution automatically starts the processing and validation flow.

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

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

b. When clicking the “Details” button, a pop-up will be displayed with the “Error Details” identifying the possible errors that the XML file manually uploaded through this option may contain; otherwise, if the document has no errors, a detail will be shown indicating that it was uploaded to the Gosocket platform successfully:

c. Finally, the document will be displayed in the Inbox received tray, with all validations completed.

3.1.1. Considerations for manual XML upload

• Up to 100 XML files can be uploaded in a single upload.
• The schema, signature, and Tax Authority validations will be performed.
• 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
• Shipping Guide - Shipper
• Shipping Guide - Carrier
• Electronic Withholding
• Electronic Collection
• Electronic Fee Receipt

info

Note - The Gosocket platform does not accept document type 15 - Electronic Reversal Document

The Gosocket platform cannot receive document type 15 - Electronic Reversal Document in Peru due to an issue with the recipient's data in the XML.

Details:

• The XML only includes the issuer's data (TaxId and name), but omits the recipient's information.
• The country's parser requires the AccountingCustomerParty node to extract the DocumentReceiverCode and the DocumentReceiverName:

{
  "PartitionKey": "pe|8|c1",
  "GlobalDocumentId": "00000000-0000-0000-0000-000000000000",
  "CountryDocumentId": "00000000000000000000",
  "CountryId": "pe",
  "Date": "2025-04-08T16:17:22.7880024",
  "DateNumber": 20250408,
  "DocumentTypeId": 15,
  "DocumentTypeName": "Reversión Electrónica",
  "NetAmount": 0,
  "DiscountAmount": 0,
  "FreeAmount": 0,
  "SurchargeAmount": 0,
  "TaxAmount": 0,
  "TipAmount": 0,
  "TotalAmount": 0,
  "CurrencyType": "PEN",
  "SeriesNumber": "RR-20250408-1",
  "Series": "RR-20250408",
  "Number": 1,
  "NumberStr": "1",
  "DocumentSenderCode": "12345678-9",
  "DocumentSenderName": "EMPRESA EMISORA S.A.",
  "DocumentReceiverCode": "",
  "DocumentReceiverName": "",
  "DocumentFinancialOwnerCode": null,
  "DocumentFinancialOwnerName": null,
  "FinancialDate": "0001-01-01T00:00:00",
  "DocumentTimeStamp": "2025-04-08T21:17:22.8817589Z",
  ...
}

  </ext:UBLExtensions>
  <cbc:UBLVersionID>2.0</cbc:UBLVersionID>
  <cbc:CustomizationID>1.0</cbc:CustomizationID>
  <cbc:ID>RR-20260420-4</cbc:ID>
  <cbc:ReferenceDate>2026-04-15</cbc:ReferenceDate>
  <cbc:IssueDate>2026-04-20</cbc:IssueDate>
  <cac:Signature>
    <cbc:ID>IDSignKG</cbc:ID>
    <cac:SignatoryParty>
      <cac:PartyIdentification>
        <cbc:ID>12345678-9</cbc:ID>
      </cac:PartyIdentification>
      <cac:PartyName>
        <cbc:Name><![CDATA[EMPRESA EMISORA S.A.]]></cbc:Name>
      </cac:PartyName>
    </cac:SignatoryParty>
    <cac:DigitalSignatureAttachment>
      <cac:ExternalReference>
        <cbc:URI>#signatureKG</cbc:URI>
      </cac:ExternalReference>
    </cac:DigitalSignatureAttachment>
  </cac:Signature>
  <cac:AccountingSupplierParty>
    <cbc:CustomerAssignedAccountID>12345678-9</cbc:CustomerAssignedAccountID>
    <cbc:AdditionalAccountID>6</cbc:AdditionalAccountID>
    <cac:Party>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName><![CDATA[EMPRESA EMISORA S.A.]]></cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <sac:VoidedDocumentsLine>
    <cbc:LineID>1</cbc:LineID>
    <cbc:DocumentTypeCode>20</cbc:DocumentTypeCode>
    <sac:DocumentSerialID>R001</sac:DocumentSerialID>
    <sac:DocumentNumberID>8776</sac:DocumentNumberID>
    <sac:VoidReasonDescription><![CDATA[DUPLICADO2042026]]></sac:VoidReasonDescription>
  </sac:VoidedDocumentsLine>
</VoidedDocuments>

document.DocumentReceiverCode = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'CustomerAssignedAccountID']", ns)?.Value ?? "";br />document.DocumentReceiverName = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'Party']/[local-name() = 'PartyLegalEntity']/[local-name() = 'RegistrationName']", ns)?.Value ?? "";

When reviewing the files in production, it was verified that this node does not exist and the receiverCode field remains empty, preventing its reception.

3.2. Exchange mailbox

This is the process by which the supplier sends its XML files through an email mailbox. Each country has specific addresses assigned according to the working environment.

The mailboxes to be used, according to the environment, are:

• Sandbox (Testing): pe_ms_sbx@inbound.gosocket.com
• Production: pe@recepcionprd.gosocket.net

info

3.2.1. 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.

a. The tax documents that can be sent through the exchange mailbox are:

• Electronic Invoice
• Electronic Sales Receipt
• Electronic Credit Note
• Electronic Debit Note
• Shipping Guide - Shipper
• Shipping Guide - Carrier
• Electronic Withholding
• Electronic Collection
• Electronic Fee Receipt

info

Note - The Gosocket platform does not accept document type 15 - Electronic Reversal Document

The Gosocket platform cannot receive document type 15 - Electronic Reversal Document in Peru due to an issue with the recipient's data in the XML.

Details:

• The XML only includes the issuer's data (TaxId and name), but omits the recipient's information.
• The country's parser requires the AccountingCustomerParty node to extract the DocumentReceiverCode and the DocumentReceiverName:

{
  "PartitionKey": "pe|8|c1",
  "GlobalDocumentId": "00000000-0000-0000-0000-000000000000",
  "CountryDocumentId": "00000000000000000000",
  "CountryId": "pe",
  "Date": "2025-04-08T16:17:22.7880024",
  "DateNumber": 20250408,
  "DocumentTypeId": 15,
  "DocumentTypeName": "Reversión Electrónica",
  "NetAmount": 0,
  "DiscountAmount": 0,
  "FreeAmount": 0,
  "SurchargeAmount": 0,
  "TaxAmount": 0,
  "TipAmount": 0,
  "TotalAmount": 0,
  "CurrencyType": "PEN",
  "SeriesNumber": "RR-20250408-1",
  "Series": "RR-20250408",
  "Number": 1,
  "NumberStr": "1",
  "DocumentSenderCode": "12345678-9",
  "DocumentSenderName": "EMPRESA EMISORA S.A.",
  "DocumentReceiverCode": "",
  "DocumentReceiverName": "",
  "DocumentFinancialOwnerCode": null,
  "DocumentFinancialOwnerName": null,
  "FinancialDate": "0001-01-01T00:00:00",
  "DocumentTimeStamp": "2025-04-08T21:17:22.8817589Z",
  ...
}

  </ext:UBLExtensions>
  <cbc:UBLVersionID>2.0</cbc:UBLVersionID>
  <cbc:CustomizationID>1.0</cbc:CustomizationID>
  <cbc:ID>RR-20260420-4</cbc:ID>
  <cbc:ReferenceDate>2026-04-15</cbc:ReferenceDate>
  <cbc:IssueDate>2026-04-20</cbc:IssueDate>
  <cac:Signature>
    <cbc:ID>IDSignKG</cbc:ID>
    <cac:SignatoryParty>
      <cac:PartyIdentification>
        <cbc:ID>12345678-9</cbc:ID>
      </cac:PartyIdentification>
      <cac:PartyName>
        <cbc:Name><![CDATA[EMPRESA EMISORA S.A.]]></cbc:Name>
      </cac:PartyName>
    </cac:SignatoryParty>
    <cac:DigitalSignatureAttachment>
      <cac:ExternalReference>
        <cbc:URI>#signatureKG</cbc:URI>
      </cac:ExternalReference>
    </cac:DigitalSignatureAttachment>
  </cac:Signature>
  <cac:AccountingSupplierParty>
    <cbc:CustomerAssignedAccountID>12345678-9</cbc:CustomerAssignedAccountID>
    <cbc:AdditionalAccountID>6</cbc:AdditionalAccountID>
    <cac:Party>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName><![CDATA[EMPRESA EMISORA S.A.]]></cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <sac:VoidedDocumentsLine>
    <cbc:LineID>1</cbc:LineID>
    <cbc:DocumentTypeCode>20</cbc:DocumentTypeCode>
    <sac:DocumentSerialID>R001</sac:DocumentSerialID>
    <sac:DocumentNumberID>8776</sac:DocumentNumberID>
    <sac:VoidReasonDescription><![CDATA[DUPLICADO2042026]]></sac:VoidReasonDescription>
  </sac:VoidedDocumentsLine>
</VoidedDocuments>

document.DocumentReceiverCode = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'CustomerAssignedAccountID']", ns)?.Value ?? "";br />document.DocumentReceiverName = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'Party']/[local-name() = 'PartyLegalEntity']/[local-name() = 'RegistrationName']", ns)?.Value ?? "";

When reviewing the files in production, it was verified that this node does not exist and the receiverCode field remains empty, preventing its reception.

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

c. They can be sent individually or as several XML files in the same email.

d. Several XML files can be sent compressed in a file, and only the .zip extension will be allowed.

e. The XML or compressed (.zip) files must be attached to the email of the mailbox provided by Gosocket.

f. Attached documents may be sent, such as the invoice PDF or other files as required.

g. The maximum size allowed in an email that includes XML and PDF files is 20MB.

h. The solution can process the graphic representation PDF, if included, and attached documents arriving at the mailbox; once received, they are stored and associated with their respective document, allowing them to be downloaded within Inbox.

The process works as follows:

• If an XML document arrives at the exchange mailbox along with an additional PDF file with the same name, for example: Factura12345.xml and Factura12345.pdf, the .pdf file is understood to be the graphic representation of the DTE, so it is synchronized that way in Gosocket and will be available for viewing.
• 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 name different from 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, only the graphic representation will be stored, provided the PDF file has the same name as the 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 has been sent; for example, if the XML is sent without attachments, another email with attached documents (PDF, Excel, Word, etc.) can be sent afterward, and these will be associated with the previously sent document, as long as the second email also includes the XML.

3.3. Reception APIs

For the document reception process, Gosocket offers two APIs that allow sending XML to the Gosocket platform:

3.3.1. UploadZipDocument:

This API allows sending a request that includes one or several XML and PDF files to Gosocket, packaged together in a compressed file (.zip). Once received, the system processes the document, generates the corresponding record, and securely stores it on the platform.

a. Tracking Management

To perform detailed end-to-end tracking of the PDF processing, from the moment the PDF enters the platform through the exchange mailbox until the supplier sends the XML and the PDF to Gosocket, this entire process is assigned two unique identifiers called "externalId" and "batchId".

b. Upload and storage

The API manages the reception of the .zip file, which must contain the PDF and its corresponding XML in Gosocket's native format for its proper integration into the ecosystem.

This API allows the reception, processing, and storage of electronic documents on the Gosocket platform.

c. Post-storage processing actions

Once the document has been successfully stored in Inbox, the following actions can be performed:

• Reception validations (Automatic): Technical verification of standards compliance, including:

o   Schema Validation.

o   Integrity of the document's Electronic Signature.

o   Validations with the corresponding Tax Authority: Indicates whether the document was accepted, rejected, or presents validation errors from the regulatory body after the fiscal validation.

• Receiver message (Automatic): Application of receiver message events according to the current regulations of the tax authority.
• Smart Supply validations (Configuration on demand): Application of logical rules and approval flows configured in the Smart Supply module.
• File Distribution (Configuration on demand): Once the document has been processed on the Gosocket platform, and based on the prior parameterization of the distribution rules, the system performs the automated transfer of the files to the configured technical destinations. This functionality allows integration with various environments, such as:

o   Windows servers.

o   File transfer protocols (SFTP / FTP).

o   Automated sending by email.

warning

You can view the configuration details of the Reception API at the following link: API Reception.zip - Generic

3.3.2. SendDocumentToUpload:

This API allows sending a request that includes a single XML to Gosocket. Once received, the system processes the document, generates the corresponding record, and securely stores it on the platform.

a. Upload and storage

The API manages the reception of the file in XML format for its integration into the Gosocket ecosystem:

• Ingestion: Uploads the document directly into the Gosocket Inbox module via the  endpoint: POST - SendDocumentToUpload
• Persistence: Ensures the storage of the XML file on the platform's servers for its subsequent management.

b. Tracking Management

The successful execution of the API generates a unique identifier called trackId. This value is returned in the response and is essential for:

• Performing detailed tracking of the processing status.
• Checking the upload result via the endpoint: GET- GetDocumentUploadStatus

c. Post-storage processing actions

Once the document has been successfully stored in Inbox, the following actions can be performed:

• Reception validations (Automatic): Technical verification of standards compliance, including:

o   Schema Validation.

o   Integrity of the document's Electronic Signature.

o   Validations with the corresponding Tax Authority: Indicates whether the document was accepted, rejected, or presents validation errors from the regulatory body after the fiscal validation.

• Receiver message (Automatic): Application of receiver message events according to the current regulations of the tax authority.
• Smart Supply validations (Configuration on demand): Application of logical rules and approval flows configured in the Smart Supply module.
• File Distribution (Configuration on demand): Once the document has been processed on the Gosocket platform, and based on the prior parameterization of the distribution rules, the system performs the automated transfer of the files to the configured technical destinations. This functionality allows integration with various environments, such as:

o   Windows servers.

o   File transfer protocols (SFTP / FTP).

o   Automated sending by email.

warning

You can view the configuration details of the Reception API at the following link: Reception API

info

Note - The Gosocket platform does not accept document type 15 - Electronic Reversal Document

The Gosocket platform cannot receive document type 15 - Electronic Reversal Document in Peru due to an issue with the recipient's data in the XML.

Details:

• The XML only includes the issuer's data (TaxId and name), but omits the recipient's information.
• The country's parser requires the AccountingCustomerParty node to extract the DocumentReceiverCode and the DocumentReceiverName:

{
  "PartitionKey": "pe|8|c1",
  "GlobalDocumentId": "00000000-0000-0000-0000-000000000000",
  "CountryDocumentId": "00000000000000000000",
  "CountryId": "pe",
  "Date": "2025-04-08T16:17:22.7880024",
  "DateNumber": 20250408,
  "DocumentTypeId": 15,
  "DocumentTypeName": "Reversión Electrónica",
  "NetAmount": 0,
  "DiscountAmount": 0,
  "FreeAmount": 0,
  "SurchargeAmount": 0,
  "TaxAmount": 0,
  "TipAmount": 0,
  "TotalAmount": 0,
  "CurrencyType": "PEN",
  "SeriesNumber": "RR-20250408-1",
  "Series": "RR-20250408",
  "Number": 1,
  "NumberStr": "1",
  "DocumentSenderCode": "12345678-9",
  "DocumentSenderName": "EMPRESA EMISORA S.A.",
  "DocumentReceiverCode": "",
  "DocumentReceiverName": "",
  "DocumentFinancialOwnerCode": null,
  "DocumentFinancialOwnerName": null,
  "FinancialDate": "0001-01-01T00:00:00",
  "DocumentTimeStamp": "2025-04-08T21:17:22.8817589Z",
  ...
}

  </ext:UBLExtensions>
  <cbc:UBLVersionID>2.0</cbc:UBLVersionID>
  <cbc:CustomizationID>1.0</cbc:CustomizationID>
  <cbc:ID>RR-20260420-4</cbc:ID>
  <cbc:ReferenceDate>2026-04-15</cbc:ReferenceDate>
  <cbc:IssueDate>2026-04-20</cbc:IssueDate>
  <cac:Signature>
    <cbc:ID>IDSignKG</cbc:ID>
    <cac:SignatoryParty>
      <cac:PartyIdentification>
        <cbc:ID>12345678-9</cbc:ID>
      </cac:PartyIdentification>
      <cac:PartyName>
        <cbc:Name><![CDATA[EMPRESA EMISORA S.A.]]></cbc:Name>
      </cac:PartyName>
    </cac:SignatoryParty>
    <cac:DigitalSignatureAttachment>
      <cac:ExternalReference>
        <cbc:URI>#signatureKG</cbc:URI>
      </cac:ExternalReference>
    </cac:DigitalSignatureAttachment>
  </cac:Signature>
  <cac:AccountingSupplierParty>
    <cbc:CustomerAssignedAccountID>12345678-9</cbc:CustomerAssignedAccountID>
    <cbc:AdditionalAccountID>6</cbc:AdditionalAccountID>
    <cac:Party>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName><![CDATA[EMPRESA EMISORA S.A.]]></cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <sac:VoidedDocumentsLine>
    <cbc:LineID>1</cbc:LineID>
    <cbc:DocumentTypeCode>20</cbc:DocumentTypeCode>
    <sac:DocumentSerialID>R001</sac:DocumentSerialID>
    <sac:DocumentNumberID>8776</sac:DocumentNumberID>
    <sac:VoidReasonDescription><![CDATA[DUPLICADO2042026]]></sac:VoidReasonDescription>
  </sac:VoidedDocumentsLine>
</VoidedDocuments>

document.DocumentReceiverCode = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'CustomerAssignedAccountID']", ns)?.Value ?? "";br />document.DocumentReceiverName = nav.SelectSingleNode("/[local-name() = 'VoidedDocuments']/[local-name() = 'AccountingCustomerParty']/[local-name() = 'Party']/[local-name() = 'PartyLegalEntity']/[local-name() = 'RegistrationName']", ns)?.Value ?? "";

When reviewing the files in production, it was verified that this node does not exist and the receiverCode field remains empty, preventing its reception.

---

4. QUERYING DOCUMENTS RECEIVED FROM GOSOCKET

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

This section shows the following screen:

**1.**Filters section to optimize the search results. **

**2.**Display order control, which allows modifying how the search results are presented. **

**3.**List of options related to export, commercial responses, and internal movements of the Electronic Documents. **

**4.**Display section with the detail of the search results and representative icons of the most relevant status changes. **

warning

* For more information on 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 displayed; in this grid, in addition to relevant document information, the document status can also 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 section XML reception process.

Icon	Status	Validation
	VALIDATED	Document approved by the TA
	REJECTED*	Document rejected by the TA
	Not Available in ET	Document does not exist at the TA
❗	ERROR*	Document Rejected or internal Gosocket exception
	Signature Error	Document with signature error
	Schema Error	Document with schema error
	Schema error but the flow continues *	The XML has a schema error, but if the configuration is enabled, this option allows the reception flow to continue.

* Note: By clicking on the document, the document preview will open, where you can review the notes related to the reason for rejection.

* Note: for cases where the document remains in “ERROR” status, the user can reprocess it through the actions, with the goal of performing the schema, signature, or TA validations again. This process is explained in detail in the section Reprocessing.

* Note: Special configuration: The XML has a schema error, but if the configuration is enabled, this option allows the reception flow to continue:

This feature can be enabled independently for each company. Its purpose is that, if a schema error is detected in the XML when the document is received in Gosocket, the specific error detail will automatically be recorded in the "Notes" section of the document.

Despite this finding, the document will continue its normal flow toward the following reception validations, such as the signature and tax authority verification.

The document will remain in Inbox as follows:

In Gosocket, the document will remain in status Validated ET with schema error and the orange icon will be displayed, as follows:

For more details on how to configure this functionality, see the following section: XML Configuration Presents Schema Errors and Reception Flow Continues

---