The Spanish version is the authoritative reference. View in Spanish
Dominican Republic: Reception of documents (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 will be able to view the documents in the Inbox Received tray, together with their respective graphic representation and attached files.
Likewise, our system performs a series of automatic validations to ensure that the structure and integrity of the information strictly comply with the requirements of the tax authorities.
The following image describes, step by step, the document reception flow within the Inbox platform:
Dominican Republic reception process
1. XML document submission methods in Gosocket:
The supplier uploads the XML document through the API defined for RD. The requirements and conditions for this process are detailed in the following points.
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. Schema validation of the document
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:
a. 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 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 XML processing for the schema error
b. Successful: If the XML schema validation is correct, the document will continue with the reception flow.
Document detail Notes section - Successful schema validation
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 with its normal flow toward the following reception validations, such as the verification of the signature and of the tax authority.
The document will remain in Inbox as follows:
- In Gosocket the document will remain in status Validated ET with schema error and the icon
orange 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 yield one of the following results:
c. Failed: This means the document has been altered; the document reception flow will be stopped due to the signature error, so it will be registered in Gosocket with the status Signature Error, the interface will display an icon 
and the reason for rejection will be indicated in the preview notes, as follows:
Signature error icon in Inbox
Document detail Notes section - Signature Error
Detail of XML processing for the signature error
d. 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, the query validation with the Tax Authority is performed. Several results can be obtained from this validation:
e. 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 communication error.
f. Prior validation of the signature certificate in Gosocket Active
Gosocket performs a prior validation to check whether the receiving company has the signature certificate uploaded and active on the Gosocket platform, for which two responses can result:
g. The receiving company does NOT have a valid certificate: in this scenario the document is neither received nor stored in inbox.
h. The receiving company DOES have a valid certificate: in this scenario, the document validation with the Tax Authority continues.
i. When performing the document validation with the Tax Authority, two responses are generated:
- The document exists in the Tax Authority (See more detail in item j)
- The document does not exist in the Tax Authority (See more detail in item m)
j. At this point of the process, when the document does exist in the tax authority , two responses can result:
- If the document exists, but has a status of Rejected
(See more detail in item k) - If the document exists, but has a status of Accepted
(See more detail in item L)
k. Document Rejected by the Tax Authority
In case the document presents any of the following errors:
“Not Received” reason codes:
1: Specification error (Invalid schema).
2: Digital signature error.
4: Buyer RNC does not match.
If the document exists in the TA, but there is a rejection reason 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
L. Document Accepted by the Tax Authority
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.
If the result of the previous validations is satisfactory and the query with the tax authority is successful, the document will be registered in Gosocket with the status Accepted. In the interface, this status will be identified with a green check icon.
Accepted icon in inbox: Successful document validation with the TA
Document detail Notes section - Successful document validation with the TA
m. For the case when the document does NOT exist in the tax authority , an automatic retry process will be carried out:
- This indicates that the received document is not registered with the TA.
- In Gosocket it will remain with status Not Available in ET and the document will be assigned the icon
.
If the document is still not 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.
Note: For each query retry with the TA, a record is generated in the Notes section.
Document detail Notes section - Document validation with the TA: Not available
and after these retries, two responses can result:
n. If after the 30 attempts the document is still not found, it will remain permanently in status Not Available in ET, showing the following icon in the Inbox.
Rejected icon in inbox: Document validation with the TA
o. If during these retries the document is found in the TA, its status is updated, the process continues, and two responses can result:
- If the document exists, but has a status of Rejected (See more detail in item k)
- If the document exists, but has a status of Accepted (See more detail in item L)
6. Icons in inbox for the reception validation result
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 |
|---|---|---|
| p | Document has a schema error | |
| q | Document has a signature error | |
| r | Communication error with the Tax Authority | |
| s | Document was Rejected by the Tax Authority | |
| t | Document was Accepted by the Tax Authority | |
| u | Document not available or does not exist in the Tax Authority | |
7. Issuance of commercial acknowledgments
Once the document has been received and validated, the mercantile or commercial acknowledgments deemed necessary can be issued from the inbox platform, or otherwise sent through the exchange mailbox. This is explained in more detail in the Commercial acknowledgments section
2. MANUAL REPROCESSING OF DOCUMENTS
Additionally, a button was implemented in Inbox that allows manually reprocessing tax documents that have the status “ERROR” ❗, “Not Available in ET” .
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 at the following path, as applicable:
- Inbox/Received/Options/Actions/Reprocess document.
Accompanied by a selector that, as its name indicates, will allow selecting an Electronic Document independently or a set of them.
Next, a pop-up window will be displayed in which the user must confirm that they want to revalidate the previously selected documents.
Once the reprocessing has been generated, a banner will be displayed at the top of the page indicating that the document(s) were sent for reprocessing:
and finally, for any of the three reprocessing types generated through this option, the notes section will indicate:
- It records the email of the user who performed the document reprocessing.
- It generates a note “Document reprocessing performed by: correo@correo.com
- The document continues the reception validation flow.
This button allows reprocessing of the different validations of the reception process:
2.1. Reprocess document:
It 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. XML SUBMISSION METHODS
Currently, there are three methods for receiving documents into the system:
- API : Connection via API for integrated processing.
3.1. API
There are three APIs involved in the reception process:
3.1.1. Authentication
Its use is optional between taxpayers; however, it is recommended to validate identity between them and the tax authority. From this, a session is generated; within the address there are two endpoints:
3.1.2. Obtain 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
- Production: https://global-gosocket-api-rd-prd.azurewebsites.net/fe/autenticacion/api/semilla
| Method | GET |
|---|---|
| Parameters | N/A |
| Response | An XML that will later have to be signed with a digital certificate 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" |
3.1.3. Seed Validation and Token Retrieval
The seed and its signature are verified, resulting in obtaining a token that the recipient issues for authentication.
- Sandbox: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/autenticacion/api/validacioncertificado
- Production: https://global-gosocket-api-rd-prd.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" |
3.1.4. Tax Document Reception URL
Tax document reception URL, where the web service that will receive the e-CFs issued to it will be found.
- Sandbox: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/recepcion/api/ecf
- Production: https://global-gosocket-api-rd-prd.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 value of the token 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: A valid digital certificate is required to sign the Acknowledgment of Receipt and issue a response through the Reception API. This ensures the correct reception of e-CFs.
The certificate must be configured in Inbox and have the Signature toggle turned on, as shown below:
3.1.5. Considerations for Sending an XML via the API
It is important to keep the following points in mind when sending documents, as this will prevent them from being rejected by the application.
- Up to n XML files can be uploaded in a single upload.
- The same schema, signature, Tax Authority availability, and certificate validations performed via the API will be applied.
- The tax documents stipulated by the tax authority must be sent in XML format. These documents are:
- Electronic Tax Credit Invoice
- Electronic Consumption 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
4. COMMERCIAL ACKNOWLEDGMENTS
The commercial acknowledgment is intended to validate tax documents with the Tax Authority, and as a result, we will have 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.
4.1. Commercial Approval URL
Commercial approval URL, where the web service that will receive the commercial acknowledgments from the document recipient will be found.
- Sandbox: https://global-gosocket-api-rd-sbx.azurewebsites.net/fe/aprobacioncomercial/api/ecf
- Production: 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 value of the token 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: To ensure the correct issuance of the Commercial Acknowledgment for e-CFs (ACECF), it is mandatory to have a valid digital certificate, since it is required to sign the ACECF.
The certificate must be configured in Inbox and have the Signature toggle turned on, as shown below:
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 the documents to be managed must be selected 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:
- When selecting Accepted the pop-up window is displayed:
- Upon sending, a commercial approval is issued.
- When selecting Rejected the pop-up window is displayed:
- Enter the reason for rejection.
- Upon sending, the commercial rejection of the document is issued, which is sent to the issuer.
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:
4.2.2. Apply 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 using the Commercial acknowledgment button.
4.2.3. Icons by commercial acknowledgment
When viewing the received documents through the Received option in Inbox, you can see the icons indicating the types of acknowledgments generated for each document.
Commercial approval: Acceptance or Rejection: This status reports on the issuance of the acknowledgment for a document, which can be displayed 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.
For more details on executing commercial acknowledgments through 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 queried from the Gosocket portal in the Inbox/Received section. **
This section shows the following screen:
- Filters section to optimize the search results. **
- Display order control, with which you can modify how the search results are presented. **
- List of options related to export, commercial responses, and internal movements of the Electronic Documents. **
- Display section with the search result details and icons representing the most relevant status changes. **
* For more information on these points, see the Inbox documentation.**
Once the document search has been performed, the main grid will display the list of received documents that met the established search criteria; in this grid, in addition to relevant document information, the document status can be observed.
**1.**Tax authority validation.
**2.**Distribution validation.
**3.**Smart Supply status validation.
In the status column (1), the result of the applied validations will be shown, as explained in the section XML reception process.
| Icon | Status | Validation |
|---|---|---|
| VALIDATED | Document approved by the TA |
| REJECTED* | Document rejected by the TA |
| Not Available in ET | Document does not exist 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 the case where the document remains in status “ERROR”, 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 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 document's "Notes" section.
Despite this finding, the document will continue with its normal flow toward the following reception validations, such as the verification of the signature and of the tax authority.
The document will remain in Inbox as follows:
- In Gosocket the document will remain in status Validated ET with schema error and the icon orange 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