Paraguay: Reception of documents (MS)

1. XML RECEPTION PROCESS

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

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:

Paraguay reception process

1. Methods for sending the XML document in Gosocket:

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

a. The supplier performs the manual upload of the XML file using Gosocket's Upload option. The requirements and conditions for this process are detailed in the section Manual upload.

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

c. The supplier uploads the XML document through Gosocket's Reception API. 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) checks.

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 it complies with the format established by the tax authority. Depending on the result of this validation, the process can lead to one of the following scenarios:

d. Failed: The document does not comply with the fiscal format, the document reception flow will be stopped due to the schema error, it will be registered in Gosocket with 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 receiving the document in Gosocket, the specific error detail will be automatically recorded in the document's "Notes" section.

Despite this finding, the document will continue its normal flow to 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 feature, see the following section: XML Configuration Presents Schema Errors and Reception Flow Continues

**4.**Second, a document electronic signature validation 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 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 XML electronic signature validation is correct, the document will continue with the reception flow.

Document detail - Notes section - Successful signature validation

5.Document validation with the Tax Authority

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

h. The document has an internal exception in Gosocket ❗

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

Error icon in inbox: No communication with the TA.

Document detail - Notes section - Document validation with the TA with a communication error.

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

• If the document exists, but it has status Rejected (For more details, see item j)
• If the document exists, but it has status Accepted (For more details, see item k)

j. Document Rejected by the Tax Authority

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

Rejected icon in inbox: Document validation with the TA rejected

Document detail - Notes section - Document validation 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 status Accepted. In the interface, this status will be identified with a green checkmark icon.

Accepted icon in inbox: Successful document validation with the TA

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

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

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

• In Gosocket, the document will remain with 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 in the Tax Authority, it will keep the status Not Available in ET and will retain the corresponding icon .

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

When the document is received and the query retries with 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 the validation with the TA has started:

Once the automatic retries have been 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 line will show a second message: “The maximum number of retries for the status query with the TA was reached”, as follows:

and after these retries, two responses can result:

m. If after 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: Document validation with the TA r

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

• If the document exists, but it has status Rejected (For more details, see item j)
• If the document exists, but it has status Accepted (For more details, see item k)

6. Icons in inbox for the reception validation results

Finally, both the issuer and the recipient can check the results of the XML document validations in Inbox, as follows:

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

7. Issuance of commercial acknowledgments

Once the document has been received and validated, the commercial or mercantile acknowledgments required can be issued, as appropriate, from the Inbox platform or, alternatively, they can be sent through the exchange mailbox. This is explained in more detail in the section Commercial acknowledgments.

---

2. MANUALLY REPROCESSING DOCUMENTS

Additionally, a button was implemented in Inbox that allows manually reprocessing tax documents with 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 the manual upload (upload).

This reprocessing option can be found at 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 group 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 shown 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 performing a reprocessing of 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 selecting the document and applying this reprocessing without schema validation, 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 selecting the document and applying this reprocessing without signature validation, 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 runs the reception validations again without skipping any validation; however, when selecting the document and applying this reprocessing, the system:

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

---

3. XML SUBMISSION METHODS

There are currently three methods for receiving documents into the system:

• Manual upload: Import of the XML file through 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 has a tool within the Inbox platform that allows the supplier to upload the XML file of their documents directly.

• 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 through the manual upload option, it will identify:

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

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

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

3.1.1. Considerations for manual XML upload

• Up to 100 XML files can be uploaded in a single upload.
• 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 Credit Note.
• Electronic Debit Note.
• Electronic remittance note.
• Electronic withholding certificate.

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 work environment.

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

• Sandbox (Testing): py_ms_sbx@inbound.gosocket.com
• Production: py@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 Credit Note.
• Electronic Debit Note.
• Electronic remittance note.
• Electronic withholding certificate.

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

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. XML files or compressed files (.zip) must be attached to the email at the mailbox provided by Gosocket.

f. Attached documents can be sent, such as the invoice PDF or others that may be required.

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

h. The solution has the ability to process the graphic representation PDFs, if included, and attached documents that arrive 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 and an additional PDF file with the same name arrive at the exchange mailbox, for example: Invoice12345.xml and Invoice12345.pdf, it is understood that the .pdf file is 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 attachment 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 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 that 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 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 files 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 stores it securely on the platform.

a. Tracking Management

To carry out detailed end-to-end tracking of the PDF processing, from when 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 correct 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, it will allow the following actions:

