Catalog of web service response errors - Direct Integration Manual Index - Electronic Bill

De tfhkacolwiki
Ir a la navegación Ir a la búsqueda

Catalog of web service response errors

In the following section you will find information regarding web service responses.

Enviar Method
Generic Codes Result Response Code Message
Successful Submission Processed 200 Document sent successfully (Synchronous).
Successful Submission Processed 201 Document received, will be sent later to DIAN (Asynchronous).
Successful Submission Processed 208 Contingency document received, will be sent later to DIAN (Asynchronous).
Error due to General Exceptions Error 103 Processing Error (Must send xml-request for analysis)
Error in TFHKA Validations layer Error 109 Ex: The field {field name} is mandatory Ex: The field {field name} must be numeric.

Exm: Client has no Folios Available (Must send xml-request for analysis)

Error due to Local XSLT Exceptions (TFHKA) Error 161 Must validate the generated XML/UBL (Must send xml-request for analysis)
Error in Local XSLT Validations (TFHKA) Error 110 Ex: Fatal: [FAR08]- (R) Invoice total 100.00 different from the sum of Total gross value + Total Taxes - Advances (+/-) Rounding : 120.00 } (Must send xml-request for analysis)
Error Invoice already issued or found in TFHKA and DIAN Error 114 Previously issued document. Document previously issued by another technology provider {NIT of the PT}. An error has occurred when consulting the XML document in DIAN.
Document rejected by DIAN Error 99 Document was rejected by DIAN (Must validate the reasons for rejection or DIANValidationRules)
Data Submission Error 111 The length of the Token [company/password] field does not comply with the allowed range. Token [company/password] field must have only numbers and letters.
Invalid Token Error 101 The Issuer Token is invalid (the environment to which the used tokens and connection URL's correspond must be validated).
Error when parsing the document Error 112 Error when extracting the information from the document to the voucher. (Must send xml-request for analysis)
Error incorrect validations in the ranges Error 117 Error. The range, invoice date or authorization date are invalid / Error the document number is invalid. (You must validate sequential configurations in the portal and ERP)
Error authorization validation error in ranges Error 118 Error, authorization number or document type is invalid / Error document number is invalid. (Must validate sequential configurations in the portal and ERP)
Folios validation error Error 119 No folios available, you must contact our billing team to purchase a transaction or folios package.
Range validation error Error 150 The numbering range does not exist (You must validate the type of document and if the range is configured in the portal).

@IMPORTANT: In case of an error code different from the above, please send the document's soap-Envelope request to the alias integracion_fel_co@thefactoryhka.com explaining the case.

EstadoDocumento Method
Generic Codes Result Response Code Message
Satisfactory Response Processed 200 Invoice data is returned.
Invalid Token Error 101 The Issuer Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Execution Error Error 103 An error has occurred in the execution of the service, please try again later.
Error when extracting data Error 105 Error when extracting document data.
EnvioCorreo Method
Generic Codes Result Response Code Message
Successful Response Processed 200 The email has been sent correctly.
Invalid Token Error 101 The Sender Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Error de Ejecución Error 103 An error has occurred in the execution of the service, please try again later.
Correo inválido Error 106 Formato de correo electrónico inválido.
DescargaPDF Method
Generic Codes Result Response Code Message
The requested file is returned Processed 200 The email has been sent correctly.
Invalid Token Error 101 Sender Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Execution Error Error 103 An error has occurred in the execution of the service, please try again later.
Error Extracting Data Error 105 Error, could not get the requested file.
DescargaXML Method
Generic Codes Result Response Code Message
Successful Response Processed 200 The requested file is returned.
Invalid Token Error 101 The Issuer Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Execution Error Error 103 An error has occurred in the execution of the service, please try again later.
Error when extracting data Error 105 Error, could not get the requested file.
GenerarContenedor Method
Generic Codes Result Response Code Message
Successful Response Processed 200 he requested file is returned.
Invalid Token Error 101 The Issuer Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Execution Error Error 103 An error has occurred in the execution of the service, please try again later.
Error when extracting data Error 105 Error, could not get the requested file.
FoliosRestantes Method
Generic Codes Result Response Code Message
Successful Response Processed 200 The requested file is returned.
Invalid Token Error 101 The Issuer Token is invalid.
Validations Error Processed 102 Invalid document number, does not exist.
Execution Error Error 103 An error has occurred in the execution of the service, please try again later.
CargarAdjuntos Method
Generic Codes Result Response Code Message
Successful Submission Processed 200 File {nombreDelArchivo}{extension} successfully stored.
Error in file upload Error 107 It was previously noted that for the {consecutivo} document issued by {NIT Emisor} the expected attachments had already been completed (i.e. the send property was already set to "1" previously).
Error in Validations Processed 109 [Error Section] the tag {nombre del campo} must have a catalog value. [Error Section] the tag {nombre del campo} is required. [Error Section] the tag {nombre del campo} debe ser un {tipo de datos} de {tamaño} {numérico/alfanumérico}.