GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. Our API is developed in GRAPHQL, for more information please visit the GraphQL website.

Use YABI•CO officially supported libraries to make API queries.
- Curl: to make API queries from the command line.
- Insomnia: API client, you can quickly and easily send REST, SOAP, GraphQL, and GRPC requests directly within Insomnia.
The examples we deliver with our plan are with this tool.

The token is created through the YABI•CO API manager.

It is the reception of electronic documents (electronic sales invoices, credit notes, debit notes and electronic invoice events) that your suppliers make to you.
Because the DIAN does not have in its web service the consultation of the list of sales invoices made by your suppliers, and you can only search the invoice by CUFE or CUDE, our API has two alternatives for the reception of the documents, the first is to automatically forward emails with electronic invoices from your suppliers to a yabi.co email or from your ERP you can send the CUFE or CUDE that you want to receive.
In the case of the credit sales invoices events that your customers generate to these, these are received by mail, but to provide security to these events yabi.co through our robot YABI-Bot periodically reviews in the DIAN through the CUFE the events sent to the credit sales invoices made.

• Acknowledgment of mail reading of Electronic Sales Invoice: It is an event that is not requested by DIAN and that we created for you to perform a tracking task of when the sales invoice has been viewed by your customers. It is executed automatically when the customer (a person) checks or reads the mail if the mail client has the remote content upload active. This event does not involve legal or contractual issues with the electronic sales invoice and as mentioned is informational only. It is not dependent on another event or a prerequisite for another event.
• Acknowledgment delivery of goods and services of the electronic sales invoice by the electronic biller: This is an event that is not requested by the DIAN and that we have created for you to follow up and inform your customer via e-mail that you have already delivered the goods or provided the service so that your customer has a starting point to continue or perform the events of the credit sales invoice that are pending. Your customer is only notified via mail if he/she has not made the event "Receipt of the goods or rendering of the service". This event does not imply legal or contractual issues with the electronic sales invoice and as indicated is only informative. It does not depend on another event or is a prerequisite for another event.
• Electronic Sales Invoice Acknowledgement of Receipt: This event only applies to the electronic invoices to credit that your suppliers make to you and can only be made by you, who is the acquirer (debtor) of the invoice. The acknowledgment indicates to your supplier that you received the invoice, this event does not imply the acceptance of the invoice or the products (goods or services). This event has no prior event.
• Receipt of the good or service rendered: This event only applies to electronic credit invoices issued by your suppliers and can only be performed by you who is the acquirer (debtor) of the invoice. The receipt of the goods only indicates that you received the products (goods or services). This event does not imply tacit acceptance of the invoice or acceptance (that the good or service was delivered in full and without any claim), only the receipt of the goods or service. As a prerequisite of this event, it is necessary to have made the event of “Electronic Invoice of Sale Acknowledgement of Receipt”.
• Express acceptance of the electronic sales invoice: This event only applies to electronic credit invoices made to you by your suppliers and can only be made by you who are the acquirer(debtor) of the invoice. The express acceptance of the invoice indicates that you accept the content of the invoice (that you have no claims), that the products (goods or services) comply with what is indicated in the invoice, and that they were delivered without any claim. Once this event has taken place, you will NOT be able to generate credit notes or debit notes due to this invoice. You have a term of three working days to make this event when you have made the event Receipt of the goods or rendering of the service, in case of not making this event in this period of time your supplier (electronic biller) can make the event of Tacit Acceptance of Electronic Invoice of Sale. As a prerequisite of this event, it is necessary to have made the event of receipt of the goods or rendering of the service.
• Tacit Acceptance of the electronic sales invoice: This event only applies to electronic credit invoices that you generate for your customers and can only be made by you as the electronic biller (who issues the invoice). The tacit acceptance of the invoice is made under oath, indicating that after three days the acquirer (debtor customer) did not expressly state the acceptance or rejection of the invoice, or claim against its content. Once this event is done, it will NOT be able to create notes, credit, or debit notes due to this invoice. This can only be done on the fourth business day and if your customer has not made the event of express acceptance of the Electronic Sale Invoice or the event of Claim of the Electronic Bill of Sale. As a prerequisite for this event, it is necessary that your customer has made the event of receipt of the goods or provision of the service.
• Rejection of the electronic sales invoice: This event only applies to electronic invoices to credit that your suppliers make to you and can only be made by you who are the acquirer (debtor) of the invoice. The claim implies that you reject or have a claim on the invoice or on the products (goods or services) received. Once this event has taken place, it will not be possible to carry out the events of express or tacit acceptance of the invoice, and it is recommended that your supplier generates a cancellation credit note. You have a period of three working days after the event of receipt of products to perform this event, if not performed in this period of time your supplier can perform the event of tacit acceptance. For this event is necessary to have made the event of receipt of the good or service rendered.

