Paraguay: Document Receipt

1. OPERATION

Document receipt flow for Paraguay

1. The provider can issue the document in two ways:
   1. The provider manually uploads the XML through the Gosocket Upload (the Submission Method - Manual XML Upload section explains the conditions to consider when sending).
   2. The provider sends the XML file through the exchange mailbox (the Submission Method - Exchange Mailbox section explains the conditions to consider when sending).

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

Upload option, both processes run schema, signature, and validation with the TA (Tax Authority).

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

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

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

4. The document's electronic signature is validated to ensure it has not been altered. Depending on the validation performed, one of the following results can be obtained:

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

5. Next, a query is made to the Tax Authority to check whether the document exists. This validation can produce one of the following results:

a.   Document not found (Failed)

• Indicates that the received document is not registered with the TA.
• In Gosocket, it will remain with Not Available in TA.
• The icon will be shown on the received documents query screen (Inbox).

If the document is not yet registered with the TA or the query service is unavailable, Automatic Retries are performed as follows:

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

Note: A record is generated in the Notes section for each query retry with the TA.

b.  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 changes to Rejected and it is assigned the icon .

c. Document has an internal exception from Gosocket ❗

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's status changes to ERROR and it is assigned the icon ❗ .

d. Document found in the TA

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

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

7. Once the document has been received and validated, the commercial or mercantile acknowledgments deemed necessary can be issued at your discretion. (This is explained in more detail in the Commercial Acknowledgments section).

a. Options Button (Manually Reprocess Document)

Additionally, a button was implemented in Inbox that allows manually reprocessing tax documents with status “ERROR” ❗ or  “Not Available in TA” .

This button allows reprocessing of the different validations in the receipt process, and it 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 you to independently select an Electronic Document or a set of them.

Within this menu you will find the Reprocess Document option, which will allow the user to start reprocessing documents that remained in Not Available in TA or ERROR ❗ status.

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

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

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

---

2. SUBMISSION METHOD

As already indicated, the solution processes the documents; once the document is received, the validation process begins.

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

a. Manual XML upload via the Gosocket Upload

b. Exchange mailbox

a. Manual XML Upload via the Gosocket Upload

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

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

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

As already indicated, the solution processes the documents; once the document is received, the validation process begins.

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

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

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

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

i. Considerations for Manual XML Upload

• Up to n XML files can be uploaded in a single upload.
• The same schema, signature, Tax Authority availability, and certificate validations performed for the exchange mailbox will be carried out.
• 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 Receipt.

b. Exchange Mailbox

The mailboxes to be used are:

• Sandbox: py_sbx@inbound.gosocket.com
• Production**:** py@recepcionprd.gosocket.net

i. Considerations for the Exchange Mailbox

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

• 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 Receipt.

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

The solution can process the graphic representation PDFs, if included, as well as attached documents that arrive at the mailbox; once received, they are stored and associated with their corresponding document, allowing download within Inbox.

The process works as follows:

• If an XML document arrives at the mailbox along with a PDF file with the same name, for example: Factura12345.xml, Factura12345.pdf, the .pdf file is understood to be the graphic representation of the DTE (Electronic Tax Document), so it is synchronized that way in Gosocket and is 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 attached documents.

• For sending attachments, it is recommended to send each DTE (Electronic Tax Document) with its attachments separately, since if more than one XML document arrives, the graphic representation will only be stored as long as the PDF file has the same name as its corresponding XML; the remaining 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. COMMERCIAL ACKNOWLEDGMENTS

In addition to allowing the receipt and validation of tax documents, Gosocket also offers the option of issuing acknowledgments for these documents.

Currently, there are 4 events related to received documents:

1. Notification Event – Receipt
2. Agreement Event
3. Disagreement Event
4. Non-Recognition Event

Through the use of these events, the receiver reports the receipt, acceptance, or rejection of each document.

The commercial acknowledgment is intended to validate tax documents with the Tax Authority, and as a result, we will see a status change within our received documents tray in the Gosocket Inbox

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

a. Options Button (Received Documents)

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

1. Section for marking one or more documents to carry out the generation of the different available actions.
2. Options menu where the functionality to generate the commercial acknowledgment will be located.

Within this menu you will find the following Commercial Acknowledgment options:

i. Notification Event - Receipt

Selecting the Notification - Receipt Event 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 XML per document. For example, if three documents have been selected and the Notification - Receipt Event 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 shown within the document preview in the notes section, and the event XML sent to the Tax Authority will be shown in the attachments section, as shown below:

Likewise, the Notification - Receipt Event will be shown in the document's status iconography.

ii. Agreement Event

Selecting the Agreement Event is the event that produces an acknowledgment of receipt showing agreement with the document. That is, the document's information is valid for the receiver.
There are two types of agreement:

1. Full agreement, which is agreement with all the document's information. This means that the receiver validated the document in its entirety.
2. Partial agreement is the type of agreement indicating that the receiver does not validate the document in its entirety, but there is correct information within it.

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

a. Select one of the two types of agreement

b. Enter the acknowledgment description followed by the validate button

c. Finally, the XML with the event acknowledgment is generated.

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

Likewise, the Agreement Event will be shown in the document's status iconography.

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

iii. Disagreement Event

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

For example, when selecting the Agreement 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 shown within the document preview in the notes section, and the event XML sent to the Tax Authority will be shown in the attachments section, as shown below:

Likewise, the Disagreement Event will be shown in the document's status iconography.

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

iv. Non-Recognition Event

Selecting the Non-Recognition Event will help notify that the receiver does not recognize the charge for the previously selected document.

For example, when selecting the Non-Recognition 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 shown within the document preview in the notes section, and the event XML sent to the Tax Authority will be shown in the attachments section, as shown below:

Likewise, the Non-Recognition event will be shown in the document's status iconography.

and within the document preview, in the upper right corner, the message “CLIENT REJECTED” will be shown, along with the text “Non-Recognition Event DE/DTE” in red

b. 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 be performed from the document preview using the Commercial Acknowledgment button.

c. Iconography by Commercial Acknowledgment

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

a. Gray , which will be 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 be shown in the following ways: For acceptance, an icon with a thumbs-up will be shown in green ; if rejected, an icon with a thumbs-down will be shown in red ; if this event is not present, the hand will be in gray .

warning

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

---

4. QUERYING RECEIVED DOCUMENTS FROM GOSOCKET

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

The following screen is shown in this section:

1. Filters section to optimize the search results. **
2. Display order control, with which you can modify 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 details of the search results and iconography representing the most relevant status changes. **

warning

* For more information on these points, refer to the Inbox documentation.**

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

1. Tax authority validation.
2. Distribution validation.
3. Smart Supply status validation
4. Acknowledgment of receipt
5. Agreement, disagreement, and non-recognition acknowledgment.

The status column (1) will show the result of the applied validations, as explained in the Operation section.

Icon	Status	Validation
	VALIDATED	Document approved by the TA
	REJECTED *	Document rejected by the TA
	Not Available in TA	Document does not exist in the TA
❗	ERROR *	Document rejected or internal exception by Gosocket

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

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

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

warning

For more information on the options available in this section, refer to the Inbox manual.

---