Dominican Republic: Document Reception

1. OPERATION

Document reception flow for the Dominican Republic

1. The supplier has the option to issue the document in two ways:
   1. The supplier issues the document and sends it to the Gosocket Reception API.
      (The section Submission Method - Via API explains the conditions to be considered for the submission).
   2. The supplier manually uploads the XML through the Gosocket Upload (The section Submission Method - Manual XML Upload explains the conditions to be considered for the submission).

Note: When the document reception channels are used, both the API and the manual XML upload through the Upload option, both processes execute the schema, signature, and TA (Tax Authority) validations.

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 guarantee that it complies with the format established by the tax authority. Depending on the validation performed, one of the following results can be obtained:

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

4. The document's electronic signature is validated, this in order to guarantee that it has not been altered. From this validation, one of the following results can be obtained:

   1. Failed: This means that the document has been altered, so it will be registered in Gosocket with rejected status and the red exclamation symbol will be shown in the icons also, the reason for the rejection is indicated in the notes. In addition, an acknowledgment of receipt is issued to the issuer with the document's rejection.
   2. Successful: If the digital signature validation is successful, it continues with the reception flow.

5. Then, it is queried with the Tax Authority whether the document exists. From this validation, one of the following results can be obtained:

a.   Document not found (Failed)

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

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

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

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

b. Document rejected by the TA

If the document presents any of the following errors:

Reason Codes “Not Received”:

1: Specification error (Invalid schema).

2: Digital signature error.

4: Buyer RNC does not match.

If the document exists in the TA but presents one of the aforementioned rejection reasons at the Tax Authority, its status in Gosocket will be Rejected .

For the above, the document is managed as follows on the Gosocket platform:

• It is stored on the platform.
• The corresponding error is recorded.
• The acknowledgment of receipt (ARECF) is generated.
• The status 1: e-CF Not Received is assigned.

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

c. Document registered with no errors at the TA, but the Signature certificate is validated

If the document is correctly registered with the TA, Gosocket performs an internal validation to verify whether the company has an active signature certificate on the platform:

With active certificate:

• The acknowledgment of receipt (ARECF) is issued and signed to the issuer.
• The document is marked with status 0: e-CF Received.
• The document is stored on the platform.

Without active certificate:

• The document is neither received nor stored on the platform.

d. Document has an internal exception by 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 the icon ❗. will be assigned to it.

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

7. Once the document has been received and validated correctly, the commercial acknowledgment is issued according to the recipient's criteria. (This is explained in more detail in the Commercial Acknowledgments section)

a. Additional automatic reprocessing of tax documents.

Reprocessing was enabled with the objective of revalidating documents that remain with Not Available in ET status, which are identified with the icon in the Inbox:

Regardless of the Tax Authority's response regarding the existence of the document, the system must generate an acknowledgment of receipt, since this is mandatory.

The execution interval is 30 reprocessing attempts every 10 minutes.

1. If a response is received from the Tax Authority during this interval, the document's status will be updated in the Inbox. However, this change will not be notified to the customer.
2. Otherwise, the document will remain with Not Available in ET status, keeping the icon in the Inbox.

b. Options Button (Manually reprocess document)

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

This button allows querying the document's status with the TA and we will find it at the following path:

Inbox/received/options/Actions/Reprocess document.

Accompanied by a selector that, as its name indicates, will allow independently selecting 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 for documents that remained in Not Available in ET or ERROR ❗ . status.

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

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

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

---

2. SUBMISSION METHOD

As already indicated, the solution performs the process of receiving documents and acknowledgments through the Gosocket API in the Dominican Republic, which must comply with the communication standard between the issuer and recipient defined by the Dirección General de Impuestos Internos (DGII).

There are two ways to carry out the document reception process in the Dominican Republic:

a. Via API

b. Manual XML upload through the Gosocket Upload

a. Via API

There are three APIs involved in the reception process:

Authentication

Its use is optional among taxpayers; however, it is recommended in order to validate identity between them and the tax authority. From this, a session is generated; within the address there are two endpoints:

i. Get Seed

A seed XML file is generated and delivered so that it can later be digitally signed with a certificate and sent to the second endpoint to obtain the token.

·       Sandbox: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/autenticacion/api/semilla

·       PRD: https://global-gosocket-api-rd-prd.azurewebsites.net/fe/autenticacion/api/semilla

Method	GET
Parameters	N/A
Response	An XML that will subsequently have to be signed with a digital certificate in order to be exchanged for a token through the ValidacionCertificado endpoint
Example	curl -X GET "https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/autenticacion/api/semilla" -H "accept: application/json"

ii. Seed Validation and Token Retrieval

The seed and its signature are verified, resulting in obtaining a token issued by the recipient for authentication.

• PRD: https://global-gosocket-api-rd-prd.azurewebsites.net/fe/autenticacion/api/validacioncertificado
• SBX: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/autenticacion/api/validacioncertificado

Method	POST
Parameters	Signed seed XML, obtained from the previous URL.
Response	A token with its expiration and issuance date.
Example	curl -X POST "https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/autenticacion/api/validacioncertificado" -H "accept: application/json" -H "Content-Type: multipart/form-data" -F "xml=@semillaFimada.xml;type=text/xml"

