Skip to main content

The Spanish version is the authoritative reference. View in Spanish

Uruguay: Acceptance and Rejection of Documents

Through the ChangeDocumentStatus method, we can also issue acknowledgments of acceptance or rejection for received documents through the API.

Let's see how to issue these events.

The request parameters to issue these events are as follows:

ChangeDocumentStatus (request)
ParameterTypeDescriptionAllowed values
globalDocumentIdStringDocument identification in Gosocket. Required if countryDocumentId is not provided36-character alphanumeric UUID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
countryDocumentIdStringCountry-level tax identifier of the document, also known as CUFE, CLAVE, UUID, ID Required if globalDocumentId is not providedSee the Country Document ID Structure table
countryId*StringCountry code of the document's country of issuanceuy
status*IntegerAcceptance or rejection codeAcceptance: 033 or 33 Rejection: 31 or 031
Description*StringAcknowledgment commentsFree text
code*StringRejection code (required only in case of rejection)See the Rejection Codes table

*Required

Rejection Codes
CodeDescription
E20Expired purchase order
E21Goods in poor condition
E22Supplier disabled by controlling body
E23Consideration not received
E24Difference in prices and/or discounts
E25Invoice with calculation error
E26Difference in terms

Request example

image-20240918-224937.png

Note: Remember that before using the method, you must authenticate within the Authorization tab.

For this method we use the Body tab, select raw, and check or select JSON in Postman.

  1. Select the method type. In this case, you must select POST.
  2. Enter the method URL.
  3. Enter the parameters shown in the table above with their corresponding values.
  4. Press Send.

Response example

image-20240918-225352.png


Once the acknowledgment has been generated, the following elements are shown within the document preview, which can be viewed from the Gosocket Inbox:

image-20240918-225523.png

In the notes section of the preview we will find:

  1. Event generation, along with the user who generated it.
  2. The commercial event generated, which can be acceptance or rejection.
  3. A list of the email addresses to which the email was sent, or a note with the error explaining why the email could not be sent.

Additionally, within the Attachments section, we see the following:

  1. XML of the event generated for the document.

From the received documents query screen within the Inbox, the acceptance () or rejection () icon is shown among the statuses on the Received documents query screen.

image-20240918-230126.png


Characteristics

  • Acknowledgments can only be generated for documents approved by the ET (AuthorityStatus=2)
  • Acknowledgments can only be generated for documents when the document's issuance date does not exceed 20 calendar days from the current date.
  • The event is sent with the acknowledgment XML attached via email.
  • The acknowledgment is not sent to the Tax Authority.