Costa Rica: 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 guarantee that the structure and integrity of the information strictly meet the requirements of the tax authorities.

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

Costa Rica reception process

1. Methods for sending the XML document in Gosocket

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

a. The supplier manually uploads the XML file through the Gosocket Upload option. The requirements and conditions for this process are detailed in the 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 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 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 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 tax format, the document reception flow will be stopped due to the schema error, it will be registered in Gosocket with the Schema Error status, 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 setting 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 with 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 the Validated ET with schema error status 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. 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 Signature Error status, the interface will display an icon and the preview notes will indicate the reason for rejection, as follows:

Signature error icon in Inbox

Document detail, Notes section - Signature Error

Detail of the XML processing for the schema 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.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 exception from Gosocket ❗

When performing the validation query with the Tax Authority for the document and Gosocket cannot connect to the TA service or there are communication errors with the service, the document changes its status to ERROR and 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 occur:

• If the document exists, but it has a Rejected status (see item j for more detail)
• If the document exists, but it has an Accepted status (see item k for more detail)

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 the Accepted status. In the interface, this status will be identified with a green check 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 the status Not Available in ET .

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 in the TA. In this scenario, the following actions are performed on the document:

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

• An automatic retries 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 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 code “TAX-CHECK” will indicate that the 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 the other line will show another 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 the 30 attempts the document is still not found, it will remain permanently in Not Available in ET status, 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 in the TA, its status is updated, the process continues, and two responses can occur:

• If the document exists, but it has a Rejected status (see item j for more detail)
• If the document exists, but it has an Accepted status (see item k for more detail)

6. Inbox iconography for the result of reception validations

Finally, both the issuer and the recipient can view 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 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

7. Issuance of commercial acknowledgments

Once the document has been received and validated, the mercantile or commercial acknowledgments considered necessary may be issued from the inbox platform, or alternatively, may 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 tax documents with “ERROR” ❗, “Not Available in ET” , “Signature error” and “Schema error” status to be manually reprocessed.

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 schema validation.
• Inbox/Received/Options/Actions/Reprocess document without signature validation.
• Inbox/Received/Options/Actions/Reprocess document.

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

Next, a pop-up window will appear 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 types of reprocessing 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 of the different validations in the reception process:

2.1. Reprocess document without schema validation:

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 signature validation:

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 performs 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. 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 entry flow through the exchange mailbox.
• Reception API: API connection for integrated processing.

3.1. Manual upload of the XML through the Gosocket Upload

Gosocket has 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 browser 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 in total were received, how many were processed successfully, and how many have errors.

b. By clicking the “Details” button, a popup will be displayed with the “Error Details” identifying the possible errors that the XML file manually uploaded through this option may contain, and if the document has no errors, a detail will be shown indicating that it was uploaded successfully 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 the 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.
• Credit Note.
• Debit Note.
• Electronic Ticket.
• Export Invoice.

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): cr_ms_sbx@inbound.gosocket.com
• Production: cr@recepcionprd.gosocket.net

info

Note: If a customized exchange mailbox is needed for a customer, it must be escalated to the commercial team since this request generates an additional cost.

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.
• Credit Note.
• Debit Note.
• Electronic Ticket.
• Export Invoice.

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 into a single file, and only the .zip extension will be allowed.

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

f. Attachments can be sent, such as the invoice PDF or other files that may be required.

g. The maximum weight 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 that arrive at the mailbox, where, once received, they are stored and associated with their corresponding 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: Invoice12345.xml and Invoice12345.pdf, the .pdf file is understood to be the graphic representation of the DTE, so it is synced 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 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 XML files to be sent 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 (.zip) file. Once received, the system processes the document, generates the corresponding record, and securely stores it on the platform.

a. Tracking Management

To carry out 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 Gosocket the XML and the PDF, 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 respective XML in Gosocket's native format for 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 will be allowed:

• 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 if it presents validation errors from the regulatory entity after the tax 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 configuration of the 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 delivery.

warning

You can find the configuration details of the Reception API in 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 through the endpoint: POST - SendDocumentToUpload
• Persistence: Ensures the XML file is stored on the platform's servers for later 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 required to:

• Track the detailed status of the processing.
• Query the upload result through the endpoint: GET- GetDocumentUploadStatus

c. Post-storage processing actions

Once the document has been successfully stored in Inbox, the following actions will be allowed:

• 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 if it presents validation errors from the regulatory entity after the tax 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 configuration of the 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 delivery.

warning

You can find the configuration details of the Reception API in the following link: Reception API

---

4. RECEIVER MESSAGE

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

By using 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.

Currently, the commercial acknowledgment is sent for received documents as follows:

**1.**Receiver message:

a. Approved

b. Partially approved

c. Rejected

Once the documents are received in inbox and have passed the reception validations, Gosocket allows commercial acknowledgments to be applied as follows:

3.1. Receive commercial acknowledgments through the exchange mailbox

3.2. Manually issue the commercial acknowledgment for these documents.

4.1. Receiving 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, select the “Options” button and look for the “Commercial acknowledgment” section, located at: Inbox / Received tray / Options Button / Section: receiver message, Within this menu, you will find the following Commercial Acknowledgment options:

When entering the commercial acknowledgment option

**3.**Select the document's approval status. This can be approved, partially approved, or rejected.

**4.**Enter the message detail that will be displayed in the XML of the acknowledgment generated once it is approved.

**5.**Enter the emails to which a copy of the acknowledgment will be sent.

**6.**Press Send to send the request to the Tax Authority.

Once all the information for the receiver message has been entered and the Send button pressed, this event will be shown within the document preview in the notes section

and the event's XML sent to the Tax Authority will be shown in the attachments section, as shown below:

---

3.2.2. Apply commercial acknowledgments from the document preview

This process can also be done from the document preview.

Select Receiver Message from the Commercial acknowledgment menu. Then, fill out the form mentioned in item a of this section.

3.2.3. Iconography according to the commercial acknowledgment

Once the process is complete, a change in the document's status will be shown according to the approval status selected during the message issuance.

1. The Client Accepted status is shown after selecting approved in the document's status within the receiver message form
2. The status changes to Rejected when rejected is selected in the document's approval status within the receiver message form.
3. Partially Accepted is shown once partially approved is selected when filling out the receiver message form.
4. Likewise, the attached documents icon will be shown in dark gray to indicate that there is an attachment from the receiver message.

In addition, the event note and the attached XML file from the process will be shown in the document preview

The receiver message will be sent to the email account associated with the acknowledgment process, and the following notification will be displayed:

warning

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

---

5. QUERY OF DOCUMENTS RECEIVED FROM GOSOCKET

Once the documents have been processed by the reception 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 results. **

**2.**Display order control, which allows you to change how the search results are presented. **

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

**4.**Display section with the search result detail and representative iconography 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 be viewed.

**1.**Tax authority validation.

**2.**Distribution validation.

**3.**Smart Supply status validation.

**4.**Receiver Message Validation

The status column (1) will show the result of the validations applied, as explained in the 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 from 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 setting 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 the case 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 Reprocessing section.

* Note: Special configuration: The XML has a schema error, but if the setting 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 with 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 the Validated ET with schema error status 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