Notes: If you want to use as support the credit sales invoices that your suppliers generate as expenses, costs, and deductible taxes, it is mandatory to make these events from July 13, 2022. If you do not make these events, you will NOT be able to use the invoices as support for expenses, costs, and deductible taxes, in case you do it for example in the VAT tax the DIAN will not know these expenses, costs, and deductible taxes, and you will have to assume the VAT of these purchases.
In other electronic invoicing platforms there is an acceptance or rejection button for electronic invoices that are made in the seller´s platform, but this is not what is requested by resolution 000085 of April 8, 2022, of the DIAN (this type of button YABI-co has not implemented them because they lack technical and legal validity), because these events should not be made by the seller (the electronic biller who generated the electronic sales invoice) and are not digitally signed, nor sent as electronic invoicing events to the DIAN. What the DIAN technically requests in this resolution, as explained above in the events, is that the acquirer (debtor customer) must perform the events as a buyer and this cannot and should not be done by the seller with this type of button, since the acquirer must digitally sign these events through its digital certificates of the files (XML) and file them digitally with the DIAN.

Sales invoice status

A sales invoice is an accounting document that records a business transaction.
Sales invoice provide the business with a record of the services they have provided to a client.
This invoice can be paid on credit or in cash, it is on credit when the payment for the products or services purchased is made after a certain period of time, and it is in cash when the payment for the products or services that have been purchased is made at the time of delivery.
This is the electronic invoice status, this field "documentStatus" can be found when querying an invoice.

Status Indicator	Description	Credit	Cash
YABICO_ CREATED	E-invoice filed with YABI•CO.	X	X
DIAN_ VALIDATING	The DIAN is currently validating the electronic invoice.	X	X
DIAN_ REJECTED	DIAN has rejected the invoice due to the following errors: - reason 1 ... - reason n	X	X
DIAN_ VALIDATED	Electronic invoice validated by DIAN.	X	X
SEND_ EMAIL	Mail sent to the customer and to the electronic biller.	X	X
PRODUCTS_ DELIVERY	The customer abc has acknowledged receipt of the sales invoice.	X	N/A
MAIL_ RECEPTION_ ACK	Your customer has opened or viewed the email, not necessarily read or reviewed it in detail.	X	X
RECEIPT_ ACK	The customer abc has acknowledged receipt of the sales invoice.	X	N/A
PRODUCTS_ RECEPTION	Your customer abc has made the receipt of the good or service provision of the electronic sales invoice.	X	N/A
EXPRESS_ ACCEPTANCE	Your customer abc has expressly accepted the electronic sales invoice from your supplier.	X	N/A
REJECTION	Your customer abc has made the claim for the electronic sales invoice, it is recommended that the cancellation credit note be generated.	X	N/A
REJECTION_ ISSUED_ CREDIT_ NOTE	Your customer abc has made the claim for the electronic sales invoice and has already made the cancellation credit note.	X	N/A
TACIT_ ACCEPTANCE	User abc has made a tacit acceptance of the electronic sales invoice, since his customer did not make the express acceptance or claim within three business days after receipt of the good or service.	X	N/A

