Diferencia entre revisiones de «Generalidades - Direct Integration Manual Index - Electronic Bill»

De tfhkacolwiki
Ir a la navegación Ir a la búsqueda
(Página creada con «<includeonly>=</includeonly>==Historial de versiones==<includeonly>=</includeonly> {| class="wikitable" style="margin: auto;" |- ! style="background:#e9e9e9; text-align:cen…»)
 
Línea 1: Línea 1:
<includeonly>=</includeonly>==Historial de versiones==<includeonly>=</includeonly>
+
 
 +
<includeonly>=</includeonly>==Version record==<includeonly>=</includeonly>
 
{| class="wikitable" style="margin: auto;"
 
{| class="wikitable" style="margin: auto;"
 
|-
 
|-
! style="background:#e9e9e9; text-align:center;"|Versión
+
! style="background:#e9e9e9; text-align:center;"|Version
! style="background:#e9e9e9; text-align:center;"|Fecha lanzamiento
+
! style="background:#e9e9e9; text-align:center;"|Launch date
! style="background:#e9e9e9; text-align:center;"|Descripción
+
! style="background:#e9e9e9; text-align:center;"|Description
 
|- valign="center"
 
|- valign="center"
 
| 0
 
| 0
 
| 07/05/2019
 
| 07/05/2019
 
|
 
|
* Versión Preliminar.
+
* Preview version.
 
|-
 
|-
 
| 1.0
 
| 1.0
 
| 14/06/2019
 
| 14/06/2019
 
|
 
|
* Versión Inicial.
+
* Initial version.
* Referencia DIAN “Anexo Técnico V1.4 (19-04-19).
+
* "Technical annex V1.4 (19-04-19)" DIAN reference.
 
|-
 
|-
 
| 1.1
 
| 1.1
 
| 04/07/2019
 
| 04/07/2019
 
|
 
|
* Actualización Referencia DIAN “Anexo técnico de factura electrónica de venta – final”
+
* "Sale electronic bill Technical annex – final" DIAN Reference update.
 
|-
 
|-
 
| 1.2
 
| 1.2
 
| 04/07/2019
 
| 04/07/2019
 
|
 
|
* Actualizaciones menores
+
* Minor updates
 
|-
 
|-
 
| 1.3
 
| 1.3
 
| 19/08/19
 
| 19/08/19
 
|
 
|
* Actualizaciones menores
+
* Minor updates
 
|-
 
|-
 
| 1.4
 
| 1.4
 
| 23/08/19
 
| 23/08/19
 
|
 
|
* Actualización respuesta ante el método enviar.
+
* Answer update in view of the send method.
* Lista de campos extensibles y catalogo de errores.
+
* List of extensible fields and bug catalog.
 
|-
 
|-
 
| 1.5
 
| 1.5
 
| 09/2019
 
| 09/2019
 
|
 
|
* Actualizaciones de comodines con base en el Anexo Técnico del 06 de septiembre
+
* Wildcards updates based on the September 6th- technical annex.
 
|-
 
|-
 
| 1.6
 
| 1.6
 
| 04/2020
 
| 04/2020
 
|
 
|
* Actualizaciones con base en el Anexo Técnico 1.8.
+
* Updates based on the technical annex 1.8.
* Acuse del adquiriente.
+
* Acknowledgment of the purchaser.
* Personalización correo.
+
* Mail personalization.
* Extras.
+
* Additional features.
* Radicar documentos en recepción.
+
* Settle documents at reception.
* Tablas de códigos.
+
* Code  tables.
* Cambio del nombre del documento.
+
* Change of the document's name.
* Entre otros cambios menores.
+
* Among other minor changes.
 
|-
 
|-
 
| 1.7
 
| 1.7
 
| 06/2020
 
| 06/2020
 
|
 
|
* Actualizaciones con base en el Anexo Técnico V1.7-2020.  
+
* Updates based on the technical annex V1.7-2020.  
 
* Ajustes de funcionalidades de la plataforma en el mes de mayo.
 
* Ajustes de funcionalidades de la plataforma en el mes de mayo.
 
|-
 
|-
Línea 64: Línea 65:
 
| 06/2021
 
| 06/2021
 
|
 
|
* Actualizaciones en base al anexo técnica V1.8 de la Resolución 000012. Campos Sector Salud. Tablas de códigos.
+
* Updates based on the technical annex V1.8 of the 000012 Resolution. Health sector fields. Code  tables.
 
|-
 
|-
 
| 2.1
 
| 2.1
 
| 10/2021
 
| 10/2021
 
|
 
|
* Actualizaciones en base al anexo técnica V1.8 de la Resolución 000012. Campos Sector Salud. Tablas de códigos.
+
* Updates based on the technical annex V1.8 of the 000012 Resolution. Health sector fields. Code  tables.
 
|-
 
|-
 
|}
 
|}
  
<includeonly>=</includeonly>==Cómo obtener soporte==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>==How to get support==<includeonly>=</includeonly>
*Soporte de 1er nivel:  
+
*First level support:  
::Soporte telefónico / email / chat o tele-conferencias en horario 5x8 para atención de consultas y fallas de usuario.
+
::Phone support / e-mail / chat or teleconference in 5x8 schedule for consultation service and user failures.
*Soporte de 2do nivel:
+
*Second level support:
::Soporte resolución remota de incidencias en el sistema en horario 5x8
+
::Support remote resolution of incidents in the system in schedule 5X8
::::Escriba  a [mailto:soporte@thefactoryhka.com.co soporte@thefactoryhka.com.co]
+
::::Write to [mailto:soporte@thefactoryhka.com.co soporte@thefactoryhka.com.co]
  
Para consultas referente a configuraciones y errores en el Portal:
+
Consultations relating to configurations and errors in the portal:
 
* soporte_fel_co@thefactoryhka.com
 
* soporte_fel_co@thefactoryhka.com
  
Para consultas referente a configuraciones de ERP, casa de software e integración:
+
Consultations relating to configurations of ERP, software house and integration:
 
* integracion_fel_co@thefactoryhka.com
 
* integracion_fel_co@thefactoryhka.com
  
  
'''Lineas de atención telefónica:'''
+
'''Telephone service lines:'''
 
* '''MASTER''' +57 (1) 746.08.12
 
* '''MASTER''' +57 (1) 746.08.12
 
*        +57 (1) 508.8990
 
*        +57 (1) 508.8990
Línea 93: Línea 94:
 
*        +57 (1) 517.6796
 
*        +57 (1) 517.6796
 
*        +57 (1) 311.3063
 
*        +57 (1) 311.3063
** '''Soporte Técnico''' → Opción 2
+
** '''Technical support''' → Option 2
** '''Integración ''' → Opción 5 Luego Opción 1
+
** '''Integration ''' → Option 5 Then Option 1
  
<includeonly>=</includeonly>===Para Sesiones:===<includeonly>=</includeonly>
+
<includeonly>=</includeonly>===Synchronous sessions:===<includeonly>=</includeonly>
  
<includeonly>=</includeonly>====Sesiones Soporte====<includeonly>=</includeonly>
+
<includeonly>=</includeonly>====technical support session====<includeonly>=</includeonly>
Inscripción como facturador electrónico, Configuración de Rangos de Numeración, Configuración Datos Fiscales, Pruebas de Habilitación, Configuración ambiente Producción, manejo y uso del Portal de Facturación electrónica de TFHKA
+
Registration as an electronic biller, configuration of numbering ranges, fiscal data configuration, Enabling Tests, Production environment configuration, managment and use of the TFHKA electronic billing portal.
  
'''Dirigido a:''' Agencias Comerciales Casas de Software Aliadas - Clientes Finales
+
'''Addressed to:''' Comercial agencies Ally software factories - Final clients
  
'''Horario:'''  Martes y Jueves a partir de las 8:30 AM
+
'''Schedule:'''  Tuesday and thursday  from 8:30 AM to 10:00 AM
  
 
[https://meet.google.com/yyg-pujr-yqv Enlace Sesiones de Soporte]
 
[https://meet.google.com/yyg-pujr-yqv Enlace Sesiones de Soporte]
  
  
<includeonly>=</includeonly>====Sesiones Área Integración<includeonly>=</includeonly>====
+
<includeonly>=</includeonly>====Integration area sessions<includeonly>=</includeonly>====
Solución Casos de Integración
+
Solución integration cases
  
'''Dirigido a:''' Clientes que realicen desarrollos de Software para integrarse con TFHKA, Casas de Software Aliadas
+
'''Addressed to:''' Clients that realice Software development to do integration with TFHKA, Ally software factories
  
'''Horario:'''  Martes y Jueves a partir de las 8:30 AM
+
'''Schedule:''' Tuesday and thursday from 8:30 AM to 10:00 AM
  
 
[http://meet.google.com/fzo-xmyc-duk Enlace Sesiones Integración]
 
[http://meet.google.com/fzo-xmyc-duk Enlace Sesiones Integración]
 
{{clear}}
 
{{clear}}
<includeonly>=</includeonly>==Descripción general==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>== General description==<includeonly>=</includeonly>
En el presente documento se describe el proceso de integración entre el modelo de facturación electrónica con validación previa de acuerdo a las actualizaciones normativas y técnicas proveniente de la DIAN y/o controles propios en nuestro modelo de integración.
+
This document describes the integration process between the electronic invoicing model with prior validation according to regulatory and technical updates from the DIAN and/or own controls in our integration model.
  
Para el desarrollo de éste documento, se tomó como referencia los '''Anexos técnicos V1.7-2020 (vigente) y V1.8 (este último liberado en octubre de 2019 por la DIAN)'''.
+
For the development of this document, was taken as reference the  '''Technical annexes V1.7-2020 (current) and V1.8 (this last released in October 2019 by the DIAN)'''.
  
'''Nota:''' No todas las funcionalidades, catalogos y escenarios de facturación referentes al Anexo Técnico V1.8 están habilitados por la DIAN.
+
'''Note:''' Not all functionalities, catalogs and billing scenarios referring to the Technical Annex V1.8 are enabled by the DIAN.
 
{{clear}}
 
{{clear}}
===¿Qué es The Factory HKA-DFACTURE?===
+
===¿What is The Factory HKA-DFACTURE?===
Es una plataforma de facturación electrónica, diseñada para dar cumplimiento a la legislación vigente en Colombia y ofrecer valores agregados mediante servicios complementarios.
+
It is an electronic billing platform, designed to comply with current legislation in Colombia and offer added values through complementary services.
===¿Qué es The Factory HKA-Dfactura?===
+
===¿What is The Factory HKA-Dfactura?===
Es un portal con capacidad de emitir documentos bajo el esquema de facturación electrónica, administrada desde el portal web y dirigido a contribuyentes que tengan la obligación de expedir factura electrónica por resolución de la DIAN.
+
It is a portal with the capacity to issue documents under the electronic invoicing scheme, managed from the web portal and Addressed to taxpayers who have the obligation to issue electronic invoices by resolution of the DIAN.
===¿Qué es Dintegración?===
+
===¿What is Dintegración?===
Es un producto dirigido al integrador y está conformado por los siguientes componentes:
+
It is a product aimed at the integrator and is made up of the following components:
*Manuales de integración.
+
*Integration manuals.
*Bolsa de horas de soporte vía email y/o tele-conferencias.
+
*Bag of support hours via email and/or teleconferences.
*Credenciales para ambiente de pruebas (DEMO) y productivo.  
+
*Credentials for test environment (DEMO) and production.  
*Templates configurables para representación gráfica.
+
*Configurable Templates for graphical representation.
 
{{clear}}
 
{{clear}}
===Funcionalidades===
+
===Functionalities===
La plataforma The Factory HKA-DFACTURE permite la emisión, recepción, consulta, visualización y descarga de los siguientes documentos en formato XML y/o su correspondiente representación gráfica en PDF:
+
The Factory HKA-DFACTURE platform allows the issuance, reception, consultation, viewing and downloading of the following documents in XML format and/or their corresponding graphic representation in PDF:
*Factura de Venta Nacional
+
*Invoice of National Sale
*Factura de Exportación
+
*Export invoice
*Factura por contingencia
+
*Contingency invoice
*Nota de Crédito
+
*Credit note
*Nota de Débito
+
*Debit note
Adicionalmente, la plataforma permite consultar el estatus del Acuse de Recibo por parte del adquirente, estatus del documento por parte de la DIAN, consultar la cantidad de timbres/folios disponibles y enviar comprobantes a través de correo electrónico.
+
Additionally, the platform allows you to check the status of the Acknowledgment of Receipt by the purchaser, the status of the document by the DIAN, check the number of available stamps/folios and send receipts via email.
  
'''@Importante:''' Solo es posible visualizar en nuestro portal web o descargar representaciones graficas (PDF de documentos electrónicos) generados por nuestra plataforma.
+
'''@Important:''' It is only possible to view or download graphic representations (PDF of electronic documents) generated by our platform on our web portal.
 
{{clear}}
 
{{clear}}
===La integración directa===
+
===The direct integration===
La integración es una actividad esencial para la puesta en marcha de la facturación electrónica en un Sistema de Facturación o Software Administrativo (ERP) y se realizará sólo una vez. Esta actividad consiste en enlazar dos plataformas con tecnologías distintas con el objetivo de transmitir los datos necesarios para la construcción de los documentos y el seguimiento exitoso del ciclo de vida.
+
Direct integration is a unique process between the embedded software and The Factory HKA-DFACTURE platform.Integration is an essential activity for the implementation of electronic invoicing in a Billing System or Administrative Software (ERP) and will be carried out only once. This activity consists of linking two platforms with different technologies in order to transmit the necessary data for the construction of the documents and the successful monitoring of the life cycle
  
En el caso de la integración directa, la comunicación se conecta directamente al Web Service, lo cual tiene como ventaja el control total del ciclo de vida del documento electrónico, desde el origen de los datos, pasando por el proceso de transmisión hasta su entrega, acuse de recibo y validación. Esta forma de integración permite reaccionar de un modo más rápido y eficiente ante errores o inconsistencias que se presenten en el proceso.
+
In the case of direct integration, the communication is connected directly to the Web Service, which has the advantage of total control of the life cycle of the electronic document, from the origin of the data, through the transmission process to its delivery, acknowledgment of receipt and validation. This form of integration allows a faster and more efficient reaction to errors or inconsistencies that arise in the process.
  
La integración directa es un proceso exclusivo entre el software integrado y la plataforma The Factory HKA-DFACTURE.
+
Direct integration is an exclusive process between the embedded software and The Factory HKA-DFACTURE platform.
  
'''@Importante:''' No es necesario implementar integración adicional ante la DIAN, ya que se cuenta con la funcionalidad completa de seguimiento del estatus del documento.  
+
'''@Important:''' It is not necessary to implement additional integration with the DIAN, since it has the complete document status tracking functionality.  
 
{{clear}}
 
{{clear}}
===Requerimientos técnicos para la integración directa===
+
===Technical requirements for direct integration===
The Factory HKA-DFACTURE es una plataforma tipo SaaS (Software as a Service): Los servicios, la información, el procesamiento, los insumos y resultados están alojados en nuestros servidores (como proveedor tecnológico), y nos ocupamos del mantenimiento, la operación, los cambios normativos y el soporte de la solución.
+
The Factory HKA-DFACTURE is a SaaS (Software as a Service) type platform: The services, information, processing, inputs and results are hosted on our servers (as technology provider), and we take care of the maintenance, operation, regulatory changes and solution support.
 +
 
 +
By DIAN regulations, the technology provider has the obligation to keep the documents and guarantee the integrity and security of the data under the ISO 27001 standard. Therefore, extensive planning of processing and storage infrastructure is not necessary to implement electronic billing.
  
Por normativa de la DIAN, el proveedor tecnológico tiene la obligación de conservar los documentos y garantizar la integridad y seguridad de los datos bajo el estándar ISO 27001. Por tanto, no es necesario una extensa planificación de infraestructura de procesamiento y almacenamiento para implementar la facturación electrónica.
+
The necessary parameters for the construction of each transaction are exposed independently at the time of consuming the services, and the result is fully delivered at the end of the operation. This means that The Factory HKA does not require managing customer or product/service databases.
 +
As a technological provider, The Factory HKA Colombia has human resources dedicated to monitoring and analyzing the regulatory changes that the DIAN progressively issues. If a significant change is generated that has an impact on the integration side, the necessary tools and instructions will be provided to apply the corrective measures in the simplest way possible.
  
Los parámetros necesarios para la construcción de cada transacción son expuestos independientemente al momento de consumir los servicios, y el resultado es entregado enteramente al final de la operación. Eso significa que The Factory HKA no requiere manejar bases de datos de clientes o productos/servicios.  
+
The Factory HKA-DFACTURE platform provides integration with a Web Service as a solution for interoperation with third parties. '''The Web Service is developed in SOAP (Simple Object Access Protocol)'''. Therefore, the only requirements for integration will be the following:
Como proveedor tecnológico, The Factory HKA Colombia cuenta con recurso humano dedicado a hacer seguimiento y analizar los cambios normativos que progresivamente emite la DIAN. De generarse un cambio significativo que impacte del lado de la integración como, se proveerá de las herramientas necesarias y de instrucciones para aplicar los correctivos de la forma más sencilla posible.
 
  
La plataforma The Factory HKA-DFACTURE pone a disposición de la integración un Web Service como solución para interoperación con terceros. '''El Web Service está desarrollado en SOAP (Simple Object Access Protocol)'''. Por tanto, como únicos requerimientos para la integración serán los siguientes:
+
*Capacity of WS SOAP consumption of the software (development environment) to use.
*Capacidad de consumo de WS SOAP del software (ambiente de desarrollo) a utilizar.
+
*Capability of capturing and validating input data.
*Capacidad de captación y validación de los datos de entrada.
+
*Optional: Ability to store a copy of the XML/PDF per transaction.
*Opcional: Capacidad para almacenar copia del XML/PDF por transacción.
+
*Ability to display the status of the electronic document life cycle.
*Capacidad para el despliegue del estado del ciclo de vida del documento electrónico.
 
 
{{clear}}
 
{{clear}}
<includeonly>=</includeonly>==Esquema de operación de la factura electrónica con validación previa==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>==Electronic invoice operation scheme with prior validation==<includeonly>=</includeonly>
===¿Qué es la Facturación Electrónica con Validación Previa?===
+
===¿What is la Facturación Electrónica con Validación Previa?===
La Facturación Electrónica (FEL) es un esquema de operación que permite emitir documentos de respaldo de las operaciones comerciales entre contribuyentes en formato digital en lugar de papel, permite la aplicación de control fiscal durante el proceso, y tiene validez legal para el ente tributario designado por el gobierno del país.
+
Electronic Invoicing (FEL) is an operation scheme that allows the issuance of supporting documents for commercial operations between taxpayers in digital format instead of paper, allows the application of fiscal control during the process, and has legal validity for the designated tax entity. by the government of the country.
  
A partir de septiembre de 2019, se tiene previsto que una factura electrónica solo será válida cuando se haya validado previamente su contenido a través de la DIAN o a través de un proveedor autorizado por la administración de impuestos.
+
As of September 2019, it is expected that an electronic invoice will only be valid when its content has been previously validated through the DIAN or through a provider authorized by the tax administration.
  
La validación previa se encuentra establecida en la ley 1943 de 2018, conocida como Ley de Financiamiento. El artículo 16 de esta Ley modifica el artículo 616-1 del Estatuto Tributario, en su parágrafo primero consagra que:
+
Prior validation is established in Law 1943 of 2018, known as the Financing Law. Article 16 of this Law modifies article 616-1 of the Tax Statute, in its first paragraph it establishes that:
  
“Todas las facturas electrónicas para su reconocimiento tributario deberán ser validadas previo a su expedición, por la DIAN o por un proveedor autorizado por esta. La factura electrónica solo se entenderá expedida cuando sea validad y entregada al adquiriente. (…)”
+
“All electronic invoices for tax recognition must be validated prior to their issuance, by the DIAN or by a provider authorized by it. The electronic invoice will only be understood as issued when it is valid and delivered to the purchaser. (…)”
  
En el modelo de facturación electrónica con validación previa se utilizarán 5 tipos de documentos:
+
In the electronic invoicing model with prior validation, 5 types of documents will be used:
*Invoice (Factura)
+
*Invoice  
*CreditNote (Nota Crédito)
+
*CreditNote
*DebitNote (Nota Débito)
+
*DebitNote  
*ApplicationResponse (Evento): Ocurrencia relacionada con un Documento Electrónico, generada por una persona o entidad relacionada con el documento (DIAN, Emisor, Adquiriente), este documento también contiene una firma electrónica.  
+
*ApplicationResponse (Event): Occurrence related to an Electronic Document, generated by a person or entity related to the document (DIAN, Issuer, Acquirer), this document also contains an electronic signature.  
*AttachedDocument (Contenedor de Documentos): La estructura de este documento tiene por objetivo contener en un único archivo XML un documento electrónico (Invoice, CreditNote ó DebitNote) y todos los eventos (ApplicationResponse) registrados hasta la fecha.
+
*AttachedDocument (Document container): The structure of this document is intended to contain in a single XML file an electronic document (Invoice, CreditNote or DebitNote) and all the events (ApplicationResponse) registered to date.
 
{{clear}}
 
{{clear}}
===¿Quiénes participan en este esquema?===
+
===¿Who participates in this scheme?===
'''El Ente Tributario (DIAN):''' Es una institución pública, nombrada por el gobierno para recaudar, controlar y regular todo lo relacionado con los tributos. Es el que tiene el derecho de aceptar y autorizar un documento electrónico. En Colombia, es la DIAN (Dirección de Impuestos y Aduanas Nacionales).
+
'''The Tax Entity (DIAN):''' It is a public institution appointed by the government to collect, control and regulate everything related to taxes. It is the one that has the right to accept and authorize an electronic document. In Colombia, it is the DIAN (Directorate of National Taxes and Customs).
  
'''El Emisor o Contribuyente:''' Es una persona natural o jurídica que posee un registro de información fiscal único y legal ante el ente tributario (NIT: Número de Identificación Tributario) y está bajo la obligación de emitir documentos para respaldar sus transacciones comerciales. El emisor adquiere el Sistema de Facturación o Software administrativo ERP para simplificar y potenciar sus labores y hace uso de él para interactuar con la plataforma de facturación electrónica.
+
'''The Issuer or Taxpayer:''' Is a natural or legal person who has a unique and legal tax information record before the tax entity (NIT: Tax Identification Number) and is under the obligation to issue documents to support their business transactions. The issuer acquires the Billing System or ERP administrative software to simplify and enhance its work and uses it to interact with the electronic billing platform.
  
'''El Proveedor Tecnológico:''' Es un ente privado autorizado por la DIAN para prestar servicios relacionados con el esquema de Facturación Electrónica: construcción del XML, control de secuenciales, firmado, control de cambio normativo, procesamiento, almacenamiento y consulta. The Factory HKA Colombia es su proveedor tecnológico.
+
'''The Technological Provider:''' It is a private entity authorized by the DIAN to provide services related to the Electronic Invoicing scheme: XML construction, sequential control, signing, regulatory change control, processing, storage and consultation. The Factory HKA Colombia is your technology provider.
  
'''El Adquiriente:''' Es la persona que da origen a una transacción comercial mediante la compra de un producto o servicio, y que finalmente, opta por recibir su documento electrónico vía email.
+
'''The Purchaser:''' Is the person who gives rise to a commercial transaction through the purchase of a product or service, and who finally chooses to receive his electronic document via email.
  
'''La Autoridad de Certificación:''' Es un ente público o privado habilitado por el Ente Tributario para expedir certificados electrónicos conforme a la ley y a las normas asociadas. En Colombia, hay varias autoridades acreditadas para expedir certificados electrónicos para facturación electrónica, entre ellas ANDES SCD.
+
'''The Certification Authority:''' It is a public or private entity authorized by the Tax Entity to issue electronic certificates in accordance with the law and associated regulations. In Colombia, there are several authorities accredited to issue electronic certificates for electronic invoicing, including ANDES SCD.
 
{{clear}}
 
{{clear}}
===Ventajas de la Facturación Electrónica===
+
===Advantages of Electronic Billing===
El esquema de Facturación Electrónica es ventajoso porque es:
+
The Electronic Billing scheme is advantageous because it is:
*Íntegro: Garantiza que la información contenida está protegida y no puede ser alterada.
+
*Full: Guarantees that the information contained is protected and cannot be altered.
*Auténtico: Permite verificar la identidad del emisor del documento.
+
*Authentic: Allows you to verify the identity of the issuer of the document.
*Legal: Este esquema está implementado y aceptado bajo el marco de la Ley.
+
*Legal: This scheme is implemented and accepted under the framework of the Law.
*Práctico: Elimina la infraestructura para el manejo, envío y almacenamiento de soportes físicos, y permite la impresión.
+
*Convenient: Eliminates infrastructure for physical media handling, shipping, and storage, and enables printing.
*Eficiente: Se basa 100% en plataforma electrónica, lo cual hace que el manejo, envío, búsqueda y almacenamiento sea más rápido y práctico.
+
*Eficiente: It is 100% based on an electronic platform, which makes handling, sending, searching and storing faster and more practical.
 
{{clear}}
 
{{clear}}
===Proceso de la Facturación Electrónica con Validación Previa===
+
===Electronic Billing Process with Prior Validation===
# El Adquiriente da origen a una transacción mediante la compra de un producto o servicio.
+
# El Emisor o Contribuyente carga los datos mediante la UI (User Interface) de su ERP.  
+
#The Acquirer originates a transaction through the purchase of a product or service.
# El Emisor o Contribuyente visualiza los timbres disponibles en la UI de su ERP.  
+
#The Issuer or Taxpayer loads the data through the UI (User Interface) of its ERP.
# El ERP construye el objeto y lo expone directamente a la plataforma DFACTURE mediante el método correspondiente del Web Service.
+
#The Issuer or Taxpayer displays the available stamps in the UI of their ERP.
# La plataforma The Factory HKA – DFACTURE:
+
#The ERP builds the object and exposes it directly to the DFACTURE platform through the corresponding method of the Web Service.
#* Valida las credenciales de acceso del Contribuyente.
+
#The Factory HKA platform – DFACTURE.
#* Valida la estructura del objeto que envía el ERP.
+
#*Validates the Taxpayer's access credentials.
#* Valida el contenido del objeto que envía el ERP.
+
#*It validates the structure of the object that the ERP sends.
#* Asigna el CUFE (Código único de Factura Electrónica) al documento.
+
#*Validates the content of the object sent by the ERP.
#* Construye el XML del documento según normativa DIAN.
+
#*Assigns the CUFE (Unique Code of Electronic Invoice) to the document.
#* Firma el documento con el Certificado Digital del Contribuyente.
+
#*It builds the XML of the document according to the DIAN regulations.
#* Opcional: Genera una representación impresa en PDF según normativa DIAN.
+
#*Sign the document with the Digital Certificate of the Taxpayer.
#* Almacena la información en Base de Datos (Conservación).
+
#*Optional: Generate a printed representation in PDF according to DIAN regulations.
#* Envía el XML a la DIAN para validación.
+
#*Stores information in Database (Conservation).
#* Espera respuesta de la DIAN con resultado de la validación.
+
#*It sends the XML to the DIAN for validation.
#* Envía el XML y PDF al email proporcionado por el Adquiriente.
+
#*Wait for response from DIAN with validation result.
#* Responde a la solicitud del ERP indicando que la operación fue satisfactoria.
+
#*Send the XML and PDF to the email provided by the Purchaser.
# Opcionalmente, el ERP puede enviar el XML y PDF al adquiriente.
+
#*It responds to the request from the ERP indicating that the operation was successful.
# Opcionalmente, el ERP puede descargar el XML y PDF para propósito interno.
+
#Optionally, the ERP can send the XML and PDF to the purchaser.
# El Adquiriente recibe el XML y el PDF (vía email).
+
#Optionally, the ERP can download the XML and PDF files for internal purposes.
# El Adquiriente tiene hasta 72 horas para dar Acuse de Recibo del documento, después de lo cual se considerará una aceptación tácita (este proceso aún no está definido totalmente por la DIAN).
+
#The Purchaser receives the XML and the PDF (via email).
# El Emisor o Contribuyente visualiza el estatus del acuse de recibo del Adquiriente en la UI de su ERP.
+
#The Acquirer has up to 72 hours to give Acknowledgment of Receipt of the document, after which it will be considered a tacit acceptance (this process has not yet been fully defined by the DIAN).
 +
#The Issuer or Taxpayer displays the status of the acknowledgment of receipt of the Acquirer in the UI of their ERP.
 +
 
  
; Proceso de Facturación Electrónica con Validación Previa
+
; Electronic Billing Process with Prior Validation
 
[[Archivo:Proceso de Facturación Electrónica con Validación PreviaDIAN.png|Proceso de Facturación Electrónica con Validación Previa (Fuente: DIAN)]]
 
[[Archivo:Proceso de Facturación Electrónica con Validación PreviaDIAN.png|Proceso de Facturación Electrónica con Validación Previa (Fuente: DIAN)]]
  
'''@Importante:''' Para ambientes de desarrollo con limitaciones para consumir Web Services SOAP de manera directa, The Factory HKA Colombia pone a disposición API’s simplificando al integrador éste proceso.
+
'''@Important:''' For development environments with limitations to consume SOAP Web Services directly, The Factory HKA Colombia makes APIs available, simplifying this process for the integrator.
 
{{clear}}
 
{{clear}}
  
<includeonly>=</includeonly>==Características del proceso con Validación Previa==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>==Process characteristics with Prior Validation==<includeonly>=</includeonly>
# En una etapa inicial, por única vez, el emisor debe registrarse y la plataforma debe ser configurada directamente desde el portal The Factory HKA-Dfactura.
+
#In an initial stage, for a single time, the issuer must register and the platform must be configured directly from The Factory HKA-Dinvoice portal.
# La plataforma opera bajo un modelo comercial de timbres o folios. Los timbres corresponden a un paquete de operaciones que el contribuyente contrata bajo un acuerdo comercial con The Factory HKA Colombia, y le da derecho a un determinado número de transacciones. El ERP puede consultar al Web Service de THE FACTORY HKA – DFACTURE los timbres disponibles.  
+
#The platform operates under a commercial model of stamps or folios. The stamps correspond to a package of operations that the taxpayer contracts under a commercial agreement with The Factory HKA Colombia, and entitles him to a certain number of transactions. The ERP can consult the Web Service of THE FACTORY HKA – DFACTURE for the available stamps.
# Para que el documento sea considerado factura electrónica, se requiere validación de la DIAN para su posterior envío al Adquiriente por parte de Dfactura.
+
#For the document to be considered an electronic invoice, DIAN validation is required for its subsequent sending to the Acquirer by Dfactura.
# En caso de que el documento no sea válido exitosamente ante la DIAN, éste deberá ser corregido y reexpedido.  
+
#In the event that the document is not successfully valid before the DIAN, it must be corrected and reissued.
# El ERP puede consumir el Web Service para descargar XML y PDF si desea un respaldo alterno u ofrecer funcionalidad de consulta offline.
+
#The ERP can consume the Web Service to download XML and PDF if you want an alternative backup or offer offline query functionality.
# El ERP opcionalmente puede decidir si enviar el XML y PDF al Adquiriente bajo su estructura.  
+
#The ERP can optionally decide whether to send the XML and PDF to the Acquirer under its structure.
# El Web Service de la plataforma ofrece la funcionalidad de consulta de estado del Acuse de Recibo por parte del Adquiriente. Éste se actualiza de forma asincrónica.
+
#The platform's Web Service offers the functionality of querying the Acknowledgment of Receipt status by the Acquirer. It is updated asynchronously.
# El Web Service de la plataforma ofrece la funcionalidad de consulta de estado del documento por parte de la DIAN. Éste se actualiza de forma asincrónica.
+
#The Web Service of the platform offers the function of querying the status of the document by the DIAN. It is updated asynchronously.
# El ERP refleja en su UI los resultados de sus consultas y operaciones con la plataforma. Sin embargo, el Emisor o Contribuyente puede hacer seguimiento o revisión a la vista de su ERP accediendo al portal The Factory HKA-Dfactura, ya que las operaciones realizadas en el Web Service se reflejan en el portal.
+
#The ERP reflects in its UI the results of your queries and operations with the platform. However, the Issuer or Taxpayer can monitor or review their ERP by accessing The Factory HKA-Dfactura portal, since the operations carried out in the Web Service are reflected in the portal.
  
; Diagrama de componentes y dependencias del sistema de facturación electrónica
+
; Diagram of components and dependencies of the electronic billing system
 
[[Archivo:DIAGRAMA COMPONENTES.png|centro|DIAGRAMA COMPONENTES]]
 
[[Archivo:DIAGRAMA COMPONENTES.png|centro|DIAGRAMA COMPONENTES]]
  
La Figura anterior muestra la forma en la que el Software de Facturación (ERP) se integra y hace uso de las funcionalidades de facturación electrónica de la plataforma The Factory HKA – DFACTURE, interactuando con los elementos externos (el emisor, el Adquiriente y la DIAN) mediante las dependencias disponibles, pueden verse las funciones que cada sistema debe realizar.
+
The figure above shows the way in which the Billing Software (ERP) integrates and makes use of the electronic billing functionalities of The Factory HKA – DFACTURE platform, interacting with external elements (the issuer, the Acquirer and the DIAN) through the available dependencies, you can see the functions that each system must perform.
 
{{clear}}
 
{{clear}}
  
<includeonly>=</includeonly>==Seguridad de la información: recomendaciones en la implementación de la factura electrónica dentro de la red y sistemas del emisor==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>==Information security: recommendations on the implementation of electronic invoicing within the issuer's network and systems==<includeonly>=</includeonly>
En este apartado se brindan recomendaciones en la implementación e integración de Factura electrónica en su organización y en la configuración de sus Sistemas y redes para mitigar riesgos de acceso indebido a datos por externos a su organización.  
+
This section provides recommendations on the implementation and integration of Electronic Invoicing in your organization and on the configuration of your Systems and networks to mitigate the risks of improper access to data by external parties to your organization.
===En General:===
+
===In General:===
# Contar con antivirus en su empresa.
+
# Have antivirus in your company.
# Tener políticas y procedimientos de backup frecuentes, realizados en un período de ejecución que sea acorde con la criticidad del negocio. Para ello tener en cuenta los siguientes aspectos:
+
# Have frequent backup policies and procedures, carried out in a period of execution that is consistent with the criticality of the business. To do this, take the following aspects into account:
#* Deben realizarse pruebas de restauración.
+
#* Restoration tests should be performed..
#* Deben estar en una infraestructura distinta a la operativa (ante un ransomware toda la infraestructura accedida estará comprometida)
+
#* They must be in an infrastructure other than the operating one (in the event of ransomware, all the accessed infrastructure will be compromised)
# De ser posible, buscar asesores y especialistas en seguridad y hacer auditorias ISO 27001:2013 que evalúen la calidad de las decisiones tomadas en la implantación de factura electrónica en su empresa.
+
# If possible, look for security consultants and specialists and carry out ISO 27001:2013 audits to assess the quality of the decisions made in the implementation of electronic invoicing in your company.
# Evitar uso de usuarios genéricos y/o Administradores en la organización y aplicar a cada usuario el control de acceso, permisología y roles que le corresponde según su función.  
+
# Avoid the use of generic users and/or Administrators in the organization and apply to each user the access control, permissions and roles that correspond to them according to their function.  
===Particulares con The Factory HKA Colombia SAS:===
+
===Individuals with The Factory HKA Colombia SAS:===
# Sólo permitir acceso a los puertos TCP/UDP 80 y 443 a los dominios indicados a continuación :
+
#Only allow access to TCP/UDP ports 80 and 443 to the domains indicated below:
#* *.thefactoryhka.com.co
+
#**.thefactoryhka.com.co
#* emisionrest21.thefactoryhka.com.co (Integración Producción)
+
#*emisionrest21.thefactoryhka.com.co (Integration Production)
#* factura21.thefactoryhka.com.co (Portal – Producción)
+
#*invoice21.thefactoryhka.com.co (Portal – Production)
#* demoemisionrest21.thefactoryhka.com.co (Integración –Demo)
+
#*demoemisionrest21.thefactoryhka.com.co (Integration –Demo)
#* demofactura.thefactoryhka.com.co (Portal – Demo)
+
#*demofactura.thefactoryhka.com.co (Portal – Demo)
# No se recomienda acceso abierto a estos puertos TCP/UDP a toda la internet.
+
#Open access to these TCP/UDP ports to the entire internet is not recommended.
# En el modelo de factura electrónica con The Factory HKA Colombia SAS las peticiones surgen del cliente solamente por lo que pueden establecer reglas desde intentos de conexión externos. (La comunicación siempre será iniciada por el software cliente).
+
#In the electronic invoice model with The Factory HKA Colombia SAS, the requests arise from the client only, so they can establish rules from external connection attempts. (The communication will always be initiated by the client software.)
# Si se hace uso de herramientas de software clientes de The Factory HKA Colombia SAS como lo son:
+
#If The Factory HKA Colombia SAS client software tools are used, such as:
#* IntTFHKAFEL21.exe
+
#*intTFHKAFEL21.exe
#* AutoFact.exe
+
#*AutoFact.exe
#: Y los mismos se visualizan como un riesgo por el sistema de antivirus o protección del cliente, debe generarse una excepción en firewall, antivirus, y cualquier otro sistema de protección única y exclusivamente para ellos.  
+
#:And they are seen as a risk by the antivirus system or client protection, an exception must be generated in the firewall, antivirus, and any other protection system solely and exclusively for them.
# Los TOKEN Empresa y TOKEN Password de producción para la Plataforma de Facturación Electrónica de The Factory HKA Colombia SAS deben ser guardados de forma confidencial y únicamente ser accesibles por personal de confianza.
+
#The Company TOKEN and production TOKEN Password for the Electronic Invoicing Platform of The Factory HKA Colombia SAS must be kept confidential and only be accessible by trusted personnel.
# Para el caso en que el emisor contrate un servicio de representación gráfica con la casa de software, o desarrollador, encargado de realizar los ajustes correspondientes en el software contable o ERP para la emisión de documentos electrónicos, se deben tener en cuenta los siguientes aspectos:
+
#In the event that the issuer contracts a graphic representation service with the software house, or developer, in charge of making the corresponding adjustments in the accounting software or ERP for the issuance of electronic documents, the following aspects must be taken into account:
#* The Factory HKA es responsable de la generación del UBL y su transmisión a la DIAN.
+
#*The Factory HKA is responsible for the generation of the UBL and its transmission to the DIAN.
#* Una vez se compruebe la correcta validación y generación del UBL la casa de software puede proceder a generar una representación gráfica que debe cumplir con:
+
#*Once the correct validation and generation of the UBL is verified, the software house can proceed to generate a graphic representation that must comply with:
#:: Los elementos de ley exigidos por la DIAN: inclusión del código QR y de la cadena del CUFE ó CUDE en los documentos, según corresponda.
+
#::The elements of law required by the DIAN: inclusion of the QR code and the CUFE or CUDE chain in the documents, as appropriate.
#:: Los elementos de ley exigidos por cualquier entidad supervisora al emisor de los documentos.
+
#::The elements of law required by any supervisory entity from the issuer of the documents.
#:: Los elementos visuales y de representación de marca exigidos por el propio cliente: logos, información bancaria, leyendas referentes a las responsabilidades tributarias del emisor, etc.
+
#::The visual and brand representation elements required by the client: logos, banking information, legends referring to the tax responsibilities of the issuer, etc.
#* La Casa de Software, en este escenario, asume la responsabilidad junto con el propio contribuyente de cualquier incidente de fraude por evasión, malinterpretación, error u omisión de información relevante y obligatoria por parte de la normativa.
+
#*The Software House, in this scenario, assumes responsibility together with the taxpayer for any incident of fraud due to evasion, misinterpretation, error or omission of relevant and mandatory information by the regulations.
#:TFHKA no resguarda esta representación en sus sistemas y deja claro que su participación como proveedor tecnológico se limita a la generación del UBL y su validación ante la DIAN.
+
#:TFHKA does not protect this representation in its systems and makes it clear that its participation as a technology provider is limited to the generation of the UBL and its validation to the DIAN.
 
{{clear}}
 
{{clear}}
  
<includeonly>=</includeonly>==Web services soap con validación previa==<includeonly>=</includeonly>
+
<includeonly>=</includeonly>==Web services soap with prior validation==<includeonly>=</includeonly>
Para el consumo de los métodos del Web Service es imprescindible el uso de las credenciales de acceso, conformadas por un '''Token Empresa''' y un '''Token Password'''. También será necesario conocer los '''URL’s de los Web Services''' del ambiente de integración con validación previa. Estos elementos serán proporcionados por el equipo de Integración de The Factory HKA Colombia.
+
To consume the methods of the Web Service, it is essential to use the access credentials, made up of a Company Token and a Password Token., To consume the methods of the Web Service, the use of access credentials, made up of a Company Token and a Password Token, is essential. It will also be necessary to know the URL's of the Web Services of the integration environment with prior validation., It will also be necessary to know the URLs of the Web Services of the integration environment with previous validation. These elements will be provided by The Factory HKA Colombia Integration team.
 
+
'''@Important:''' This document refers to the integration process with prior validation, its technical and regulatory change controls and its differences with the web service with subsequent validation.
'''@Importante:''' En éste documento se hace referencia al proceso de integración con validación previa, sus controles de cambios técnicos y normativos y sus diferencias con el servicio web con validación posterior.
 
  
A continuación, se muestran los métodos que estarán disponibles en los '''Web Services de THE FACTORY HKA-DFACTURE''' para la facturación electrónica con validación previa:
+
Below are the methods that will be available in THE FACTORY HKA-DFACTURE Web Services for electronic invoicing with prior validation:
  
 
{| class="wikitable" style="margin: auto;"
 
{| class="wikitable" style="margin: auto;"
 
|-
 
|-
! style="background:#e9e9e9; text-align:center;"|Servicio
+
! style="background:#e9e9e9; text-align:center;"|Service
! style="background:#e9e9e9; text-align:center;"|Método
+
! style="background:#e9e9e9; text-align:center;"|Method
 
|- valign="center"
 
|- valign="center"
| Emisión Web SOAP
+
| Issue Web SOAP
 
|
 
|
 
* Enviar
 
* Enviar
Línea 310: Línea 313:
 
* GenerarEvento (Nuevo)
 
* GenerarEvento (Nuevo)
 
|-
 
|-
| Adjuntos Web SOAP
+
| Attached Web SOAP
 
|  
 
|  
 
*CargarAdjuntos  
 
*CargarAdjuntos  
 
|-
 
|-
|Reportes Web SOAP (Nuevo)
+
|Reports Web SOAP (New)
 
|
 
|
 
* DescargarReporte
 
* DescargarReporte

Revisión del 08:11 28 feb 2022

Version record

Version Launch date Description
0 07/05/2019
  • Preview version.
1.0 14/06/2019
  • Initial version.
  • "Technical annex V1.4 (19-04-19)" DIAN reference.
1.1 04/07/2019
  • "Sale electronic bill Technical annex – final" DIAN Reference update.
1.2 04/07/2019
  • Minor updates
1.3 19/08/19
  • Minor updates
1.4 23/08/19
  • Answer update in view of the send method.
  • List of extensible fields and bug catalog.
1.5 09/2019
  • Wildcards updates based on the September 6th- technical annex.
1.6 04/2020
  • Updates based on the technical annex 1.8.
  • Acknowledgment of the purchaser.
  • Mail personalization.
  • Additional features.
  • Settle documents at reception.
  • Code tables.
  • Change of the document's name.
  • Among other minor changes.
1.7 06/2020
  • Updates based on the technical annex V1.7-2020.
  • Ajustes de funcionalidades de la plataforma en el mes de mayo.
2.0 06/2021
  • Updates based on the technical annex V1.8 of the 000012 Resolution. Health sector fields. Code tables.
2.1 10/2021
  • Updates based on the technical annex V1.8 of the 000012 Resolution. Health sector fields. Code tables.

How to get support

  • First level support:
Phone support / e-mail / chat or teleconference in 5x8 schedule for consultation service and user failures.
  • Second level support:
Support remote resolution of incidents in the system in schedule 5X8
Write to soporte@thefactoryhka.com.co

Consultations relating to configurations and errors in the portal:

  • soporte_fel_co@thefactoryhka.com

Consultations relating to configurations of ERP, software house and integration:

  • integracion_fel_co@thefactoryhka.com


Telephone service lines:

  • MASTER +57 (1) 746.08.12
  • +57 (1) 508.8990
  • +57 (1) 517.6795
  • +57 (1) 517.6796
  • +57 (1) 311.3063
    • Technical support → Option 2
    • Integration → Option 5 Then Option 1

Synchronous sessions:

technical support session

Registration as an electronic biller, configuration of numbering ranges, fiscal data configuration, Enabling Tests, Production environment configuration, managment and use of the TFHKA electronic billing portal.

Addressed to: Comercial agencies – Ally software factories - Final clients

Schedule: Tuesday and thursday from 8:30 AM to 10:00 AM

Enlace Sesiones de Soporte


Integration area sessions

Solución integration cases

Addressed to: Clients that realice Software development to do integration with TFHKA, Ally software factories

Schedule: Tuesday and thursday from 8:30 AM to 10:00 AM

Enlace Sesiones Integración

General description

This document describes the integration process between the electronic invoicing model with prior validation according to regulatory and technical updates from the DIAN and/or own controls in our integration model.

For the development of this document, was taken as reference the Technical annexes V1.7-2020 (current) and V1.8 (this last released in October 2019 by the DIAN).

Note: Not all functionalities, catalogs and billing scenarios referring to the Technical Annex V1.8 are enabled by the DIAN.

¿What is The Factory HKA-DFACTURE?

It is an electronic billing platform, designed to comply with current legislation in Colombia and offer added values through complementary services.

¿What is The Factory HKA-Dfactura?

It is a portal with the capacity to issue documents under the electronic invoicing scheme, managed from the web portal and Addressed to taxpayers who have the obligation to issue electronic invoices by resolution of the DIAN.

¿What is Dintegración?

It is a product aimed at the integrator and is made up of the following components:

  • Integration manuals.
  • Bag of support hours via email and/or teleconferences.
  • Credentials for test environment (DEMO) and production.
  • Configurable Templates for graphical representation.

Functionalities

The Factory HKA-DFACTURE platform allows the issuance, reception, consultation, viewing and downloading of the following documents in XML format and/or their corresponding graphic representation in PDF:

  • Invoice of National Sale
  • Export invoice
  • Contingency invoice
  • Credit note
  • Debit note

Additionally, the platform allows you to check the status of the Acknowledgment of Receipt by the purchaser, the status of the document by the DIAN, check the number of available stamps/folios and send receipts via email.

@Important: It is only possible to view or download graphic representations (PDF of electronic documents) generated by our platform on our web portal.

The direct integration

Direct integration is a unique process between the embedded software and The Factory HKA-DFACTURE platform.Integration is an essential activity for the implementation of electronic invoicing in a Billing System or Administrative Software (ERP) and will be carried out only once. This activity consists of linking two platforms with different technologies in order to transmit the necessary data for the construction of the documents and the successful monitoring of the life cycle

In the case of direct integration, the communication is connected directly to the Web Service, which has the advantage of total control of the life cycle of the electronic document, from the origin of the data, through the transmission process to its delivery, acknowledgment of receipt and validation. This form of integration allows a faster and more efficient reaction to errors or inconsistencies that arise in the process.

Direct integration is an exclusive process between the embedded software and The Factory HKA-DFACTURE platform.

@Important: It is not necessary to implement additional integration with the DIAN, since it has the complete document status tracking functionality.

Technical requirements for direct integration

The Factory HKA-DFACTURE is a SaaS (Software as a Service) type platform: The services, information, processing, inputs and results are hosted on our servers (as technology provider), and we take care of the maintenance, operation, regulatory changes and solution support.

By DIAN regulations, the technology provider has the obligation to keep the documents and guarantee the integrity and security of the data under the ISO 27001 standard. Therefore, extensive planning of processing and storage infrastructure is not necessary to implement electronic billing.

The necessary parameters for the construction of each transaction are exposed independently at the time of consuming the services, and the result is fully delivered at the end of the operation. This means that The Factory HKA does not require managing customer or product/service databases. As a technological provider, The Factory HKA Colombia has human resources dedicated to monitoring and analyzing the regulatory changes that the DIAN progressively issues. If a significant change is generated that has an impact on the integration side, the necessary tools and instructions will be provided to apply the corrective measures in the simplest way possible.

The Factory HKA-DFACTURE platform provides integration with a Web Service as a solution for interoperation with third parties. The Web Service is developed in SOAP (Simple Object Access Protocol). Therefore, the only requirements for integration will be the following:

  • Capacity of WS SOAP consumption of the software (development environment) to use.
  • Capability of capturing and validating input data.
  • Optional: Ability to store a copy of the XML/PDF per transaction.
  • Ability to display the status of the electronic document life cycle.

Electronic invoice operation scheme with prior validation

¿What is la Facturación Electrónica con Validación Previa?

Electronic Invoicing (FEL) is an operation scheme that allows the issuance of supporting documents for commercial operations between taxpayers in digital format instead of paper, allows the application of fiscal control during the process, and has legal validity for the designated tax entity. by the government of the country.

As of September 2019, it is expected that an electronic invoice will only be valid when its content has been previously validated through the DIAN or through a provider authorized by the tax administration.

Prior validation is established in Law 1943 of 2018, known as the Financing Law. Article 16 of this Law modifies article 616-1 of the Tax Statute, in its first paragraph it establishes that:

“All electronic invoices for tax recognition must be validated prior to their issuance, by the DIAN or by a provider authorized by it. The electronic invoice will only be understood as issued when it is valid and delivered to the purchaser. (…)”

In the electronic invoicing model with prior validation, 5 types of documents will be used:

  • Invoice
  • CreditNote
  • DebitNote
  • ApplicationResponse (Event): Occurrence related to an Electronic Document, generated by a person or entity related to the document (DIAN, Issuer, Acquirer), this document also contains an electronic signature.
  • AttachedDocument (Document container): The structure of this document is intended to contain in a single XML file an electronic document (Invoice, CreditNote or DebitNote) and all the events (ApplicationResponse) registered to date.

¿Who participates in this scheme?

The Tax Entity (DIAN): It is a public institution appointed by the government to collect, control and regulate everything related to taxes. It is the one that has the right to accept and authorize an electronic document. In Colombia, it is the DIAN (Directorate of National Taxes and Customs).

The Issuer or Taxpayer: Is a natural or legal person who has a unique and legal tax information record before the tax entity (NIT: Tax Identification Number) and is under the obligation to issue documents to support their business transactions. The issuer acquires the Billing System or ERP administrative software to simplify and enhance its work and uses it to interact with the electronic billing platform.

The Technological Provider: It is a private entity authorized by the DIAN to provide services related to the Electronic Invoicing scheme: XML construction, sequential control, signing, regulatory change control, processing, storage and consultation. The Factory HKA Colombia is your technology provider.

The Purchaser: Is the person who gives rise to a commercial transaction through the purchase of a product or service, and who finally chooses to receive his electronic document via email.

The Certification Authority: It is a public or private entity authorized by the Tax Entity to issue electronic certificates in accordance with the law and associated regulations. In Colombia, there are several authorities accredited to issue electronic certificates for electronic invoicing, including ANDES SCD.

Advantages of Electronic Billing

The Electronic Billing scheme is advantageous because it is:

  • Full: Guarantees that the information contained is protected and cannot be altered.
  • Authentic: Allows you to verify the identity of the issuer of the document.
  • Legal: This scheme is implemented and accepted under the framework of the Law.
  • Convenient: Eliminates infrastructure for physical media handling, shipping, and storage, and enables printing.
  • Eficiente: It is 100% based on an electronic platform, which makes handling, sending, searching and storing faster and more practical.

Electronic Billing Process with Prior Validation

  1. The Acquirer originates a transaction through the purchase of a product or service.
  2. The Issuer or Taxpayer loads the data through the UI (User Interface) of its ERP.
  3. The Issuer or Taxpayer displays the available stamps in the UI of their ERP.
  4. The ERP builds the object and exposes it directly to the DFACTURE platform through the corresponding method of the Web Service.
  5. The Factory HKA platform – DFACTURE.
    • Validates the Taxpayer's access credentials.
    • It validates the structure of the object that the ERP sends.
    • Validates the content of the object sent by the ERP.
    • Assigns the CUFE (Unique Code of Electronic Invoice) to the document.
    • It builds the XML of the document according to the DIAN regulations.
    • Sign the document with the Digital Certificate of the Taxpayer.
    • Optional: Generate a printed representation in PDF according to DIAN regulations.
    • Stores information in Database (Conservation).
    • It sends the XML to the DIAN for validation.
    • Wait for response from DIAN with validation result.
    • Send the XML and PDF to the email provided by the Purchaser.
    • It responds to the request from the ERP indicating that the operation was successful.
  6. Optionally, the ERP can send the XML and PDF to the purchaser.
  7. Optionally, the ERP can download the XML and PDF files for internal purposes.
  8. The Purchaser receives the XML and the PDF (via email).
  9. The Acquirer has up to 72 hours to give Acknowledgment of Receipt of the document, after which it will be considered a tacit acceptance (this process has not yet been fully defined by the DIAN).
  10. The Issuer or Taxpayer displays the status of the acknowledgment of receipt of the Acquirer in the UI of their ERP.


Electronic Billing Process with Prior Validation

Proceso de Facturación Electrónica con Validación Previa (Fuente: DIAN)

@Important: For development environments with limitations to consume SOAP Web Services directly, The Factory HKA Colombia makes APIs available, simplifying this process for the integrator.

Process characteristics with Prior Validation

  1. In an initial stage, for a single time, the issuer must register and the platform must be configured directly from The Factory HKA-Dinvoice portal.
  2. The platform operates under a commercial model of stamps or folios. The stamps correspond to a package of operations that the taxpayer contracts under a commercial agreement with The Factory HKA Colombia, and entitles him to a certain number of transactions. The ERP can consult the Web Service of THE FACTORY HKA – DFACTURE for the available stamps.
  3. For the document to be considered an electronic invoice, DIAN validation is required for its subsequent sending to the Acquirer by Dfactura.
  4. In the event that the document is not successfully valid before the DIAN, it must be corrected and reissued.
  5. The ERP can consume the Web Service to download XML and PDF if you want an alternative backup or offer offline query functionality.
  6. The ERP can optionally decide whether to send the XML and PDF to the Acquirer under its structure.
  7. The platform's Web Service offers the functionality of querying the Acknowledgment of Receipt status by the Acquirer. It is updated asynchronously.
  8. The Web Service of the platform offers the function of querying the status of the document by the DIAN. It is updated asynchronously.
  9. The ERP reflects in its UI the results of your queries and operations with the platform. However, the Issuer or Taxpayer can monitor or review their ERP by accessing The Factory HKA-Dfactura portal, since the operations carried out in the Web Service are reflected in the portal.
Diagram of components and dependencies of the electronic billing system
DIAGRAMA COMPONENTES

The figure above shows the way in which the Billing Software (ERP) integrates and makes use of the electronic billing functionalities of The Factory HKA – DFACTURE platform, interacting with external elements (the issuer, the Acquirer and the DIAN) through the available dependencies, you can see the functions that each system must perform.

Information security: recommendations on the implementation of electronic invoicing within the issuer's network and systems

This section provides recommendations on the implementation and integration of Electronic Invoicing in your organization and on the configuration of your Systems and networks to mitigate the risks of improper access to data by external parties to your organization.

In General:

  1. Have antivirus in your company.
  2. Have frequent backup policies and procedures, carried out in a period of execution that is consistent with the criticality of the business. To do this, take the following aspects into account:
    • Restoration tests should be performed..
    • They must be in an infrastructure other than the operating one (in the event of ransomware, all the accessed infrastructure will be compromised)
  3. If possible, look for security consultants and specialists and carry out ISO 27001:2013 audits to assess the quality of the decisions made in the implementation of electronic invoicing in your company.
  4. Avoid the use of generic users and/or Administrators in the organization and apply to each user the access control, permissions and roles that correspond to them according to their function.

Individuals with The Factory HKA Colombia SAS:

  1. Only allow access to TCP/UDP ports 80 and 443 to the domains indicated below:
      • .thefactoryhka.com.co
    • emisionrest21.thefactoryhka.com.co (Integration – Production)
    • invoice21.thefactoryhka.com.co (Portal – Production)
    • demoemisionrest21.thefactoryhka.com.co (Integration –Demo)
    • demofactura.thefactoryhka.com.co (Portal – Demo)
  2. Open access to these TCP/UDP ports to the entire internet is not recommended.
  3. In the electronic invoice model with The Factory HKA Colombia SAS, the requests arise from the client only, so they can establish rules from external connection attempts. (The communication will always be initiated by the client software.)
  4. If The Factory HKA Colombia SAS client software tools are used, such as:
    • intTFHKAFEL21.exe
    • AutoFact.exe
    And they are seen as a risk by the antivirus system or client protection, an exception must be generated in the firewall, antivirus, and any other protection system solely and exclusively for them.
  5. The Company TOKEN and production TOKEN Password for the Electronic Invoicing Platform of The Factory HKA Colombia SAS must be kept confidential and only be accessible by trusted personnel.
  6. In the event that the issuer contracts a graphic representation service with the software house, or developer, in charge of making the corresponding adjustments in the accounting software or ERP for the issuance of electronic documents, the following aspects must be taken into account:
    • The Factory HKA is responsible for the generation of the UBL and its transmission to the DIAN.
    • Once the correct validation and generation of the UBL is verified, the software house can proceed to generate a graphic representation that must comply with:
    The elements of law required by the DIAN: inclusion of the QR code and the CUFE or CUDE chain in the documents, as appropriate.
    The elements of law required by any supervisory entity from the issuer of the documents.
    The visual and brand representation elements required by the client: logos, banking information, legends referring to the tax responsibilities of the issuer, etc.
    • The Software House, in this scenario, assumes responsibility together with the taxpayer for any incident of fraud due to evasion, misinterpretation, error or omission of relevant and mandatory information by the regulations.
    TFHKA does not protect this representation in its systems and makes it clear that its participation as a technology provider is limited to the generation of the UBL and its validation to the DIAN.

Web services soap with prior validation

To consume the methods of the Web Service, it is essential to use the access credentials, made up of a Company Token and a Password Token., To consume the methods of the Web Service, the use of access credentials, made up of a Company Token and a Password Token, is essential. It will also be necessary to know the URL's of the Web Services of the integration environment with prior validation., It will also be necessary to know the URLs of the Web Services of the integration environment with previous validation. These elements will be provided by The Factory HKA Colombia Integration team. @Important: This document refers to the integration process with prior validation, its technical and regulatory change controls and its differences with the web service with subsequent validation.

Below are the methods that will be available in THE FACTORY HKA-DFACTURE Web Services for electronic invoicing with prior validation:

Service Method
Issue Web SOAP
  • Enviar
  • EstadoDocumento
  • EnvioCorreo
  • DescargaPDF
  • DescargaXML
  • FoliosRestantes
  • CargarCertificado (Uso interno)
  • DescargarEventoXML (Nuevo)
  • GenerarContenedor (Nuevo)
  • GenerarEvento (Nuevo)
Attached Web SOAP
  • CargarAdjuntos
Reports Web SOAP (New)
  • DescargarReporte
  • ProgramarReporte
  • SolicitudReporteSincrono