Compliance with Mexico SAT Requirements

The Mexico Localization SuiteApp enables compliance with specific legal requirements established by the SAT to issue electronic accounting files and electronic invoices in Mexico.

Most of the latest catalogs from the SAT are supported by the SuiteApp. SAT catalogs contain codes and values that describe or classify a product or service, transaction, payment, tax category, industry type and other business elements. The SAT requires fields with these codes and values to be included in the Mexico Electronic Accounting Files and Electronic Invoices for Mexico.

When you install the Mexico Localization SuiteApp, the catalogs are stored in NetSuite as custom records. Custom fields are automatically integrated or mapped to applicable NetSuite transactions or records to capture information in the SAT catalogs. The values you can choose from these custom fields are sourced from the catalogs.

Most of the SAT custom fields are required by the SAT and you must specify values for them.

The following table summarizes the SAT-required custom fields that are integrated with NetSuite records.

SAT Custom Field Name	NetSuite Records where SAT Custom Field is Available	Catalog Record Name in NetSuite	Description
SAT Unit Code (c_ClaveUnidad)	—	Mexico Mapping Value	Units of measure defined by the SAT applicable to the quantity expressed for each item. The units of measure must be manually entered. Follow the steps described in SAT Unit Codes. NetSuite Units of Measure must correspond to the SAT-defined unit codes. For more information, see Mexico Localization Field Mapping.
SAT Item Code (c_ClaveProdServ)	Item Fulfillment, Invoice, Cash Sale, Credit Memo Item	Mexico SAT Item Code	Codes defined by the SAT to classify the product or service described in the item field. Item codes must be manually entered. Follow the steps described in SAT Item Codes. The SAT Item Code must be defined on the Item record.
SAT Account Grouping (c_CodigoAgrupador)	—	Mexico Mapping Value	Codes defined by the SAT to classify and group the accounts assigned to a company or subsidiary. All the accounts of your company’s or subsidiary’s Chart of Accounts must be mapped to the most similar SAT Account Grouping codes. For more information, see Mexico Localization Field Mapping. Note: Do not add accounts with duplicated ID in parent or child records. Otherwise the mapping fails and error may be caused in reports.
SAT Bank (c_Bancos)	—	Mexico Mapping Value	Codes defined by the SAT to classify Mexican banks. You must assign your company’s or subsidiary’s bank accounts to the SAT-defined banks. For more information, see Mexico Localization Field Mapping. Note: Do not add accounts with duplicated ID in parent or child records. Otherwise the mapping fails and errors may be caused in reports.
SAT Customs Request Number (NumeroPedimento)	Sales Order, Item Fulfillment, Invoice, Cash Sale, Credit Memo	—	Customs request number assigned to first-hand sales of imported goods.
SAT Cadastre ID (CuentaPredial)	Sales Order, Item Fulfillment, Invoice, Cash Sale, Credit Memo	—	In real property items, number assigned to the property when entered in the cadastre registry.
SAT Payment Method (c_FormaPago)	Sales Order, Invoice, Cash Sale, Customer Payment	Mexico Mapping Value	List of payment methods defined by the SAT (cash, check, credit card...). NetSuite Payment Methods must be mapped to the SAT-defined payment methods. For more information, see Mexico Localization Field Mapping.
SAT Payment Term (c_MetodoPago)	Invoice, Cash Sale	Mexico SAT Payment Term	Type of payment defined by the SAT that applies to the transaction being generated (for example: single payment or installment).
SAT Tax Category (c_Impuesto)	—	Mexico Mapping Value	Codes defined by the SAT to identify the type of taxes in Mexico (IVA, ISR, IEPS). Existing NetSuite Tax Types must be mapped to the SAT-defined tax types. For more information, see Mexico Localization Field Mapping.
SAT Tax Factor Type (c_TipoFactor)	Tax Code	Mexico SAT Tax Factor Type	Tax attribute applicable to the tax type (Rate, Fixed Value or Exempt).
Addendum (Addenda)	Sales Order, Item Fulfillment, Invoice, Cash Sale, Credit Memo, Customer Payment	—	Additional information that can be optionally included in the CFDI. The content included in this field is not regulated by the SAT. If you want the Addendum to be included in the CFDI, you need to manually add this field to the XML before being sent for certification.
SAT Industry Type (c_RegimenFiscal)	Company Information, Subsidiary, Customer	Mexico SAT Industry Type	Tax regime defined by the SAT to classify the industry type of your company or subsidiary.
SAT Voucher Type (c_TipoDeComprobante)	—	—	ID defined by the SAT that identifies the type of e-document being issued.
Relationship Type (c_TipoRelacion)	Item Fulfillment, Invoice, Cash Sale, Credit Memo, Customer Payment	Mexico SAT Relationship Type	Codes defined by the SAT to describe the relation existing between the current transaction and certified transactions.
Related CFDI (CfdiRelacionado)	Item Fulfillment, Invoice, Cash Sale, Credit Memo, Customer Payment	—	CFDI (and UUID) associated with the transaction being generated. You can add multiple related CFDIs to a transaction only if they are of the same type. Adding multiple related CFDIs of different types within the same transaction is not supported.
CFDI Usage (c_UsoCFDI)	Item Fulfillment, Invoice, Cash Sale, Credit Memo	Mexico SAT CFDI Usage	Codes defined by the SAT to identify the specific use that is given to the CFDI.
RFC	Employee, Vendor, Lead, Prospect, Customer, Contact, Partner	—	Entity's tax ID number that has a specific format and length. The RFC field is required for DIOT reporting and Electronic Invoicing. To learn more about the RFC field, see RFC Field.
Customer RFC	Sales Order, Invoice, Cash Sale, Credit Memo, Customer Payment	—	Entity's tax ID number. The value in this field is sourced from the Customer record RFC field.
UUID (folio fiscal)	Item Fulfillment, Invoice, Cash Sale, Credit Memo, Customer Payment	—	This is the Universal Unique Identifier (tax folio) assigned to the CFDI upon approval from the SAT.
UUID Received	Vendor Bill, Vendor Credit, Bill Payment	—	This is the Universal Unique Identifier (tax folio) assigned to the CFDI upon approval from the SAT.
Certification Timestamp	Item Fulfillment, Invoice, Cash Sale, Credit Memo, Customer Payment	—	Date and time when the CFDI was certified by the SAT.
Operation Type	Purchase Order, Vendor Bill, Expense Report, Vendor Credit, Check	—	Indication of the transaction operation type. This field is required for DIOT reporting. If you do not select any value, the DIOT report uses Others as the default operation type for the transaction. On an Expense Report with a Mexican vendor, you can specify the Operation Type for each expense line. Note: You can optionally indicate the Operation Type on a Purchase Order to capture this information before converting the PO into a Vendor Bill.
Vendor	Expense Report	—	In the DIOT file, all line items on expense reports must indicate the name of the vendor or supplier.
Payment ID	Customer Payment	—	Any number that identifies the payment (for example: check number, authorization number, reference number).
Issuer Entity RFC	Customer Payment	—	RFC of the entity (bank, financial institution, or others) from which the payment was issued. If the issuer is a foreign entity, then use the generic RFC ‘XEXX010101000’.
Issuer Bank Name	Customer Payment	—	Enter the name of the bank from which the payment was issued. This name is required when the paying entity is a foreign bank.
Payer Account	Customer Payment	—	Account number used by the paying party to make the payment.
Recipient Entity RFC	Customer Payment	—	RFC of the entity (bank, financial institution, or others) where the payment was received.
Recipient Account	Customer Payment	—	Account number where the beneficiary received the payment.
Payment String Type	Customer Payment	—	Payment string ID generated by the recipient entity.
Payment Certificate	Customer Payment	—	Payment certificate as a text string formatted in base64.
Payment String	Customer Payment	—	Enter the original string of the receipt generated by the payment recipient entity.
Payment Signature	Customer Payment	—	Digital signature of approval associated to the payment as a text string formatted in base64.
Tax Object (c_Objetolmp)	Invoice, Cash Sale, Credit Memo	—	A SAT defined code of tax object on the Item record. When issuing a transaction using Customer payment XML templates, the system uses following logic to source “ObjetolmpDR” and “Objetolmp” fields: If at least one item is Objetolmp = 02, then ObjetolmpDR = 02 If no item is Objetolmp = 02, then select the Objetolmp = 01 hardcoded.
Export Type (c_Exportacion)	Item Fulfillment, Invoice, Cash Sale, Credit Memo	—	The code defined by SAT that corresponds to the type of export that will be used for moving goods. If you select code 02, Foreign Trade Complement may be required by the SAT.
SAT Registered Name	Company, Customer, Subsidiary	—	The name of the company or subsidiary as registered in SAT.

Related Topics