Contents
Introduction
1-Filling guide for the global Online Digital Tax Receipt (CFDI) Version 4.0
Glossary
Appendix 1 General Notes
Appendix 2 Case using an expense CFDI applicable to a global CFDI
Appendix 3 Specific instructions to fill in the global CFDI applicable to hydrocarbons and oil products
Filling guide´s change control for the global CFDI Version 4.0
Introduction
Issuance of Internet digital tax receipts (CFDIs) for the acts or activities carried out, for the income received or for the withholding of contributions made by taxpayers, is an obligation for both individual and corporation taxpayers in accordance with article 29, first and second paragraphs, section IV and penultimate paragraph of the Fiscal Code of the Federation (CFF); and 39 of the Regulations of the CFF, according to regulation 2.7.1.21.; and Chapter 2.7 of the Online Digital Tax Receipts or Electronic Invoice of the current Omnibus Tax Resolution (RMF).
Article 29-A of the CFF in its section IV establishes the requirement to include in the tax receipt the code in the Federal Taxpayers Registry Code (RFC) of the receiver of the same. That provision clarifies that when no such code is available in the RFC, will be indicated the generic code that establish the Tax Administration Service by general rules. That code is published in rule 2.7.1.23. of the current RMF.
In spite of the foregoing and considering that according to the provisions of the article 29, penultimate paragraph of the article of said Code, the Tax Administration Service by means of general rules, may establish administrative facilities for taxpayers to issue their tax receipts through their own means, through service providers or with electronic means, determined by said rules. This decentralized body has established in rule 2.7.1.21. a facility for transactions that do not have the code in the receiver's RFC, consisting in being able to issue to its clients that do not request a CFDI in these transactions that are known as "executed with the general public". A simplified receipt for operations with the general public that cannot be used for deduction or accreditation purposes, being this condition to have to also prepare a global CFDI which includes:
- The amounts corresponding to each of the transaction carried out with the general public, of the period.
- The folio´s number or transaction of each one of the receipts of transactions with the general public that were issued in the period.
- Issue this global Online Digital Tax Receipt including as a code in the RFC of its receiver the generic code in the RFC for global CFDI, referred to in rule 2.7.1.23.
The global Online Digital Tax Receipt must be issued no later than 24 hours after the close of the transactions that comprise it.
The amount of the Value Added Tax and the Special Tax on Production and Services must be expressly and separately disaggregated into global CFDIs.
When the purchasers of the goods or recipients of the services do not request receipts of transactions with the general public, taxpayers will not be obliged to provide them when the amount is less than $100.00 (one hundred Mexican pesos 00/100 MN). However, they must include them within the global CFDI in which the transactions carried out with the general public are recorded.
The global CFDI, in which the transactions performed with the general public are recorded, should be sent to the Tax Administration Service or to the CFDI certification provider, as applicable, within 24 hours following the closing of transactions performed on a daily, weekly, monthly or bimonthly basis.
Technical documents specify the structure, form and syntax of the CFDI issued by taxpayers (individuals and corporations), which allows the information to be entered in an organized manner on the receipt.
Section I of this document describes how to fill the data to be recorded in the global CFDI version 4.0.
In the event of any doubt or situation regarding the filling of the global receipt that is not resolved in this guide, the taxpayer should refer to the following documents, which are published in the paragraph “Related Content” section of the Tax Administration Service website.
- Technical documents of Annex 20.
https://www.sat.gob.mx/consultas/35025/formato-de-factura-electronica-(anexo-20)
- Questions and answers of the Online Digital Tax Receipts.
https://www.sat.gob.mx/consultas/35025/formato-de-factura-electronica-(anexo-20)
- Use cases of Online Digital Tax Receipts.
This filling guide is a document which purpose is to explain to taxpayers the correct way to complete and issue a CFDI, observing the definitions of the technological standard of Annex 20 and the applicable legal provisions in force, using examples to facilitate the explanations. Therefore, it is important to clarify that the data used for the examples are fictitious and only for didactic purposes to easily explain how a CFDI is filled.
For the foregoing, the reader should be clear that the explanations made in this filling guide do not replace the existing legal or regulatory tax provisions, so in matters other than the correct form of filling and issuing a CFDI, as may be those relating to the determination of contributions, subjects, object, rates, tariffs, calculation mechanics, requirements of deductions, among others, taxpayers must comply with applicable tax regulations.
- Filling guide for the global Online Digital Tax Receipt (CFDI) version 4.0
When issuing a CFDI, it should be done with the specifications indicated in each of the fields expressed in non-computer language that are included in this section.
This document refers to the description of the information that must contain such CFDI.
When the following descriptions establish the use of a value, it is indicated in quotation marks, but in the CFDI, it must be entered without including the quotes, keeping upper and lower case, numbers, spaces and punctuation.
Name of the node or attribute
| Description
|
Node: Comprobante
Receipt
| Standard form of the Online Digital Tax Receipt.
|
Version
Version
| Must have the value “4.0”.
This data is integrated by the system used by the public entity for the issuance of the tax receipt.
|
Serie
Series
| It is the serial number used by the taxpayer for internal control of their information. This field accepts from one (1) to 25 alphanumeric characters.
|
Folio Folio
| It is the folio of internal control that the taxpayer allocates to the receipt, it can be conformed from one (1) to 40 alphanumeric characters.
|
Fecha
Date
| It is the date and time of issuance of the tax receipt. It is expressed in YYYY-MM-DDThh: mm: ss, and must correspond to the local time where the receipt is issued.
This data is integrated by the system used by the taxpayer for the issuance of the tax receipt.
Example: Date= 2022-01-27T11:49:48 |
Sello
Stamp
| It is the digital stamp of the tax receipt generated with the certificate of digital stamp of the taxpayer issuing the receipt. It functions as the signature of the issuer of the receipt and it is integrated by the system that the taxpayer uses for the issuance of the receipt.
| ||||||||||
MetodoPago
Payment method | The payment method code, with which the simplified general public operation receipt of the largest amount of the contents in the global CFDI was settled, should be entered. If there are two or more receipts with the same amount but different payment methods, the taxpayer may enter at its own discretion, one of the payment methods with which the same was received.
The different codes for payment methods are included in the catalogue c_FormaPago (c_PaymentMethods).
Example: Payment Method= 02
| ||||||||||
NoCertificado Certificate no. | It is the number that identifies the certificate of the issuer's digital stamp, which is included in the tax receipt by the system used by the taxpayer to issue the tax receipt. | ||||||||||
Certificado Certificate | It is the content of the certificate of the issuer's digital stamp and it is integrated by the system used by the taxpayer to issue the tax receipt. | ||||||||||
CondicionesPago | This field must not exist. |
Subtotal
Subtotal
| It is the sum of the amounts of the concepts before discounts and taxes. Negative values are not allowed.
This field must have up to the number of decimal places that the currency supports, see example on the Currency field. The amount entered in this field must be equal to the rounding of the sum of the amounts of the registered concepts.
| ||||||||||||
Descuento
Discount | The total amount of discounts applicable before taxes can be entered. Negative values are not allowed. It should be entered when discount concepts exist.
| ||||||||||||
Moneda
Currency | The code of the currency used to express the amounts must be recorded. When using national currency, "MXN" (Mexican pesos) is recorded, in accordance with the ISO 4217 specification.
The different currency codes are included in the catalogue c_Moneda (c_Currency).
Example: Currency= MXN
| ||||||||||||
TipoCambio Exchange rate | The exchange rate FIX can be recorded according to the currency recorded on the receipt. |
| This field is required when the currency code is different from "MXN" (Mexican peso) and the code "XXX" (the codes assigned for transactions involving any currency).
If the value is outside the percentage applicable to the currency, taken from the catalogue c_Moneda (c_Currency), the issuer must obtain from the CFDI certification provider that the CFDI will be stamped, not automatically, a confirmation code to confirm that the value is correct, and enter that code in the Confirmation field.
The upper limit is obtained by multiplying the published value of the FIX exchange rate by the sum of one plus the percentage applicable to the currency taken from the catalogue c_Moneda (c_Currency).
The lower limit is obtained by multiplying the published value of the FIX exchange rate by the sum of one minus the percentage applicable to the currency taken from the catalogue c_Moneda (c_Currency). If this limit is negative, zero is taken.
Important note: This validation will be effective only after the Tax Administration Service publishes in its website the procedures to generate the confirmation code and to parameterize the applicable maximum ranges.
|
Total | It is the sum of the subtotal, minus the applicable discounts, plus the contributions received (taxes). Negative values are not allowed.
This field must have up to the number of decimal places that the currency supports, see example on the Currency field.
When the equivalent value in MXN (Mexican peso) of this field exceeds the established limit, the Confirmation field must exist.
Important note: This validation will be effective only after the Tax Administration Service publishes in its website the procedures to generate the confirmation code and to parameterize the applicable maximum ranges.
|
| If withholdings are made, the facility of rule 2.7.1.21 cannot be applied of the current RMF, and a CFDI must be issued for each transaction. | ||||||
TipoComprobante
Receipt type | The code “I” must be entered, according to the catalogue c_TipoComprobante (c_ReceiptType). | ||||||
MetodoPago
Payment Method | The code "PUE" (payment in a single display) must always be entered, in accordance with the catalogue c_MétodoPago (c_PaymentMethod).
Example: Payment Method= PUE
| ||||||
LugarEmision
Issuance place
| The zip code of the issuance place of the receipt (address of the parent company or the branch) must be entered. It must correspond to a zip code included in the catalogue c_CodigoPostal (c_ZipCode)
If a tax receipt is issued in a branch, in this document, the zip code must be entered, regardless of whether the billing systems of the company are in a different address than the branch.
By entering the zip code in this field, the requirement to indicate the address and place of issue of the receipt referred to in sections I and III of Article 29-A of the CFF, is met. According to Rule 2.7.1.29., Section I of the Miscellaneous Fiscal Resolution in force.
The different zip codes are included in the catalogue c_CodigoPostal (c_ZipCode).
If the zip code catalogue c CodigoPostal does not include information on the zip code, the zip code closest to the place, where the fiscal receipt was issued should be recorded.
Example: Issuance Place= 01000
| ||||||
Confirmacion
Confirmation | The unique and unrepeatable confirmation code issued by the Online Digital Tax Receipt Certification Provider, or Tax Administration Service to issuers (users) must be entered, to issue the receipt with amounts outside the established range.
Example: Confirmation= ECVH1
Five-digit alphanumeric values must be entered.
Important note: The use of this code will be effective only after the Tax Administration Service publishes in its website, the procedures to generate the confirmation code and to parameterize the applicable amounts and maximum ranges. | ||||||
Node Informacion Global GlobalInforma tion | This node should include information related to the general public operation global receipt. | ||||||
Periodicidad Frequency | Field required to record the period corresponding to data in the global receipt. When the value in this field is “05”, the Tax Regime field should be “621”. Example: Frequency=02
| ||||||
Meses Months | The code for the month or months the information on operations with the general public corresponds to should be recorded; the different codes in force are included in catalogue c_Meses.
Example: Months=05
| ||||||
Año Year | The year corresponding to the global receipt information should be recorded. The value recorded should be the same as the current year or the immediately preceding year considering the year recorded in the field for the Date the receipt was issued. Example:
Year=2022
| ||||||
Node: CfdiRelacionado Related CFDI | In this node, the information of related tax receipts can be expressed. | ||||||
TipoRelacion Relation type | The relationship´s code between this receipt (global invoice) that is being generated and the previous CFDIs that have some relation to each other must be entered. The code of Relation Type is included in the catalogue c_TipoRelación (c_RelationType), published in the Tax Administration Service website.
When the relation type has the code “04” substitution, the receipt that is been generated (global invoice) as a substitute, is type “I” (Income). Example: Relation Type= 04
| ||||||
Node: CfdiRelacionado RelatedCFDI |
In this node, the information of related tax receipts must be expressed. | ||||||
UUID | The tax folio (UUID) of a tax receipt related to this receipt, must be entered.
Example: UUID= 5FB2822E-396D-4725-8521-CDC4BDD20CCF |
Node: Emisor Issuer
| In this node, the information regarding the taxpayer and its tax receipts must be entered. | ||||||||||||||||||||
RFC Federal Taxpayers Registry Code
| The code of the issuer of the receipt must be entered in the Federal Register of Taxpayers.
In the case that the issuer is an individual, this field must contain 13 characters. In the case of corporations, it must contain 12 characters.
Example: If is an individual, enter: RFC= CABL840215RF4
If it is a corporation, enter: RFC= PAL7202161U0 | ||||||||||||||||||||
Nombre Name
| The name or business name included in the RFC of the issuer of the receipt, it shall be necessary to record.
The Name should correspond to the RFC recorded in this Node´s RFC field. This information shall be checked in the fiscal status certificate provided by SAT, which can be obtained in the following link:
https://www.sat.gob.mx/aplicacion/login/53027/genera-tu-constancia-de-situacion-fiscal.
Example: If it is an individual, enter: Name= Marton Aleejandro Sanzi Fierror
If it is a corporation, enter: Name= La Palma Aei0 S A de C V | ||||||||||||||||||||
RegimenFiscal Tax regime
| The tax regime code in force of the issuing taxpayer, under which the receipt is being issued, must be specified.
The codes of the various regimes are included in the catalogue c_RegimenFiscal (c_TaxRegime).
This information will be checked in the certificate on fiscal status issued by SAT, in the following link:
https://www.sat.gob.mx/aplicacion/login/53027/genera-tu-constancia-de-situacion-fiscal.
Example: If the issuer is a corporation registered in the General Regime of the Corporations Act, enter the following: Tax Regime= 601
|
FacAtrAdquirente | This field is not applicable. |
Node: Receptor Receiver | In this node, the information of the taxpayer receiving the receipt must be expressed. |
RFC
Federal Taxpayers Registry Code | Enter the value “XAXX010101000.
Example: RFC= XAXX010101000
|
Nombre | This field should not exist. This field should include value “PUBLICO EN GENERAL”. |
DomicilioFiscal Receptor
Fiscal Domicilie Receiver | This field should include the same zip code as the code indicated in field LugarExpedicion.
Example:
ReceiverFiscalDomicile= 01000
|
ResidenciaFiscal Tax Address | This field must not exist. |
NoRegldTrib | This field must not exist. |
TaxLawReceiver TaxLawReceiver
| This field should include code “616”. |
UsoCfdi CFDI Use | Enter the code “S01” (With no fiscal effect). |
Node: Conceptos Concepts | In this node, the concepts described in the receipt, must be expressed. |
Node: Concepto Concept | In this node, the detailed information of each of the transactions receipts must be expressed with the general public. |
ClaveProdServ
CodeProdServ
| In this field, the code “01010101” from catalogue c_ClaveProdServ (c_CodeProdServ) published in the Tax Administration Service, must be entered.
Example: CodeProdServ= 01010101
|
|
| ||||||||
NoIdentificacion.
Identification no. | In this field, the number of folio or transaction of the operating receipts with the general public should be entered. It should have from one to 100 alphanumeric characters.
Example: Identification no.= 150 | ||||||||
Cantidad
Quantity | The value “1”, must be entered.
Example: Quantity= 1 | ||||||||
ClaveUnidad
Unite code | The code “ACT” from the catalogue c_CaveUnidad (c_UnitCode), published in the Tax Administration website, must be entered.
Example: Unit Code= ACT
| ||||||||
Unidad Unit | This field must not exist. | ||||||||
Descripcion
Description | The value “Sale”, must be entered.
Example: Description: Sale | ||||||||
ValorUnitario Unit Value | In this field, the subtotal of the transaction receipt with the general public must be entered, which can contain from zero to six decimal places. |
| If the type of receipt is “I” (Income), this value must be greater than zero.
Example: Unit Value= 1230.00 | ||||||||
Importe
Amount | It must be equivalent to the result of multiplying the Quantity by the Unit Value expressed in the concept, which will be calculated by the system that generates the receipt and will consider the rounding that this field has registered. Negative values are not allowed.
This field could include from cero to six decimal digits.
Example: Amount= 1230.00
| ||||||||
Descuento
Discount | Enter the number of applicable discounts for each transaction receipt with the general public. It must have up to the number of decimals that the field value of the concept has registered and must be less or equal to the Amount field. Negative values are not allowed.
This field could include from cero to six decimal digits. Example: Discount= 864.10
| ||||||||
ObjetoImpuesto
ObjectTax
| The corresponding code should be recorded to indicate whether the trading operation is taxable or not.
Example: ObjetoImp= 02
| ||||||||
Node: Impuestos Taxes | In this node, the taxes applicable to each transaction receipt with the general public can be entered.
If information is entered in this node, the transfers section must exist. | ||||||||
Nodo: Traslados Transfer | In this node, the transferred taxes applicable to each transaction receipt, with the general public can be entered. |
Nodo: Traslado Transfer
| In this node, the detailed information of a tax transfer corresponding to transaction receipt with the general public, must be entered.
In the case that a concept contains tax transferred by Rate, it must be expressed in different sections.
Note: It should be considered that these receipts do not actually have a receiver that could use them for credit, so the transferred tax breakdowns are intended to give control and easy identification of this data to its issuer. | ||||||
Base Base | The value for the calculation of the tax that is transferred must be entered. It can contain from zero to six decimal places.
The value of this field must be greater than zero. | ||||||
Impuesto
Tax | The code of the type of transferred tax applicable to each transaction receipt with the general public, which are included in the catalogue c_Impuesto (c_Tax) published in the Tax Administration Service website, must be entered.
Example: Tax= 002
| ||||||
TipoFactor
Factor Type | The factor type, applicable to the tax base that is included in the catalogue c_TipoFactor (c_FactorType) published in the Tax Administration Service website, must be entered.
Example: Factor Type: Rate
|
TasaOCuota
Rate or Fee | Enter the value of the tax rate or fee that is transferred for each transaction receipt with the general public. It is required when the Factor Type field corresponds to Rate or Fee.
Example: Rate or Fee= 0.160000
| |||||||||||||||||
Importe
Amount | The amount of the transferred tax that applies to each concept, can be entered. Negative values are not allowed. This field is required when in the Factor Type field has been entered as Rate or Fee.
The value of this field will be calculated by the system that generates the receipt and will consider the rounding that this field had registered. For more reference, see the technical documentation published in the Tax Administration Service website.
This field could include between 0 and six decimal digits.
| |||||||||||||||||
Nodo: Retenciones Withholdings | This node must not exist. | |||||||||||||||||
Nodo: ACuentaTerceros OnBehalfofThirdParties | This node should not exist. | |||||||||||||||||
Nodo: InformacionAduanera Customs information | This node must not exist. |
Nodo: CuentaPredial Property account | This node must not exist. | ||||||||||||
Nodo:Complemento Concepto Complement Concept | This node must not exist. | ||||||||||||
Nodo: Parte Part | This node must not exist. | ||||||||||||
Nodo: Impuestos Taxes | In this node, the summary of the applicable taxes must be entered. | ||||||||||||
TotalImpuestos Retenidos Total withheld tax | This field must not exist. | ||||||||||||
TotalImpuestos Trasladados
Total transferred taxes | It is the total of the transferred taxes that are derived from the concepts contained in the tax receipt, which must be equal to the sum of the amounts recorded in the Transfers section. Negative values are not allowed and is required when the concepts are registered transferred taxes.
| ||||||||||||
Nodo: Retenciones Withholdings | This node must not exist. | ||||||||||||
Node: Traslados Transfers | In this node, the applicable transferred taxes are entered, and is required when the concepts register a transferred tax.
If there are only concepts in the CFDI with an exempt Factor Type, this node should only include fields Base, Impuesto and TipoFactor. | ||||||||||||
Nodo: Traslado
Transfer | In this node, the detailed information of a specific tax transfer is entered.
There should be only one registration with the same combination of tax, factor and fee for each transfer. | ||||||||||||
Base
Base | The base amount of the transferred tax should be recorded, classified by Impuesto, TipoFactor and TasaOCuota, which shall include the number of decimal digits supported by the currency.
No negative numbers are allowed, and it should be equal to the rounding of the tax amount in the transferred Base fields recorded in items where the item tax is equal to the Tax field in this item and the TasaOCuota of the item, which is equal to field TasaOCuota in this item. Example: For each tax type, the corresponding amount should be recorded, in the case of accounting services the corresponding base amount is $15,000.00.
If there are only items with TipoFactor Exento, the amount in this item should be equal to the rounding of the addition of amounts in the Base fields recorded in the items.
| ||||||||||||
Impuesto
Tax | The code for the type of transferred tax, must be entered, which is included in the catalogue c_Impuesto (c_Tax), published in the Tax Administration Service website. |
| Example: Tax=002 |
TipoFactor
Factor Type | The factor type applicable to the tax base, must be entered, which is included in the catalogue c_TipoFactor (c_FactorType), published in the Tax Administration Service website.
Example: FactorType= Rate |
TasaOCuota
Quote or Fee | The value of the rate or fee of the transferred tax for each transaction receipt with the general public registered in the receipt could be recorded, which is included in the catalogue c_TasaOCuota (c_RateORFee), published in the Tax Administration Service website.
The value of the rate or fee that is recorded must correspond to a record where the tax column corresponds to the Tax field and the factor column corresponds to the field Factor Type.
Example: Rate or Fee= 0.160000 |
Importe
Amount | The amount of the transferred tax can be recorded, grouped by Rate or Fee and Factor Type, which must have up to the number of decimals that the currency supports, negative values are not allowed and must be equal to the rounding of the sum of the amounts of the transferred taxes recorded in the concepts where the tax of the concept is equal to the tax field of this section and the Rate or Fee of the concept is equal to the Rate or Fee of this section.
Example: Amount= 2400.00 |
Nodo: Complemento Complement
| In this node, the CFDI Certification Provider must include the Digital Tax Stamp complement, in mandatory way, and in its case, the Tax Administration Service website must include the CFDI Tax Registry complement when the global CFDI is issued through the electronic tool “Factura Fácil”. |
Node: Addenda | In this node, the extensions to this form that are useful to the taxpayer can be entered. For the rules of its use, refer to the technical documentation. |
Glossary
Node, element, paragraph or section: It is a data set.
Attribute or field: It is a single data.
FIX: Is an exchange rate established by Banco de Mexico to pay for mandatory obligations.
Appendix 1 General Notes
Note 1: The document includes didactic examples and uses fictional information for such purpose.
Appendix 2 Case using an expense CFDI applicable to a global CFDI
General Guidelines
All taxpayers for actions or activities performed by them, for the income they earn, for payment of wages and salaries or for tax withholdings they carry out, should issue tax receipts through digital documents via the Tax Administration Service website.
This example is a description of how to apply an expense CFDI for a discount, return or allowance of an operation documented in a global CFDI.
It is worth mentioning that we can observe to ways to reduce an operation included in a global CFDI to issue an income CFDI in an individual and nominative manner.
I. Example of CFDI Global with expense CFDI connected to a return from an item.
a) Generating a receipt from operations with the general public.
b) Issuing a Global CFDI (Attachment 20 version 4.0).
c) Issuing an expense CFDI for the return of an item included in the receipt of operations with the general public.
d) Issuing a nominative CFDI.
II. Example of cancelation of a Global CFDI for a request to generate an income CFDI from an operation documented in such invoice.
a) Cancelling Global CFDI.
b) Generating Global CFDI excluding the receipt of operations with the general public for the operation billed in a nominative manner.
c) Generating the nominative CFDI for the operation included in the receipt for operations with the general public.
Legal basis: Articles 29 and 29-A of the Federal Tax Code; Rule 2.7.1.21. of the Miscellaneous Fiscal Resolution in force.
APPROACH
I. Example of Global CFDI with expense CFDI connected to a return of an item.
Taxpayer La Linterna, S.A de C.V., carries out operations with the general public and issues a CFDI based on rule 2.7.1.21. In 11 June, it issued the following receipts of operations with the general public:
a) Generating a receipt for operations with the general public
Taxpayer generated a global CFDI to document sales occurring on 11 June.
- Issuing Global CFDI (Attachment 20 version 4.0)
After generating the global CFDI, customer Markuz Kuri returned La Linterna S.A: de C.V. an item included in the receipt for operations with the general public identified with number 17-2358-4569 amounting to $208.79 including VAT.
Taxpayer La Linterna S.A: de C.V. generated an expense CFDI for the amount of the return item made by customer, which was documented in the simplified receipt number 17-2358-4569 and connected it to the global CFDI integrated to the operation. Likewise, taxpayer issued another expense CFDI amounting to $208.79 including VAT, for a discount, in order to fully reduce the operation of ticket number 17-2358-4569.
C1) Issuing expense CFDI (discount) to reduce the other part of the operation included in the receipt for operations with the general public.
Customer Markuz Kuri requests La Linterna S.A: de C.V. issuing the invoice for the rest of items included in the receipt for operations with the general public number 17-2358-4569, and the company issues the income CFDI to its customer for items that were not returned.
II. Example cancelling a Global invoice for a request to generate an income CFDI for an operation documented in such invoice.
In this option, taxpayer can cancel the global CFDI, to issue it again excluding the operation documented in the receipt for operations with the general public number 17-2358-4569, for which the individual invoice is requested.
a) Cancelling Global CFDI
Cancelling the invoice in SAT website or through the CFDI Certification Provider; in this example, invoice is cancelled with UIDD AAAca0c2-3ea4-4506-abe3-f05771737e69.
Afterwards, taxpayer La Linterna S.A. de C.V. issues the global invoice excluding the operation included in the receipt for operations with the general public number 17-2358-4569 and it will issue a nominative CFDI.
b) Generating a Global CFDI excluding the receipt for operations with the general public of the operation invoiced in a nominative manner.
Finally, taxpayer La Linterna S.A: de C.V. generates the nominative invoice for the operation documented in the receipt for operations with the general public number 17-2358-4569.
c) Generating nominative CFDI for the operation included in the receipt for operations with the general public.
Appendix 3 Specific instructions to fill in the global CFDI applicable to hydrocarbons and oil products
Validity: The provisions in this appendix shall be optional as of 13 January 2020 and shall be enforceable as of 1 April that same year.
Appendix 2 in this Guide includes an example describing the way to apply an expense CFDI for a discount, return or allowance of an operation documented in a global CFDI.
In this regard, it is worth mentioning that for the global CFDI applicable to Hydrocarbons and Oil Products and provided that the sales is carried out, global CFDIs shall not be cancelled, the only way to cancel an operation which was performed and is included in a global CFDI, is the issuance of a connected expense CFDI for the return of an item, under the terms of Appendix 2, to generate an income CFDI in an individual and nominative manner, if requested by a customer.
Nodes and fields not included in this procedure should be included in the tax receipt according to the general guidelines in this guide.
FormaPago | The code for the form of payment with which the receipt for operations with the general public was paid should be recorded. If there are receipts for operations with the general public with different forms of payment, a global CFDI should be prepared for each one of them. The different codes for the form of payment are included in catalogue c_FormaPago. Example: FormaPago= 02 |
|
| ||||||||
Node:Concepto | This node should include detailed information about every receipt for operations with the general public. | ||||||||
ClaveProdServ | This field should include the code in catalogue c_ClaveProdServ available in SAT website, for the corresponding producto:
Example: ClaveProdServ= 15101505 | ||||||||
NoIdentificacion | This field should include the number of license granted by the Energy Regulating Commission, followed by a dash in order to record a single and consecutive number by hosepipe, which will consist of less than 40 characters.
Licenses whose nomenclature should be recorded are the following: |
|
Example A: For distribution to the public of gasolines and diesel, through a service station, the following ID number will be issued: NoIdentificacion = PL/00320/EXP/ES/2019-1 Example B: |
| For distribution to the public of Liquefied Petroleum Gas, through a service station with specific purpose, the following ID number will be issued: NoIdentificacion = LP/00751/EXP/ES/2016-105012365
If it is an expense receipt, this field should include information from NoIdentificacion field in the tax receipt related to this CFDI. Note: When code “15121500” is entered, the folio number or the number of operation of the receipts for operations with the general public should be recorded, and will consist of less than 40 characters. |
Amount | This field will include the amount in liters of diesel, gasoline, liquefied petroleum gas or cubic meters, in the case of natural gas, corresponding to each item.
Note: When measurement is in a different unit, the corresponding conversion should be performed. |
UnitCode | “LTR” code should be recorded in the case of diesel, gasoline, liquefied petroleum gas and “MTQ”, in the case of natural gas, from catalogue c_ClaveUnidad published in SAT website. Note: When measurement is in a different unit, the corresponding conversion should be performed. Example: ClaveUnidad= LTR |
Description | This field will include the product description. |
UnitValue | This field should include the unit value or price for every item, which will consist of zero to six decimal digits. Whether the receipt is “I”-type (Income) or “E”-type (Expense), this value should be above zero. Example: ValorUnitario= 1230.00 |
Node: Taxes | This node should include taxes applicable to every item. If information is recorded in this node, transfer section should exist. |
Node:Transfers | This node should include transferred taxes applicable to this item. |
Node:Transfer | This node should include detailed information about a tax transfer applicable to every item. If an item includes taxes transferred for Fee and Rate, it should be entered into different sections. Note: It should be considered that these receipts do not really have a receiver who could use them for crediting purposes; thus, the breakdown of transferred taxes is intended to give control and make the identification of this information easier to their issuer. |
Tax | The code for the type of transferred tax applicable to every item, which are included in catalogue c_Impuesto published in SAT website. Example: Tax= 002
| |||||||||||||||||
FeeOrRate | The value for the fee or rate of the transferred tax for every item should be recorded. Required when the TipoFactor field corresponds to TasaOCuota. If the value recorded is fix, it should correspond to the type of tax and factor according to catalogue catálogo c_TasaOCuota. If the value recorded is variable, it should correspond to the range between the minimum and maximum value indicated in the catalogue. Example: TasaOCuota= 0.160000
| |||||||||||||||||
Amount | The amount of transferred tax applicable to every item should be recorded. No negative values are allowed. |
| This field is required in field TipoFactor when it is recorded as TasaOCuota. The value in this field will be estimated by the system issuing the receipt and will consider the roundings recorded for this field in technical standard in Attachment 20, see the technical documents for more information in SAT website. This field should include between zero to six decimal digits. |
Change control of the filling guide for global Online Digital Tax Receipt (CFDI) Version 4.0
Guide published in the Tax Administration Service website, on December 31, 2021
¿Le fue útil este artículo?
¡Qué bueno!
Gracias por sus comentarios
¡Sentimos mucho no haber sido de ayuda!
Gracias por sus comentarios
Comentarios enviados
Agradecemos su iniciativa, e intentaremos corregir el artículo