• 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 has validation errors from the regulatory body after fiscal validation.

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

o   Windows servers.

o   File transfer protocols (SFTP / FTP).

o   Automated email submission.

warning

You can check the Reception API configuration details 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 stores it securely 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 Gosocket's Inbox module via the endpoint: POST - SendDocumentToUpload
• Persistence: Ensures storage of the XML file on the platform's servers for later management.

b. Tracking Management

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

• Tracking the processing status in detail.
• Checking the upload result via the endpoint: GET- GetDocumentUploadStatus

c. Post-storage processing actions

Once the document has been successfully stored in Inbox, it will allow the following actions:

• 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 has validation errors from the regulatory body after fiscal validation.

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

o   Windows servers.

o   File transfer protocols (SFTP / FTP).

o   Automated email submission.

warning

You can check the Reception API configuration details at the following link: Reception API

---

4. COMMERCIAL ACKNOWLEDGMENTS

The purpose of the commercial acknowledgment is to validate tax documents with the Tax Authority, resulting in a status change within our received documents tray in the Gosocket Inbox.

Through the use of these events, the recipient reports the reception, acceptance, or rejection of each document.

These events can be generated from two different points in Inbox, which we will explore below.

There are currently 4 commercial acknowledgments for received documents:

**a.**Notification Event – Reception

**b.**Conformity Event

**c.**Nonconformity Event

**d.**Disavowal Event

Once the documents have been received in the inbox and have passed the reception validations, Gosocket allows applying commercial acknowledgments as follows:

4.1. Receive commercial acknowledgments through the exchange mailbox

4.2. Manually issue the commercial acknowledgment for these documents.

4.1. Reception of commercial acknowledgments through the exchange mailbox

To receive commercial acknowledgments through the exchange mailbox, the file must strictly comply with the specific structure required by the TA and be in XML format.

<ApplicationResponse
xmlns="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:sts="dian:gov:co:facturaelectronica:Structures-2-1"
xmlns:xades="http://uri.etsi.org/01903/v1.3.2#"
xmlns:xades141="http://uri.etsi.org/01903/v1.4.1#"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<ext:UBLExtensions>
...
</ext:UBLExtensions>
<cbc:UBLVersionID>UBL 2.1</cbc:UBLVersionID>
<cbc:CustomizationID>1</cbc:CustomizationID>
<cbc:ProfileID>DIAN 2.1: ApplicationResponse de la Factura Electrónica de Venta</cbc:ProfileID>
<cbc:ProfileExecutionID>1</cbc:ProfileExecutionID>
<cbc:ID>0000000000000000000</cbc:ID>
<cbc:UUID schemeID="1" schemeName="CUDE-SHA384">000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</cbc:UUID>
<cbc:IssueDate>2026-06-30</cbc:IssueDate>
<cbc:IssueTime>15:14:00-05:00</cbc:IssueTime>
<cbc:Note>OK</cbc:Note>
<cac:SenderParty>
...
</cac:SenderParty>
<cac:ReceiverParty>
...
</cac:ReceiverParty>
<cac:DocumentResponse>
<cac:Response>
<cbc:ResponseCode>030</cbc:ResponseCode>
<cbc:Description>Acuse de recibo de Factura Electrónica de Venta</cbc:Description>
</cac:Response>
<cac:DocumentReference>
<cbc:ID>FV0000</cbc:ID>
<cbc:UUID schemeName="CUFE-SHA384">000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</cbc:UUID>
<cbc:DocumentTypeCode>01</cbc:DocumentTypeCode>
</cac:DocumentReference>
<cac:IssuerParty>
<cac:Person>
...
</cac:Person>
</cac:IssuerParty>
</cac:DocumentResponse>
</ApplicationResponse>