Purchase invoice status

A purchase invoice is an invoice that is used in conjunction with a purchase order. It is used to indicate how much money the buyer owes to the seller. Purchase invoices are the invoices that companies generate for you as a buyer. This invoice can be paid on credit or in cash, it is on credit when the payment for the products or services purchased is made after a certain period of time, and it is in cash when the payment for the products or services that have been purchased is made at the time of delivery.

This is the electronic invoice status, this field "documentStatus" can be found when querying an invoice.

Status Indicator	Description	Credit	Cash
DIAN_ VALIDATED	The electronic sales invoice from your supplier has been added to YABI-CO via mail/API.	X	X
RECEIPT_ ACK	User abc has acknowledged receipt of the sales invoice from his supplier.	X	N/A
PRODUCTS_ RECEPTION	The user abc has received the receipt of the good or service from the electronic sales invoice from his supplier.	X	N/A
EXPRESS_ ACCEPTANCE	User abc has expressly accepted the electronic sales invoice from his supplier.	X	N/A
REJECTION	User abc has claimed the electronic sales invoice from his supplier and his supplier is pending to generate the credit note to cancel the invoice.	X	N/A
REJECTION_ ISSUED_ CREDIT_ NOTE	User abc has made a claim for the electronic sales invoice from his supplier and his supplier has already generated a credit note to cancel the invoice.	X	N/A
TACIT_ ACCEPTANCE	Your supplier has made a tacit acceptance of the electronic sales invoice, since he did not make the express acceptance or claim within three business days after receipt of the good or service.	X	N/A

Credit note status

A legal document used in purchase and sale transactions involving a discount subsequent to the issuance of the invoice, a total cancellation, a collection of an over-incurred expense or the partial or total return of goods.

Status Indicator	Description
YABICO_CREATED	The credit note has been filed with YABI-CO.
DIAN_VALIDATING	The credit note is being validated at DIAN.
DIAN_REJECTED	The credit note was rejected by DIAN for the following reasons: - reason 1...- reason n
DIAN_VALIDATED	The credit note has been validated by DIAN.
SEND_EMAIL	The credit note was sent to the acquirer (debtor customer) and to the electronic biller.

Debit note status

It is a document or accounting voucher used to specify the debts incurred by the acquirer of the document.

Status Indicator	Description
YABICO_CREATED	The debit note has been filed with YABI-CO.
DIAN_VALIDATING	The debit note is being validated at DIAN.
DIAN_REJECTED	The debit note was rejected by DIAN for the following reasons: - reason 1...- reason n
DIAN_VALIDATED	The debit note has been validated by DIAN.
SEND_EMAIL	The debit note was sent to the acquirer (debtor customer) and to the electronic biller.

Acquisition support document status

It is the document that supports the purchase of a good or the rendering of a service when the supplier is not obliged to issue electronic invoices.

Status Indicator	Description
YABICO_CREATED	The supporting document for acquisitions from non-obligated parties has been filed with YABI-CO.
DIAN_VALIDATING	The supporting document for acquisitions from non-obligated parties is being validated at the DIAN.
DIAN_REJECTED	The supporting document for acquisitions from non-obligated parties was rejected by the DIAN for the following reasons: - reason 1 - reason n
DIAN_VALIDATED	The supporting document for acquisitions from non-obligated parties has been validated by the DIAN.
SEND_EMAIL	The support document for acquisitions from non-obligated parties was sent to the acquiring mail (debtor client) and to the electronic invoicer.

Error processing

In the standard defined by Neia SAS, all errors must have:

• id: Error code defined under the standard of the present document.
• type: General type of the error (e.g. inputError, formError, etc.).
• subType: Error subtype that specifies the general type. This should be defined by the microservice, application or web portal as appropriate.
• message: A message explaining the error itself.
• title: A title or name of the error itself.
• helpText: A help text that can be used by the person receiving the error to understand the cause of the error and how to correct it or, in the worst case, notify the help desk. In general, this should be a URL to which the user who has received the error can go to find useful information about the error.
• language: Language in which the error is returned. By default all errors are returned in English (en-US).