---

iii. Tax Document Reception URL

Tax document reception URL, where the web service that will receive the ECF issued to it will be located.

• PRD: https://global-gosocket-api-rd-prd.azurewebsites.net/fe/recepcion/api/ecf
• SBX: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/recepcion/api/ecf

Method	POST
Parameters	e-CF (XML)
Conditional on authentication having been declared	An Authorization header with the Bearer scheme and the token value obtained during authentication (if used).
Response	An XML containing the acknowledgment of receipt information (signed with a digital certificate)
Example	curl -X POST "https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/recepcion/api/ecf" -H "accept: application/xml" -H "Content-Type: multipart/form-data" -F "xml=Factura.xml;type=text/xml"

note

Note: It is necessary to have a valid digital certificate in order to sign the Acknowledgment of Receipt and issue a response through the Reception API. This way, the correct reception of the e-CF is guaranteed.

The certificate must be configured in the Inbox and have the Signature toggle turned on as shown below:

b. Manual XML upload through the Gosocket Upload

Gosocket has a tool within the Inbox platform, through which the supplier 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 performs the processing of the documents, where, once the document is received, it begins the validation process.

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 popup will be shown with the “Error Details” identifying the possible errors that the XML file manually uploaded through this option may contain, and otherwise, if the document has no errors, a detail will be shown indicating that it was successfully uploaded to the Gosocket platform:

3. finally, the document will be displayed in the received tray of the Inbox:

i. Considerations for the manual XML upload

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

• In a single upload, up to n XML files can be uploaded.
• The same schema, signature, Tax Authority availability, and certificate validations performed via the API will be carried out.
• The tax documents stipulated by the tax authority must be sent in XML format. These documents are:
  • Electronic Credit Invoice
  • Electronic Consumer Invoice
  • Electronic Debit Note
  • Electronic Credit Note
  • Electronic Purchases
  • Electronic Minor Expenses
  • Special Regimes Electronic
  • Electronic Government
  • Electronic Export Voucher
  • Electronic Foreign Payment Voucher
  • Consumption Invoice Summary

---

3. COMMERCIAL ACKNOWLEDGMENTS

a. Commercial approval URL

Commercial approval URL, where the web service that will receive the commercial acknowledgments from the document's recipient will be located.

• SBX: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/aprobacioncomercial/api/ecf
• PRD: https://global-gosocket-api-rd-prd.azurewebsites.net/fe/aprobacioncomercial/api/ecf

Method	POST
Parameters	ACECF (XML with the commercial acknowledgment signed with a digital certificate)
Conditional on authentication having been declared	An Authorization header with the Bearer scheme and the token value obtained during authentication (if used).
Response	HTTP 200
Example	curl -X POST "https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/aprobacioncomercial/api/ecf" -H "accept: application/json" -H "Content-Type: multipart/form-data" -F "xml=ACECF.xml;type=text/xml"

note

Note: To guarantee the correct issuance of the Commercial Acknowledgment of the e-CF (ACECF), it is mandatory to have a valid digital certificate, since this is necessary to sign the ACECF.

The certificate must be configured in the Inbox and have the Signature toggle turned on as shown below:

b. Generation of commercial acknowledgments

In addition to allowing the reception and validation of tax documents, Gosocket also has the option to issue commercial approval for these documents.

The commercial acknowledgment's purpose is to validate the documents with the Tax Authority and, as a result, we will have a status change within our received documents tray in the Gosocket Inbox

These events can be generated from two different points in the Inbox that we will explore below:

i. Options Button (Received Documents)

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

1. Section to mark one or several documents in order to carry out the different actions available.
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:

1. By selecting Accepted the pop-up window is shown:
   1. By clicking Send, a commercial approval is issued.

2. By selecting Rejected the pop-up window is shown:
   1. Enter the reason for the rejection.
   2. By sending, the commercial rejection of the document is issued, which is sent to the issuer.

Once the commercial acknowledgment has been generated, its record will be shown in 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 we see below:

ii. Apply commercial acknowledgments from the document preview

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

iii. Icons according to the commercial acknowledgment

When accessing the received documents through the Received option in the Inbox, you can see the icons that indicate the types of acknowledgments that have been generated for each document.

Commercial approval: Acceptance or Rejection: This status informs about the issuance of the acknowledgment for a document, which can be shown in two scenarios:

a. Gray, indicates that the document does not yet have an acknowledgment of receipt.

b. Green, indicates that the acknowledgment was issued as Accepted.

c. Red, indicates that the acknowledgment was issued as Rejected.

warning

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

---

4. QUERYING RECEIVED DOCUMENTS 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 result. **
2. Display order control, with which you can modify the way 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 result and icons representing the most relevant status changes. **

warning

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

Once the document search has been performed, the main grid will show the list of received documents that met the established search criteria; in this grid, in addition to relevant document information, you can also see the document's status.

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

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

Icon	Status	Validation
	VALIDATED	Document approved by the 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

**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 the case in which the document remains in “ERROR” status, the user can reprocess it through the “Reprocess document” button in order to perform the schema, signature, or TA validations again. This process is explained in detail in the “Options Button (Reprocess document)”.

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

warning

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