<ApplicationResponse
xmlns="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:sts="dian:gov:co:facturaelectronica:Structures-2-1"
xmlns:xades="http://uri.etsi.org/01903/v1.3.2#"
xmlns:xades141="http://uri.etsi.org/01903/v1.4.1#"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<ext:UBLExtensions>
...
</ext:UBLExtensions>
<cbc:UBLVersionID>UBL 2.1</cbc:UBLVersionID>
<cbc:CustomizationID>1</cbc:CustomizationID>
<cbc:ProfileID>DIAN 2.1: ApplicationResponse de la Factura Electrónica de Venta</cbc:ProfileID>
<cbc:ProfileExecutionID>1</cbc:ProfileExecutionID>
<cbc:ID>0000000000000000000</cbc:ID>
<cbc:UUID schemeID="1" schemeName="CUDE-SHA384">000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</cbc:UUID>
<cbc:IssueDate>2026-06-30</cbc:IssueDate>
<cbc:IssueTime>15:14:00-05:00</cbc:IssueTime>
<cbc:Note>OK</cbc:Note>
<cac:SenderParty>
...
</cac:SenderParty>
<cac:ReceiverParty>
...
</cac:ReceiverParty>
<cac:DocumentResponse>
<cac:Response>
<cbc:ResponseCode>032</cbc:ResponseCode>
<cbc:Description>Recibo del bien y/o prestación del servicio</cbc:Description>
</cac:Response>
<cac:DocumentReference>
<cbc:ID>FV0000</cbc:ID>
<cbc:UUID schemeName="CUFE-SHA384">000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</cbc:UUID>
<cbc:DocumentTypeCode>01</cbc:DocumentTypeCode>
</cac:DocumentReference>
<cac:IssuerParty>
<cac:Person>
...
</cac:Person>
</cac:IssuerParty>
</cac:DocumentResponse>
</ApplicationResponse>

<ApplicationResponse
xmlns="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:sts="dian:gov:co:facturaelectronica:Structures-2-1"
xmlns:xades="http://uri.etsi.org/01903/v1.3.2#"
xmlns:xades141="http://uri.etsi.org/01903/v1.4.1#"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<ext:UBLExtensions>
...
</ext:UBLExtensions>
<cbc:UBLVersionID>UBL 2.1</cbc:UBLVersionID>
<cbc:CustomizationID>1</cbc:CustomizationID>
<cbc:ProfileID>DIAN 2.1: ApplicationResponse de la Factura Electrónica de Venta</cbc:ProfileID>
<cbc:ProfileExecutionID>1</cbc:ProfileExecutionID>
<cbc:ID>0000000000000000000</cbc:ID>
<cbc:UUID schemeID="1" schemeName="CUDE-SHA384">000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</cbc:UUID>
<cbc:IssueDate>2026-06-30</cbc:IssueDate>
<cbc:IssueTime>15:14:00-05:00</cbc:IssueTime>
<cbc:Note>OK</cbc:Note>
<cac:SenderParty>
...
</cac:SenderParty>
<cac:ReceiverParty>
<cac:PartyTaxScheme>
...
</cac:PartyTaxScheme>
<cac:Contact>
...
</cac:Contact>
</cac:ReceiverParty>
<cac:DocumentResponse>
<cac:Response>
<cbc:ResponseCode>033</cbc:ResponseCode>
<cbc:Description>Aceptación expresa</cbc:Description>
</cac:Response>
<cac:DocumentReference>
...
</cac:DocumentReference>
</cac:DocumentResponse>
</ApplicationResponse>

This XML file, which contains the commercial acknowledgment structure, must be sent once the invoice is already registered in Inbox, sending it to the same reception mailbox.

Once the acknowledgment is received through this channel, it can be viewed as an attached file within the Attachments section in the document preview, as follows:

4.2. Manually issue the commercial acknowledgment for these documents.

These commercial events can be generated manually from two different points in Inbox, which we will explore below:

4.2.1. Options Button (Received Documents)

**1.**To access this option and manually generate the commercial acknowledgment required for the document(s), in inbox you must select the documents to be managed using the checkbox or selector.

**2.**Now, you must select the “Options” button and look for the “Commercial acknowledgment” section located at: Inbox / Received Tray / Options Button / Section: commercial acknowledgment, Within this menu, you will find the following Commercial Acknowledgment options:

• Acknowledgment of receipt of the Electronic Sales Invoice.
• Express acceptance: This option can only be used once an acknowledgment of receipt of goods or services has been issued.
• Receipt of goods or service rendering.
• Claim for the Electronic Sales Invoice.

When accessing any of the acknowledgments, a pop-up window with a form will be displayed to add an observation. You can also enter an additional email address to receive a copy of the Acknowledgment and, in the case of the claim acknowledgment, a list of rejection types.

This event will be displayed within the document preview in the notes section, and the XML of the event sent to the Tax Authority will be shown:

and in the attachments section as shown below:

i. Notification Event - Reception

Selecting the Notification Event - Reception generates a notification that the previously selected document was successfully received. This option only applies to documents in accepted status.
This action will generate the event's XML per document. For example, if three documents were selected and the Notification Event - Reception is selected from the Options button, a pop-up window is generated to enter the acknowledgment description, followed by the validate button, generating the three event acknowledgment XMLs.