Error Code Standard

Any error code will be a three-digit string `XXX` specifying the general error type, followed by a hyphen and an alphanumeric subtype modifier `Y`.
Below you will find the types, subtypes and codes defined to date. These will be returned in the `type`, `subType` and `id` fields respectively. Each type and subtype will go with its respective code. General errors will generally not have an alphanumeric modifier.

Application errors

Code range:`0XX-YYZ`

Request Errors (000-XY):

It may occur because the request does not include mandatory values or does not define one of the allowed values for a certain field.

Code	Name	Description
000-99	unknownError	Error unknown or not contemplated in the request.

Validation errors (001-XYZ):

Validation errors occur when there are fields with inconsistent or incorrectly filled out information.

General Errors

Code	Name	Description
001-T1	taxes Inconsistencies	Inconsistencies presented in the taxes.
001-T2	taxes Dont Exist In Lines	The document reported taxes that do not exist in the lines.
001-T3	taxes Dont Exist	Taxes that do not exist in the (type) of the document were reported in the lines.
001-T4	sum Of Taxes Error	When comparing the sum of taxes of the lines is different from the sum of those reported in the document.
001-T5	sum Of Taxes Not Consistent	When operating sum(documentLines/ taxDescription/ taxAmount) = A , it is not consistent with sum(taxDescription/ taxAmount) = B.
001-T6	sum Of Taxes Not Consistent	When operating sum(documentLines/ taxDescription/ roundingAmount) = A, it is not consistent with sum(taxDescription/ roundingAmount) = B.
001-T7	taxes Reported Are Different	The taxes reported on the lines are different from the taxes reported at the document level.
001-T8	tax Not Found In Totals	The taxNameDescription reported in the lines is not found in the totals.
001-LT1	line Totals Error	The sum of sum(documentLines/ taxDescription/ taxAmount) = A , it is not consistent with taxDescription/ taxAmount = B.
001-DS1	withholding Subtotals Error	The inconsistencies presented in the subtotals of witholdings
001-DS2	taxes Subtotals Error	The inconsistencies presented in the subtotals of taxes
001-DS3	percent Subtotals Error	The percent reported subtotals of tax_name in the lines are not consistent with those in the document.
001-DS4	subtotals Error	The sum of sum(documentLines/ taxDescription/ taxAmount) = A when it is {tax_name}, it is not consistent with taxDescription/ taxAmount = B.
001-DS5	subtotals Error	The sum of sum(documentLines/ taxDescription/ taxableAmount) = A when it is {tax_name}, it is not consistent with taxDescription/ taxableAmount = B.
001-LA1	line Extension Amount Error	Error presented in lineExtensionAmount
001-LA2	line Extension Amount Error	When operating (price - discounts) + charges = A, it is not consistent with the entered value B.
001-LA3	line Extension Amount Error	When operating (price - discounts) + charges = A = value, must be greater than or equal to 0.
001-PD1	payment Description Error	PaymentDescription(Prepayments): Error presented in the list of prepaids.
001-ID1	issue Date Error	The date (date_time) must be less than the invoice issue date.
001-PM1	price Modifier Error	Error presented in priceModifier object of type X.
001-PC1	price Change Error	When operating (base_amount * (percentage / 100)) = A, it is not consistent with the entered value B.
001-TD1	tax Description Error	Error presented in the taxDescription: tax_name
001-TD2	tax Groups Error	There cannot be two tax groups of the same type in a line.
001-TD3	tax Inconsistencies	When operating sum(taxSubtotal/ taxAmout) = A, it is not consistent with the entered value B.
001-TD4	tax Inconsistencies	When operating (sum((taxSubtotal/ taxableAmout * taxSubtotal/ percent) - taxSubtotal/ taxAmout) withholding_name, it is not consistent with the entered value X.
001-TS1	tax Subtotals Error	Error presented in the tax subtotals: There must be subtotals of the tax paid.
001-TS2	tax Subtotals Value Error	The value of taxable_amount(A) must be greater than or equal to 0.
001-TS3	tax Subtotals Value Error	The value of taxable_amount(A) must be less than or equal to (B).
001-TS4	tax Subtotals Percentage Error	There cannot be two percentages in the subtotals with the same value.
001-LT2	sum Lines Error	Totals: Error presented when comparing the total results and the sum of the lines.
001-DT1	discounts Error	When we compare documentTotals/ allowanceTotalAmount(A) with the sum of discounts(B) on the lines it does not match.
001-DT2	charges Error	When we compare documentTotals/ chargeTotalAmount(A) with the sum of charges(B) on the lines it does not match.
001-DT3	line Error	When we compare documentTotals/ lineExtensionAmount(A) with the sum of line extension amounts(B) on the lines it does not match.
001-DT4	tax Exclusive Error	When we compare documentTotals/ taxExclusiveAmount(A) with the sum of tax amount(B) on the lines it does not match.
001-DT5	tax Inclusive Error	When we compare documentTotals/ taxInclusiveAmount(A) with the sum of tax amount(B) on the lines it does not match.
001-DT6	prePaid Amount Error	When we compare documentTotals/ prePaidAmount(A) with the sum of prepayments(B) it does not match.
001-DW1	withholdings Inconsistencies	Inconsistencies presented in the withholdings.
001-DW2	withholdings Inconsistencies	The witholdings reported on the lines are different from the witholdings reported at the document level.
001-DW3	withholding Description Error	Error presented in the withholdingDescription:
001-DW4	withholding Groups Error	There cannot be two withholding groups of the same type in a line.
001-DW5	withholding Subtotal Error	When operating sum(withholdingSubtotal/ taxAmout) = A, it is not consistent with the entered value B.
001-DW6	not Consistent Withholdings Error	When operating (sum((withholdingSubtotal/ taxableAmout * withholdingSubtotal/ percent) - withholdingSubtotal/ taxAmout) = A, it is not consistent with the entered value B.
001-DW7	withholdings Subtotals Error	There must be subtotals of the withholding paid.
001-DW8	withholdings Percent Error	"When operating ({taxable_amount} * ({withholding.percent} / 100)) = A, it is not consistent with the entered value B.
001-DW9	taxable Amount Error	The value of taxable_amount(A) must be greater than or equal to 0
001-DW10	taxable Amount Error	The value of taxable_amount(A) must be less than or equal to (B).
001-DW11	subtotals Percentages Error	There cannot be two percentages in the subtotals with the same value.
001-F1	field Not Exist	The field cannot exist, since the X field exists.
001-N1	Name Error	You must enter the corporate name or full name of the person
001-N2	Name Error	the first name of the person must be entered in first_name
001-N3	Sur Name Error	the first surname of the person must be entered in first_surname
001-N4	invalid Corporate Name	According to the type of identification, the corporate name must be entered.
001-D1	wrong Date	Compares the dates and returns the error if it was found
001-FN1	non-floating Number	The value X is not floating and not decimal
001-V1	Wrong Value	In the value X, the value must be greater than or equal to N
001-V2	Wrong Value	In the value X, the value must be less than or equal to N
001-V3	Wrong Value	In the value X, the number of decimal places in its floating part must have at least N digits
001-V4	Wrong Value	In the value X, the number of decimal places in its floating part must have N or fewer digits
001-V5	Wrong Value	In the value X, the number of decimal places in its floating part must be between N and M digits
001-V6	Wrong Value	The value X entered does not correspond to a GTIN
001-V7	not A Nit	The value X entered does not correspond to a NIT
001-V8	percentage Error	The percentage must be a whole 1 and 100 with only two digits in its decimal part if it has one.
001-V9	not A Nit	It is responsible for validating the size of a text.

Validation errors for specific documents

Invoice Errors

Code	Name	Description
001-EI1	Invoice Request Error	This error only occurs in the context of invoices and only applies to invoice processes.
001-AIU1	Invalid AIU	The AIU invoice creation request does not meet the standards for this type of invoice.
001-AIU2	Invalid AIU	The AIU invoice creation request has a utility of less than 10%.
001-AL1	Invalid AIU Product Lines	The AIU invoice creation request includes more than two detail lines.
001-AT1	Invalid AIU Taxes	The AIU invoice creation request has tax validation errors.
001-ALM1	Invalid AIU Modifiers	The AIU invoice creation request has detail line modifiers (Charges or Discounts).
001-ALM2	Invalid AIU Modifiers	The electronic document request has detail lines with validation errors. The recordable basis reported in the document totals differs from the net taxable basis in the detail lines.

Credit Note

Code	Name	Description
001-EC1	Credit Note Request Error	This error only occurs in the context of credit notes and only applies to credit note processes.

Debit Note

Code	Name	Description
001-ED1	Debit Note Request Error	This error only occurs in the context of debit memos and only applies to debit note processes.

Support Document Request errors

Code	Name	Description
001-AS1	Support Document Request Error	This error only occurs in the context of acquisition support documents and only applies to acquisition support documents processes.

DIAN Errors (002-X)

This type of error only occurs in applications made to DIAN.

Code	Name	Description
002	DIAN Request Error	This error only occurs in applications made to DIAN.

Pagination Errors (003-X)

Paging errors occur because the request includes values that fall outside the range of allowed or possible results.

Code	Name	Description
003-1	Page Number Error	Page number error. This is usually due to the request including a page number that is outside the range of allowed or possible results.
003-2	Page Size Error	Page size error. This is usually due to the request including a page number that is outside the range of allowed or possible results.

YABI•CO Errors (004-X)

These are YABI-CO internal errors, usually document generation or database errors.

Code	Name
004-1	Database error
004-2	PDF generation error
004-3	Error generating XML
004-4	Database partitioning error
004-5	Insertion record error
004-6	Structure entering error
004-7	Modifying record error
004-8	Structure error when modifying record

Authentication Errors (090)

Authentication errors can be due to invalid credentials.

Code	Name	Description
090	Authentication Error	Authentication error due to invalid credentials.

Key errors or non-existent data (1XX-Y)

These errors may be caused by trying to use a key or data that does not exist within the system.

General errors

Code	Name	Description
100	dataNotFound	Usually occurs in creation or update contexts. It is due to the lack of information associated to one or more of the identifiers (UUID, NIT, C.C., etc.) present in the request.
110	userNotFound	Occurs in user handling contexts. This includes; session management, user queries or user modifications.

Business Unit Errors

Code	Name	Description
100-BU1	Business Unit Not Found	This is because there is no Business Unit associated with the uuid present in the application.

Invoice errors

Code	Name	Description
100-EI1	Invoice Not Found	This is because there is no Invoice associated with the UUID or consecutive present in the request.

Credit Note errors

Code	Name	Description
100-EC1	Credit Note Not Found	This is because there is no Credit Note associated to the uuid or consecutive present in the application.

Debit Note errors

Code	Name	Description
100-ED1	Debit Note Not Found	This is because there is no Debit Note associated to the uuid or consecutive present in the application.

Support Document errors

Code	Name	Description
100-AS1	Support Document Not Found	This is because there is no Supporting Document associated to the uuid or consecutive present in the request.

Existing or already used data errors (2XX-Y)

These errors may be caused by trying to use a key or data that already exists within the system.

General Errors:

Code	Name	Description
200	dataAlreadyUsed	One or more fields in the request have unique values already used.

Invoice errors

Code	Name	Description
200-EI1	Invoice Consecutive Already Used	The invoice consecutive has already been used.

Credit Note errors

Code	Name	Description
200-EC1	Credit Note Consecutive Already Used	The credit note consecutive has already been used.

Debit Note errors

Code	Name	Description
200-ED1	Debit Note Consecutive Already Used	The debit note consecutive has already been used.

Support Document errors

Code	Name	Description
200-AS1	Support Document Consecutive Already Used	The support document consecutive has already been used.

In the documentation we are going to find that some fields contain elements such as:

• [1-n]: Identifies that the element or group is mandatory, with a maximum of N occurrences.
• [0-n]: Identifies that the element or group is optional (possible not to be reported), with a maximum of n occurrences, where n is any integer value.
• Acquirer: Natural person, legal entity and other subjects that acquire goods and/or services that are obliged to demand and exhibit the sales invoice or equivalent document.
• Array[a-n]: Means that the object receives a list of objects with a minimum of a object and a maximum of n elements of the specified type. Where n is an integer.
• Acquisition Support Document: It is the document that supports the purchase of a good or the rendering of a service when the supplier is not obliged to issue electronic invoices. To learn more about the acquisition support document please visit the following DIAN website.
• Credit Note: A legal document used in purchase and sale transactions involving a discount subsequent to the issuance of the invoice, a total cancellation, a collection of an over-incurred expense or the partial or total return of goods. Our system does not support all types of credit notes, it only accepts the cancellation credit note (voidInvoice) and the partial credit note. To learn more about the credit note document please visit the following DIAN website.
• Debit Note: It is a document or accounting voucher used to specify the debts incurred by the acquirer of the document. To learn more about the credit note document please visit the following DIAN website.
• DIAN Events: Prerequisites of the electronic bill of sale as a security instrument. To know more about if, follow the next link.
• Electronic invoicing (FE) Subject obliged to issue electronic sales invoices, debit notes, credit notes and other electronic documents derived from the electronic sales invoice, in accordance with the requirements, characteristics and conditions, terms and technical and technological mechanisms established by the DIAN.
• Error: An error message indicates a reason for document rejection by YABI•CO or DIAN.
• Invoice: A commercial document that reflects all the information of a purchase and sale transaction. The fundamental information that appears in an invoice must reflect the delivery of a product or the provision of a service together with the date of accrual. Additionally; it must indicate the amount to be paid in relation to stocks, goods of a company to be sold for ordinary use of the operation or for its transformation or incorporation to the productive process. Finally, you must indicate the Value Added Tax rate to be applied in relation to the transaction based on the goods or services negotiated. To learn more about the credit note document please visit the following DIAN website.
• Product: It is defined as the result of processes, either a tangible or intangible element (a good or a service), which generates an income or an added value to whoever produces it.
• Goods: Goods are of a tangible nature, either an object or a commodity and have certain characteristics:
• Material: goods can be touched, they are tangible, so their transformation is also possible.
• Utility: they are capable of satisfying a large number of human desires.
• Scarcity: goods are scarce because, in general, they are not found in abundance, and therefore almost always have an unrelated value. For example, milk is a scarce good because it is a limited commodity.
• Transferable: goods can be transferred between individuals by buying and selling.
• Services: Services are intangible and are defined as an activity provided by a service provider. They have other characteristics different from goods:
• Intangibility services cannot be touched, but symbolize an action, process or activity.
• Variability: services are always different from each other, no two services are ever the same since the delivery of each service is performed by a person or personnel in specific places and at specific times. When any of these aspects change, the service offered changes.
• Inseparability: the services provided are not separated from the one receiving the service, but the process is simultaneous.
• Notification: It is a message that informs in a formal way any kind of important information about the document. (e.g. "The document is in validation status").
• String(a-n): indicates that the field will receive a String with a minimum of a and a maximum of n characters. Where a and n are integer values.
• Transactions: Is a request that is made to the system, where the invoice is registered in our system. It refers to the communication that there is either with our API or from our API to another information system.
• Warning: A warning message indicates a reason or advice why the document might be rejected.