Inicio  |  Timbrado  |  Pruebas de cancelación de Web Services de timbrado
La LCO fue actualizada por última vez el 01/may/2024

Cancelation examples in testing environment for timbrado

Description and examples of the usage for the cancelation-webvervices in timbrado.

This document describes how the available methods for the new version of invoice cancelation can be used in several cases. All available methods behave the same and return the same exit codes. The only difference is in the number of parameters given to each method.
Since this is a testing environment, the maximum time elapsed for invoice cancelation is 5 minutes instead of the average 72 hours.
Please keep in mind, that all methods receive the UUID of an invoice to be canceled only when its was Solución Factible® the entity which stamped (timbro) the invoice. If the invoice was stamped (timbrado) by another entity, the printed expression (Expresion impresa) of the invoice must be included in the UUID parameter.

Available Web services

Cases

timbrado:cancelar

Returns

timbrado:cancelarBase64

Returns

cancelacion (timbrado): cancelar

Returns

cancelacion (timbrado): cancelarAsincrono

This method's advantage is that if the process is successful, an email will be sent to you notifying you with the result of the operation.

Returns

Cases

The method cancelar of the cancelacion webservice in timbrado is used in all cases.

Cancelling an invoice with a related document

Response

Trying to cancel an invoice already in a cancelation attempt

Response

The attempt to cancel an invoice returns a denial-to-cancel response by the invoice's recipient

Response

The attempt to cancel an invoice returns a successful cancelation response

Response

After waiting 5 minutes and executing the method again the next response will be received:

Cancelling an invoice which Solución Factible did not stamped, using the invoice's printed expression

Response

After waiting 5 minutes and executing the method again the next response will be received:

Datos de contacto
comments powered by Disqus