This event will be displayed within the document preview in the notes section, and the XML of the event sent to the Tax Authority will be shown in the attachments section as shown below:

Likewise, the Notification Event - Reception will be displayed in the document's status icons.

ii. Conformity Event

Selecting the Conformity Event is the event that produces an acknowledgment of receipt showing that there is conformity with the document. That is, that the document's information is valid for the recipient.
There are two types of conformity:

**1.**Full conformity, which is conformity with all the document's information. This means the recipient validated the document in its entirety.

**2.**Partial conformity, which is the type of conformity that indicates that the recipient does not validate the document in its entirety, but there is correct information within it.

For example, when selecting the Conformity Event from the Options button, a pop-up window is generated to:

a. Select one of the two conformity types

b. Enter the acknowledgment description followed by the validate button

c. Finally, the event acknowledgment XML is generated.

This event will be displayed within the document preview in the notes section, and the XML of the event sent to the Tax Authority will be shown in the attachments section as shown below:

Likewise, the Conformity Event will be displayed in the document's status icons.

and within the document preview, in the upper right corner, the message “ACCEPTED BY CLIENT” will be shown, and in green the text “Conformity Event”

iii. Nonconformity Event

Selecting the Nonconformity Event is the event that helps the recipient show that they do not agree with the information shown within the document.

For example, when selecting the Conformity Event from the Options button, a pop-up window is generated where the acknowledgment description is entered, followed by the validate button.

This event will be displayed within the document preview in the notes section, and the XML of the event sent to the Tax Authority will be shown in the attachments section as shown below:

Likewise, the Nonconformity Event will be displayed in the document's status icons.

and within the document preview, in the upper right corner, the message “REJECTED BY CLIENT” will be shown, and in red the text “Nonconformity Event”

iv. Disavowal Event

Selecting the Disavowal Event will help notify that the recipient does not recognize the charge of the previously selected document.

For example, when selecting the Disavowal Event from the Options button, a pop-up window is generated where the acknowledgment description is entered, followed by the validate button.

This event will be displayed within the document preview in the notes section, and the XML of the event sent to the Tax Authority will be shown in the attachments section as shown below:

Likewise, the disavowal event will be displayed in the document's status icons.

and within the document preview, in the upper right corner, the message “REJECTED BY CLIENT” will be shown, and in red the text “Disavowal Event DE/DTE”

4.2.2. Applying commercial acknowledgments from the document preview

These events can also be generated from the Inbox document preview, which we will explore below.

This action can also be performed from the document preview via the Commercial acknowledgment button.

4.2.3. Icons according to the commercial acknowledgment

Depending on the commercial acknowledgment previously assigned, the document may show one of the following icons when viewed from Received:

1. Document acknowledgment of receipt: This status reports the issuance of the acknowledgment for a document, which can be shown in two scenarios:

a. Gray, shown when the document does not yet have an acknowledgment of receipt.

b. Green, which indicates that the acknowledgment was issued successfully. (When a document is received, the acknowledgment of receipt is automatically issued to the issuer.

2. Commercial approval: Acceptance or Rejection: This icon can appear in the following ways: For acceptance, an icon with a hand pointing up in green will be shown; if rejected, an icon with a hand pointing down in red will be shown; if this event is not present, the hand will be in gray.

warning

For more details on running commercial acknowledgments from the API available in this section, see the Inbox and API Manual.

---

5. QUERYING RECEIVED DOCUMENTS 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 you to modify how the search results are presented. **

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

**4.**Display section with the search result details and representative icons for 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 shown; in this grid, in addition to relevant document information, the document status can be seen.

**1.**Tax Authority validation.

**2.**Distribution validation.

**3.**Smart Supply status validation.

In the status column (1), the results 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 in the TA
❗	ERROR*	Document Rejected or internal exception by Gosocket
	Signature Error	Document with signature error
	Schema Error	Document with schema error
	Schema error but flow continues *	The XML has a schema error, but if the configuration is enabled, this option allows the reception flow to continue.

Note: Clicking on the document will open the document preview 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, in order to run 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 receiving the document in Gosocket, the specific error detail will be automatically recorded in the "Notes" section of the document.

Despite this finding, the document will continue its normal flow to 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 feature, see the following section: XML Configuration Presents Schema Errors and Reception Flow Continues

---