Mexico 102400

Epicor ERP
Mexico Country Specific

Functionality Guide
10.2.400
Disclaimer
This document is for informational purposes only and is subject to change without notice. This document and its
contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its
date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with
regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a
particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is
likely to be unique in their requirements in the use of such software and their business processes, users of this document
are always advised to discuss the content of this document with their Epicor account manager. All information contained
herein is subject to change without notice and changes to this document since printing and other important information
about the software product are made or published in release notes, and you are urged to obtain the current release
notes for the software product. We welcome user comments and reserve the right to revise this publication and/or
make improvements or changes to the products or programs described in this publication at any time, without notice.
The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of
any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage
of the solution(s) described in this document with other Epicor software or third party products may require the purchase
of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements
in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws
and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly
Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of
platform and product compatibility in this document shall be considered individually in relation to the products referred
to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also
stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible
with both of the products running at the same time on the same platform or environment. Additionally platform or
product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and
Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs
released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2019.
All rights reserved. Not for distribution or republication. Information in this document is subject to Epicor license
agreement(s).
90510-905-3064-608
10.2.400
Revision: May 14, 2019 12:31 a.m.
Total pages: 144
sys.ditaval
Mexico Country Specific Functionality Guide Contents
Contents
Mexico CSF Guide...................................................................................................................7
Setup...............................................................................................................................................................8
Additional Post-Migration Steps................................................................................................................8
Remove CSF Mexico BPMs From Epicor ERP 10..................................................................................8
Remove the LongDescription UD Field...............................................................................................9
Payment Method (SAT) Update..........................................................................................................9
Payment Method (SAT) Update Fields.........................................................................................9
Run the Conversion Program......................................................................................................9
Set Up CSF Default Settings on Country License Change...........................................................................9
Setup - Mexico Localization....................................................................................................................10
Solution Workbench........................................................................................................................10
Load User Defined Codes.........................................................................................................11
User Defined Codes Maintenance....................................................................................................12
Add UD Codes to MXProdServ Code Type................................................................................12
Add UD Codes to MXUOMCFDI Code Type..............................................................................12
Add UD Codes to MXCountry Code Type.................................................................................12
Tax Type Maintenance.....................................................................................................................13
Mexico Fields............................................................................................................................13
Create Tax Type Codes.............................................................................................................13
Journal Code Maintenance..............................................................................................................14
Mexico Fields............................................................................................................................14
Create a Journal Code..............................................................................................................14
General Ledger Account Maintenance.............................................................................................15
Mexico Fields............................................................................................................................15
Specify a Concept....................................................................................................................15
Electronic Interface Maintenance.....................................................................................................15
Set Up Electronic Interface for Modifying an Electronic XML file................................................15
Supplier Maintenance......................................................................................................................16
Mexico Fields............................................................................................................................16
Bank/Remit To-Mexico Fields....................................................................................................17
Payment Method Maintenance........................................................................................................17
Mexico Fields............................................................................................................................17
Create a Payment Method........................................................................................................17
Bank Account Maintenance.............................................................................................................18
Mexico Fields............................................................................................................................18
Country Maintenance......................................................................................................................18
Mexico Fields............................................................................................................................18
Set Up a Country......................................................................................................................19
Setup - Digital Tax Receipt......................................................................................................................19
Migration from Epicor 9 to Epicor ERP 10........................................................................................20
Develop the MXCustomPAC.dll File.................................................................................................20
Epicor ERP | 10.2.400 3

Contents Mexico Country Specific Functionality Guide
Create a Digital Tax Receipt Document Type....................................................................................20

Digital Certificate Store....................................................................................................................21
Load a Certificate.....................................................................................................................21
PAC Configuration Maintenance.....................................................................................................22
Detail Fields..............................................................................................................................22
List Fields..................................................................................................................................22
Configure PAC.........................................................................................................................23
Company Configuration..................................................................................................................23
Mexico Fields............................................................................................................................23
Set Up Digital Tax Receipts.......................................................................................................24
Tax Regime Maintenance.................................................................................................................25
Detail Fields..............................................................................................................................25
List Fields..................................................................................................................................26
Specify a Tax Regime................................................................................................................26
Lot Number Entry............................................................................................................................26
Mexico Fields............................................................................................................................27
Site Maintenance.............................................................................................................................27
Mexico Fields............................................................................................................................27
Unit of Measure Maintenance.........................................................................................................27
Mexico Fields............................................................................................................................27
Miscellaneous Charge Maintenance.................................................................................................28
Mexico Fields............................................................................................................................28
Part Maintenance............................................................................................................................28
Mexico Fields............................................................................................................................28
Customer Maintenance...................................................................................................................29
Mexico Fields............................................................................................................................29
Ship To-Mexico Fields...............................................................................................................30
Mexico Fields............................................................................................................................30
Set Up a Customer...................................................................................................................30
General Operations........................................................................................................................................31
General Operations - Mexico Localization................................................................................................31
Asset Maintenance..........................................................................................................................32
Add Tax Information to an Asset Record...................................................................................32
AP Payment Entry............................................................................................................................32
Mexico Fields............................................................................................................................33
Enter Payment Information Using Existing Supplier...................................................................33
Enter Payment Information Using One-Time Supplier................................................................34
Supplier Tracker...............................................................................................................................34
Mexico Fields............................................................................................................................35
Supplier Display...............................................................................................................................35
Mexico Fields............................................................................................................................35
General Operations - Digital Tax Receipt.................................................................................................36
AR Invoice Entry..............................................................................................................................36
Header-Mexico Tab..................................................................................................................37
Mexico Fields............................................................................................................................39
4 Epicor ERP | 10.2.400

Mexico Country Specific Functionality Guide Contents
Create a Digital Tax Receipt AR Invoice.....................................................................................40

AR Invoice Posting....................................................................................................................42
Cancellation of Digital Tax Receipt AR Invoices.........................................................................42
Posted AR Invoice Update................................................................................................................44
Customer Shipment Entry................................................................................................................44
AR Invoice Tracker...........................................................................................................................44
Header-Mexico Tab..................................................................................................................44
View the Status of a Digital Tax Receipt AR Invoice...................................................................47
CFDI Digital Tax Receipt XML File Structure...............................................................................48
Electronic International Trade CFDI Supplement XML File Structure...........................................58
Error Messages.........................................................................................................................65
SAT AR Invoice Form................................................................................................................66
Cancellation Invoice Status MX........................................................................................................78
Advanced Search Fields............................................................................................................78
Cancellation Invoice Status Fields..............................................................................................78
Review the Cancellation Status of an Invoice............................................................................79
AP Invoice Entry...............................................................................................................................80
Posted AP Invoice Update................................................................................................................80
AP Invoice Tracker...........................................................................................................................81
Payment Tracker MX.......................................................................................................................81
Advance Search Fields..............................................................................................................81
Detail Fields..............................................................................................................................82
List Fields..................................................................................................................................84
Check Detail Fields...................................................................................................................86
Journal Entry...................................................................................................................................87
Journal Detail Tracker......................................................................................................................87
Update Invoice Fiscal Folio MX.........................................................................................................87
Import Fields............................................................................................................................88
Parameters Fields......................................................................................................................89
Import and Process an XML File with AP Invoice Information.....................................................90
Update Journal Fiscal Folio MX........................................................................................................91
Import Fields............................................................................................................................91
Import and Process an XML File with Journal Information.........................................................94
Update Payment Fiscal Folio MX......................................................................................................94
Import Fields............................................................................................................................95
Import and Process an XML File with AP Payment Information..................................................97
Cash Receipts Entry.........................................................................................................................98
Cash Receipt Posting................................................................................................................98
Mexico Fields............................................................................................................................98
Mexico Fields............................................................................................................................99
Create a Cash Receipt..............................................................................................................99
Cash Receipt Tracker.....................................................................................................................100
Mexico Fields..........................................................................................................................100
Epicor ERP | 10.2.400 5

Contents Mexico Country Specific Functionality Guide
Electronic CFDI Payment Supplement File Structure.................................................................101

Cash Receipt Payment Supplement Report..............................................................................105
Reports........................................................................................................................................................109
Important Notes on Accounts and Payment Method Types....................................................................109
DIOT Report MX...................................................................................................................................110
Create a DIOT Report MX..............................................................................................................111
List Of Accounts MX Report..................................................................................................................112
Selection Fields..............................................................................................................................115
Create a List Of Accounts MX Report.............................................................................................115
Trial Balance MX Report........................................................................................................................116
Create a Trial Balance MX Report..................................................................................................119
GL Journals MX Report.........................................................................................................................120
Create a GL Journals MX Report....................................................................................................132
Folio Number's Auxiliary (Report E).......................................................................................................133
Mexico Folio Number's Auxiliary-Selection Fields............................................................................137
Create a Folio Number's Auxiliary (Report E)..................................................................................137
Account's Auxiliary (Report F)...............................................................................................................137
Account's Auxiliary-Selection Fields................................................................................................139
Create an Account's Auxiliary (Report F)........................................................................................139
Withholding Tax Certificate MX Report.................................................................................................139
Complete Steps Before You Create a Report..................................................................................142
Create a Withholding Tax Certificate MX Report............................................................................143
6 Epicor ERP | 10.2.400

Mexico Country Specific Functionality Guide Mexico CSF Guide
Mexico CSF Guide
Use the Mexico Country Specific Functionality (CSF) Guide to set up electronic invoicing (digital tax receipts)
and localization reports. The localization reports comply with basic regulations to complete taxes for SAT compliance
(Servicio de Administracion Tributaria) in Mexico.
The Mexico CSF performs many necessary calculations to determine the main federal taxes in accordance with
regulations to help your company realize accurate financial planning.
Digital Tax Receipts

Electronic Invoicing is mandatory in Mexico and it involves the creation of an XML document sent to an authorized
certification supplier or PAC (Proveedor Autorizado de Certificación) who validates the information by certifying
the XML document and appends the document with the digital fiscal stamp, TFD (TimbreFiscalDigital), and other
unique data per requirement.
You can use Epicor ERP to create digital tax receipt XML documents for AR invoice or AR credit memos as well
as generating a compliant PDF file once certified. This process is initiated using the AR Invoice Posting process.
The Digital Seal (sello) encryption uses two key files (.key and .cer) for the certificates. The key files are unique
to Mexico and are acquired from SAT, along with a password.
Storage of the XML documents is the responsibility of each company per SAT's requirements. It is the
recommendation of Epicor to have a background process to replicate the certificates in a secure server and define
a naming convention.
Cash Receipt with Payment Supplement

When an invoice is issued, a customer needs to specify if it was paid at that time or will be paid in a further date.
As of September 2018, there is a new XML document required in Mexico to certify that cash has been received
when an invoice is not paid at the moment of generation and/or is paid in various installments.
The XML certification process is practically identical to the one for the AR invoice but with the difference that
this XML document is generated from Cash Receipt Entry.
Electronic Accounting
Monthly accounting reports in XML format need to be delivered to Mexican fiscal authority SAT and these can
be generated from Epicor ERP.
Files need to be manually submitted each month to SAT portal for List of Accounts MX (Catálogo de cuentas)
and Trial Balance MX (Balanza de Comprobación).
There is also an option to generate GL Journals MX (Pólizas del periodo), Folio Auxiliary (Auxiliar de folios de
comprobantes fiscales), and Account Auxiliary (Auxiliar de cuenta y subcuenta), which are submitted to fiscal
authority upon request.
This Guide is also available in a separate .pdf file format. You can both display this file or print out a hard copy.
When you click on the Mexico CSF Functionality Guide.pdf link, the PDF file opens in a separate tab.
Epicor ERP | 10.2.400 7

Mexico CSF Guide Mexico Country Specific Functionality Guide
Setup
Use the Setup topics to complete required localization tasks for Mexico.
The Setup tasks are organized as follows:
• Mexico Localization - setup tasks required for correct operation of the Mexico CSF
• Digital Tax Receipt - setup tasks related specifically to the Digital Tax Receipt functionality
The Mexico CSF requires your base currency to be the Mexican peso so that monthly tax and other reports will
be reported using the Mexican peso.
Note Users need to be granted the Security Manager rights to perform the Mexico CSF installation and
initial setup for processing Digital Tax Receipts. Refer to User Account Security Maintenance topic in ERP
Help for details.
The procedures that follow only reflect changes specific to Mexico. Refer to the program topics in the Application
and Field Help for additional information.
Additional Post-Migration Steps
After the migration of Epicor 9.05.702A with Mexico CSF to Epicor ERP 10 (review the Epicor 10 Migration
Guide for details), complete the following additional steps for Mexico CSF in Epicor ERP 10.
Note The Monthly Report of Receipts Issued became obsolete since CFD is no longer supported.
The posting rule in the Mexico CSF for AR Invoice transactions became obsolete and was removed in scope
of CFDI 3.3 implementation.
Remove CSF Mexico BPMs From Epicor ERP 10
Epicor 9 CSF Mexico contains the following BPM:

• Mexico_SupplierValidation.bpm
In Epicor ERP 10, this BPM is no longer needed because the functionality was moved to the BO source code.
After the migration from Epicor 9 and the conversion of BPM Directives, remove this BPM from Epicor ERP 10.
1. Navigate to Method Directives.

Menu Path: System Management > Business Process Management > Method Directives Maintenance
Important This program is not available in Epicor Web Access.
2. Click the Method Code button.

The Method Search dialog box displays.
3. Select the Search by Directives option.
4. In the Directive Group field, search for the Mexico group.
5. Select this group and click the Search button.
6. Select the required method and click OK.
8 Epicor ERP | 10.2.400

7. In the Method Directives window, delete method directives for the selected group.
Note You can delete only method directives that belong to your company.
Remove the LongDescription UD Field

If you are migrating from Epicor ERP 10.1.301 or 10.1.400 versions, you may have created the LongDescription
UD field for the TaxRegime table as it is described in the Adjust the Tax Regime Field Length section (review
the Mexico CSF Guides 10.1.301 or 10.1.400 for details). Starting from Epicor ERP 10.1.500 version, this field is
not used, and you can remove it.
Payment Method (SAT) Update
Use the Payment Method (SAT) Update conversion program to apply values to the PayMethod.MXPaidAs
and InvcHead.MXPaidAs DB fields.
Menu Path: System Management > Rebuild Processes > Finance > Payment Method (SAT) Update MX
Payment Method (SAT) Update Fields

Payment Method (SAT) Update
Fields for the current sheet are listed on this topic.

Some fields on the interface have a context menu, which is indicated by a triangle in the upper right corner of
the field. To open the context menu, right-click on the field.
Schedule
From this list, select the schedule option during which you would like the report or process to run. Options include
Now, Startup Task Schedule, and any other user-defined schedules created for your company.
To learn more about creating schedules, review the System Agent Maintenance > Schedules Details topic.
Run the Conversion Program
1. Navigate to Payment Method (SAT) Update.

Menu Path: System Management > Rebuild Processes > Finance > Payment Method (SAT) Update MX
2. If you wish to immediately run the process, verify the Schedule drop-down list displays the Now option.
This indicates that the process will run immediately when you start it.
3. Click the Submit button.
4. Exit Payment Method (SAT) Update.
Set Up CSF Default Settings on Country License Change

The appropriate country code (CSF license) must be selected in Company Properties in Epicor ERP Administration
Console. For more information, review the following topics in Epicor 10 Installation Guide and Epicor 10
Migration Guide.
• Installation and Configuration > 4. Configure Epicor Server and Application Server > Import License File and
Enable Modules
Epicor ERP | 10.2.400 9

• Installation and Configuration > 4. Configure Epicor Server and Application Server > Add Company
• Supplemental Installations > Configure Country Specific Functionality (CSF)
1. Run Epicor ERP.
2. Navigate to Company Configuration.

Menu Path: System Setup > Company/Site Maintenance > Company Configuration
3. Navigate to the Modules > All Modules > Localization > Detail sheet and verify that the Localization
field displays Mexico.
Other parameters in Company Configuration are automatically updated with default values for the selected
country. To set up other options, review the Activate Options for a Country topic in Application Help.
4. Exit Company Configuration.
5. In the confirmation message that asks you to save the changes, click Yes.
The default values for country-specific parameters are saved.
Setup - Mexico Localization
Use the Setup - Mexico Localization topics to complete necessary tasks to create Mexico localization tax reports.
Use the following programs to set up Mexico localizations:
• Solution Workbench
• User Defined Codes Maintenance
• Tax Type Maintenance
• Journal Code Maintenance
• General Ledger Account Maintenance
• Electronic Interface Maintenance
• Supplier Maintenance
• Payment Method Maintenance
• Bank Account Maintenance
• Country Maintenance
Solution Workbench
Use Solution Workbench to import a cab file with user defined codes to Epicor ERP.
The MXSATCatalogs_Customer Solution_3.2.400.0.cab file contains the following dictionaries with values.
Code Type ID Description Long Description SAT Name or

Comment
INCOTERM INCOTERM INCOTERM c_INCOTERM
MXCustDoc Custom Document Code Clave de Pedimiento c_ClavePedimento
MXMoveReas Moving Reason Catálogo de motivos por el cual c_MotivoTraslado
se desplaza mercancia
MXUOMCust Customs Unit of Measure Unidad Medida Aduana c_UnidadAduana
10 Epicor ERP | 10.2.400


Comment
MXPaymForm Form of Payment Catálogo de formas de pago c_FormoPago
MXTaxType Tax Type Catálogo de impuestos c_Impuesto
MXPaymMeth Method of Payment Catálogo de Método de Pago c_MetodoPago
MXFactType Factor Type Catálogo tipo factor c_TipoFactor
MXRelType Invoices Relation Type Catálogo de tipos de relación c_TipoRelacion
entre CFDI
MXPurType Purchase Type Catálogo de uso de comprobantes c_UsoCFDI
MXTranType MXTranType DIOT Transaction Type N/A
The following dictionaries are available in the cab file, but do not contain code values. You can add codes for
these dictionaries manually in User Defined Codes Maintenance.

Comment
MXProdServ Product or Service Code Catálogo de productos / servicios c_ClaveProdServ
MXUOMCFDI Unit of Measure for CFDI Catálogo de unidades de medida c_ClaveUnidad
para los conceptos en el CFDI
MXCountry Country Code Catálogo de países c_Pais
You can take the values from corresponding catalogs on the following web site: http://www.sat.gob.mx.
Menu Path: System Management > Solution Management > Solution Workbench
Load User Defined Codes
1. Navigate to Solution Workbench.

Menu Path: System Management > Solution Management > Solution Workbench
2. From the Actions menu, select the Install Solution command.

The Install Solution window displays.
3. Click the Solution File button and navigate to the Epicor ERP directory, and then to the <Epicor install
directory>server/CSF/MX and locate the MXSATCatalogs_Customer Solution_3.2.400.0.cab file.
4. Select the Only Target Current Company check box.
5. Click Install.
6. Exit Solution Workbench.
Epicor ERP | 10.2.400 11

User Defined Codes Maintenance
Use User Defined Codes Maintenance to add user-defined codes for SAT payment methods.
You can enter any optional codes in this program along with the codes mentioned in the following topics. You
may need to specify such codes, for example, when dealing with multiple payments. It is your responsibility to
enter correct codes as entered codes are not validated in Epicor ERP.
Add UD Codes to MXProdServ Code Type
1. Navigate to User Defined Codes Maintenance.

Menu Path: System Setup > System Maintenance > User Codes
2. Click the Code Type ID button to search for and select MXProdServ.
3. Navigate to the Codes sheet.
4. From the New menu, select New UD Code.
5. In the Code field, enter the code ID.
6. In the Description field, enter the code description.
7. Click Save.
For information about codes and their descriptions, refer to the Catálogo de productos / servicios catalog on
the following web site: http://www.sat.gob.mx.
Add UD Codes to MXUOMCFDI Code Type

2. Click the Code Type ID button to search for and select MXUOMCFDI.
7. Click Save.
For the information about codes and their descriptions refer to the Catálogo de unidades de medida para
los conceptos en el CFDI catalog on the following web site: http://www.sat.gob.mx.
Add UD Codes to MXCountry Code Type

12 Epicor ERP | 10.2.400

2. Click the Code Type ID button to search for and select MXCountry.
7. Click Save.
For the information about codes and their descriptions refer to the Catálogo de países catalog on the following
web site: http://www.sat.gob.mx.
Tax Type Maintenance
Use the Tax Type Maintenance program to define the tax types needed for the tax reports.
Mexico Fields
Tax Type Maintenance

Category
Specifies the tax type category for Mexico to display correctly classified values in the DIOT report. Options include:
• General
• Border
• Import
Factor Type
Specifies a sales tax factor type for digital tax receipts. The field accepts values from the MXFactType dictionary.
Tax Type
Specifies a sales tax type for digital tax receipts. The field accepts values from the MXTaxType dictionary. Options
include:
• IVA
• ISR
• IEPS
Create Tax Type Codes
1. Navigate to Tax Type Maintenance.

Menu Path: Financial Management > Accounts Payable > Setup > Tax Type
2. From the New menu, select New Tax Type Code.
Epicor ERP | 10.2.400 13

3. Navigate to the Mexico sheet and specify a tax type category in the Category field.
4. In the Tax Type field, select a required tax type and in the Factor Type field, select a required factor type.
5. Click Save.
6. Exit Tax Type Maintenance.
Journal Code Maintenance
Use the Journal Code Maintenance program to define codes used to group journals associated with posting
processes.
Use the Mexico sheet to select a type of transaction assigned to the selected code.
Mexico Fields
Journal Code Maintenance

Policy
Specifies a type of transaction. Options include:
• Income
• Expenses
• Journal
Create a Journal Code
To create a journal code:
1. Navigate to Journal Code Maintenance.

Menu Path: Financial Management > General Ledger > Setup > Journal Code
2. Click New.
3. In the Journal Code field, enter a value to identify the code to internal processes.
4. Enter other required information.
5. Navigate to the Mexico sheet.
6. In the Policy field, select a transaction type.
7. Click Save.
14 Epicor ERP | 10.2.400

General Ledger Account Maintenance
Use the General Ledger Account Maintenance program to specify a concept for the GL account. This concept
is defined by the Account Catalog published by SAT for Electronic Accounting Reports.
Mexico Fields
General Ledger Account Maintenance

Concept
Specifies a concept for the selected GL account.
Specify a Concept
To specify a concept for the GL account:
1. Navigate to General Ledger Account Maintenance.

Menu Path: Financial Management > General Ledger > Setup > General Ledger Account
2. In the Chart of Accounts field, select a COA.
3. Click the GL Account... button to select a GL account.
5. In the Concept field, enter an appropriate value.
6. Click Save.
Electronic Interface Maintenance
Use Electronic Interface Maintenance to set up the required electronic interfaces.

You can set up the following interfaces:
• An interface for modifying an electronic XML file before sending it to PAC for stamping
• An interface for electronic funds transfer (EFT) for the .txt file created from the Monthly Report of Receipts
Issued process
Set Up Electronic Interface for Modifying an Electronic XML file
1. Navigate to Electronic Interface Maintenance.

Menu Path: Financial Management > Accounts Payable > Setup > Electronic Interface
2. From the New menu, select New Interface.
3. In the Interface name field, enter an appropriate name.
Epicor ERP | 10.2.400 15

For example, enter Customized Interface.
4. In the Type field, select Digital Tax Receipt.
5. Click the Program button and select the

Erp\EI\MXGenCustomDigitalTaxReceipt\MXGenCustomDigitalTaxReceipt.cs file from the list. Click
OK.
6. In the Description field, enter a description.

For example, enter Customized Interface.
7. Click Save.
Note When modifying an electronic XML file, this electronic interface uses the MXLoadComprobante.cs
component located in the \server\Erp\EI\MXLoadComprobante folder.
Supplier Maintenance
Use the Supplier Maintenance program to create supplier records and to assign retention and TAR codes to
the supplier record.
If the name of the supplier you create consists of more than 50 characters, use the Legal Name field on the
Supplier > Address sheet in Supplier Maintenance to enter such a name. If you populated both the supplier
name and supplier legal name fields when creating a supplier record, the application pulls the supplier's legal
name from the record and adds it to the DIOT Report MX (review the Reports > DIOT Report MX topic of this
guide). If the supplier's legal name is empty, the supplier name is added to the report instead.
Retention codes provided by SAT are used to classify different reasons for withholding tax specific to Mexico. If
a supplier has a retention code, it is used to assign a retention code to the AP invoice where these taxes are
applied. Otherwise, you can enter it in the AP Invoice Entry program. When you print a Withholding Tax Certificate
MX report, an XML file with the name including this retention code is generated.
Menu Path: Financial Management > Accounts Payable > Setup > Supplier
Mexico Fields

DIOT Transaction Type

Specifies a DIOT transaction type.
Retention Code
Specifies a retention code.
TAR Code
Specifies a TAR code that is used to define the location where DIESEL was purchased. The value must be numeric
and consist of three characters taken from a catalog published by SAT.
16 Epicor ERP | 10.2.400

Bank/Remit To-Mexico Fields


SAT Code
Specifies a SAT code for the bank per published catalog.
Payment Method Maintenance
Use the Payment Method Maintenance program to specify types of payments applied to digital tax receipts
and to enter SAT codes.
Use the Mexico sheet to enter Mexico-specific information.
Mexico Fields
Payment Method Maintenance

Form of Payment...
Specifies a code and description of the form of payment.
Payment Method (SAT)

Specifies a SAT payment method. Options include:
• PPD - Pago en parcialidades o diferido
• PUE - Pago en una sola exhibición
Require Bank Reconciliation

When selected, this check box indicates that the payment or cash receipt needs to wait for bank reconciliation
to consider that income or deduction as effectively received or paid.
Create a Payment Method
1. Navigate to Payment Method Maintenance.

Menu Path: Financial Management > Accounts Payable > Setup > Payment Method
2. Click New.
3. In the Payment Method... field, enter a payment method name.
4. In the Scope field, select a scope for the method.
Epicor ERP | 10.2.400 17

5. In the Pay Method Type field, select a method type.
7. Select the Require Bank Reconciliation check box in the Income Tax section, if required.
8. In the Payment Method (SAT) field, select a required value. Payment methods are now mandatory during
creation of AR invoice.
9. Click the Form of Payment button to search for and select a form of payment. Click OK.
10. Click Save.
11. Exit Payment Method Maintenance.
Bank Account Maintenance
Use Bank Account Maintenance to create a bank account with SAT code, used in electronic accounting.
After creating a bank account as described in ERP Application Help, navigate to the Mexico sheet and select a
SAT code for this account.
Menu Path: Financial Management > Accounts Payable > Setup > Bank Account
Mexico Fields
Bank Account Maintenance

SAT Code
Specifies a SAT code per published catalog for Electronic Accounting reports.
Country Maintenance
Use the Country Maintenance program to set up the DIOT country code and External Country Code for Mexico.
Mexico Fields
Country Maintenance

DIOT Country Code

Specifies the DIOT country code.
External Country Code

Specifies an external country code.
18 Epicor ERP | 10.2.400

Set Up a Country
1. Navigate to Country Maintenance.

Menu Path: Financial Management > Accounts Payable > Setup > Country
2. Click Country and select Mexico.

Note Review the Country topics in the Application Help for information on setting up a country
code for Mexico if one does not exist.
4. In the DIOT Country Code field, enter a country code.
5. In the External Country Code field, select an external country code.

Note External Country Code is mandatory.
6. Click Save.
7. Repeat the steps 2 through 5 for each country you plan to use.
8. Exit Country Maintenance.
Setup - Digital Tax Receipt
Use the Setup - Digital Tax Receipt topics to complete required localization tasks for setting up the Digital Tax
Receipt functionality or correcting the existing Digital Tax Receipt settings after migration from Epicor 9.05.702a
to Epicor 10.
Besides the setup topics listed under this section, you must also complete setup tasks in the following programs:
• Payment Method (SAT) Maintenance
• Digital Certificate Store
• PAC Configuration Maintenance
• Company Maintenance
• GL Transaction Type Maintenance
• Tax Regime Maintenance
• Lot Number Entry
• Site Maintenance
• Unit of Measure Maintenance
• Customer Maintenance
• Miscellaneous Charge Maintenance
• Part Maintenance
Epicor ERP | 10.2.400 19

Migration from Epicor 9 to Epicor ERP 10

If you are migrating from Epicor 9 to Epicor ERP 10, pay special attention to correct naming and namespace of
the MXCustomPAC.dll component and to the referenced DLL used when setting up the Digital Tax Receipt
functionality.
The target .NET Framework for the MXCustomPAC.dll file must be .NET Framework 4.5.2.
Develop the MXCustomPAC.dll File

If you want to use a custom Authorized Certification Provider, you need to develop an external .NET component.
This component named MXCustomPAC.dll is required to implement connection to the selected PAC. The
MXCustomPAC.dll file is an external component that needs to be developed by users or contracting organizations.
Epicor ERP only provides the ability to plug in this component into the CFDI flow.
You need to save this file developed to work with a custom Authorized Certification Provider into the following
folder with the following filename: ..[Epicor Root]\Server\Assemblies\MXCustomPAC.dll.
This component must reference Erp.Internal.Lib.MXDigitalReceiptsLib.dll and implement the
Erp.Internal.Lib.PACAdapters.IPACAdapter2 interface. The MXCustomPAC component must implement at least
the Connect() and CertifyDigitalReceipt(ref ComprobanteBase cfdi, string outputPat
h, bool mxDebugMode = false) methods.
• The Connect method establishes connection to selected PAC and sets the IsConnect property as true on
a successful connection.
• The CertifyDigitalReceipt method receives the ComprobanteBase object that was created by
Epicor.Mfg.CSF.MXDigitalReceiptsLib.dll. This object calls a corresponding PAC method to certify created XML
and processes the response from PAC. This method should update the ComprobanteBase object with the
Complemento.TimbreFiscalDigital element if certification is completed successfully or return PACException in
case of failure.
To find the MXCustomPAC example developed for Custom Interfactura Certification Provider, navigate to:
..[EpicorRoot]\server\CSF\MX\MXCustomPACAdapter.
Create a Digital Tax Receipt Document Type

To create a document type for digital tax receipts, complete the following steps.
1. Navigate to Document Type Maintenance.

Menu Path: System Management > Document Management > Document Type Maintenance
2. Click New.
3. In the Type ID field, enter an identifier, and in the Description field, enter a description, for example,
Digital Tax Receipts.
4. In the Storage Type field, select File System Document.
5. In the Base URL field, enter a path where you want your documents to be saved.
These documents will be the generated invoice XML files and, if you use Digital Tax Receipts over the Internet
(CFDI), the generated image files for bar codes.
Note The selected path should be an existing location on your server. Verify the SQL Server Reporting
Services account has read permissions for this folder.
6. Select the Receipt check box.
20 Epicor ERP | 10.2.400

7. Click Save.
The Digital Tax Receipt document type will be required when loading certificates in Company Configuration.
If you want to use a custom PAC adapter, create an electronic interface as described in the Electronic Interface
Maintenance > Set Up Electronic Interface for Modifying an Electronic XML file topic.
Digital Certificate Store
Use the Digital Certificate Store program to load invoicing certificates.

Important It is required to load two sets of certificates. One of the sets is required for SAT, while the
other is required for Interfactura. Therefore, you need to perform the process described later twice - one
for each of the certificate sets.
Menu Path: System Setup > Company/Site Maintenance > Digital Certificate Store
Load a Certificate
To load a certificate, complete the following steps.
1. Navigate to Digital Certificate Store.

Menu Path: System Setup > Company/Site Maintenance > Digital Certificate Store.
2. Click New.
3. Navigate to the Load Certificate sheet.
4. Click Browse... next to the Certificate (*.cer, *.crt, *.pfx, *.p12) field to specify a path to the *.cer, *.crt,
*.pfx, or *.p12 files.
5. Click Browse... next to the Private Key (*.key, *.pfx, *.p12) field to specify a path to the *.key, *.pfx,
or *.p12 file.
Note If you are importing a Digital Seal Certificate (SAT), this step is required. If you are importing a
Connection Certificate (Interfactura), this step is optional.
6. In the Key Password field, enter the password for the private key.
Note If you are importing a Digital Seal Certificate (SAT), this step is required. If you are importing a
Connection Certificate (Interfactura), this step is optional.
7. Click Save.
8. Navigate to the Details sheet.
9. Review the certificate details.
10. Click Save.
If you need to delete an existing certificate, select the certificate in the tree view and click Delete on the Standard
toolbar.
Epicor ERP | 10.2.400 21

PAC Configuration Maintenance
Use PAC Configuration Maintenance to set up PAC (Authorized Certification Provider) details.
Menu Path:System Setup > Company/Site Maintenance > PAC Configuration MX
Detail Fields

Certificate
Specifies an X509 certificate code.
PAC Code
Specifies the PAC code description.
PAC Code...
Click this button to search for existing records. This search program retrieves the record type displayed on the
button label.
Target URL
Specifies the target URL. For example, for INTERFACTURA PAC, the URL is https://pruebasproducto.interfactura.
com/TimbreServicios/TimbreServicios.asmx.
List Fields

Certificate
Specifies the X509 certificate code.
PAC Code
Specifies the PAC code. Options to be entered in this field are:
• INTERFACTURA
• CUSTOM
Target URL
Specifies the target URL.
22 Epicor ERP | 10.2.400

Configure PAC
1. Navigate to PAC Configuration Maintenance.

Menu Path:System Setup > Company/Site Maintenance > PAC Configuration MX
2. Click New.
3. In the PAC Code field, enter one of the following PAC codes.
• INTERFACTURA
• CUSTOM
4. In the Target URL field, enter the URL required to connect to the PAC.
5. In the Certificate field, select an existing Connection Certificate code (Interfactura Certificate Code). Review
the Digital Certificate Store topic for information on entering certificate codes.
6. Click Save.
Company Configuration
Use Company Configuration to set up digital tax receipts for Epicor ERP.
Use the Modules > All Modules > Localization > Digital Tax Receipt sheet to enter digital tax receipt details.
Mexico Fields
Company Configuration

Authorized Certification Provider

Specifies a PAC code of certification provider. This field is available if the Digital Receipt Type field is set to
Digital Tax Receipts over the Internet (CFDI).
Certificate
Specifies an X509 certificate code.
Debug Mode
Select this check box to save additional data for debugging purposes. Two files are saved to the directory defined
in Document Type Maintenance where XML files are saved.
Digital Tax Receipt Type

Specifies a digital tax receipt type. Options include:
• Digital Tax Receipts over Internet (CFDI)
Epicor ERP | 10.2.400 23

• Disabled - CFDI is not generated. If this option is selected, the Fiscal Folio (UUID) field on the Header >
Mexico sheet in AR Invoice Entry becomes available and you can enter the UUID of the related CFDI.
Document Type
Specifies a document type set up in Document Type Maintenance.
Electronic Interface
Specifies an electronic interface used to modify the Digital Tax Receipt XML files.
Issuing Place
Specifies the issue place for digital tax receipts.
Locality Code
Specifies a locality code.
Municipio Code
Specifies a municipio code.
Use Site on Expedido En Address

When selected, this check box indicates that site information is included in the Digital Tax Receipt xml file and
SAT Report.
Set Up Digital Tax Receipts

To set up digital tax receipts to work with Epicor ERP, complete the following steps.
1. Navigate to Company Configuration.

2. Make sure that correct information is entered in the Federal ID, Tax ID, and Tax Liability fields.
Important The Tax ID must match the Tax ID of the certificate provided to you by SAT.
3. If you plan to use the International Trade CFDI Supplement functionality, you should fill out Company Address
fields State, Postal Code, and Country according to catalogues Catálogo de entidades o estados, Catálogo
de códigos postales, and Catálogo de países on the following web site: http://www.sat.gob.mx.
4. Navigate to the Modules > All Modules > Localization > Mexico sheet.
5. From the Digital Tax Receipt Type list, select a digital tax receipt type.
6. From the Authorized Certification Provider list, select a certification provider code. Review the PAC
Configuration Maintenance topic for information on entering provider codes.
7. From the Certificate list, select a Digital Seal Certificate code (SAT Certificate code). Review the Digital
Certificate Store topic for information on entering certificate codes.
24 Epicor ERP | 10.2.400

8. From the Document Type list, select a document type. Review the Create a Digital Tax Receipt Document
Type topic for information on entering document types.
9. If you want to modify the Digital Tax Receipt XML files, in the Electronic Interface field, select an electronic
interface. Otherwise, leave the field blank.
Review the Electronic Interface Maintenance > Set Up Electronic Interface for Modifying an Electronic
XML file section for the information about the electronic interface.
10. In the Issuing Place field, enter a required value.
11. In the Locality Code and Municipio Code fields, enter respective codes, if required.
12. If needed, select the Use Site on Expedido En Address check box to include site information in the Digital
Tax Receipt xml file and SAT Report.
13. Select the Debug Mode check box to save additional data for debugging purposes.
When this check box is selected, two files are saved to the directory defined in Document Type Maintenance
where xml files are designated to be saved.
14. Click Save.
15. Exit Company Configuration.
Tax Regime Maintenance
Use Tax Regime Maintenance to specify tax regimes for processing digital tax receipts. You can add multiple
tax regimes.
Menu Path: Financial Management > Accounts Receivable > Setup > Tax Regime MX
Detail Fields

Tax Regime
Specifies a tax regime name.
Default
When selected, this check box indicates that this tax regime is the default one.
Description
Specifies a tax regime description.
Tax Regime...
button label.
Epicor ERP | 10.2.400 25

List Fields

Tax Regime
Specifies the tax regime name.
Default
Indicates that the selected tax regime is default.
Description
Specifies a tax regime description.
Specify a Tax Regime
1. Navigate to Tax Regime Maintenance.

Menu Path: Financial Management > Accounts Receivable > Setup > Tax Regime MX.
2. Click New.
3. In the Tax Regime field, enter a tax regime name.
4. In the Description field, enter a tax regime description.
5. Select the Default check box to indicate that this is the default regime.
6. Click Save.
Lot Number Entry
Use Lot Number Entry to add custom import information to lot-tracked inventory parts.
For a lot-tracked part, enter information in the following fields on the Mexico sheet.
• Import Date - date of import
• Import Location- port of entrance
This will control which customs date and port of entrance that will be referenced for the customer shipment on
the digital tax receipt.
Menu Path: Material Management > Inventory Management > Setup > Lot
26 Epicor ERP | 10.2.400

Mexico Fields
Lot Number Entry

Import Date
Specifies the date of import.
Import Location
Specifies the port of entrance.
Site Maintenance
Use Site Maintenance to assign an issuing place to a site record for use with digital tax receipts.
On the Detail > Mexico sheet, enter a required value in the Issuing Place field. If you plan to use the International
Trade CFDI Supplement functionality, you should fill out Site Address fields State, Postal Code, and Country
according to catalogues Catálogo de entidades o estados, Catálogo de códigos postales, and Catálogo de países
on the following web site: http://www.sat.gob.mx.
Menu Path: Material Management > Inventory Management > Setup > Site Maintenance
Mexico Fields
Site Maintenance

Issuing Place
Specifies the issue place for digital tax receipts (lugar de expedición).
Note For information about valid codes, refer to the Catálogo de municipios catalog on the following
web site: http://www.sat.gob.mx.
Unit of Measure Maintenance
Use Unit of Measure Maintenance to define customs UOM. The application uses it when generating customs
information supplement to electronic invoices.
Menu Path: Material Management > Inventory Management > Setup > UOM
Mexico Fields
Unit of Measure Maintenance

Epicor ERP | 10.2.400 27

Customs UOM
Specifies the customs unit of measure per SAT catalog.
SAT Code
Specifies a SAT code and description. This field accepts values from the MXUOMCFDI user defined dictionary.
SAT Code...
button label.
Miscellaneous Charge Maintenance
Use Miscellaneous Charge Maintenance to create miscellaneous charges that you can later select from other
programs.
Menu Path: Financial Management > Accounts Receivable > Setup > Miscellaneous Charge
Mexico Fields
Miscellaneous Charge Maintenance

Product or Service Code

Specifies a product or service code and full description. The field is required and accepts values from the
MXProdServ dictionary.
Product or Service Code...

button label.
Part Maintenance
Use Part Maintenance to set up product or service codes for parts used in digital tax receipts.
Menu Path: Material Management > Inventory Management > Setup > Part
Mexico Fields
Part Maintenance

Customs Duty
Specifies a customs duty code.
28 Epicor ERP | 10.2.400

Get Customs UOM from

Defines the UOM option that will be used to generate Digital Tax Receipt XML for Customs. The system uses the
selected option to determine UOM code and the specified value to recalculate the amount and price for Customs.
The available options include:
• Sales UOM
• Unit Net Weight
• Unit Gross Weight
• Unit Net Volume
Note To enter values and UOM codes for these options, navigate to the Part > Detail sheet. If Sales UOM
option is selected no recalculation occurs.

button label.

Specifies a product or service code and full description. The field accepts values from the MXProdServ dictionary.
Customer Maintenance
Use Customer Maintenance to add specific information to a customer record which is used with digital tax
receipts.
Menu Path: Financial Management > Accounts Receivable > Setup > Customer
Mexico Fields

Account Number
Specifies an account number for digital tax receipts. This number will be used during AR invoices creation.
General Public
When selected, this check box indicates that the customer's invoices are considered as global invoices.
Legal Name
Specifies the customer's legal name.
If the name of the customer you create consists of more than 50 characters, use this field to enter such a name.
If you populated both the Customer Name and customer Legal Name fields when creating a customer record,
the application pulls the customer legal name from the record and uses during creation of a digital tax receipt
and generation of an Original String (cadena original). If the customer legal name is empty, the application uses
the customer name instead.
Epicor ERP | 10.2.400 29

Municipio
Specifies the issuing place (lugar de expedición) for digital tax receipts.
Type of Purchase
Specifies a type of purchase code and description. The field accepts values from the MXPurType dictionary.
Type of Purchase...
button label.
Ship To-Mexico Fields


Federal ID
Specifies a Ship To identification number or the fiscal registration number from the customer's country of residence.
The field is used for foreign customers.
Municipio
Specifies an issuing place (lugar de expedición).
Mexico Fields

RFC
Specifies a tax ID.
SAT Code
Specifies a SAT code ID.
Set Up a Customer
1. Navigate to Customer Maintenance.

Menu Path: Financial Management > Accounts Receivable > Setup > Customer
2. From the New menu, select New Customer.
3. On the Detail sheet, enter appropriate details.
30 Epicor ERP | 10.2.400

5. In the Digital Tax Receipt pane, enter customer information related to digital tax receipts.
6. In the Official Registration pane, enter the customer legal name.
7. Navigate to the Billing > Detail sheet. The address filled on the Bill To sheet will be used for digital tax
receipts.
8. In the Tax ID field, enter a required value if you have not already done so during the installation process.
Important The Mexican Tax Agency (SAT) recommends using a Tax ID of XEXX010101000 for foreign
customers.
9. Navigate to the Ship To > Mexico sheet.
10. Enter information related to digital tax receipts.
11. Navigate to the Banks > Mexico sheet.
12. In the RFC field, enter a tax ID used for digital tax receipts.
13. In the SAT Code field, enter a required SAT code ID.
14. Click Save.
15. Exit Customer Maintenance.
General Operations
Use the General Operations topics for additional information specific to the Mexico localization.
Note Refer to the Setup topics to configure the Mexico CSF features before completing the procedures
in the General Operations topics.
The General Operations topics are separated by the following functions:

• Mexico Localization
• Digital Tax Receipt
The procedures that follow only reflect changes specific to Mexico. Refer to the Epicor Application Help in the
main module for detailed information about the use of the standard programs.
General Operations - Mexico Localization
Use the General Operations - Mexico Localization topics for additional user information specific to the Mexico
localization.
Once you have completed the Setup procedures, you will now be able to complete the following tasks related
to the Mexico localization:
• Enter tax information in Asset Management for your assets using the codes you created.
• Record payments to suppliers in AP Invoice Entry, using the tax destinations and categories you created.
Epicor ERP | 10.2.400 31

• Use AP Payment Entry to enter bank and customer tax information.

• Use Supplier Tracker and Supplier Display to view supplier records with Mexico-specific details.
Asset Maintenance
Use the Asset Maintenance program to enter and update records for fixed assets.
After you activate and set up Mexico CSF, the Mexico sheet displays in the Asset Maintenance program. Use
this sheet to enter tax information for your asset.
Add Tax Information to an Asset Record

To add tax information to an asset record:
1. Navigate to Financial Management > Asset Management > Setup > Asset.
2. From the New menu, select New Asset.
3. In the Asset Number field, enter an asset number. In the Description field, enter the asset description.
4. In the Asset Group field, select an asset group.
5. Enter required information in other fields.
6. Navigate to the References sheet.
7. Click Supplier ID to search for and select a supplier.
8. Click Invoice to search for and select an invoice.
10. In the Annual Depreciation % field, enter annual depreciation.
11. In the Asset Life Year field, enter a required value.

The other fields are calculated automatically.
12. Click Save.
AP Payment Entry
Use the AP Payment Entry to pay AP invoices through check or electronic payments.
If you enter an electronic AP payment and the supplier is not specified, the information about bank account,
bank identifier, and RFC (tax registration number of the supplier) entered on the Payment > Mexico sheet is
verified.
Before saving a payment, if a supplier was not specified, the following validations are performed:
• If the payment type is other than Check (CheckHed.PMUID-> PayMethod.MXSATCode <> 02), the Bank
Account, Bank Identifier, and RFC fields cannot be empty. If the fields are empty, an error message displays
and the payment cannot be saved.
• If the payment type is Check (CheckHed.PMUID->PayMethod.MXSATCode = 02), the RFC field cannot be
empty. If the field is empty, an error message displays and the payment cannot be saved.
32 Epicor ERP | 10.2.400

Menu Path
Navigate to this program from the Main Menu:
• Financial Management > Accounts Payable > General Operations > Payment Entry
• Financial Management > Cash Management > General Operations > Payment Entry
Mexico Fields
AP Payment Entry

Bank Account
Specifies the supplier's bank account. If Supplier ID is not specified, the field is available for payments with a type
different from Check. In other cases, the field is disabled.
Bank Identifier
Specifies the supplier's bank identifier. If Supplier ID is not specified, the field is available for payments with a
type different from Check. In other cases, the field is disabled.
RFC
Specifies a tax payer ID (RFC). If Supplier ID is not specified, the field is available for any type of payments. In the
other case, the field is disabled.
Enter Payment Information Using Existing Supplier
To enter payment information using an existing supplier:
1. Navigate to AP Payment Entry.

Menu Path: Financial Management > Accounts Payable > General Operations > Payment Entry
2. From the New menu, select New Group to create a new group.
3. In the Group field, enter a group ID.
4. In the Bank Account field, select a bank account.
5. In the Payment Method field, select an electronic payment method.
6. Click Save.
7. From the New menu, select New Payment.
8. Click Supplier... and select the supplier.
9. Click Save.
Epicor ERP | 10.2.400 33

Enter Payment Information Using One-Time Supplier
To enter payment information using one-time supplier:
1. Navigate to AP Payment Entry.

Menu Path: Financial Management > Accounts Payable > General Operations > Payment Entry
2. From the New menu, select New Group to create a new group.
3. In the Group field, enter a group ID.
4. In the Bank Account field, select a bank account.
5. In the Payment Method field, select payment method.
6. Click Save.
7. From the New menu, select New Payment.
8. In the Name and Address fields, enter one-time supplier information.
9. Click Save.
10. Navigate to the Payment > Mexico sheet.
11. In the Bank Account field, specify the supplier's bank account.
12. In the Bank Identifier field, specify the supplier's bank identifier.
13. In the RFC field, specify the supplier's RFC (tax registration number).
14. Click Save.
Supplier Tracker
Use Supplier Tracker to review supplier records with Mexico-specific details.
Menu Path
• Executive Analysis > Trackers > Supplier Tracker
• Financial Management > Accounts Payable > General Operations > Supplier Tracker
• Material Management > Purchase Contracts Management > General Operations > Supplier Tracker
• Material Management > Purchase Management > General Operations > Supplier Tracker
• Material Management > Supplier Relationship Management > General Operations > Supplier Tracker
• Production Management > Quality Assurance > General Operations > Supplier Tracker
34 Epicor ERP | 10.2.400

Mexico Fields
Supplier Tracker


Retention Code
TAR Code
Supplier Display
Use Supplier Display to review current information about selected supplier records with Mexico-specific details.
Menu Path
• Executive Analysis > Trackers > Supplier Display
• Financial Management > Accounts Payable > General Operations > Supplier Display
• Material Management > Purchase Contracts Management > General Operations > Supplier Display
• Material Management > Purchase Management > General Operations > Supplier Display
Mexico Fields
Supplier Display


Retention Code
TAR Code
Epicor ERP | 10.2.400 35

General Operations - Digital Tax Receipt
Use the General Operations - Digital Tax Receipt topics for additional information specific to the Mexico
digital tax receipts.
Note Refer to the Setup topics to configure the Mexico CSF features before completing the procedures
in the General Operations topic.
Once you have completed the Setup tasks, you are now able to complete the following tasks related to digital
tax receipts:
• Enter information into various programs required for digital tax receipts
• Create a digital tax receipt invoice using AR Invoice Entry
• Cancel a digital tax receipt invoice using AR Invoice Entry
• Review the status, including error code details, of a digital tax receipt invoice and cash receipt using Review
Journal
• Print the digital tax receipt of a posted AR invoice using AR Invoice Tracker
• Create a cash receipt using Cash Receipts Entry
• Print the digital tax receipt of a posted cash receipt using Cash Receipt Tracker
AR Invoice Entry
Use AR Invoice Entry to create an invoice to bill a customer. After you activate and set up the Mexico CSF, you
can provide a printed invoice that includes required digital tax receipt information.
You must select the method of payment that applies to a digital tax receipt. On the Mexico > Detail sheet,
select one of the following options from the Payment Method (SAT) field:
• Pago en una sola exhibición (default)
• Pago en parcialidades o diferido
All amounts in CFDI xml document are expressed in the invoice currency. To provide it, the xml documents have
a node indicating the base currency to invoice currency exchange rate.
The New Advance Billing and New Advance Billing Credit Memo commands on the New menu are disabled
for the Mexico CSF. According to SAT requirements, creation of advance billing and advance billing credit memos
in AR Invoice Entry must not be supported for Mexican functionality with CFDI 3.3.
Review the Application Help and Field Help for detailed non-country specific information regarding AR Invoice
Entry.
Menu Path: Financial Management > Accounts Receivable > General Operations > Invoice Entry
Customer Legal Name

If the customer legal name is populated in the customer record, the application pulls it from the record and uses
during creation of a digital tax receipt and generation of an Original String (cadena original). This name is specified
in Customer Maintenance (the Legal Name field on the Mexico sheet). Refer to the Setup > Digital Tax Receipt
> Customer Maintenance topic.
36 Epicor ERP | 10.2.400

Header-Mexico Tab
Header > Mexico
The Header > Mexico tab contains the Detail, Export Data, and Ref.Invoices sheets where you enter
Mexico-specific information for AR invoices.
Detail Fields
AR Invoice Entry

Cancellation ID
Specifies the cancellation ID of the invoice returned by SAT. This value is the same for both original and cancellation
invoice.
Cancellation Mode
Specifies a cancellation mode for credit memos. Options include:
• Folio Cancellation Request (default) - Credit Memo generates a cancellation request (scenario 1)
• Digital Tax Receipt Generation - Credit Memo generates a digital tax receipt without a cancellation request
(scenario 2)
Cancellation Status
Specifies the cancellation status of the invoice returned by SAT. The values include:
• Cancelado (Cancelled) - Invoice has been successfully cancelled by SAT.
• EnProceso (In Progress) - Invoice has not been approved or rejected yet.
• Rechazado (Rejected) - Invoice cannot be canceled.
• Error - There was an error during the cancellation process.
• Desconocido (Unknown) - There are no events in the cancellation invoice flow so cancellation request needs
to be sent again.
Confirmation Code
Specifies confirmation code for invoices in currencies with exchange rate higher or lower than the allowed
maximum or minimum.
Domestic Transfer
Indicates if this is a domestic transfer invoice. It is a special invoice with unit price of 0 and the total amount of
0, which is created to advise the detail of the amount and products being moved. For example, a company is
moving products from one plant to another, but the ownership remains as is.
This check box is available only for miscellaneous invoices.
Fiscal Folio (UUID)
Specifies the UUID of the related CFDI. This field is available if the Digital Tax Receipt Type parameter in
Company Configuration is set to Disabled.
Folio
Specifies a folio.
Specifies a form of payment. Options include:
Epicor ERP | 10.2.400 37

• Pago en parcialidades o diferido - the information about the payment number is taken from the payment
method settings. Review the Setup > Digital Tax Receipt > Payment Method Maintenance topic for details.
Serie
Specifies a serie.
Tax Regime
Specifies a tax regime.
The application displays the default tax regime specified for the company. For more information, review the
Setup > Digital Tax Receipt topic.
Type of Purchase
Specifies a purchase type. The field accepts values from the MXPurType dictionary.
Type of Purchase...
button label.
Export Data Fields

AR Invoice Entry

Customs Document Code
Specifies a customs document code. The field contains descriptions from the MXCustDoc user defined dictionary.
Incoterm
Specifies an Incoterm code. Incoterm is a series of international rules that define at which point the risks and
charges are transferred to the buyer. The field displays descriptions from the INCOTERM user defined dictionary.
The default value is taken from the shipment if it exists.
Moving Reason
Indicates that moving reason is required. When you select this check box, the drop-down list next to it becomes
available.
Moving Reason (Untitled)
Specifies a moving reason code and description. The field displays descriptions from the MXMoveReas user defined
dictionary.
Number of Reliable Exporter
Specifies a number of reliable exporter.
Operation Type
Specifies an operation type. The following options are available:
• Empty (default)
• 2 - Export - if this value is selected, other fields become available.
Origin Certificate
When selected, this check box indicates that an origin certificate exists.
Origin Certificate Number
Specifies an origin certificate number. The minimum length is six digits.
Owner External Country Code
38 Epicor ERP | 10.2.400

Specifies the owner's external country code. The field displays descriptions from the MXCountry user defined
dictionary.
Owner Fiscal Registration Number
Specifies the owner's fiscal registration number.
Ref.Invoices Fields
AR Invoice Entry

Apply Date
Specifies the apply date of the reference invoice.
Balance
Specifies the reference invoice balance in the document currency.
Credit Memo
Indicates if this is a credit memo.
Invoice
Specifies a reference invoice number.
Invoice Date
Specifies the date of the reference invoice.
Invoice Relation Type
Specifies a type of relation between invoices. The field accepts values from the MXRelType dictionary. If the
invoice has related Deposit Billings, the default value with the code 07 displays.
Invoices...
button label.
Type
Specifies a reference invoice type.
Mexico Fields
AR Invoice Entry

Customs Duty
Specifies customs duty information.
A full list of valid customs duty codes is available in Catálogo de fracción arancelaria on the following web
site: http://www.sat.gob.mx.
Epicor ERP | 10.2.400 39

Get Customs UOM from

Defines the UOM option that will be used to generate Digital Tax Receipt XML for Customs. The system uses the
selected option to determine UOM code and the specified value to recalculate the amount and price for Customs.
The default value for this field is defined in Part Maintenance.
The available options include:
• Sales UOM
• Unit Net Weight
• Unit Net Volume

Specifies a product or service code and full description. The field accepts values from the MXProdServ dictionary.

button label.
Create a Digital Tax Receipt AR Invoice
1. Navigate to AR Invoice Entry.

Menu Path: Financial Management > Accounts Receivable > General Operations > Invoice Entry
2. Click Group to select a group or create a new group.
3. Create a new invoice or select an existing one.
4. From the Payment Method list, specify the payment method.
5. Navigate to the Header > Mexico > Detail sheet.
6. In the Payment Method (SAT) field, select one of the options.
7. Click the Type of Purchase button to search for and select a type of purchase for the invoice.
8. In the Invoice Relation Type list, select a required value.
9. In the Confirmation Code field, enter a required value.
10. In the Tax Regime field, specify the required tax regime.
11. In the Fiscal Folio (UUID) field, enter the UUID of the related CFDI.
12. Click Save.
13. Remain in AR Invoice Entry.
40 Epicor ERP | 10.2.400

Enter Export Data for an AR Invoice
1. Navigate to the Header > Mexico > Export Data sheet.
2. In the Operation Type field, select 2 - Export Type.
3. In the Customs Document Code field, select A1 - IMPORTACION O EXPORTACION DEFINITIVA.
4. If the origin certificate exists, select the Origin Certificate check box.
5. In the Origin Certificate Number field, enter the certificate number.
6. In the Number of Reliable Exporter field, enter the reliable exporter's number.
7. In the Incoterm field, select an Incoterm code.
8. If a moving reason is required, select the Moving Reason check box and enter a value in the Moving
Reason field.
9. In the Owner Fiscal Registration Number field, enter a required value.
10. In the Owner External Country Code field, select a country code.
11. Click Save.
Add Invoice References to an AR Invoice
You can link the current AR invoices to several other AR invoices
1. Navigate to the Header > Mexico > Ref.Invoices sheet.
2. Click the Invoices button.
3. In the Accounts Receivable Invoice Search window that displays, select a required invoice and click OK.
The search window displays invoices that meet the following criteria:
• They belong to the same customer as the original invoice.
• They have the same currency as the original invoice.
• They are posted.
Tip You can select several invoices using the Ctrl or Shift key.
4. Click Save.
Create an Invoice Line
1. From the New menu, select New Line.
Epicor ERP | 10.2.400 41

2. On the Line > Detail sheet, enter line information.
3. Navigate to the Line > Mexico sheet.
4. In the Customs Duty field, enter customs duty information, if required.
5. The value in the Get Customs UOM from field defaults from the UOM specified for the invoiced part on
the Part > Detail > Mexico sheet in Part Maintenance. The system uses the selected UOM and the part
conversion factor to recalculate the amount in Sales UOM to amount in Customs UOM that you want to
be displayed in the digital tax receipt outgoing XML.
You can keep the default value or change it to one of the following:
• Sales UOM
• Unit Net Weight
• Unit Net Volume
6. Click the Product or Service Code button to select a required product or service code.
7. In the User Code Search window that displays, select a required code and click OK.
8. Click Save.
9. Exit AR Invoice Entry.
AR Invoice Posting
AR electronic invoices are posted according to the following rules.

• AR invoice is posted after an electronic invoice is accepted, in other words, a response with no error is received
from PAC.
• If an error occurs during XML generation, or a response from PAC contains errors, a new record is created in
Review Journal where the error text is displayed. Information about posting is also available in the System
Monitor.
• If an error occurs during posting, you should correct the invoice and then post it again. A new XML will be
generated.
Cancellation of Digital Tax Receipt AR Invoices
You can cancel digital tax receipt AR invoices using either or the following two scenarios.
1. Cancellation invoice (credit memo) does not generate DTR, cancellation request is sent. You can cancel
digital tax receipt AR invoices 72 hours after the original invoice was posted. For this purpose, you create
and post a cancellation invoice. After posting a cancellation invoice, the application generates a cancellation
request XML file and sends it to web service in the same way it is done during Digital Tax Receipt generation.
When the cancellation response is received, it is attached to the created credit memo and to the cancelled
invoice. If the response XML contains an error, the credit memo is not posted. You should post it one more
time until a successful response is received from the web service.
2. Cancellation invoice (credit memo) generates DTR, no cancellation request is created. For this purpose, you
create and post a cancellation invoice. After a cancellation invoice is posted, a Digital Tax Receipt is generated
and sent to web service.
42 Epicor ERP | 10.2.400

Use the Create Cancellation Invoice command from the Actions menu of AR Invoice Entry to directly cancel
a posted digital tax receipt AR invoice.
Cancel a DTR Invoice (Scenario 1)
1. From the Actions menu, select the Create Cancellation Invoice command. This action opens the Create
Cancellation Invoice program.
2. Click the Legal Number button.
3. In the Legal Number Search window that displays, search for and select the invoice that you want to cancel
and click OK.
4. From the Document Type field, select a document type configured for credit memo.
5. Click OK.
6. Click Yes in the confirmation window.
8. In the Cancellation Mode field, select Folio Cancellation Request.
9. Click Save.
10. Post the invoice.
The cancellation invoice is posted. You will receive a response from SAT with the cancellation ID and the status
of this invoice. If the status is Cancelado (Cancelled), the cancellation process has been successful. To manage
the unposted cancellation invoices with other statuses, use Review Journal.
You can review the status of the cancellation invoice on the Header > Mexico > Detail sheet in AR Invoice
Entry or AR Invoice Tracker and in Cancellation Invoice Status MX.
Cancel a DTR Invoice (Scenario 2)
1. From the Actions menu, select the Create Cancellation Invoice command. This action opens the Create
Cancellation Invoice program.
2. Click the Legal Number button.
3. In the Legal Number Search window that displays, search for and select the invoice that you want to cancel
and click OK.
4. From the Document Type field, select a document type configured for credit memo.
5. Click OK.
6. Click Yes in the confirmation window.
8. In the Cancellation Mode field, select Digital Tax Receipt Generation.
9. Click Save.
Epicor ERP | 10.2.400 43

10. Post the invoice.
Posted AR Invoice Update
Use Posted AR Invoice Update to review posted AR invoices. All invoice details displayed within this program
are read-only, because it is not possible to change AR invoices after XML has been sent to SAT.
On the Header > Mexico > Detail sheet, you can review the UUID of the CFDI specified in the AR Invoice Entry
program.
On the Header > Mexico > Export Data sheet, you can review the export data for posted invoices.
On the Header > Mexico > Ref.Invoices sheet, you can review reference invoices information.
On the Line > Mexico sheet, you can review the customs duty information.
Menu Path: Financial Management > Accounts Receivable > General Operations > Posted Invoice Update
Customer Shipment Entry
Use Customer Shipment Entry to specify an Incoterm code for a customer shipment.
Incoterm is a series of international rules that define at which point the risks and charges are transferred to the
buyer.
Use the Incoterm field on the Header > Mexico sheet to select an Incoterm code.
Menu Path: Material Management > Shipping / Receiving > General Operations > Customer Shipment Entry
AR Invoice Tracker
Use AR Invoice Tracker to retrieve and review AR invoice records with Mexico-specific details. All the fields in
AR Invoice Tracker are read-only.
Menu Path: Financial Management > Accounts Receivable > General Operations > Invoice Tracker
Header-Mexico Tab
Use the sheets under the Header > Mexico tab to review Mexico-specific information on AR invoices.
All the fields on the Detail, Export Data, Digital Tax Receipt, and Ref.Invoices sheets are read-only.
Detail Fields
AR Invoice Tracker

Cancellation ID
Specifies the cancellation ID of the invoice returned by SAT. This value is the same for both original and cancellation
invoice.
Cancellation Mode
Specifies a cancellation mode for the selected invoice or credit memo. Possible values:
• Folio Cancellation Request (default)
• Digital Tax Receipt Generation
44 Epicor ERP | 10.2.400

Cancellation Status
to be sent again.
Confirmation Code
Specifies confirmation code for invoices in currencies with exchange rate higher or lower than the allowed
maximum or minimum.
Domestic Transfer
Indicates if this is a domestic transfer invoice. It is a special invoice with unit price of 0 and the total amount of
0, which is created to advise the detail of the amount and products being moved. For example, a company is
moving products from one plant to another, but the ownership remains as is.
This check box can be selected only for miscellaneous invoices.
Folio
Specifies a folio.
Invoice Relation Type
Specifies a type of relation between invoices.
Specifies a form of payment. Possible values:
• Pago en parcialidades o diferido - the information about the payment number is taken from the payment
method settings.
Serie
Specifies a serie.
Tax Regime
Specifies a tax regime.
Type of Purchase
Specifies a purchase type.
Export Data Fields

AR Invoice Tracker

Customs Document Code
Specifies a customs document code.
Incoterm
Specifies an Incoterm code.
Moving Reason
Epicor ERP | 10.2.400 45

Indicates that moving reason is required.

Moving Reason (Untitled)
Specifies a moving reason code and description.
Specifies a number of reliable exporter.
Operation Type
Specifies an operation type.
Origin Certificate
When selected, this check box indicates that an origin certificate exists.
Specifies an origin certificate number.
Owner External Country Code
Specifies the owner's external country code.
Owner Fiscal Registration Number
Specifies the owner's fiscal registration number.
Digital Tax Receipt Fields

AR Invoice Tracker

Certificate SN
Specifies a certificate serial number.
Digital Seal
Specifies a digital seal.
Fiscal Folio (UUID)
Specifies a fiscal folio (UUID).
Original String
Specifies the original string.
SAT Certificate SN
Specifies a SAT certificate serial number.
SAT Seal
Specifies a SAT seal.
TFD Original String
Specifies a TFD original string.
Time Stamp
Specifies a time stamp in the YYYY-MM-DDTHH:MM:SS format.
46 Epicor ERP | 10.2.400

Ref.Invoices Fields
AR Invoice Tracker

Apply Date
Specifies the apply date of the reference invoice.
Balance
Specifies the reference invoice balance in the document currency.
Credit Memo
Indicates if this is a credit memo.
Inv Date
Specifies the date of the reference invoice.
Invoice
Specifies a reference invoice number.
Type
Specifies a reference invoice type.
View the Status of a Digital Tax Receipt AR Invoice
1. Navigate to Financial Management > Accounts Receivable > General Operations > Invoice Tracker.
2. In the Invoice field, enter the invoice number.
3. Navigate to the Header > Mexico > Digital Tax Receipt sheet.
The digital tax receipt results display, along with CFDI certification information.
The following digital tax receipt results are displayed:
• Certificate SN
• Digital Seal
• Original String
• Time Stamp
• Fiscal Folio (UUID)
• SAT Certificate SN
• SAT Seal
• TFD Original String

For the digital tax receipts, the following information displays:
• Serie
• Folio
• Payment Method (SAT)
• Type of Purchase
Epicor ERP | 10.2.400 47

• Invoice Relation Type

• Confirmation Code
• Domestic Transfer
The following information displays in the Tax Regime section:
• Tax Regime
The following information displays in the Cancellation section:
• Cancellation Mode
• Cancellation ID
• Cancellation Status
5. Review the following files that are available in Tree View Invoice Number > Attachments (2) > Digital Tax
Receipts (2) node.
• Digital Tax Receipt (XML file)
• QR Barcode (JPG file)
CFDI Digital Tax Receipt XML File Structure
The following table contains the structure of the CFDI Digital Tax Receipt XML file.
Node Name Attribute Name Value

<cfdi:Comprobante> xsi:schemaLocation http://www.sat.gob.mx/cfd/3
http://www.sat.gob.mx/sitio_internet/cfd/3/cfdv33.xsd
xmlns:xsi http://www.w3.org/2001/XMLSchema-instance
xmlns:cfdi http://www.sat.gob.mx/cfd/3
version Constant = 3.3
Serie InvcHead.MXSerie
Folio InvcHead.MXFolio
Fecha DTR creation timestamp. Current Date and Time in the format
YYYY-MM-DDThh:mm:ss.
Sello InvcHead.MXDigitalSeal
FormaPago
InvcHead.PMUID -> PayMethod.MXSATCode
The attribute is not created if
cfdi:Comprobante/@TipoDeComprobante = T.
NoCertificado InvcHead.MXCertificateSN
Certificado InvcHead.MXCertificate
CondicionesDePago InvcHead.TermsCode -> Terms.Description
1) cfdi:Comprobante/@TipoDeComprobante = "T"
or
48 Epicor ERP | 10.2.400


2) Invoice is a Global Invoice (Customer.MXGeneralPublic =
1).
SubTotal
Sum(ABS(InvcDtl.DocExtPrice)) +
Sum(ABS(InvcMisc.DocMiscAmt))
Descuento
Sum of {Line's Discount} for all invoice lines (InvcDtl).
Total
@subTotal - @descuento + {(InvcTax.CollectionType = 0) ->
Sum(ABS(InvcTax.DocTaxAmt))} - {(InvcTax.CollectionType =
1) -> Sum(ABS(InvcTax.DocTaxAmt))}
MetodoPago
InvcHead.MXPaidAs
TipoDeComprobante
IF Moving Reason is specified
OR
Transaction is a Domestic Transfer
THEN
Value = T (Traslado)
ELSE {IF NOT(Credit Memo) THEN Value = I (Ingreso); ELSE
Value = E (Egreso)}
LugarExpedicion The field depends on the value of the Use site en expedido
en address check box in Company Configuration (Modules
> All Modules > Localization > Digital Tax Receipts sheet).
• Company.MXMunicipio if the check box is clear
• Plant.MXMunicipio if the check box is selected
TipoCambio InvcHead.ExchangeRate
Moneda InvcHead.CurrencyCode -> Currency.CurrencyID
Confirmacion
InvcHead.MXConfirmationCode
The attribute is created only if the value <> Empty string
cfdi:Comprobante\ The node is created if:

cfdi:CfdiRelacionados
1. Invoice has linked Deposit Billing(s)
2. There is no linked Deposit Billing, but the invoice has

reference to other Invoice(s):
• InvcHead.InvoiceRef <> Empty string OR
Epicor ERP | 10.2.400 49


• There is at least one MXInvcRef record for the current
Invoice.
<cfdi:CfdiRelacionados> Specifies the information of related vouchers.

TipoRelacion InvcHead.MXInvoiceRelationType
Indicates the Relationship Type Code between this invoice
and the reference invoice.
cfdi:Comprobante/ Several nodes can be created:

cfdi:CfdiRelacionados/
1. If Deposit Billings are linked, then one node is created
cfdi:CfdiRelacionado for each Deposit Billing.
2. If no Deposit Billing is linked, then one node is created

for each referenced invoice:
• One node for referenced invoice if
InvcHead.InvoiceRef <> Empty string;
• One node for each MXInvcRef record corresponding
to the current Invoice.
<cfdi:CfdiRelacionado> Information about Deposit Billing or Referenced Invoice.

UUID
• In case of Deposit Billing:
InvcHead.MXFiscalFolio of Deposit Billing;
• In case of referenced Invoice:
• InvcHead.InvoiceRef -> InvcHead.MXFiscalFolio;
• InvcHead.InvoiceNum -> MXInvcRef.RefInvoiceNum ->
InvcHead.MXFiscalFolio.
<cfdi:Comprobante\
cfdi:Emisor>
Rfc Company.StateTaxID
Nombre Company.Name
RegimenFiscal InvcHead.MXTaxRegime
<cfdi:Comprobante\
cfdi:Receptor>
Rfc Customer.ResaleID
Nombre
Customer.LegalName; Customer.BTName if Legal Name is
empty.
50 Epicor ERP | 10.2.400


The attribute is not created in case of Global Invoice
(Customer.MXGeneralPublic = 1).
ResidenciaFiscal
Customer.BTCountryNum -> Country.MXExternalCode
The node is created if:
1. Customer.BTCountryNum -> Country.MXExternalCode

<> MEX and
2. Invoice is not a Global Invoice

NumRegIdTrib
Customer.FederalID
The node is created only if:
1. Customer.BTCountryNum -> Country.MXExternalCode

<> MEX and
2. Invoice is not a Global Invoice

UsoCFDI InvcHead.MXPurchaseType
<cfdi:Comprobante\
cfdi:Conceptos>
<cfdi:Comprobante\ Additional validation is performed to check if the current

Invoice Line should be shown or not in the XML:
cfdi:Conceptos\
If the Invoice Line is linked with Sales Order Line
cfdi:Concepto>
(InvcDtl.OrderNum <> Empty String AND InvcDtl.OrderLine
<> Empty String) THEN
1. IF linked Sales Order Line is a component of Sales Kit

(OrderLine <> KitParentLine in the OrderDtl row), THEN
corresponding Invoice Line is not shown. If such Invoice
Line has Tax Lines, then these Tax Lines (<Impuestos>
node) are shown as if they are linked to the parent
Invoice Line.
2. IF linked Sales Order Line is NOT a component of Sales

Kit (OrderLine = KitParentLine for the OrderDtl row),
THEN the Invoice Line is shown as previously.
If the Invoice Line is not linked to a Sales Order Line, it is

shown as previously.
Epicor ERP | 10.2.400 51


ClaveProdServ
• InvcDtl.MXProdServCode (new) in case of Invoice Line;
• InvcMisc.MiscCode -> MiscChrg.MXProdServCode (new)
in case of Miscellaneous Charge Line.
Cantidad
1. In case of InvcDtl:
For Deposit Billing (InvcHead.InvoiceType = DEP): value
= 1;
For other: value = ABS(InvcDtl.SellingShipQty);
2. In case of InvcMisc: value = 1
ClaveUnidad
If the Invoice is:
1. a Deposit Billing (InvcHead.InvoiceType = DEP) or
2. a Global Invoice (Customer.MXGeneralPublic = 1)
then
• ACT (predefined constant);
Else
• InvcDtl.SalesUM -> UOM.MXSATCode for InvcDtl;
• SAT Code of the EA for InvcMisc.
Unidad
In case of InvcDtl:
value = InvcDtl.SalesUM -> UOM.UOMCode.
In case of InvcMisc:
value = EA.
The attribute is not created in case of Global Invoice
Descripcion If the Invoice is a Deposit Billing (InvcHead.InvoiceType =

DEP), then:
• Anticipo del bien o servicio (predefined constant);
Else
• For InvcDtl in case there is no related Deposit Billing:
InvcDtl.LineDesc
• For InvcDtl in case there is related Deposit Billing:
InvcDtl.LineDesc + " - CFDI por remanente de un
anticipo";
• For InvcMisc: InvcMisc.Description.
52 Epicor ERP | 10.2.400


ValorUnitario
If the Invoice is a Deposit Billing (InvcHead.InvoiceType
= DEP), then value = ABS(InvcDtl.DocExtPrice)
Else
If the Line's Part is a Sales Kit with Component Pricing
(InvcDtl.PartNum -> Part.TypeCode = K and
InvcDtl.PartNum-> PartPlant.KitPricing = C)
Then {IF InvcDtl.PricePerCode = E: value = Sum of
ABS(InvcDtl.DocUnitPrice/
Price Factor (Invc.Dtl.PricePerCode) = 1 (E, 100 (C) or
1000 (M)) of Invoice Lines corresponding to all
components of the Sales Kit (see details below);
IF InvcDtl.PricePerCode = C:
value = Sum of ABS(InvcDtl.DocUnitPrice/Price Factor
(Invc.Dtl.PricePerCode) = 1 (E) , 100 (C) or 1000 (M))/100
of Invoice Lines corresponding to all components of the
Sales Kit;
IF InvcDtl.PricePerCode = M: value = Sum of
ABS(InvcDtl.DocUnitPrice/Price Factor
(Invc.Dtl.PricePerCode) = 1 (E) , 100 (C) or 1000 (M)) /
1000 of Invoice Lines corresponding to all components
of the Sales Kit;}
Else //Not Sales Kit OR Sales Kit //with Parent Pricing.
{IF InvcDtl.PricePerCode = E: value =
ABS(InvcDtl.DocUnitPrice); IF InvcDtl.PricePerCode = C:
value = ABS(InvcDtl.DocUnitPrice) /100;
IF InvcDtl.PricePerCode = M: value =
ABS(InvcDtl.DocUnitPrice) /1000.}
2. In case of InvcMisc: value = ABS(InvcMisc.DocMiscAmt).
Example
To define a set of other Invoice Lines corresponding to
components of the Sales Kit, the following rules should
be applied.
For example, the current Invoice Line:
• Contains Part which is a Sales Kit;
• Corresponds to Sales Order Line with Number N.
Invoice Line corresponds to the component of the Sales
Kit if:
1. It is linked to Sales Order Line (InvcDtl.OrderNum

<> Empty String AND InvcDtl.OrderLine <> Empty
String);
Epicor ERP | 10.2.400 53


2. Linked Sales Order Line corresponds to the
component the Sales Kit, that is
OrderDtl.KitParentLine = N.
Importe
1. In case of InvcDtl: ABS(InvcDtl.DocExtPrice);
2. In case of InvcMisc: ABS(InvcMisc.DocMiscAmt).
Descuento
Line's discount.
Only one node can be created. The node is created only in

cfdi:Comprobante/
case there is at least one Tax Line for the current Invoice.
cfdi:Conceptos/
cfdi:Concepto/
cfdi:Impuestos/
cfdi:Traslados/
cfdi:Traslado
Sales Tax Information

cfdi:Impuestos/
cfdi:Traslados
<cfdi:Traslados/ The node is repeated for each Sales Tax Type linked to the
current Invoice Line. The following conditions should be met
cfdi:Traslado>
to expose the node:
1. InvcTax.CollectionType = 0 (Invoicing).
2. InvcTax.TaxCode -> SalesTax.MXTaxType = 002 (IVA) or

003 (IEPS).
Base InvcTax.DocTaxableAmt
Impuesto InvcTax.TaxCode -> SalesTax.MXTaxType
54 Epicor ERP | 10.2.400


TipoFactor
• InvcTax.TaxCode -> SalesTax.MXTypeFactor in case
InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt
TasaOCuota
• InvcTax.Percent in case there is no exemption
(InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt).
The value is shown as decimal value (16% -> 0.160000)
• The attribute is not created in case of exemption.
Importe
• InvcTax.DocTaxAmt in case there is no exemption
(InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt);
• The attribute is not created in case of exemption.
cfdi:Comprobante/ The node is repeated for:

cfdi:Conceptos/
1. Each Withholding Tax Type linked to the current Invoice
cfdi:Concepto/ Line
cfdi:Impuestos/
2. Each Withholding Tax Type linked to the component
cfdi:Retenciones/ Invoice Line in case the current Invoice Line corresponds
to parent Sales Kit order line.
cfdi:Retencion
<cfdi:Retenciones/ The node is repeated for each Withholding Tax Type linked
to the current Invoice Line. The following conditions should
cfdi:Retencion>
be met to expose the node:
1. InvcTax.CollectionType = 1 (Withholding)

001 (ISR).
Base InvcTax.DocTaxableAmt
TipoFactor InvcTax.TaxCode -> SalesTax.MXTypeFactor
TasaOCuota
InvcTax.Percent
The value is shown as decimal value (16% -> 0.160000).
Importe InvcTax.DocTaxAmt
<cfdi:Comprobante\
cfdi:Conceptos\
cfdi:Concepto\
cfdi:InformacionAduanera>
NumeroPedimento PartLot.ImportNum
Epicor ERP | 10.2.400 55


<cfdi:Comprobante\
The node is not created if
cfdi:Impuestos>
TotalImpuestosRetenidos Sum of ABS(InvcTax.DocTaxAmt) of Retenidos

TotalImpuestosTrasladados Sum of ABS(InvcTax.DocTaxAmt) of Translados
<cfdi:Comprobante\
cfdi:Impuestos\
cfdi:Retenciones>
<cfdi:Comprobante\ The node is repeated for each group of Withholding Taxes

on this Invoice having the same MXTaxType. The following
cfdi:Impuestos\
conditions should be met to expose the node:
cfdi:Retenciones\
1. InvcTax.CollectionType = 1 (Withholding)
cfdi:Retencion>
001 (ISR).

Importe Sum of ABS(InvcTax.DocTaxAmt) for taxes in the group
</cfdi:Retencion>
</cfdi:Retenciones>
cfdi:Comprobante/ Only one node can be created.

cfdi:Impuestos/ The node is created only in case there is at least one Invoice
Line without exemption (that is, such an Invoice Line has all
cfdi:Traslados
InvcTax records meeting the following condition:
InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt).
The node is created for an Invoice Line that has no exemption.

<cfdi:Comprobante\
If the Invoice Line has exemption, that is at least one related
cfdi:Impuestos\ Tax Line has InvcTax.DocReportableAmt <>
InvcTax.DocTaxableAmt), then the node is not created.
cfdi:Traslados>
cfdi:Traslado>
<cfdi:Traslados/ The node is repeated for each group of Sales Taxes on this
invoice having the same MXTaxType, MXTypeFactor, and
cfdi:Traslado>
Percent. The following conditions should be met to expose
the node:
1. InvcTax.CollectionType = 0 (Invoicing);

003 (IEPS).
56 Epicor ERP | 10.2.400


3. InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt
(Tax Line without exemption is shown only).
Sales Tax Information

<cfdi:Impuestos/
cfdi:Traslados>

TipoFactor
• InvcTax.TaxCode -> SalesTax.MXTypeFactor in case
InvcTax.DocReportableAmt = InvcTax.DocTaxableAmt
TasaOCuota
InvcTax.Percent
The value is shown as decimal value (16% -> 0.160000).
Importe
Sum of InvcTax.DocTaxAmt for taxes in the group.
</cfdi:Traslado>
</cfdi:Traslados>
</cfdi:Impuestos>
<cfdi:Complemento>
<cfdi:TimbreFiscalDigital>
version Constant = 1.0 This field is provided by the PAC
UUID This field is provided by the PAC
FechaTimbrado This field is provided by the PAC
selloCFD It is calculated in Epicor ERP using the original string, two
algorithms (SHA-1 and RSA), and two keys (.key and .cer).
Epicor = New field. WS will update it.
noCertificadoSAT This field is provided by the PAC
selloSAT This field is provided by the PAC
</cfdi:TimbreFiscalDigital>
<cfdi:Addenda>
N/A
</cfdi:Addenda>
</cfdi:Comprobante>
</xs:schema>
Note Amount of prepaid deposit is displayed as a discount on lines (Concepto/@Descuento values). Deposit
billing taxes are subtracted from line taxes.
Epicor ERP | 10.2.400 57

Electronic International Trade CFDI Supplement XML File Structure
The following table describes the structure of the Electronic International Trade CFDI Supplement XML file.
Node Name Attribute Name Value and Comments
<Complemento/ Supplement to integrate export goods/services

information to the CFDI
cce:ComercioExterior>
<cce:ComercioExterior/ Version
"1.1"
Version
MotivoTranslado InvcHead.MXMovingReason
Moving reason.
TipoOperacion
InvcHead.MXExportOperationType
Operation Type. The only value is allowed:
• 2 = Exportación (Export)
ClaveDePedimento InvcHead.MXExportCustDocCode
Customs document code
Note The XSD schema allows only for A1
value here.
CertificadoOrigen InvcHead.MXExportCertOrigin
Origin Certificate
NumCertificadoOrigen InvcHead.MXExportCertOriginNum
If InvcHead.MXExportCertOrigin = 0, the attribute is
not created.
NumeroExportadorConfiable InvcHead.MXExportConfNum
Incoterm InvcHead.MXIncoterm
Incoterm
Subdivision Subdivision flag

TipoCambioUSD Exchange rate Base Currency -> USD
(Currency.CurrencyID = USD) on invoice apply date.
Exchange rate from Base Currency to USD.
TotalUSD The sum of values from the attribute @ValorDolares

(rounded with 2 decimals)
Total Amount in USD.
58 Epicor ERP | 10.2.400

<cce:ComercioExterior/ Issuing Party (Company Data).

Emisor>
Issuing Party's Address

<cce:ComercioExterior/
cce:Emisor/ cce:Domicilio>
Calle
Company.Address1
Street
NumeroExterior Company.Address2
Address Line 2
Colonia Company.Address3
Address Line 3
Municipio XbSyst.MXMunicipioCode
Municipio Code
Estado Company.State
State
País
Company.Country -> Country.MXExternalCode
Country
CodigoPostal Company.Zip
Postal Code
Localidad XbSyst.MXLocality
Locality Code
Information about owner of the product.

The node is created only if
cce:Propietario>
InvcHead.MXNumRegIdTrib <> Empty string.
NumRegIdTrib InvcHead.MXNumRegIdTrib
Owner identifier.
ResidenciaFiscal InvcHead.MXExternalCode
External code of the residence country of the owner.
Recipient (Customer Data)
cce:Receptor>
NumRegIdTrib Customer.FederalID
Customer Identification number or fiscal registration
from country of residence
<cce:ComercioExterior/ Recipient's Address
Epicor ERP | 10.2.400 59


cce:Receptor/ cce:Domicilio>
Calle Customer.BTAddress1
Street
NumeroExterior Customer.BTAddress2
Address Line 2
Colonia Customer.BTAddress3
Address Line 3
Municipio Customer.MXMunicipio
Municipio
Estado
Customer.BTState
State
País Customer.BTCountryNum ->

Country.MXExternalCode
Country
CodigoPostal
Customer.BTZip
Postal Code
<cce:ComercioExterior/ Node to inform when the Ship To party is different

from the Bill To party.
cce: Destinatario>
NumRegIdTrib ShipTo.MXFederalID
Ship To Identification number or fiscal registration
from country of residence
Nombre ShipTo.Name
Ship To Party Name
<cce:ComercioExterior/ Ship To Party's Address

cce:Destinatario/
cce:Domicilio>
Calle ShipTo.Address1
Street Address Line 1
NumeroExterior ShipTo.Address2
Colonia ShipTo.Address3
60 Epicor ERP | 10.2.400


Municipio ShipTo.MXMunicipio
Municipio
Estado ShipTo.State
State
País ShipTo.CountryNum -> Country.MXExternalCode

Country
CodigoPostal ShipTo.Zip
Postal Code
<cce:ComercioExterior/ Invoice Line (InvcDtl) or Miscellaneous Charge

(InvcMisc)
cce:Mercancias/
For each concept registered in the
cce:Mercancia>
cfdi:Comprobante/Conceptos element, a part in
the supplement cce:ComercioExterior must exist,
where the attribute
cce:ComercioExterior/
Mercancias/
Mercancia/
@NoIdentificacion
is equal to the attribute
cfdi:Comprobante/
Conceptos/
Concepto/
@NoIdentificacion.
NoIdentificacion
• InvcDtl.InvoiceLine + "-" +
InvcDtl.PartNum for Invoice Line;
• InvcMisc.InvoiceLine + "-" +
InvcMisc.Description for Miscellaneous Charge.
Identifier
FraccionArancelaria InvcDtl.MXCustomsDuty
The attribute is not created if either
cce:ComercioExterior/
Mercancias:Mercancia/
@UnidadAduana = 99
or
cfdi:Comprobante/
Conceptos/
Epicor ERP | 10.2.400 61


Concepto/
@unidad = 99
Customs Duty
CantidadAduana
IF the Invoice is a Deposit Billing
(InvcHead.InvoiceType = DEP),
THEN value = 1;
ELSE value = InvcDtl.SellingShipQty *
{CustomsFactor}
2. In case of InvcMisc: value = 1.
The quantity of goods at the customs office

according to the customs UOM
UnidadAduana
(InvcHead.InvoiceType = "DEP")
THEN value = 99;
ELSE Depending on
InvcDtl.MXCustomsUMFrom:
= 0: value = Part.SalesUM ->
UOM.MXCustomsUOM;
=1: value = Part.NetWeightUOM ->
UOM.MXCustomsUOM;
=2: value = Part.GrossWeightUOM ->
UOM.MXCustomsUOM;
=3: value = Part.NetVolumeUOM ->
UOM.MXCustomsUOM.
2. In case of InvcMisc: value = 99.
Customs UOM
ValorUnitarioAduana
(InvcHead.InvoiceType = "DEP")
THEN value = ABS({Extended Price})
ELSE
• IF (InvcDtl.PricePerCode = "E")
• THEN value = ABS({Unit Price}) /
{CustomsFactor};
62 Epicor ERP | 10.2.400


• IF (InvcDtl.PricePerCode = "C")
• THEN value = 100 * ABS({Unit Price}) /
{CustomsFactor};
• IF (InvcDtl.PricePerCode = "M")
• THEN value = 1000 * ABS({Unit Price}) /
{CustomsFactor};
2. In case of InvcMisc: value = ABS({Misc Amount});

{Extended Price} =
InvcDtl.DocExtPrice OR
InvcDtl.ExtPrice OR
InvcDtl.Rpt1ExtPrice OR
InvcDtl.Rpt3ExtPrice
depending on which field value is stored in USD
(CurrencyID = "USD")
{Unit Price} =
InvcDtl.DocUnitPrice OR
InvcDtl.UnitPrice OR
InvcDtl.Rpt1UnitPrice OR
InvcDtl.Rpt3UnitPrice
{Misc Amount} =
InvcMisc.DocMiscAmt OR
InvcMisc.MiscAmt OR
InvcMisc. Rpt1MiscAmt OR
InvcMisc. Rpt3MiscAmt
If there is no currency with CurrencyID = USD , then

0 is shown.
Unit customs value shown in USD.
ValorDolares @CantidadAduana * @ValorUnitarioAduana

The value should be rounded by 2 decimals.
Line Amount in USD ( = Quantity * Unit Price)
Epicor ERP | 10.2.400 63

cce:Mercancia/ Each node corresponds to one serial number linked

to the invoice line (@NumeroSerie attribute).
cce:DescripcionesEspecificas>
The node is created only if the part has filled
Commercial Brand field (Part.CommercialBrand). If
the field is empty the <DescripcionesEspecificas>
node is not created.
Specific Descriptions.
Marca InvcDtl.PartNum -> Part.CommercialBrand

Brand Field at Part Maintenance Attributes
Modelo InvcDtl.PartNum -> Part.CommercialSubBrand

Sub-brand Field at Part Maintenance Attributes
NumeroSerie
[InvcDtl.Company + InvcDtl.PartNum +
InvcDtl.PackNum + InvcDtl.PackLine] ->
SerialNo.SerialNumber
Serial Number
Depending on presence of the <CommercioExterior> node, the following nodes and attributes are printed or
not printed in other parts of the Digital Tax Receipt XML file:
XML Element <CommercioExterior> is <CommercioExterior> is Comment

NOT present present
InvcHead.MXPurchaseType P01 Type of
cfdi:Comprobante/
Purchase
cfdi:Receptor/
@UsoCFDI>
The attribute is not Identifier

cfdi:Comprobante/ • InvcDtl.InvoiceLine + "-" +
printed
InvcDtl.PartNum for Invoice
Conceptos/
Line;
Concepto/ • InvcMisc.InvoiceLine + "-" +
@NoIdentificacion InvcMisc.Description for
Miscellaneous Charge.
The attribute is printed. The attribute is not printed. Import Number

<cfdi:InformacionAduanera/
@NumeroPedimento>
If the <CommercioExterior> node is present and the Moving Reason flag (InvcHead.MXMovingReasonFlag)
is on, the following nodes and attributes are printed or not printed.
64 Epicor ERP | 10.2.400

XML Element <CommercioExterior> is <CommercioExterior> is Comment

not present or Moving present and Moving
Reason Flag = 0 Reason Flag = 1
The attribute contains a The attribute value is T. Type of Receipt
<cfdi:Comprobante/
value.
@TipoDeComprobante>
The attribute is printed. The attribute is not printed. Payment Terms

<cfdi:Comprobante/
@CondicionesDePago>
The attribute is printed. The attribute is not printed. Discount

<cfdi:Comprobante/
@Descuento>
The attribute is printed. The attribute is not printed. Form of Payment

<cfdi:Comprobante/
according to SAT
@FormaPago> catalog
The attribute is printed. The attribute is not printed. Method of Payment

<cfdi:Comprobante/
according to SAT
@MetodoPago> catalog
The node is printed. The node is not printed. Tax information.

<cfdi:Comprobante/
cfdi:Impuestos>
Error Messages
PAC or the Web Service may return errors during certification. Errors will be registered for the invoice, so you
will be aware that the invoice was not certified. You can re-certify an invoice from AR Invoice Tracker.
Important These tables only apply when using CFDIs.
The following table shows possible errors returned by the Web Service.
Code Description (Spanish) Translation

M301 Esquema no válido XSD Schema is not valid
M302 El Sello del Comprobante no es válido Digital Sea lis not valid
M303 El Rfc del Emisor no corresponde al Rfc del RFC of seller does not match RFC in
Certificado certificate
M304 El Certificado se encuentra en la lista de Certificate is in SAT's "blacklist"
revocación del SAT
M304B El Certificado aún no se encuentra en la lista de Certificate is not yet in SAT's certificate list
certificados del SAT
M305 Certificado de sello no válido Certificate is not valid
M306 El Comprobante fue firmado con una FIEL The document was signed with a FIEL
M307 El comprobante ya contiene un timbre The document already has a stamp
M308 Emitido por una AC no válida Issued by an invalid AC
Epicor ERP | 10.2.400 65


M401 La fecha de expedición del comprobante es mayor Document was issued more than 72 hours
a 72 horas ago
M402 EL RFC del emisor no existe conforme al régimen RFC of seller does not exist with this
autorizado (Lista de validación de régimen) LCO scheme
M403 El CFD fue emitido antes del 01 Enero de 2011 Document was issued before January 1st,
2011
The following table shows possible errors returned by a PAC.

401 La fecha de emision del comprobante Date outside range for certification
esta fuera de rango de 72 hrs para
Note The cause of this error is that the date and time
su timbrado
of the invoice is more than 72 hours old or there is a
time difference between the invoice and the PAC server.
Important Synchronize your server date and time with

the PAC's server date and time to prevent this error
from occurring in the future. As a workaround, use the
Regenerate Digital Tax Receipt action menu item
from AR Invoice Tracker to re-certify the document if
your local date/time is ahead of the PAC's date/time.
603 No hemos recibido un Certificado de Interfactura has not received a certificate for the used
Conexión adjunto a la peticion connection. Possible reason: invalid company tax ID.
G101 El PAC no está configurado PAC is not correctly configured
correctamente
G404 No se pudo establecer la conexión Could not establish connection with PAC
con el PAC
G999 Error interno Internal error
SAT AR Invoice Form
Use the SAT AR Invoice form to print the invoice PDF with required data for submission to the authorities. The
layout of this report is defined by Mexican Tax Agency (SAT).
Note The SAT AR Invoice form contains data that is generated after the invoice is posted. Thus the report
can be printed correctly only from AR Invoice Tracker. Although the report is also available in the AR Invoice
Entry form, it should not be used there.
Use the Print command on the Actions menu to print the SAT AR Invoice form. The form contains data generated
after signing a digital tax receipt, so it must be printed after posting the invoice.
The Place and Date and Issued by field values are defined by the Use Site on Expedido En Address check
box on the Modules > All Modules > Localization > Digital Tax Receipts sheet in Company Configuration.
The Issued by field is displayed only if this check box is selected.
The following fields display data from the invoice lines:
• Quantity
• UM
66 Epicor ERP | 10.2.400

• Description
• Unit price
• Amount
The following fields are shown only if their values are not equal to 0:
• Discount
• Charges
• Adv.Billed
• Deposit
• List of taxes
The ImportNum and ImportDate fields are linked to the invoice line. The fields are shown only if at least one
of them contains a non-empty value.
The Total and Total amount fields depend on the Enable Tax Withholdings for Invoice Total check box on
the Modules > All Modules > Localization > Detail sheet in Company Configuration.
International Trade Section

If the operation type of the invoice is Export, the report displays details for the International Trade section.
The following fields of the section display data from the invoice or miscellaneous charge lines:
• Customs Duty
• Customs UM
• Quantity
• PartNum
• Serial Num
• Unit price
• USD Amount
• Total USD
• International Trade Information
• Operation Type
• Customs Document Code
• Tax ID
• Origin Certificate
• Reliable Exporter
• INCOTERM
• Exchange Rate USD
If the Ship To and Bill To addresses are different, the following fields are printed as well:
• Ship To Information
• Customer Ship To Name
• Customer Ship To Address
• Tax ID
The following fields are printed if the Moving Reason check box is selected:
• Transfer
• Moving Reason
Epicor ERP | 10.2.400 67

• Owner Tax ID
• Owner's External Country
All amounts of the report form are shown with the currency symbol prefix.
Note The following table contains references to the CustomsFactor value.
{CustomsFactor} is used to convert selling UOM to UOM used by customs. It is defined depending on value
of the InvcDtl.MXCustomsUMFrom parameter:
• Value = 0: {CustomsFactor} = 1;
• Value = 1: {CustomsFactor} = Part.NetWeight;
• IF Part.NetWeight = 0 THEN {CustomsFactor} = 1;
• Value = 2: {CustomsFactor} = Part.GrossWeight;

• IF Part. GrossWeight = 0 THEN {CustomsFactor} = 1;
• Value = 3: {CustomsFactor} = Part.NetVolume;

• IF Part. NetVolume = 0 THEN {CustomsFactor} = 1.
Field Name Field Name Value Comment

(English) (Spanish)
Page N of M Página N de M Page number Page number
{LegalNumber} = InvcHead.LegalNumber Type of the transaction
• CM: + • NC: +
{LegalNumber} {LegalNumber}
if Credit for Credit
Memo is Memo;
created AND • Factura: +
InvcHead. {LegalNumber}
MXPartPmt for other
= 0; cases.
• Invoice: +
{LegalNumber}
for other
cases.
Folio Fiscal Folio Fiscal InvcHead.MXFiscalFolio Folio Fiscal - Fiscal Folio

(UUID)
Payment Método de pago Payment Method (PUE,
InvcHead.PMUID -> PayMethod.MXPaidAs + " -
Method PPD)
" + {"MXPaymMeth" UD Dictionary}.CodeDesc
Form of Forma de pago Form of Payment

InvcHead.PMUID -> PayMethod.MXSATCode + "
Payment
- " + {"MXPaymForm" UD Dictionary}.CodeDesc
Currency Moneda InvcHead.CurrencyCode -> Currency.CurrencyID Currency Code

Exchange Rate Tipo de Cambio Exchange Rate
InvcHead.ExchangeRate The field is shown only
in case the invoice currency differs from the base
currency.
68 Epicor ERP | 10.2.400


(English) (Spanish)
Certificate Serial No de serie del InvcHead.MXCertificateSN Certificate number for
Number Certificado del issuing party
CSD
Place and Date Lugar, fecha y {Municipio} + " " + Current date and time in Place and issue date
hora de emisión format YYYY-MM-DDThh:mm:ss.
{Municipio} =
• InvcHead.Plant -> Plant.MXMunicipio in case
the switch is activated;
• otherwise InvcHead.Company ->
Company.MXMunicipio.
Issued by Expedido en Address of the issuing

InvcHead.Plant->Plant.Name+" "+
party (if the company
InvcHead.Plant->Plant.Address1+" "+ has more than one
plant where invoices
InvcHead.Plant->Plant.Address2+" "+
are issued)
InvcHead.Plant->Plant.Address3+" "+
InvcHead.Plant->Plant.City+" "+
InvcHead.Plant->Plant.State+" "+
InvcHead.Plant->Plant.Zip+" "+
InvcHead.Plant->Plant.CountryNum ->
Country.Description
Issuer Emisor N/A Issuer

N/A N/A Company.Name Company Name
Tax ID RFC Company.StateTaxId Tax ID of the issuing
party
N/A N/A Company address
Company.Address1 +" "+
Company.City +" "+
Company.State +" "+
Company.ZIP +" " +
Company.Country ->
Country.Description
Tax Regime Régimen fiscal Tax Regime

InvcHead.MXTaxRegime ->
MXTaxRegime.TaxRegime + " - " +
MXTaxRegime.Description
Receptor Receptor N/A Receptor

N/A N/A Customer.LegalName Legal name of the
receptor
Epicor ERP | 10.2.400 69


(English) (Spanish)
Tax ID RFC InvcHead.CustomerID -> Customer.ResaleID Tax ID of the receptor
N/A N/A Receptor's address
Customer.BTAddress1 +" "+
Customer.BTCity +" "+
Customer.BTState +" "+
Customer.BTZIP +" "+
Customer.BTCountryNum ->
Country.Description
CFDI Use Uso de CFDI

InvcHead.MXPurchaseType + " - " +
{"MXPurType" UD Dictionary}.CodeDesc
ProdServCode ClaveProdServ InvcDtl.MXProdServCode Product or Service Code

UM CFDI ClaveUnidad InvcDtl.SalesUM -> UOM.MXSATCode Unit of measure for
CFDI
Quantity Cantidad Line quantity
• InvcDtl.MXSellingShipQty for advance billing
and advance billing credit memo
• InvcDtl.SellingShipQty for other invoice types
For credit memos and cancellation invoices the
quantity is shown as a positive value
UM Unidad de medida InvcDtl.SalesUM Unit of measure

ImportNum Number of the customs
No. de [InvcDtl.PackNum +
document (for imports
Importación
InvcDtl.PackLine] -> only)
ShipDtl.LotNum ->
PartLot.ImportNum
ImportDate Date of the customs

Feca de [InvcDtl.PackNum +
document (for imports
importación
InvcDtl.PackLine] -> only)
ShipDtl.LotNum ->
PartLot.MXImportDate
70 Epicor ERP | 10.2.400


(English) (Spanish)
Description Descripción Description of the item
• InvcDtl.LineDesc in case there is no related or service
Deposit Billing
• InvcDtl.LineDesc + " - " + "CFDI per remainder
of an advance" in case there is a {Related
Deposit Billing}
Unit price Precio Unitario Unit price

• InvcDtl.MXSellingShipQty for advance billing
and advance billing credit memo
• InvcDtl.DocUnitPrice for other invoice types
Amount Importe InvcDtl.DocExtPrice Line amount

For credit memos and cancellation invoices the
quantity is shown as a positive value.
Subtotal Subtotal Sum of InvcDtl.DocExtPrice for all invoice lines Subtotal

Discount Descuento Sum of InvcDtl.DocDiscount for all Invoice Lines Total discount
Charges Cargos Sum of InvcDtl.DocTotalMiscChrg for all Invoice Total charges
Lines
Adv.Billed Cobro antic. Sum of InvcDtl.DocAdvanceBillCredit for all Invoice Advance billed amount
Lines
Deposit Deposito Prepaid deposit amount
InvcHead.DocInvoiceAmt
This value is taken from related Deposit Billing
Invoice that has:
1. InvcHead.InvoiceType = DEP
2. InvcHead.Posted = 1
3. The same Order (InvcHead.OrderNum) as the

current Invoice.
N/A N/A List of invoice taxes: Tax name (InvcTax.TaxCode Tax amounts separated
-> SalesTax.Description) and Tax Amount by tax type and rate
(InvcTax.DocTaxAmt)
Printed taxes are grouped by Tax Code.
Total Total Invoice amount as

• InvcHead.DocInvoiceAmt - number
InvcHead.DocWithholdAmt if the Enable Tax
Withholdings is on;
• InvcHead.DocInvoiceAmt if the Enable Tax
Withholdings is off.
Total amount Total con letra Value from the Total field printed as text Invoice amount as text
Epicor ERP | 10.2.400 71


(English) (Spanish)
Related CFDIs CFDI relacionados Type of relation
InvcHead.MXInvoiceRelationType + " - " +
{"MXRelType" UD Dictionary}.CodeDesc
N/A N/A List of related Invoices

List of UUID (InvcHead.MXFiscalFolio) of linked
(UUID)
Invoices:
In case of referenced Invoice:
• InvcHead.InvoiceRef -> InvcHead.MXFiscalFolio
• For each linked Deposit Billing:
InvcHead.MXFiscalFolio of the Deposit Billing
Customs Duty Fracción InvcDtl.MXCustomsDuty

Customs
Arancelaria
Duty
72 Epicor ERP | 10.2.400


(English) (Spanish)
Customs UM UM Aduana Customs UOM
• In case of InvcDtl:
(InvcHead.InvoiceType = "DEP") THEN
value = "99" + " - " + Description from the
MXUOMCust UD dictionary;
ELSE
Depending on InvcDtl.MXCustomsUMFrom:
= 0: value = Part.SalesUM ->
UOM.MXCustomsUOM + " - " + Description
from the MXUOMCust UD dictionary;
=1: value = Part.NetWeightUOM ->
=2: value = Part.GrossWeightUOM ->
=3: value = Part.NetVolumeUOM ->
from the MXUOMCust UD dictionary.
• In case of InvcMisc:
value = "99" + " - " + Description from the
MXUOMCust UD dictionary.
Quantity Cantidad The quantity of goods

• In case of InvcDtl: at the customs office
IF the Invoice is a Deposit Billing according to the
(InvcHead.InvoiceType = "DEP") THEN customs UOM
value = 1;
ELSE
value = InvcDtl.SellingShipQty *
{CustomsFactor}
value = 1;
PartNum NumParte Part Identifier

• InvcDtl.InvoiceLine + "-" + InvcDtl.PartNum
for Invoice Line;
• InvcMisc.InvoiceLine + "-" +
InvcMisc.Description for Miscellaneous Charge.
Serial Num NumSerie List of Serial Numbers delivered to Customer Serial Number(s)
separated with "," characters.
Set of Serial Numbers is retrieved from the
Epicor ERP | 10.2.400 73


(English) (Spanish)
SerialNo table using the following relation:
[InvcDtl.Company +
InvcDtl.PartNum +
InvcDtl.PackNum +
InvcDtl.PackLine] -> SerialNo.SerialNumber
74 Epicor ERP | 10.2.400


(English) (Spanish)
Unit Price Precio unitario
• In case of InvcDtl:
(InvcHead.InvoiceType = "DEP") THEN
value = ABS( {Extended Price} )
ELSE
IF (InvcDtl.PricePerCode = "E")
THEN value = ABS( {Unit Price} ) /
{CustomsFactor} ;
IF (InvcDtl.PricePerCode = "C") THEN
value = ABS( {Unit Price} ) / (100 *
{CustomsFactor}) ;
IF (InvcDtl.PricePerCode = "M") THEN
value = ABS( {Unit Price} ) / (1000 *
{CustomsFactor}) ;
value = ABS( {Misc Amount} );
-------------------------------------------
{Extended Price} =
InvcDtl.DocExtPrice OR
InvcDtl.ExtPrice OR
InvcDtl.Rpt3ExtPrice
depending on which field value is stored in
USD (CurrencyID = "USD")
{Unit Price} =
InvcDtl.DocUnitPrice OR
InvcDtl.UnitPrice OR
InvcDtl.Rpt3UnitPrice
{Misc Amount} =
InvcMisc.DocMiscAmt OR
InvcMisc.MiscAmt OR
Epicor ERP | 10.2.400 75


(English) (Spanish)
InvcMisc. Rpt3MiscAmt
If there is no currency with CurrencyID =
"USD" , then 0 is shown.
USD Amount Valor USD Line Amount in USD

value =
Quantity field * Unit Price field
The value should be rounded by 2 decimals.
Total USD Total USD The sum values from the USD Amount field of Total Amount in USD
all lines in the grid (rounded up to 2 decimals)
International Información de N/A International Trade
Trade Comercio Exterior Information
Information
N/A N/A Operation Type
InvcHead.MXExportOperationType + " - " +
Description (hardcoded constant)
Only one value is available now:
• 2 - Exportación
N/A N/A InvcHead.MXExportCustDocCode + " - " + Customs document

Description from the MXCustDoc UD dictionary code
Tax ID ID fiscal InvcHead.CustNum -> Customer.FederalID Customer's Federal ID
Origin Certificado de InvcHead.MXExportCertOrigin Origin Certificate
Certificate origen
Reliable Exporter Exportador InvcHead.MXExportConfNum Number of Reliable
confiable Exporter
INCOTERM INCOTERM InvcHead.MXIncoterm NCOTERM
Exchange rate Tipo de cambio Exchange rate Base Currency -> USD Exchange rate from
USD USD (Currency.CurrencyID = "USD") on Invoice Apply Base Currency to USD
Date
Ship to Destinatario N/A Ship To Information
N/A N/A ShipTo.Name Customer Ship To name
N/A N/A Customer Ship To
ShipTo.Address1 + " " +
address
ShipTo.Address2 + " " +
ShipTo.Address3
Tax ID ID fiscal ShipTo.MXFederalID Ship To Identification

number or fiscal
76 Epicor ERP | 10.2.400


(English) (Spanish)
registration from
country of residence
Transfer Traslado N/A Transfer Information
N/A N/A InvcHead.MXMovingReason + " - " + Description Moving Reason
from the MXMoveReas UD dictionary
Owner Tax ID ID fiscal del InvcHead.MXNumRegIdTrib Owner's Fiscal
Propietario Registration Number
N/A N/A InvcHead. MXExternalCode -> Country.Description Owner's External
Country
Digital Seal Sello digital del InvcHead.MXDigitalSeal Digital seal of the
CFDI issuing party
SAT Seal Sello del SAT InvcHead.MXSATSeal SAT Seal
N/A N/A Barcode image generated after invoice posting Barcode.
Printed in a square with
sides not smaller than
2.75cm each (about
1.08 inches)
Original string Cadena original InvcHead.MXOriginalString Original string

del complemento
de certificación
digital del SAT
SAT Certificate No de Serie del InvcHead.MXSATCertificateSN Certificate number for
Number Certificado del SAT
SAT
Date and Time Fecha y hora de InvcHead.MXCertifiedTimestamp Date and time of the
of Certification certificación invoice certification
This document Este documento N/A Label
is a printed es una
representation representación
of a CFDI impresa de un
CFDI
Create a SAT AR Invoice Form

Note Before you print the form, verify the SQL Server Reporting Service account has read permissions for
the folder defined in the Base URL field in Document Type Maintenance.
To print the SAT AR Invoice form:
1. Navigate to AR Invoice Tracker.

2. Click the Invoice button to select an invoice. Make sure that you select a posted invoice.
Epicor ERP | 10.2.400 77

3. From the Actions menu, select Print.

The Print Invoice window displays.
4. In the Report Style field, select Standard MX - SSRS.
5. Click Print Preview to view the report on the screen.
Cancellation Invoice Status MX
Use Cancellation Invoice Status MX to review the cancellation status and other relevant details of an invoice.
Menu Path: Financial Management > Accounts Receivable > General Operations > Cancellation Invoice Status
MX
Advanced Search Fields


Cancellation Status =
Specifies the cancellation status of the invoice. The options include:
• Cancelado (Cancelled)
• EnProceso (In Progress)
• Rechazado (Rejected)
• Error
• Desconocido (Unknown)
Cust. ID =
Specifies the customer ID.
Original Invoice Date Range

Specifies the date range of the original invoices.
Cancellation Invoice Status Fields


Cancellation ID
Specifies the cancellation ID returned by SAT.
78 Epicor ERP | 10.2.400

Cancellation Invoice
Specifies the number of the cancellation invoice.
Cancellation Invoice Date

Specifies the date of the cancellation invoice.
Cancellation Status
to be sent again.
Cust. ID
Specifies the customer ID.
GroupID
Specifies the invoice group ID.
Legal Number
Specifies the legal number.
Original Invoice
Specifies the number of the original invoice.
Original Invoice Date

Specifies the date of the original invoice.
Posted
Indicates whether the invoice has been posted.
Review the Cancellation Status of an Invoice
1. Navigate to Cancellation Invoice Status MX.

Menu Path: Financial Management > Accounts Receivable > General Operations > Cancellation Invoice
Status MX
The Cancellation Invoice Status pane is populated with the details of all available cancellation invoices.
If you want to specify the search, continue with the following steps.
2. In the Cust. ID field, enter the ID if the customer for which you want to review the cancellation statuses of
invoices.
Epicor ERP | 10.2.400 79

3. In the Original Invoice Date range fields, specify the date range of the original invoices.
4. From the Cancellation status drop-down list, select the cancellation status for which you want to review
the invoices. The options include:
• Cancelado (Cancelled)
• EnProceso (In Progress)
• Rechazado (Rejected)
• Error
• Desconocido (Unknown)
5. Click Refresh.
The Cancellation Invoice Status pane is populated with the details of only those cancellation invoices that
fit the search conditions.
6. Exit Cancellation Invoice Status MX.
AP Invoice Entry
Use the AP Invoice Entry to create invoices to pay your suppliers.

In the Fiscal Folio (UUID) field on the Header > Mexico sheet you must specify the UUID of the related CFDI.
In the CFD CBB Seria field on the Header > Mexico sheet you must specify the CBB Seria of the related CFD.
In the CFD CBB Folio Number field on the Header > Mexico sheet you must specify the CBB Folio Number of
the related CFD.
In the Retention Code and TAR Code fields on the Header > Mexico sheet you can specify the retention code
and TAR code (refer to Setup - Digital Tax Receipt - Supplier Maintenance for details). By default these values are
taken from supplier settings. You can enter or adjust the codes on this sheet if required.
The application displays this information on the Header > Mexico sheet in the following programs:
• Posted Invoice Update (Financial Management > Accounts Payable > General Operations)
• Invoice Tracker (Financial Management > Account Payable > General Operations)
Posted AP Invoice Update
Posted AP Invoice Update gives you limited control over posted invoices.
On the Header - Mexico sheet you can view and adjust the following fields specified in the AP Invoice Entry
program.
• CFD CBB Seria
• CFD CBB Folio Number
• Retention code
• TAR code
80 Epicor ERP | 10.2.400

AP Invoice Tracker
This tracker is a display-only version of the primary entry program. Use the tracker to review current information
about a selected record. You cannot add or edit records in a tracker.
On the Header - Mexico sheet you can view the following fields specified in the AP Invoice Entry program.
• Tax Destination
• CFD CBB Seria
• CFD CBB Folio Number
• Retention code
• TAR code
Payment Tracker MX
Use Payment Tracker to retrieve and review AP payment records.

Menu Path: Financial Management > Accounts Payable > General Operations > Payment Tracker MX
Advance Search Fields

Advance Search Fields
Use the Advance Search fields to specify the information about the payments for which you wish to search. To
enter a value, click anywhere on the fields.
Bank Account =
Specifies the name of a bank account.
Check >=
Provides the number of the check.
Check Amt =
Specifies the check amount details.
Fiscal Year =
Specifies the fiscal year.
Legal Number =
Specifies the legal number.
Name >=
Specifies the name of the supplier.
Period
Specifies the period.
Epicor ERP | 10.2.400 81

Supplier ID =
Specifies the supplier ID.
Detail Fields
Payment Tracker MX
Bank
Provides the bank identifier.
Bank Account MX
Specifies the supplier's bank account.
Bank Identifier MX
Specifies the supplier's bank identifier.
Bank Slip
Provides the identifier of the bank statement to which this transaction was matched during bank reconciliation
progress.
Bank/Remit To
Specifies the ID of the supplier's bank or remit to.
Batch Reference
Specifies the batch reference number.
Check
Provides the number of the check for the selected payment.
Check Amt
Displays the amount of the check for the selected payment.
Check Amt
Displays the amount of the check upon choosing the currency code and exchange rate.
Check Apply Date

Specifies the apply date of the check for the selected payment.
Cleared
Indicates whether this check is cleared. When the bank statement is posted, all checks must be cleared.
82 Epicor ERP | 10.2.400

Cleared Amount
Displays the amount cleared for this check.
Cleared Date
Displays the date when the check was cleared.
Currency Code
Displays the currency code for this payment.
Description
Displays the bank account description.
Electronic Payment
Indicates whether this payment was by electronic funds transfer.
Entry Person
Displays the name of the person who made this entry.
Exchange Rate
Displays the exchange rate that is used for this check.
Fiscal Folio MX
Specifies the fiscal folio (UUID).
Note This field is enabled. You can enter or modify the value if required.
Form of Payment MX
Specifies the form of payment for the selected record.
Group
Displays the ID of the group to which the transaction is assigned.
Legal Number
Displays the legal number of the check.
Manual
Indicates that the entry is manual and not generated by selecting a payment.
Own Reference
Specifies any reference provided by the user.
Epicor ERP | 10.2.400 83

Payment Msg. ID
Specifies the payment message ID for this check.
RFC MX
Specifies a tax payer ID (RFC).
Supplier
Specifies the name and unique identifier of the supplier.
Void
Indicates whether this check is voided.
List Fields
Payment Tracker MX
Bank Account ID
Specifies the unique identifier of the bank account.
Bank Slip
Provides the identifier of the bank statement to which this transaction was matched during bank reconciliation
progress.
Bank/Remit To Name
Specifies the ID of the supplier's bank or remit to.
Batch Reference
Specifies the batch reference number.
Change Date
Specifies the date of the last record change.
Changed By
Specifies the username of the person who changed the record.
Check
Provides the number of the check for the selected payment.
Check Amt
84 Epicor ERP | 10.2.400

Check Amt
Displays the amount of the check upon selection of the currency code and exchange rate.
Check Apply Date

Specifies the apply date of the check for the selected payment.
Cleared
Indicates whether this check is cleared. When the bank statement is posted, all checks must be cleared.
Cleared Amount
Displayed the amount cleared for this check.
Cleared Date
Displays the date when the check was cleared.
Currency Code
Displays the currency code for this payment.
Description
Displays the bank account description.
Electronic Payment
Indicates whether this payment was by electronic funds transfer.
Entry Person
Displays the name of the person who made this entry.
Exchange Rate
Displays the exchange rate that is used for this check.
Fiscal Year
Specifies the fiscal year of the selected payment.
Fiscal Year Suffix

Identifies the suffix of the fiscal year linked to the payment.
Group
Displays the ID of the group to which the transaction is assigned.
Manual
Indicates that the entry is manual and not generated by selecting a payment.
Epicor ERP | 10.2.400 85

Name
Specifies the name of the supplier.
Own Reference
Specifies any reference provided by the user.
Payment Legal Number

Specifies the payment legal number, if one exists.
Payment Msg.Id
Specifies the payment message ID for this check.
Period
Specifies the period of the selected payment.
Supplier ID
Specifies the unique identifier of the supplier.
Void
Indicates whether this check is voided.
Void Legal Number

Specifies the voided legal number of the payment.
Check Detail Fields

Check Detail Fields
Amount
Change Date
Specifies the date of the last record change.
Changed By
Specifies the username of the person who changed the record.
Comment
Provides the comment for the selected payment.
Description
Displays the payment details description.
86 Epicor ERP | 10.2.400

Discount
Displays the discount for the selected payment.
Fiscal Year
Specifies the fiscal year linked to the selected payment.
Fiscal Year Suffix

Identifies the suffix of the fiscal year linked to the payment.
Invoice
Displays the identifier of the invoice for the selected payment.
Period
Specifies the period of the selected payment.
Journal Entry
Use Journal Entry to create, reverse, and post allocations and manual journal entries.
On the Mexico sheet you can view and specify the following electronic accounting information:
• Fiscal Folio (UUID of the related CFDI)
• RFC (tax registration number).
Journal Detail Tracker
This tracker is a display-only version of the primary entry program. Use the tracker to review current information
about a selected record. You cannot add or edit records in a tracker.
On the Mexico sheet you can view the following fields specified in the Journal Detail Tracker program.
• Fiscal Folio (UUID of the related CFDI)
• RFC (tax registration number).
Update Invoice Fiscal Folio MX
Use Update Invoice Fiscal Folio MX to perform mass processing of XML files.
This program enables you to review imported XML files, match imported files with the AP invoices meeting
definite criteria (refer to the Matching Standards - Application Logic section). This can be done either automatically
or manually. After matching you can update selected AP invoices with the UUID information. The application will
extract the information about the UUID from XML file and populate the Fiscal Folio (UUID) field of the invoices.
To provide correct data retrieval from the imported XML files, you can set up the functionality by specifying the
XPath expressions. These parameters define how the application extracts the information about supplier ID,
invoice number, Fiscal Folio, and other parameters from the imported file. To save and retrieve these settings,
use standard Epicor ERP commands in the Actions menu - Save Defaults and Get Defaults.
Matching Standards - Application Logic
Epicor ERP | 10.2.400 87

The application searches for the following values in the AP invoices and compares them with the values in XML
file:
• Supplier tax ID - if this value does not match, the file will not be marked as matched. It is the primary
matching condition.
• Serie and Folio - if invoices with the same supplier tax ID, and Invoice Number (one of these combinations:
"Serie-Folio", "SerieFolio", "Serie Folio") as in the XML file are found, the file is marked as matched to them
(unless an invoice with similar Fiscal Folio exists already).
• Amount and Date - if invoices with the same supplier tax ID, invoice amount, and date but with different
Serie and Folio are found, the file is suggested for matching with them.
If the application considers the XML file as matched, it selects the Is matched check box near the file name. If
it suggests invoice(s) for matching, you need to review them and match manually using the Match button. To
deselect matched files, clear the check box. To automatically update the Fiscal Folio information for all matched
invoices, use the Update Fiscal Folio button.
Menu Path: Financial Management > Accounts Payable > General Operations > Update Invoice Fiscal Folio MX
Import Fields

Amount
Indicates the invoice amount.
Amount
Indicates the invoice amount in imported file.
Error Message
Indicates an error message if file import was completed with an error.
File Name
Indicates the imported file name.
Files to Import...
Click this button to import XML files with the information about AP invoices.
Fiscal Folio
Indicates the Fiscal Folio information in AP invoice.
Fiscal Folio
Indicates the Fiscal Folio information in imported file.
Folio
Indicates the Folio information in imported file.
88 Epicor ERP | 10.2.400

Invoice
Indicates the invoice number.
Invoice Date
Indicates the invoice date.
Invoice Date
Indicates the invoice date in imported file.
Is Matched
Indicates if this XML file is matched to an AP invoice.
Match
Click this button to match imported XML file to an AP invoice.
Serie
Indicates the serie in the imported file.
Supplier Name
Indicates the supplier name in AP invoice.
Supplier Tax ID
Indicates the supplier tax ID in imported file.
Update Fiscal Folio

Click this button if you want to update the Fiscal Folio information on the AP invoice in the ERP application.
Parameters Fields

XPath to Fiscal Folio field

Indicates the XPath to the Fiscal Folio details in the imported file.
XPath to Invoice Amount field

Indicates the XPath to the invoice amount details in the imported file. Select the check box if you wish to include
the parameter in additional search for manual matching.
Epicor ERP | 10.2.400 89

XPath to Invoice Date field

Indicates the XPath to the invoice date details in the imported file. Select the check box if you wish to include
XPath to Invoice Folio field

Indicates the XPath to the Invoice Folio details in the imported file.
XPath to Invoice Serie field

Indicates the XPath to the Invoice Serie details in the imported file.
XPath to Supplier Tax ID field

Indicates the XPath to the supplier tax ID details in the imported file.
Import and Process an XML File with AP Invoice Information
To import an XML file with AP invoice information, match it to the invoice in the application, and update the
Fiscal Folio information for the invoice, complete the following steps.
1. Navigate to the Update Invoice Fiscal Folio MX program.

Menu Path: Financial Management > Accounts Payable > General Operations > Update Invoice Fiscal Folio
MX
2. Navigate to the Parameters sheet.
3. Specify the parameters for retrieving data from imported XML files or accept the default ones.
4. Navigate to the Import sheet.
5. Click Files to Import....
6. Browse to the folder where the XML files are stored and select one or multiple files. Then click Open.
The application imports selected files and displays them in the Files pane. It attempts to match imported
files with the existing AP invoices. The Is Matched check box next to the file name becomes selected if the
imported file was matched to an AP invoice. If you want to deselect matching, clear the check box.
7. To start manual matching, select an XML file in the Files pane.

When you select an XML file, the application displays all invoices suggested for matching in the Invoices
pane.
8. Review in the grid the information retrieved from the imported file and compare it with the suggested
invoices.
Invoices suggested for matching to the selected file are shown in the Invoices pane.
9. To match any of the invoices with the selected XML file, select this invoice and click Match.
10. To update the Fiscal Folio field of AP invoices with the information from all selected XML files, click Update
Fiscal Folio.
90 Epicor ERP | 10.2.400

Update Journal Fiscal Folio MX
Use Update Journal Fiscal Folio MX to perform mass processing of XML files.
This program enables you to review imported XML files containing journal-related data, match imported files
with the journal entries in the application meeting definite criteria (refer to the Matching Standards - Application
Logic section). This can be done either automatically or manually. After matching you can update selected journal
entries with the UUID information. The application will extract the information about the UUID from XML file
and populate the Fiscal Folio (UUID) field of the journal entries.
XPath expressions. These parameters define how the application extracts the information about tax ID, RFC, legal
number and other parameters from the imported file. To save and retrieve these settings, use standard Epicor
ERP commands in the Actions menu - Save Defaults and Get Defaults.
The application searches for the following values in the journal entries and compares them with the values in
XML file:
• RFC (Tax ID) - if this value does not match, the file will not be marked as matched. It is the primary matching
condition.
• Serie and Folio - if journal entries with the same RFC (Tax ID), and Legal Number (one of these combinations:
"Serie-Folio", "SerieFolio", "Serie Folio") as in the XML file are found, the file is marked as matched to them
(unless a journal with similar Fiscal Folio exists already).
• Amount and Date - if journal entries with the same RFC (Tax ID), journal amount, and date but with different
Serie and Folio are found, the file is suggested for matching with them.
If the application considers the XML file as matched, it selects the Is matched check box near the file name. If
it suggests journal(s) for matching, you need to review them and match manually using the Match button. This
button also enables you to deselect matched files. To automatically update the Fiscal Folio information for all
matched journals, use the Update Fiscal Folio button.
Menu Path: Financial Management > General Ledger > General Operations > Update Journal Fiscal Folio MX
Import Fields

Book ID
Indicates the GL book ID. The field displays the book marked as Main Book by default.
Error Message
Indicates the error message if file import was completed with an error.
File Name
Files to Import...
Click this button to import XML files with the information about journal entries.
Epicor ERP | 10.2.400 91

Fiscal Folio
Indicates the Fiscal Folio information in the journal entry.
Fiscal Folio
Indicates the Fiscal Folio information in the imported file.
Fiscal Year
Indicates the fiscal year. The field displays current year by default.
Fiscal Year Suffix

Indicates the fiscal year suffix.
Folio
Indicates the Folio information in imported file.
Is Matched
Indicates if this XML file is matched to a journal entry.
Journal Amount
Indicates the journal amount in the imported file.
Journal Amount
Indicates the amount in the journal entry.
Journal Code
Indicates the journal code. The field displays the General Journal code by default.
Journal Date
Indicates the journal date in the imported file.
Journal Date
Indicates the date in the journal entry.
Journal Number
Indicates the journal number.
Legal Number
Indicates the legal number of the journal entry.
Match
Click this button to match imported XML file to a journal entry.
92 Epicor ERP | 10.2.400

Serie
Indicates the serie in the imported file.
Tax ID
Indicates the journal tax ID.
Tax ID
Indicates the tax ID in the imported file.
Update Fiscal Folio

Click this button if you want to update the Fiscal Folio information on the journal entry in the ERP application.
Parameters Fields


XPath to Journal Amount field

Indicates the XPath to the Journal Amount details in the imported file. Select the check box if you wish to include
XPath to Journal Date field

Indicates the XPath to the Journal Date details in the imported file. Select the check box if you wish to include
XPath to Journal Folio field

Indicates the XPath to the Journal Folio details in the imported file.
XPath to Journal Serie field

Indicates the XPath to the Journal Serie details in the imported file.
XPath to Tax ID field

Indicates the XPath to the Tax ID details in the imported file.
Epicor ERP | 10.2.400 93

Import and Process an XML File with Journal Information
To import an XML file with journal information, match it to the journal entry in the application, and update the
Fiscal Folio information for the journal, complete the following steps.
1. Navigate to the Update Journal Fiscal Folio MX program.

Menu Path: Financial Management > General Ledger > General Operations > Update Journal Fiscal Folio
MX
5. Specify Fiscal Year, Fiscal Year Suffix, Book ID, and Journal Code.
6. Click Files to Import....
7. Browse to the folder where the XML files are stored and select one or several files. Then click Open.
files with the existing journals using information about the company, fiscal year, book ID, journal code, RFC,
and legal number. The Is Matched check box becomes selected if the imported file was matched. If you
want to cancel matching, clear the check box.

When you select an XML file, the application displays all journals suggested for matching in the GL Journals
pane.
9. Review the journal details that the application extracted from the imported file and displayed in the grid.
Journals that are matched or potentially can be matched to the selected file are shown in the GL Journals
pane.
10. To match any of the journals with the selected XML file, select this journal and click Match.
11. To update the Fiscal Folio field of the selected journal with the information from the selected XML file,
click Update Fiscal Folio.
Update Payment Fiscal Folio MX

Use Update Payment Fiscal Folio MX to perform mass processing of XML files.
This program enables you to review imported XML files, match imported files with the AP payments meeting
definite criteria (refer to the Matching Standards - Application Logic section). This can be done either automatically
or manually. After matching, you can update selected AP payments with the UUID information. The application
will extract the information about the UUID from an XML file and populate the Fiscal Folio (UUID) field of the
payments.
XPath expressions. These parameters define how the application extracts the information about supplier tax ID,
payment date, Fiscal Folio, and other parameters from the imported file. To save and retrieve these settings, use
standard Epicor ERP commands in the Actions menu - Save Defaults and Get Defaults.
94 Epicor ERP | 10.2.400

The application searches for the following values in the AP payments and compares them with the values in XML
file:
• RFC (Tax ID) - if this value does not match, the file will not be marked as matched. It is the primary matching
condition. You can use both supplier tax ID and check tax ID for this condition.
• Check Number - if payments with the same supplier tax ID and payment number as in the XML file are found,
the file is marked as matched to them.
• Payment Amount and Payment Date - if payments with the same supplier tax ID, payment amount, and
date but with different check number are found, the file is suggested for matching with them.
If the application considers the XML file as matched, it selects the Is matched check box next to the file name.
If it suggests payment(s) for matching, you need to review them and match manually using the Match button.
This button also enables you to deselect matched files. To automatically update the Fiscal Folio information for
all matched payments, use the Update Fiscal Folio button.
Menu Path: Financial Management > Accounts Payable > General Operations > Update Payment Fiscal Folio
MX
Import Fields
Check Amount
Displays the check amount from the imported file.
Check Amount
Displays the check amount of the payment.
Check Num
Displays the check number of the payment.
Check Num
Displays the check number from the imported file. The field displays 0 if Check Number in the file is not numeric.
Error Message
Displays an error message if match attempt resulted in an error.
File Name
Files to Import...
Click this button to import XML files with the information about AP payments.
Fiscal Folio
Displays the Fiscal Folio information from the imported file.
Epicor ERP | 10.2.400 95

Fiscal Folio
Displays the Fiscal Folio information in the AP payment.
Form of Payment
Displays the code for the form of payment in the imported file.
Form of Payment
Displays the code of form of payment used for the payment.
Is Matched
Indicates if this XML file is matched to an AP payment.
Match
Click this button to match the imported XML file to an AP payment.
Payment Date
Displays the payment date from the imported file.
Payment Date
Displays the payment date.
Supplier Tax ID
Displays the supplier tax ID from the imported file.
Supplier Tax ID
Displays the supplier tax ID of the payment.
Update Fiscal Folio

Click this button if you want to update the Fiscal Folio information on the AP payment in the ERP application.
Parameters Fields
XPath to Check Amount field

Indicates the XPath to the Check Amount details in the imported file. Select the check box if you wish to include
additional search for manual matching.
XPath to Check Number field

Indicates the XPath to the Check Number details in the imported file.
96 Epicor ERP | 10.2.400


XPath to Form of Payment field

Indicates the XPath to the Form of Payment details in the imported file. Select the check box if you wish to include
XPath to Payment Date field

Indicates the XPath to the Payment Date details in the imported file. Select the check box if you wish to include
XPath to Tax ID field

Indicates the XPath to the supplier tax ID details in the imported file.
Import and Process an XML File with AP Payment Information
Use the following steps to import an XML file with AP payment information, match it to the payment in the
application, and update the Fiscal Folio information for the payment.
1. Navigate to the Update Payment Fiscal Folio MX program.

Menu Path: Financial Management > Accounts Payable > General Operations > Update Payment Fiscal
Folio MX
5. Click the Files to Import... button.
6. Browse to the folder where the XML files are stored and select one or multiple files. Then click Open.
files with the existing AP payments using information about tax ID, payment method, check number, payment
date, and check amount. The Is Matched check box next to the file name becomes selected if the imported
file was matched to an AP payment. If you want to deselect matching, clear the check box.

When you select an XML file, the application displays all payments suggested for matching in the Payments
pane.
8. Review in the grid the information retrieved from the imported file and compare it with the suggested
payments.
Payments suggested for matching to the selected file are shown in the Payments pane.
9. To match any of the payments with the selected XML file, select a payment and click Match.
10. To update the Fiscal Folio field of AP payments with the information from all selected XML files, click
Update Fiscal Folio.
Epicor ERP | 10.2.400 97

Cash Receipts Entry
Use Cash Receipts Entry to enter cash receipts with payment supplements that will be created and sent to PAC
for validation.
Use the A/R Receipt > Mexico sheet to indicate whether a payment supplement is required. If a payment
supplement is required, an XML file is created and sent to PAC for validation during posting of payment. If a
payment supplement is not required, a cash receipt is posted through the standard process with no additional
documents created.
Similarly to DTR for AR invoices, requests and responses XMLs for cash receipts are saved to disk. This allows
sending XMLs manually, if necessary and checking the generated data for debugging. If DTR debug mode is
activated (the Debug Mode check box is selected in Company Configuration > Modules > All Modules >
Localization > Digital Tax Receipts), the request XML and response XML are saved to the disk as follows:
• {Parent Folder}\{Company Name}\CashHead\DigitalReceiptRequest_{Internal Counter}.xml
• {Parent Folder}\{Company Name}\CashHead\DigitalReceiptResponse_{Internal Counter}.xml
where {Parent Folder} is a directory specified for the Document Type used for DTR. Response XML is also attached
to the cash receipt in Cash Receipt Tracker.
Menu Path
• Financial Managemet > Accounts Receivable > General Operations > Cash Receipt Entry
• Financial Management > Cash Management > General Operations > Cash Receipt Entry
Cash Receipt Posting
The following rules apply when posting cash receipts.

• Cash receipts are posted to GL after an electronic XML is accepted, in other words, a response from PAC
without errors is received.
• If errors occur during XML generation, or a response from PAC contains errors, a new record is created in
Review Journal where you can view the error text.
• If an error occurs during posting, you should correct the receipt, and then post it again. A new XML will be
generated.
• If a response from PAC contains no errors and the receipt can be posted, the following additional actions are
performed in the application:
• The CashHead.MXFiscalFolio field is updated with the value of the
Resultado/cfdi:Comprobante/cfdi:Complemento/tfd:TimbreFiscalDigital/@UUID attribute from the
response XML.
• The CashDtl.MXPaymentNum field is updated with a calculated {Payment Number} value.
Mexico Fields
Cash Receipts Entry

98 Epicor ERP | 10.2.400

Confirmation Code
Specifies a confirmation code for special cash receipts.
Customer Bank
Specifies the customer's bank ID. By default, the primary bank is displayed.
Fiscal Folio (UUID)

Specifies the fiscal folio (UUID) for the cash receipt. The field is available if the Digital Tax Receipt Type parameter
in Company Configuration is disabled. If this parameter is enabled, the Fiscal Folio (UUID) value is assigned
automatically and the field is read-only.
Original Check
Specifies the check number of the original receipt being corrected.
You may want to correct a receipt in case of an error in the original cash receipt that was reversed. When you
enter a cash receipt number here, the following conditions must be met:
• The check exists in the current company.
• The check belongs to the current customer.
• The check is reversed.
Original Check...
button label.
Payment Supplement required

Indicates if a payment supplement is required. This check box is available if the Digital Tax Receipt Type
parameter in Company Configuration has a value other than Disabled.
Mexico Fields
Cash Receipts Entry

RFC
Specifies a tax ID. This field is required for entering mandatory data in case a customer is not specified for cash
receipt. If a customer ID is not specified, this field becomes available. Before saving the receipt, if a customer is
not specified, the application checks that this field is not empty.
Create a Cash Receipt
1. Navigate to Cash Receipts Entry.

Menu Path: Financial Management > Accounts Receivable > General Operations > Cash Receipt Entry
Epicor ERP | 10.2.400 99

2. Create a new group.
3. From the New menu, select New Invoice Payment.
4. On the A/R Receipt > Header sheet, enter required cash receipt information and click Save.
5. Navigate to the A/R Receipt > Mexico sheet.
6. Select the Payment Supplement required check box if XML generation is required.
7. In the Customer Bank field, select a customer's bank from the list. A blank value is allowed.
8. If you want to correct an existing cash receipt, click the Original Check button to search for and select a
cash receipt.
10. If you did not specify a customer ID for the cash receipt, in the RFC field, enter a customer's tax ID.
11. Click Save.
12. From the Actions menu, select Post.

The Cash Receipt Post Process window displays.
13. Click the Submit button.
14. Exit Cash Receipts Entry.
Cash Receipt Tracker
Use Cash Receipt Tracker to review posted cash receipts with Mexico-specific information.
Use the A/R Receipt > Mexico sheet to review information related to digital tax receipts. All the fields on this
sheet are read-only. If a response from PAC is received, it is attached to the cash receipt. The attached XML file
is stored on disk as {Parent Folder}\{Company Name}\CashHead\CFD_{CompanyName}_{CashHead.HeadNum}.xml.
Menu Path: Financial Management > Accounts Receivable > General Operations > Cash Receipt Tracker
Mexico Fields
Cash Receipt Tracker

Confirmation Code
Specifies a confirmation code for special cash receipts.
Customer Bank
Specifies the customer's bank ID.
100 Epicor ERP | 10.2.400

Fiscal Folio (UUID)

Specifies the fiscal folio (UUID) for the cash receipt.
Original Check
Specifies the check number of the original receipt being corrected.
Payment Number
Specifies the payment number for AR invoice. The field is updated automatically.
Payment Supplement required

Indicates if a payment supplement is required.
Electronic CFDI Payment Supplement File Structure
The following table describes the structure of the Electronic Payment Supplement XML file.

Information about Cash Receipt
<cfdi:Comprobante>
Version 3.3
xsi:schemaLocation http://www.sat.gob.mx/cfd/3
http://www.sat.gob.mx/sitio_internet/cfd/3/cfdv33.xsd
http://www.sat.gob.mx/Pagos
http://www.sat.gob.mx/sitio_internet/cfd/Pagos/Pagos10.xsd
Fecha DTR creation timestamp. Current date and time in the format
YYYY-MM-DDThh:mm:ss.
NoCertificado CashHead.MXCertificateSN
Certificate Serial Number
Certificado
CashHead.MXCertificate
Certificate Number
TipoDeComprobante
"P"
Type of Document.
LugarExpedicion
Company.MXMunicipio.
Issuing Place.
Confirmacion
CashReceipt.MXConfirmationCode.
The attribute is created only if the value <> empty string.
Subtotal Subtotal "0".

Total Total "0".
Epicor ERP | 10.2.400 101


Moneda Currency "XXX".
Information about our Company
cfdi:Comprobante/
cfdi:Emisor
Rfc Company.StateTaxID
Nombre Company.Name
RegimenFiscal
CashDtl.InvoiceNum -> InvcHead.MXTaxRegime
(first CashDtl record for the current receipt can be used
(sorted by InvoiceNum ASC)).
Tax Regime according to SAT catalog.
Information about Customer
cfdi:Comprobante/
cfdi:Receptor
Rfc Customer.ResaleID
Nombre Customer.LegalName; Customer.BTName if Legal Name is
empty.
ResidenciaFiscal
CashHead.CustID -> Customer.Country ->
Country.MXExternalCode
The node is created only if Customer.Country ->
Country.MXExternalCode <> "MEX".
NumRegIdTrib
CashHead.CustID -> Customer.FederalID
The node is created only if Customer.Country ->
Country.MXExternalCode <> "MEX".
UsoCFDI Type of Purchase. Fixed value - P01.

Specifies the information of related vouchers. The node is
cfdi:Comprobante/
created only if CashHead.MXOriginalCheckRef <> Empty
cfdi:CfdiRelacionados string.
TipoRelacion 04
Information about Referenced Cash Receipt
cfdi:Comprobante/
cfdi:CfdiRelacionados/
cfdi:CfdiRelacionado
UUID
CashHead.MXOriginalCheckRef if the value <> Empty string
UUID of the Referenced Cash Receipt.
cfdi:Comprobante/
cfdi:Conceptos/
cfdi:Concepto
102 Epicor ERP | 10.2.400


ClaveProdServ 84111506
Cantidad 1
ClaveUnidad ACT
Descripcion Pago
ValorUnitario 0
Importe 0
Supplement containing payment information
cfdi:Comprobante/cfdi:Complemento/
pago10:Pagos
http://www.sat.gob.mx/Pagos
<pago10:Pagos/@xmlns:pago10>
Version 1.0
pago10:Pagos/pago10:Pago
Information about the payment.

<pago10:Pagos/
pago10:Pago>
FechaPago Date and time of payment.

CashHead.TranDate in the format YYYY-MM-DDThh:mm:ss.
FormaDePagoP
CashHead.PMUID -> PayMethod.MXSATCode.
Payment method according to SAT catalog.
MonedaP
CashHead.ReceiptCurrencyCode -> Currency.CurrencyID.
Currency of cash receipt according to SAT catalog.
TipoCambioP
Exchange rate from the currency of the cash receipt to the
MXN currency (Currency.CurrencyID = MXN) on payment
date.
The attribute is created only if the currency of the cash
receipt differs from MXN.
Monto
CashHead.DocTranAmt + Sum of CashDtl.DocDiscount for
all shown cash lines.
Cash receipt amount.
RfcEmisorCtaOrd
CashHead.MXBankID -> CustBank.MXRFC
Customer's bank tax ID.
NomBancoOrdExt
CashHead.MXBankID -> CustBank.LegalName.
Customer's bank name.
The attribute is created only if Company.Country <>
CustBank.Country.
Epicor ERP | 10.2.400 103


CtaOrdenante
CashHead.MXBankID -> CustBank.BankAcctNumber.
Account number with which the payment was done.
NumOperacion
CashHead.CheckRef
Check reference.
Several nodes can be created. Each node corresponds to one
CashDtl record that:
pago10:Pagos/ pago10:Pago/
• has a link to an AR invoice (CashDtl.InvoiceNum <> Empty
pago10:DoctoRelacionado String) and
• has CashDtl.TranType = PayInv.
Information about paid AR Invoice.

<pago10:Pago/
pago10:DoctoRelacionado>
IdDocumento
CashDtl.InvoiceNum -> InvcHead.MXFiscalFolio.
UUID of the invoice being paid.
Serie
CashDtl.InvoiceNum -> InvcHead.MXSerie.
Serie of the invoice.
Folio
CashDtl.InvoiceNum -> InvcHead.MXFolio.
Folio of the invoice.
MonedaDR
CashDtl.InvoiceNum -> InvcHead.CurrencyCode ->
Currency.CurrencyID.
Invoice currency.
TipoCambioDR
Exchange rate from invoice currency to cash receipt currency
on payment date.
The attribute is created only if the currencies are different.
MetodoDePagoDR
CashDtl.InvoiceNum -> InvcHead.PMUID ->
PayMethod.MXPaidAs.
Payment method specified in AR invoice.
NumParcialidad Payment Number
ImpSaldoAnt Previous balance of the AR invoice (the balance before this
payment).
Depending of the moment of time, different formulas are
used: CashDtl.InvoiceNum -> InvcHead.DocInvoicBal - this
value is valid if cash receipt has not been posted yet
OR
CashDtl.InvoiceNum -> InvcHead.DocInvoicBal +
CashDtl.DocTranAmt - this value is valid if cash receipt has
been already posted.
104 Epicor ERP | 10.2.400


ImpPagado
CashDtl.DocTranAmt
Amount being paid to the invoice.
ImpSaldoInsoluto Remaining balance of the AR invoice (the balance after this
payment).
Depending of the moment of time, different formulas are
used: CashDtl.InvoiceNum -> InvcHead.DocInvoicBal -
CashDtl.DocTranAmt - this value is valid if cash receipt has
not been posted yet
OR
CashDtl.InvoiceNum -> InvcHead.DocInvoicBal - this value
is valid if cash receipt has been already posted.
Cash Receipt Payment Supplement Report
Use the Cash Receipt Tracker program to print the cash receipt PDF with required data for submission to the
authorities. The layout of this report is defined by Mexican Tax Agency (SAT).
To print the report, select the Print Digital Receipt command from the Actions menu. The form contains data
generated after signing a digital tax receipt, so it must be printed after posting the cash receipt.
The Place and Date and Issued by field values are defined by the Use Site on Expedido En Address check
box on the Modules > All Modules > Localization > Digital Tax Receipts sheet in Company Configuration.
The Issued by field is displayed only if this check box is selected.
The following fields display data from the cash receipt lines:
• Serie-Folio
• UUID
• Payment Method
• Installment
• Currency
• Exchange Rate
• Previous Balance
• Remaining Balance
• Payment Amount
All amounts are shown with the currency symbol prefix.
Field Name Field Name (Spanish) Value Comment

(English)
Page N of M Página N de M Page number Page number
Payment Receipt Recibo de Pago CashHead.CheckRef Type of the document
Folio Fiscal Folio Fiscal CashHead.MXFiscalFolio Fiscal Folio (UUID)
Payment Method Método de pago CashHead.PMUID -> Payment Method (PUE,
PayMethod.MXPaidAs + " - " + PPD)
{"MXPaymMeth" UD
Dictionary}.CodeDesc
Epicor ERP | 10.2.400 105


(English)
Form of Payment Forma de pago CashHead.PMUID -> Form of Payment
PayMethod.MXSATCode + " - " +
{"MXPaymForm" UD
Dictionary}.CodeDesc
Currency Moneda CashHead.ReceiptCurrencyCode -> Cash Receipt Currency
Currency.CurrencyID
Certificate Serial No de serie del CashHead.MXCertificateSN Certificate number for
Number Certificado del CSD issuing party
Place and Date Lugar, fecha y hora de {Municipio} + " " + Current date and Place and issue date
emisión time in the format
YYYY-MM-DDThh:mm:ss. {Municipio}
=
• Plant.MXMunicipio in case the
switch is activated;
• Company .MXMunicipio in the
other case.
Issued by Expedido en CashHead.Plant -> Plant.Name+" "+ Address of issuing party (in
CashHead.Plant -> Plant.Address1+" case the company has more
"+ CashHead.Plant -> than one plant where
Plant.Address2+" "+ CashHead.Plant invoices are issued)
-> Plant.Address3+" "+
CashHead.Plant -> Plant.City+" "+
CashHead.Plant -> Plant.State+" "+
CashHead.Plant -> Plant.Zip+" "+
CashHead.Plant -> Plant.CountryNum
-> Country.Description
Issuer Emisor N/A Issuer
N/A N/A Company.Name Company name
Tax ID Emisor Company.StateTaxId Tax ID of the issuing party
N/A Company.Address1 +" "+ Company address
Company.City +" "+ Company.State
+" "+ Company.ZIP +" " +
Company.Country ->
Country.Description
Tax Regime Régimen fiscal InvcDtl (any record related to current Tax regime
Receipt).InvoiceNum ->
InvcHead.MXTaxRegime ->
MXTaxRegime.TaxRegime + " - " +
MXTaxRegime.Description
Recipient Receptor N/A Recipient
106 Epicor ERP | 10.2.400


(English)
N/A N/A Legal name of the recipient
• CashHead.CustNum ->
Customer.LegalName in case
Customer.LegalName <> empty
string;
• CashHead.CustNum ->
Customer.BTName in case
Customer.LegalName = empty
string.
Tax ID RF C CashHead.CustNum -> Tax ID of the recipient

Customer.ResaleID
N/A N/A CashHead.CustNum -> Recipient's address
Customer.BTCity +" "+
Customer.BTState +" "+
Customer.BTZIP +" "+
Customer.BTCountryNum ->
Country.Description
Bank Banco CashHead.MXBankID -> Bank Information
CustBank.LegalName + " " +
CashHead.MXBankID ->
CustBank.BankAcctNumber
Serie-Folio Serie-Folio InvcDtl.InvoiceNum -> Invoice Legal Number
InvcHead.LegalNumber
UUID UUID InvcDtl.InvoiceNum -> Invoice UUID
InvcHead.MXFiscalFolio
Payment Method Método de pago CashDtl.InvoiceNum -> Payment Method
InvcHead.PMUID ->
PayMethod.MXSATCode
Installment Parcialidad InvcDtl.MXPaymentNum Number of installment
Currency Moneda InvcDtl.InvoiceNum -> Invoice Currency
InvcHead.CurrencyCode ->
Currency.CurrencyID
Exch Rate Tipo de Cambio 1/ Exchange rate from Invoice
CashHead.SettlementExchangeRate10D Currency to Cash Receipt
rounded to 6 decimals Currency on Payment Date
Previous Bal Saldo Anterior InvcDtl.InvoiceNum -> Previous Invoice Balance (in
InvcHead.DocInvoiceBal + the Invoice Currency)
CashDtl.DocTranAmt (with currency
symbol from the field 11)
Remaining Bal Saldo Insoluto InvcDtl.InvoiceNum -> Remaining Invoice Balance
InvcHead.DocInvoiceBal (with currency (in the Invoice Currency)
Epicor ERP | 10.2.400 107


(English)
Payment Amt Imp Pagado CashDtl.DocTranAmt - Payment Amount (in the
CashDtl.DocDiscount (with currency Invoice currency)
Settlement Amount CashHead.DocTranAmt (with currency Total Settlement Amount
symbol form the field 11) in the Invoice currency
Total Total CashHead.ReceiptAmt (with currency Total Receipt Amount in
symbol from the field 3.3) the Cash Receipt currency
Total amount Total con letra Value from the Field 16.2 printed as Total Receipt Amount in
text (amount is printed in the Cash words in the Cash Receipt
Receipt currency (field 3.3)) currency
Exchange Rate Tipo de Cambio CashDtl.ExchangeRate (First CashDtl Exchange Rate from the
record corresponding to the Cash Cash Receipt's Currency to
Receipt should be used) the Base Currency on
Payment Date
Related CFDIs CFDI relacionados "04 - " + {"MXRelType" UD Type of relation
Dictionary}.CodeDesc for the code
"04". The field is printed only if the
next field is NOT empty.
N/A N/A CashHead.MXOriginalCheckRef if the UUID of the Referenced
value <> Empty string Cash Receipt
Digital Seal Sello digital del CFDI CashHead.MXDigitalSeal Digital seal of the issuing
party
SAT Seal Sello del SAT CashHead.MXSATSeal SAT Seal
N/A N/A QR code image generated after Cash QR Code. Printed in a
Receipt posting square with sides no
smaller than 2.75cm each
(about 1.08 inches)
TFD Original string Cadena original del CashHead.MXOriginalStringTFD Original string
complemento de
certificación digital del
SAT
SAT Certificate No de Serie del CashHead .MXSATCertificateSN Certificate number for SAT
Number Certificado del SAT
Date and Time of Fecha y hora de CashHead.MXCertifiedTimestamp Date and time of the
Certification certificación invoice certification
This document is a Este documento es N/A Label
printed una representación
representation of a impresa de un CFDI
CFDI
108 Epicor ERP | 10.2.400

Print Cash Receipt Payment Supplement Report
Use these steps to print a digital Cash Receipt Payment Supplement Report.
1. Navigate to Cash Receipt Tracker.

Menu Path: Financial Management > Accounts Receivable > General Operations > Cash Receipt Tracker
2. Click the Check button to select a cash receipt. Make sure that you select a posted cash receipt.
3. From the Actions menu, select Print Digital Receipt. The Mexico Payment Supplement Report dialog
displays.
4. In the Report Style field, select Standard MX - SSRS.
5. Optionally, modify the additional report options, such as Schedule, Archive Period, and User Description.
6. Click Print Preview to view the report on the screen.
Reports
Use the Reports topic for instructions on accessing and processing reports specific to Mexico.
Note Refer to the Setup topics to configure the Mexico CSF before completing the procedures in the
Report topics.
You can access the following localization reports from Epicor ERP:
• DIOT Report MX
• List of Accounts MX Report
• Trial Balance MX Report
• GL Journals MX Report
• Folio Number's Auxiliary (Report E)
• Account's Auxiliary (Report F)
• Withholding Tax Certificate Report
Important Notes on Accounts and Payment Method Types

GL Account Concept
Users are responsible for the proper assignment of the concept codes to GL accounts according to SAT catalog.
Menu Path: Financial Management> General Ledger> Setup> General Ledger Account (the Mexico sheet)
Hierarchy of the Chart of Accounts
Users are responsible for the proper creation of the GL accounts hierarchy so that accounts are correctly shown
in the List of Accounts MX and Trial Balance MX reports. This means that for each account located on level N (N
>= 2) it is necessary to create a parent account located on level N-1 of the catalog (chart of accounts).
Epicor ERP | 10.2.400 109

In the following example GL account A is considered as a parent for GL account B since:

• the last significant segment of B is segment 3 (the significant segment contains a value which differs from
the sequence of 0 characters or empty string)
• the last significant segment of A is segment 2. Segments 3 and 4 contain either empty strings or sequences
of 0 characters (the number of 0 characters in the segment must be equal to minimum length of the segment)
• Segments 1 and 2 of accounts A and B are equal
• Only controlled segments are considered.
GL account Segment 1 Segment 2 Segment 3 (min. length = Segment 4

2)
A (parent) 1001 001 00 or empty string 00 or empty string
B (child) 1001 001 0002 00
Payment Method Type

Users are responsible for the proper specification of the AP payment methods types so that corresponding
payments are correctly shown in GL Journals MX report.
Menu Path: Financial Management> Accounts Payable> Setup> Payment Method (the Mexico sheet)
DIOT Report MX
Use DIOT Report MX to access the DIOT auxiliary tax report specific to Mexico. This report is only available after
you complete the Setup - Mexico Localization topics in this guide.
Records in the reports will be sorted by Supplier/Bank account and then by Tax Category in the following fixed
order:
• IVA 0%
• IVA 16%
• IMP 0%
• IMP 16%
• RET 16%
• Dev/Desc. (Debit Memo)
The following is an example of the report layout:
110 Epicor ERP | 10.2.400

You can also generate this report in a TXT format. The following is an example of the report generated in the
TXT format:
Menu Path: Financial Management > Accounts Payable > Reports > DIOT Report MX
Create a DIOT Report MX
1. Navigate to DIOT Report MX.

Menu Path: Financial Management > Accounts Payable > Reports > DIOT Report MX
2. In the Fiscal Year field and Fiscal Period fields, enter the appropriate values for which you want to run
the report.
3. The Standard MX - SSRS report style is selected by default.
4. If you wish to generate this report through a regular, automatic schedule, select an option from the Schedule
drop-down list, then select the Recurring check box. This indicates that each time the system clock activates
this schedule, the report will automatically generate.
Tip You create the schedules within System Agent Maintenance. You can create Interval schedules
that activate after a certain number of minutes/hours, as well as daily, weekly, and monthly schedules.
Epicor ERP | 10.2.400 111

5. From the Archive Period drop-down list, enter how long you wish this report to remain available after it
generates by selecting an option. As long as the system clock has not passed this time span, the report is
available on the server to preview and print.
6. To help identify this run of the report, enter text in the User Description field. This User Description text
displays in the System Monitor to help you locate an archived report.
7. If the report style generates an SSRS report, it may have a routing rule; the routing rule determines how the
report output generates, prints, and distributes. If the style has a rule, the Routing check box is selected.
To shut off this rule, clear the Routing check box.
8. Before you print the report, you can select the Output Format option that you wish to use from the drop-down
list.
9. Click the Print Preview button to preview the report on your screen before printing it out or saving it as
an electronic file.
10. To print the report, click the Print button. A menu displays with the Server Printer and Client Printer
options.
• Server Printer - Sends the report to an SSRS printer available on your network.
• Client Printer - Sends the report to a printer connected to your local machine.
Depending on which option you select, either the SSRS Printer or SSRS Client Printer window displays.
Use the sheets on these windows to select the printer and other print output options. You can also use
these windows to send the report as an e-mail attachment or a fax.
11. If you want to generate a report in a TXT format, click Generate Only.
The TXT file is generated and saved to \\<localhost>\EpicorData\Companies\<company
name>\MXDIOTNNNNPP.txt, where NNNN is the fiscal year and PP is the fiscal period (if it is a one-character
period, the format will be MXDIOTNNNNP.txt).
12. Exit DIOT Report MX.
List Of Accounts MX Report
Use the List Of Accounts MX Report to generate an .xml file with the list of accounts required by SAT (Mexican
Tax Agency).
The file is named {Company.StateTaxId} + {Fiscal Year} + {Fiscal Period} + CT.xml.
Example For a company with Tax ID ESC840101JQ7 in February 2017, the file name will be
ESC840101JQ7201702CT.xml.
The generated XML file is valid against the CatalogoCuentas_1_3.xsd schema and uses the following mapping
between XML attributes and Epicor values.
The report shows all active accounts which are present in the application now. Using the Fiscal Year, Fiscal
Suffix, and Fiscal Period parameters, you cannot get a list of accounts that were available in the previous time
periods. These parameters only allow you to set up correct date of the report. Thus, it is possible to change the
year and month presented in the XML in case the report must be dated with the date from the previous periods.
112 Epicor ERP | 10.2.400

The Level of inactive flag validation field specifies which accounts will be considered as inactive by the
application. By default, this parameter is set to 3.
• If the account level is less than this parameter value, the application does not consider the Inactive check
box in this account as selected. This account information will be shown in the report unless other restrictions
are applied (refer to the Level of printed accounts field description).
• If the account level is equal or greater than this parameter value, the application considers the Inactive check
box in this account as selected. This account information will not be shown in the report.
The Level of printed accounts field specifies which accounts will be shown in the report. Only accounts whose
level is equal or less than this field's value will be shown. By default, this parameter is set to 3.
XML attribute Value Comment

<Catalogo> Chart of accounts that is delivered as part
of the Electronic Accounting
<Catalogo/Version> 1.3 Format version
<Catalogo/RFC> Company.StateTaxId The RFC of the taxpayer that sends data
<Catalogo/Mes> Current period specified as incoming Selected period
parameter in format MM
<Catalogo/Anio> Fiscal year in the YYYY format Fiscal year
<Catalogo/Ctas> Each <Ctas> element corresponds to one GL Details of each account (required).
account retrieved. All active accounts
(GLAccount.Active = 1) from specified Chart
of Accounts are retrieved.
<Ctas/CodAgrup> GLAccount.MXConcept The grouping code according to the
catalog published by the SAT. Each
account should be grouped in the
corresponding concept.
<Ctas/NumCta> GLAccount.GLAccount The key with which the account is
recognized in the accounts (required).
<Ctas/Desc> GLAccount.AccountDesc The name of the account.
<Ctas/SubCtaDe> Parent sub-account for the current
If N is the level of the current account (see
sub-account (optional).
business rule B1), then the parent account
from N-1 level is shown here (see business
rule B2).
If parent account is NOT found, then the
attribute is not created.
If the account has level N = 1, then the
attribute is not created.
<Ctas/Nivel> Account's level (see business rule B1). The level at which the account is located
in the catalog.
Epicor ERP | 10.2.400 113


<Ctas/Natur>
• D if COASegValues.NormalBalance = D The nature of the account or sub-account.
[COASegValues.SegmentCode = (D - Debtor, A - Creditor).
GLAccount.SegValue1];
(Active = D)
• A if COASegValues.NormalBalance = C
[COASegValues.SegmentCode = (Liabilities = A)
GLAccount.SegValue1];
(Capital = A)
Empty string in other cases.
(Income = A)
(Cost = D)
(Expense = D)
(Comprehensive Financing = D and / or A)
(Memorandum accounts = D and / or A).
Note All active accounts (GLAccount.Active = 1) from the specified Chart of Accounts are retrieved.
Business rule B1. Definition of the GL Account's level

Level of the GL Account is the number of its last (maximum) significant segment. Significant segment is the
segment, which value:
1. differs from the string containing only 0 characters AND
2. differs from the empty string
The segment is not a significant one if:
1. its value is an empty string OR
2. Its value is a sequence of 0 characters
Example. All the segments have minimum length = 2.
Accounting string Level

1001-00-00-00 1
1001--- 1
1001--ABC-00 3
1001--ABC-0000 3
1001-01-000-01 4
1001-01--01 4
Business rule B2. Definition of the parent GL Account

rd
For example, the current sub-account is 1111-22-001-000, its level N = 3. Minimum length of the 3 segment
is 2.
To define the parent account, the application initially attempts to find the account 1111-22--- where the values
of all segments N>=3 are empty strings. If such an account is found, it is considered as parent.
114 Epicor ERP | 10.2.400

If such an account is not found, the application initially attempts to find the account 1111-22-00-00, where the
values of all segment N>=3 are replaced with one or several 0 characters (number of 0 characters equals the
minimum length of the segment, 2 in the current case). If such an account is found, it is considered as parent;
otherwise, it is supposed that a parent account does not exist. For sub-accounts with level = 1, it is supposed
that no parent account exists.
Menu Path: Financial Management > General Ledger > Reports > List Of Accounts MX
Selection Fields
Mexico List Of Accounts

Chart Of Accounts
Specifies a chart of accounts used as a basis for the report.
Fiscal Period
Specifies fiscal period for the report.
Fiscal Year
Specifies fiscal year for the report.
Fiscal Year Suffix

Specifies fiscal year suffix for the report.
Output Directory
Specifies the path to the report file.
Output Directory...
Click this button to browse to a folder where you want to save the generated report file.
Create a List Of Accounts MX Report

To create a List Of Accounts MX report:
1. Navigate to Mexico List of Accounts.

Menu Path: Financial Management > General Ledger > Reports > List Of Accounts MX
2. Select appropriate options in the report fields.

Review the Selection Fields topic for report parameter details.
3. In the Level of inactive flag validation field, specify the number of levels.
If the account level is less than this parameter value, the application doesn't consider the Inactive checkbox
in this account as selected. This account is printed in the report.
If the account level is equal or greater than this parameter value, the application considers the Inactive
checkbox in this account as selected. An inactive account is not printed in the report.
Epicor ERP | 10.2.400 115

4. To save these report options as the default values for the current report, click the Actions > Save Defaults.
The next time you launch this report window, the values you defined on the Selection sheet display.
5.
If you wish to print several reports on a recurring schedule, click the Save Process Set ( ) button to
add the report as a task on a process set.
Within the process set, you can define the order in which these tasks run and then schedule when the
process set activates. You set up this sequence within Process Set Maintenance.
6. Click the Process button to generate the report.
Trial Balance MX Report
Use the Trial Balance MX Report to generate an .xml file with the trial balance required by SAT (Mexican Tax
Agency).
The file is named {Company.StateTaxId} + {Fiscal Year} + {Fiscal Period} + {Type}.xml where {Type} is:
• BN for a new report.
• BC for a revised report.
Example For a company with Tax ID ESC840101JQ7 in February 2017, the file name for a new trial balance
will be ESC840101JQ7201702BN.xml.
The generated XML file is valid against the BalanzaComprobacion_1_3.xsd schema and uses the following mapping
between XML attributes and Epicor values.
The Trial Balance MX report does not show a dynamic segment in the accounting string only if the Include in
summary balance flag is set to FALSE for the segment.
The balances are represented correctly only if the Include in summary balance flag is set to TRUE for controlled
segments.
The Level of printed accounts field specifies which accounts will be shown in the report. Only accounts whose
level is equal or less than this field's value will be shown. By default, this parameter is set to 3.

<Balanza> Trial balance that comes as part of
the Electronic Accounting
<Balanza /Version> 1.3 Format version
<Balanza /RFC> Company.StateTaxId The RFC of the taxpayer that sends
data
<Balanza/Mes> End period specified as incoming parameter in Selected ending period
the MM format
<Balanza/Anio> Fiscal year in the YYYY format Selected year
116 Epicor ERP | 10.2.400


<Balanza/TipoEnvio> The balance type:
• N - if there is no MXTrialBalInfo record
corresponding to the current report or the • N (Normal) - a new Trial Balance
Print as New check box is selected. for the selected period.
• C - in other cases. • C (Complementary) - A revised
version of an already sent Trial
Balance for the selected period.
<Balanza/FechaModBal> The last date of balance change (in the The date of the last accounting
YYYY-MM-DD format), if <Balanza/TipoEnvio> change in the balance. It is required
is C. when <TipoEnvio> is C
The attribute is not created in other cases.
The last date of balance change is calculated as
equal to the latest posted date among the
records that have the Company, Book ID, Fiscal
Year, and Fiscal Period fields corresponding to
the report parameters (the Fiscal Period field is
compared with the End Fiscal Period parameter).
<Balanza/Ctas> Each <Ctas> element corresponds to one GL The details of each accounting
account retrieved. All accounts from Chart Of balance (required)
Accounts linked to the specified Book are
retrieved.
<Ctas/NumCta> GLAccount.GLAccount
Account or sub-account
<Ctas/SaldoIni> For account's opening balance, refer to the

The amount of the opening balance
Financial Management > General Ledger >
of the account or sub-account in the
Reports > Trial Balance report. This value should
selected period
be multiplied by -1 if GLAccount.SegValue1 ->
COASegValues.NormalBalance = C (credit
account).
<Ctas/Debe> For account's debit movements, refer to the
The amount of debit movement on
Financial Management > General Ledger >
the account or sub-account during
Reports > Trial Balance report.
the selected period
<Ctas/Haber> For account's credit movements, refer to the The amount of credit movement on
Financial Management > General Ledger > the account or sub-account during
Reports >Trial Balance report. This value should the selected period
COASegValues.NormalBalance = C (credit
account).
<Ctas/SaldoFin> For account's closing balance, refer to the The amount of the closing balance of
Financial Management > General Ledger > the account or sub-account in the
Reports > Trial Balance report. This value should selected period.
COASegValues.NormalBalance = C (credit 1. For debit account CB = opening
account). balance + debit movement -
credit movement;
Epicor ERP | 10.2.400 117


2. For credit account CB = opening
balance - debit movement +
credit movement.
For each exposed GL account (account A) parent account should be defined (see Business Rule B2 in the List of
Accounts MX Report section). If the parent account is found (account B), then value of its open balance, close
balance, debit and credit movement are increased with corresponding values from account A. As a result, after
processing of all child accounts, the parent account B will show summarized values of its child.
Menu Path: Financial Management > General Ledger > Reports > Trial Balance MX
Selection Fields
Mexico Trial Balance

Book
Specifies the book used as a basis for the report. The default is the main book for the company.
Ending Fiscal Period

Specifies the end of the reporting period.
Fiscal Year
Specifies the fiscal year used as a basis for the report. The current year displays by default.
Output Directory
Output Directory...
Print as New
Select this check box to print a report as new. If you leave this check box clear, the type of report is defined
automatically. If <Balanza/TipoEnvio> is N, the report is new. If <Balanza/TipoEnvio> is C, the report
is revised.
The following table shows possible business scenarios.
118 Epicor ERP | 10.2.400

Scenario Result
You print the Trial Balance for the current period for the
• <Balanza/TipoEnvio> is shown as N.
first time.
• <Balanza/FechaModBal> is not present in the
Print as New is clear.
XML.
• <Balanza/TipoEnvio> is shown as C.
second or third time.
• <Balanza/FechaModBal> shows the posting
Print as New is clear.
date of the last GL transition.
• <Balanza/TipoEnvio> is shown as N.
second or third time.
• <Balanza/FechaModBal> is not present in the
Print as New is selected.
XML.
Starting Fiscal Period

Specifies the start of the reporting period.
Year Suffix
Specifies a fiscal year suffix, if one exists.
Create a Trial Balance MX Report

To create a Trial Balance MX report:
1. Navigate to Mexico Trial Balance.

Menu Path: Financial Management > General Ledger > Reports > Trial Balance MX
2. Select appropriate options in the report fields.

Review the Selection Fields topic for report parameter details.
4.
Epicor ERP | 10.2.400 119

GL Journals MX Report
Use the GL Journals MX Report to generate an .xml file with GL journals information required by SAT (Mexican
Tax Agency).
Select the Folio Number's Auxiliary check box to generate the Folio Number's Auxiliary (E) report along
with GL journals.
Select the Account's Auxiliary check box to generate the Account's Auxiliary (F) report along with GL journals.
The application generates an XML file named {Company.StateTaxId} + {Fiscal Year} + {Fiscal Period} + PL.xml.
ESC840101JQ7201702PL.xml.
The GLJrnDtl record can be linked with different entities through the TranGLC table. The identifier of a linked
entity is stored in the Key1…Key6 table fields. The type of linked entity is defined based on the value of the
TranGLC.RelatedToFile field according to the following map:
Related entity Value of the TranGLC.RelatedToFile field

AR Invoice (InvcHead table) InvcHead
AR Invoice Line (InvcDtl table) InvcDtl
AP Invoice (APInvHed table) APInvHed
AP Invoice Line (APInvDtl table)
APInvExp
Key1 = Supplier Number;
Key2 = Invoice Number;
Key3 = Line Number.
Part Transaction (PartTran table) PartTran
The generated XML file should be valid against the PolizasPeriodo_1_3.xsd schema. The following table shows
the mapping between XML attributes and Epicor values.

<Polizas> Policies that
come as part of
the Electronic
Accounting
<Polizas/@Version> 1.3 Format version
<Polizas/@RFC> Company.StateTaxId The RFC of the
taxpayer sending
data
<Polizas/@Mes> End period specified as incoming parameter in the MM The month
format corresponding to
the end period
<Polizas/@Anio> Fiscal year in the YYYY format The year
corresponding to
the end period
120 Epicor ERP | 10.2.400


<Polizas/@TipoSolicitud> 2-letter code specified as the Journal Type report's Journal type:
parameter
• AF - Control
Act
• FC - Audit
• DE -
Returning
• CO -
Compensation
<Polizas/@NumOrden> A serial number

Value of the Serial Number report's parameter in case
assigned to the
<TipoSolicitud>= AF or FC
report in case the
The attribute is not created in other cases. Journal Type is AF
or FC
<Polizas/@NumTramite> A serial number
Value of the Serial Number report's parameter in case
assigned to the
<TipoSolicitud>= DE or CO
report in case the
The attribute is not created in other cases. Journal Type is
DE or CO
<Polizas/Poliza> <Poliza> element corresponds to GLJrnDtl records grouped Details of each
by FiscalYear + FiscalPeriod + JournalCode + JournalNum. Journal (required)
Several GLJrnDtl records are retrieved according to
parameters specified for the report.
<Poliza/@NumUnIdenPol> {CC} + GLJrnDtl.JournalNum + GLJrnDtl.JournalCode The unique
number of the
{CC} =
Journal
• IN in case GLJrnHed.JournalCode -> JrnlCode.MXPolicy
= 1;
• EG in case GLJrnHed.JournalCode -> JrnlCode.MXPolicy
= 2;
• DR in case GLJrnHed.JournalCode -> JrnCode.MXPolicy
= 3.
<Poliza/@Fecha> GLJrnDtl.JEDate Registration date

of the Journal
<Poliza/@Concepto> The concept of
Depending on GLJrnHed.JournalCode:
the operation
• SJ (Sales Journal):
• = NC- + GLJrnDtl.Description for Credit Memo;
• = FACT- + GLJrnDtl.Description for other cases;
• PJ (Purchase Journal): =
FACT- + GLJrnDtl.Description;
• CR (Cash Receipt Journal): =
COBRO- + GLJrnDtl.Description;
• CD (Cash Disbursement Journal): =
Epicor ERP | 10.2.400 121


PAGO- + GLJrnDtl.Description;
• Other cases: = GLJrnDtl.Description.
<Poliza/Transaccion> <Transaccion> element corresponds to one GLJrnDtl record Details of each

transaction
within the
Journal
<Transaccion/@NumCta> The number of
GLJrnDtl.GLAccount
the account or
Dynamic segments are NOT exposed subaccount that
is affected by the
transaction
<Transaccion/@DesCta> GLJrnDtl.GLAccount -> GLAccount.AccountDesc The name of the
account or
subaccount that
is affected by the
transaction
<Transaccion/@Concepto> The concept of
Depending on GLJrnHed.JournalCode:
the transaction
• SJ (Sales Journal):
= InvcDtl.SellingShipQty + " " +
+ InvcDtl.SalesUM + " " +
+ InvcDtl.PartNum + " " +
+ InvcDtl.LineDesc;
• PJ (Purchase Journal):
= APInvDtl.VendorQty + " " +
+ APInvDtl.PUM + " " +
+ APInvDtl.PartNum + " " +
+ APInvDtl.Description
• IJ (Inventory Journal):
= PartTran.TranQty + " " +
+ PartTran.UM + " " +
+ PartTran.PartDescription + " " +
+ PartTran.TranReference;
• CR (Cash Receipt Journal):
= COBRO- + GLJrnDtl.Description;
• CD (Cash Disbursement Journal):
= PAGO- + GLJrnDtl.Description;
• Other cases:
= GLJrnDtl.Description
122 Epicor ERP | 10.2.400


<Transaccion/@Debe> GLJrnDtl.BookDebitAmount The debit amount
of the account
for the
transaction (in
the base
currency)
<Transaccion/@Haber> GLJrnDtl.BookCreditAmount The credit
amount of the
account for the
transaction (in
the base
currency)
<Transaccion/CompNal> The node is created only for the first GLJrnDtl record sorted Details of the
by GLJrnDlt.JournalLine. Document
related to CFDI
transaction
• InvcHead.MXFiscalFolio <> "" for AR invoice or (optional)
• APInvcHed.MXFiscalFolio <> "" for AP invoice or

• CashHead.MXFiscalFolio <> "" in case there is a related
cash receipt or
• CheckHed.MXFiscalFolio <> "" in case there is a related
AP Payment or
• GLJrnHed.MXFiscalFolio <> "" for other cases.
<CompNal/@UUID_CFDI> UUID of the CFDI

related
APInvHead.MXFiscalFolio
CashHead.MXFiscalFolio
CheckHed.MXFiscalFolio
GLJrnHed.MXFiscalFolio
<CompNal/@RFC> Customer/Supplier
Customer.ResaleID
Tax ID
Vendor.TaxPayerID
Customer.ResaleID
Vendor.TaxPayerID
GLJrnHed.MXRFC
<CompNal/@MontoTotal> Document
amount
APInvHed.DocInvoiceAmt
CashHead.DocTranAmt
CheckHed.DocCheckAmt
GLJrnHed.TotDebit
Epicor ERP | 10.2.400 123


<CompNal/@Moneda> The foreign
• [InvcHead.CurrencyCode/APInvHed.CurrencyCode] -> currency used in
Currency.CurrencyID in case a currency that differs from the Invoice
the base currency is used; according to SAT
• CashHead.ReceiptCurrencyCode/CheckHead.CurrencyCode catalog
-> Currency.CurrencyID in case the currency differs from
the base currency.
• The attribute is not created if the base currency is used
or there is no linked AR/AP invoice.
<CompNal/@TipCamb> The exchange

• InvcHead.ExchangeRate/APInvHed.ExchangeRate in case rate for the
a currency that differs from the base currency is used; foreign currency
• CashHead.ExchangeRate/CheckHed.ExchangeRate in
case the currency differs from the base currency.
• The attribute is not created if the base currency is used
or there is no linked AR/AP invoice.
<Transaccion/CompNalOtr> Details of a
The node corresponds to AP/AR Invoice related to GLJrnDtl
national Invoice
via TranGLC with APInvHed or InvcHead in
related to the
TranGLC.RelatedToFile. The node is created only for the
transaction other
first GLJrnDtl record sorted by GLJrnDlt.JournalLine.
than CFDI
The node is created if: (optional)
• InvcHead.MXFiscalFolio = "" for AR Invoice,
APInvcHed.MXFiscalFolio = "" for AP Invoice
AND
• Customer's BillTo Country ID/ Supplier's country ID =
Company's country ID
<CompNaOtrl/@CFD_CBB_Serie> CFD CBB Seria

InvcHead.MXSerie/APInvHed.MXSerie
(optional)
<CompNaOtrl/@CFD_CBB_NumFol> CFD CBB Folio
InvcHead.MXFolio/APInvHed.MXFolio
Number
(required)
<CompNaOtrl/@RFC> Customer/Supplier
Customer.ResaleID/Vendor.TaxPayerID
Tax ID
<<CompNaOtrl/@MontoTotal> Invoice amount
InvcHead.DocInvoiceAmt/APInvHed.DocInvoiceAmt
124 Epicor ERP | 10.2.400


<CompNaOtrl/@Moneda> The foreign
the base one is used; according to SAT
• The attribute is not created if the base currency is used. catalog
<CompNaOtrl/@TipCamb> The exchange

the currency which differs from the base one is used; foreign currency
• The attribute is not created if the base currency is used.
<Transaccion/CompExt> The node corresponds to AP/AR Invoice related to GLJrnDtl Details of a

via TranGLC with "PInvHed or InvcHead in foreign invoice
TranGLC.RelatedToFile. The node is created only for the related to the
first GLJrnDtl record sorted by GLJrnDlt.JournalLine. transaction
(optional)
AND
• Customer's BillTo country ID/ Supplier's country ID <>
Company's country ID
<CompExt/@NumFactExt> InvcHead.InvoiceNum/APInvHed.InvoiceNum Invoice number

<CompExt/@TaxID> Customer/Supplier
Customer.FederalID/Vendor.TaxPayerID
Tax ID
<CompExt/@MontoTotal> Invoice amount
<CompExt/@Moneda> The foreign

the base one is used; according to SAT
• The attribute is not created if the base currency is used. catalog
<CompExt/@TipCamb> The exchange

the currency which differs from the base one is used; foreign currency
<Transaccion/Cheque> Details of the

The element corresponds either to:
linked check.
• AP Payment (the record linked to GLJrnDtl via Payment
TranGLC.RelatedToFile = CheckHed) or methods must be
• AR Cash Receipt (TranGLC.RelatedToFile = CashHead). set up according
to SAT
CheckHed/CashHead record must meet the following classification
criteria:
CheckHed.PMUID/CashHead.PMUID ->
PayMethod.MXSATCode = 02 (Check)
Epicor ERP | 10.2.400 125


<Cheque/@Num> CheckHed.CheckNum Payment Check
Number
CashHead.CheckRef
<Cheque/@BanEmisNal> CheckHed.BankAcctID -> BankAcct.MXSATCode Identifier of the

national issuing
CashHead.MXBankID -> CustBank.MXSATCode
Bank according
to SAT catalog
<Cheque/@BanEmisExt> Full name of the
• CheckHed.BankAcctID -> BankAcct.BankName in case foreign issuing
CheckHed.BankAcctID -> BankAcct.MXSATCode = 999 bank
• The attribute is not created if BankAcct.MXSATCode<>
999.
• CashHead.MXBankID -> CustBank.BankName in case
CashHead.MXBankID -> CustBank.MXSATCode = 999
• The attribute is not created if CustBank.MXSATCode <>
999.
<Cheque/@CtaOri> CheckHed.BankAcctID -> BankAcct.CheckingAccount Bank Account

Number
CashHead.MXBankID -> CustBank.BankAcctNumber
<Cheque/@Fecha> CheckHed.CheckDate Date of the check

CashHead.TranDate
<Cheque/@Monto> CheckHed.DocCheckAmt Amount

CashHead.ReceiptAmt
<Cheque/@Benef> CheckHed.VendorNum -> Vendor.Name Beneficiary name

for the cheque
Company.Name
<Cheque/@RFC> CheckHed.VendorNum Tax ID related to

the movement
• Vendor.TaxPayerID if a supplier is specified;
• CheckHed.MXRFC otherwise.
• CashHead.CustNum -> Customer.ResaleID in case the
customer is specified.
• CashHead.MXRFC otherwise.
126 Epicor ERP | 10.2.400


<Cheque/@Moneda> The foreign
• CheckHed.CurrencyCode -> Currency.CurrencyID in case currency used in
a currency that differs from the base currency is used; the Check
• CashHead.CurrencyCode-> Currency.CurrencyID in case according to SAT
the currency differs from the base currency; catalog
<Cheque/@TipCamb> The exchange

• CheckHed.ExchangeRate in case a currency that differs rate for the
from the base currency is used; foreign currency
• CashHead.ExchangeRate in case the currency differs
from the base currency;
<Transaccion/Transferencia>
The element corresponds either to: Details of an
electronic
• AP Payment (the record linked to GLJrnDtl via payment.
TranGLC.RelatedToFile = CheckHed) or Payment
• AR Cash Receipt (TranGLC.RelatedToFile = CashHead) methods must be
or set up according
• Bank Funds Transfer (TranGLC.RelatedToFile = BankTran). to SAT
classification
CheckHed/CashHead record must meet the following
criteria:
PayMethod.MXSATCode = 03 (Transfer)
Epicor ERP | 10.2.400 127


<Transferencia/@CtaOri> Source account
• CheckHed.BankAcctID -> BankAcct.CheckingAccount from which the
• CashHead.MXBankID -> CustBank.BankAcctNumber funds are
• BankTran.BankAcctID of the record having transferred
BankTran.TranAmt < 0
<Transferencia/@BancoOriNal> Identifier of the

• CheckHed.BankAcctID -> BankAcct.MXSATCode national original
• CashHead.MXBankID -> CustBank.MXSATCode Bank according
• BankTran.BankAcctID (where BankTran.TranAmt < 0) to SAT catalog
-> BankAcct.MXSATCode
<Transferencia/@BancoOriExt> Full name of the

• CheckHed.BankAcctID -> BankAcct.BankName in case foreign original
CheckHed.BankAcctID -> BankAcct.MXSATCode = 999 bank
999.
• CashHead.MXBankID -> CustBank.BankName in case
CustBank.MXSATCode = 999;
• The attribute is not created if CustBank.MXSATCode <>
999.
• BankTran.BankAcctID (where BankTran.TranAmt < 0)
-> BankAcct.BankName in case BankAcct.MXSATCode
= 999.
999.
<Transferencia/@CtaDest> Destination
• CheckHed.VendorBankID -> VendBank.BankAcctNumber account number,
in case the Supplier is specified. which receives
• CheckHed.MXBankAcctNumber otherwise. resources
• CashHead.BankAcctID -> BankAcct.CheckingAccount. (required)
• BankTran.BankAcctID (where BankTran.TranAmt > 0)
-> BankAcct.CheckingAccount.
Note The supplier's bank should be flagged as
primary bank
<Transferencia/@BancoDestNal> Identifier of the

• CheckHed.VendorBankID -> VendBank.MXSATCode in national target
case the supplier is specified. Bank according
• CheckHed.MXBankIdentifier otherwise. to SAT catalog
• CashHead.BankAcctID -> BankAcct.MXSATCode.
-> BankAcct.MXSATCode.
Note The supplier's bank should be flagged as
primary bank
<Transferencia/@BancoDestExt> Full name of the
128 Epicor ERP | 10.2.400


• CheckHed.VendorBankID -> VendBank.LegalName in foreign target
case Supplier is specified AND VendBank.MXSATCode bank
= 999;
• The attribute is not created if VendBank.MXSATCode
<> 999 or supplier is not specified.
• CashHead.BankAcctID -> BankAcct.LegalName in case
BankAcct.MXSATCode = 999.
• The attribute is not created if BankAcct.MXSATCode <>
999.
-> BankAcct.LegalName in case BankAcct.MXSATCode
= 999.
999.
<Transferencia/@Fecha> CheckHed.CheckDate The date of the

payment
CashHead.TranDate
(required)
BankTran.TranDate (where BankTran.TranAmt > 0).
<Transferencia/@Benef> CheckHed.Name Name of the

beneficiary
Company.Name
associated with
the target
account
(required)
<Transferencia/@RFC> Tax ID related to
• CheckHed.VendorNum -> Vendor.TaxPayerID in case the movement
the Supplier is specified. (required)
Customer is specified.
• Company.StateTaxId
<Transferencia/@Monto> CheckHed.DocCheckAmt The amount

transferred
CashHead.ReceiptAmt.
(required)
BankTran.TranAmt (where BankTran.TranAmt > 0).
Epicor ERP | 10.2.400 129


<Transferencia/@Moneda> The foreign
a currency that differs from the base one is used; the payment
• CashHead.CurrencyCode -> Currency.CurrencyID in case according to SAT
the currency differs from the base one.
• BankTran.CurrencyCode (where BankTran.TranAmt >
0) -> Currency.CurrencyID in case the currency differs
from the base one.
<Transferencia /@TipCamb> The exchange

from the base currency is used. foreign currency
from the base currency.
• BankTran.ExchangeRate (where BankTran.TranAmt >
0).
<Transaccion/OtrMetodoPago>
The element corresponds either to: Details of other
payments.
• AP Payment (the record linked to GLJrnDtl via Payment
TranGLC.RelatedToFile = CheckHed) or methods must be
• AR Cash Receipt (TranGLC.RelatedToFile = CashHead). set up according
to SAT
CheckHed/CashHead record must meet the following
classification.
criterion:
PayMethod.MXSATCode differs from 02 and 03.
<OtrMetodoPago/@MetPagoPol > Payment method

• CheckHed.PMUID -> PayMethod.MXSATCode of operation
• CashHead.PMUID -> PayMethod.MXSATCode according to the
SAT catalog
<OtrMetodoPago/@Fecha > CheckHed.CheckDate The date of the
payment
CashHead.TranDate
(required)
<OtrMetodoPago/@Benef> CheckHed.Name Name of the
beneficiary
Company.Name
associated with
the target
account
(required)
130 Epicor ERP | 10.2.400


<OtrMetodoPago/@RFC> Tax ID related to
• CheckHed.VendorNum -> Vendor.TaxPayerID in case the payment
the supplier is specified. (required)
customer is specified.
<OtrMetodoPago/@Monto> CheckHed.DocCheckAmt The amount

transferred
CashHead.ReceiptAmt
(required)
<OtrMetodoPago/@Moneda> The foreign
a currency that differs from the base one is used; the payment
• CashHead.CurrencyCode -> Currency.CurrencyID in case according to SAT
the currency differs from the base one. catalog
<OtrMetodoPago/@TipCamb> The exchange

from the base currency is used foreign currency
from the base currency
Menu Path: Financial Management > General Ledger > Reports > GL Journals MX
Selection Fields
Mexico GL Journals

Account's Auxiliary
Select this checkbox to generate the Account's Auxiliary (F) report along with GL journals.
Book
Specifies the book used as a basis for the report. The default is the main book for the company.
Ending Fiscal Period

Specifies the end of the reporting period.
Fiscal Year
Specifies the fiscal year used as a basis for the report. The current year displays by default.
Epicor ERP | 10.2.400 131

Folio Number's Auxiliary

Select this checkbox to generate the Folio Number's Auxiliary (E) report along with GL journals.
Output Directory
Output Directory...
Serial Number
Enter the serial number in accordance with the selected type of journal. The field length must be up to 14
characters.
Starting Fiscal Period

Specifies the start of the reporting period.
Type of Journal
Select the type of journal to generate.
Available options are:
• Control Act
• Audit
• Returning
• Compensation
Year Suffix
Specifies a fiscal year suffix, if one exists.
Create a GL Journals MX Report

To create a GL Journals MX report:
1. Navigate to Mexico GL Journals.

2. In the Fiscal Year, Year Suffix, Starting, and Ending Fiscal Period fields, select required values.
3. In the Book field, select a book.
4. In the Type of Journal field, select a required value.
5. In the Serial Number field, enter a required value.

If the field is blank, a warning message displays.
6. In the Output Directory field, enter a required value.
132 Epicor ERP | 10.2.400

7. Select the Folio Number's Auxiliary check box to generate the Folio Number's Auxiliary (E) report
along with GL journals.
8. Select the Account's Auxiliary check box to generate the Account's Auxiliary (F) report along with GL
journals.
10.
Folio Number's Auxiliary (Report E)
Use the GL Journals MX Report with the selected Folio Number's Auxiliary checkbox to generate Folio
Number's Auxiliary (E) report.
The application generates an XML file named {Company.StateTaxId} + {Fiscal Year} + {Fiscal Period} + XF.xml.
ESC840101JQ7201702XF.xml.
The generated XML file should be valid against the AuxiliarFolios_1_3.xsd schema. The following table shows
the mapping between XML attributes and Epicor values.

<RepAuxFol> Auxiliary report for tax
receipts policies
<RepAuxFol/@Version> 1.3 Format version
<RepAuxFol/@RFC> Company.StateTaxId The RFC of the taxpayer
sending data
<RepAuxFol/@Mes> End period specified as incoming parameter in the The month corresponding
MM format to the end period
<RepAuxFol/@Anio> Fiscal year in the YYYY format The year corresponding to
the end period
<RepAuxFol/@TipoSolicitud> 2-letter code specified as the Journal Type report's Journal type:
parameter
• AF - Control Act
• FC - Audit
• DE - Returning
• CO - Compensation
<RepAuxFol/@NumOrden> A serial number assigned to

Value of the Serial Number report's parameter in
the report in case the
case <TipoSolicitud>= AF or FC
Journal Type is AF or FC
Epicor ERP | 10.2.400 133


<RepAuxFol/@NumTramite> A serial number assigned to
Value of the Serial Number report's parameter in
the report in case the
case <TipoSolicitud>= DE or CO
Journal Type is DE or CO
<RepAuxFol/DetAuxFol> The element corresponds to GLJrnDtl records Details of the tax receipts
grouped by FiscalYear + FiscalPeriod + JournalCode that are included in the
+ JournalNum. Several GLJrnDtl records are Journal
retrieved according to parameters specified for the
report.
<DetAuxFol/@NumUnIdenPol> {CC} + GLJrnDtl.JournalNum + The unique number of the
GLJrnDtl.JournalCode Journal
{CC} =
• "IN" in case GLJrnHed.JournalCode ->
JrnlCode.MXPolicy = 1;
• "EG" in case GLJrnHed.JournalCode ->
• "DR" in case GLJrnHed.JournalCode ->
JrnCode.MXPolicy = 3.
<DetAuxFol/@Fecha> GLJrnDtl.JEDate Registration date of the

Journal
<DetAuxFol/@ComprNal> The node corresponds to AP/AR Invoice related to Details of the Document
GLJrnDtl via TranGLC with APInvHed or InvcHead related to CFDI transaction
in TranGLC.RelatedToFile. (optional)
• InvcHead.MXFiscalFolio <> "" for AR Invoice or
• APInvcHed.MXFiscalFolio <> "" for AP Invoice
or
• CashHead.MXFiscalFolio <> "" in case there is
a related cash receipt or
• CheckHed.MXFiscalFolio <> "" in case there is
a related AP Payments or
• GLJrnHed.MXFiscalFolio <> "" for other cases.
<ComprNal/@UUID_CFDI> UUID of the CFDI related

APInvHead.MXFiscalFolio
CashHead.MXFiscalFolio
GLJrnHed.MXFiscalFolio
<ComprNal/@MontoTotal> Document amount

APInvHed.DocInvoiceAmt
CashHead.DocTranAmt
GLJrnHed.TotDebit
134 Epicor ERP | 10.2.400


<ComprNal/@RFC> Customer/Supplier/Employee
Customer.ResaleID
Tax ID
Vendor.TaxPayerID
Customer.ResaleID for cash receipt
GLJrnHed.MXRFC
<ComprNal/@MetPagoAux> InvcHead.PMUID -> PayMethod.MXSATCode Payment method of

operation according to the
APInvHed.PMUID -> PayMethod.MXSATCode
SAT catalog
CashHead.PMUID -> PayMethod.MXSATCode
The attribute is not created in case of GLJrnDtl.
<ComprNal/@Moneda> The foreign currency used

• [InvcHead.CurrencyCode/APInvHed.CurrencyCode] in the invoice according to
-> Currency.CurrencyID in case a currency that SAT catalog
differs from the base one is used;
• CashHead.ReceiptCurrencyCode ->
Currency.CurrencyID in case the currency differs
from the base one.
• The attribute is not created if the base currency
is used.
<ComprNal/@TipCamb> The exchange rate for the

• InvcHead.ExchangeRate/APInvHed.ExchangeRate foreign currency
in case a currency that differs from the base
currency is used.
• CashHead.ExchangeRate in case the currency
differs from the base currency.
is used.
<DetAuxFol/ComprNalOtr> The node corresponds to AP/AR Invoice related to Details of a national invoice
GLJrnDtl via TranGLC with "APInvHed" or related to the transaction
"InvcHead" in TranGLC.RelatedToFile. other than CFDI (optional)
• InvcHead. MXFiscalFolio <> "" for AR Invoice,
APInvcHed.MXFiscalFolio <> "" for AP Invoice
AND
• Customer's BillTo country ID/Supplier's country
ID = Company's country ID
<ComprNalOtr/@CFD_CBB_Serie> CFD CBB Seria

InvcHead.MXSeries/APInvHead.MXSerias
<ComprNalOtr/@CFD_CBB_NumFol> CFD CBB Folio Number

InvcHead.MXFolio/APInvHead.MXFolio
<ComprNalOtr/@MontoTotal> Invoice Amount

<ComprNalOtr/@RFC> Customer/Supplier Tax ID

Customer.ResaleID/Vendor.TaxPayerID
Epicor ERP | 10.2.400 135


<ComprNalOtr/@MetPagoAux> InvcHead.PMUID/APInvHed.PMUID -> Payment method of
PayMethod.MXSATCode operation according to the
SAT catalog
<ComprNalOtr/@Moneda> The foreign currency used
• [InvcHead.CurrencyCode/APInvHed.CurrencyCode] in the Invoice according to
is used.
<ComprNalOtr/@TipCamb> The exchange rate for the

in case the currency which differs from the base
one is used;
is used.
<DetAuxFol/@ComprExt> Details of a foreign Invoice

The node corresponds to AP/AR Invoice related to
related to the transaction
GLJrnDtl via TranGLC with "APInvHed" or
(optional)
"InvcHead" in TranGLC.RelatedToFile.
AND
• Customer's Bill To country ID/Supplier's country
ID <> Company's country ID
<ComprExt/@NumFactExt> InvcHead.InvoiceNum/APInvHed.InvoiceNum Invoice Number

<ComprExt/@TaxID> Customer/Supplier Tax ID
Customer.FederalID/Vendor.TaxPayerID
<ComprExt/@MontoTotal> Invoice Amount

<ComprNalOtr/@MetPagoAux> InvcHead.PMUID/APInvHed.PMUID -> Payment method of

PayMethod.MXSATCode operation according to the
SAT catalog
136 Epicor ERP | 10.2.400


<ComprExt/@Moneda> The foreign currency used
• [InvcHead.CurrencyCode/APInvHed.CurrencyCode] in the Invoice according to
is used.
<ComprExt/@TipCamb> The exchange rate for the

in case the currency which differs from the base
one is used;
is used.
Mexico Folio Number's Auxiliary-Selection Fields

Refer to the GL Journals MX Report Selection Fields section.
Create a Folio Number's Auxiliary (Report E)

Refer to the Create a GL Journals MX Report section.
Account's Auxiliary (Report F)
Use the GL Journals MX Report with the selected Account's Auxiliary checkbox to generate Account's Auxiliary
(E) report.
The application generates an XML file named {Company.StateTaxId} + {Fiscal Year} + {Fiscal Period} + XC.xml.
ESC840101JQ7201702XC.xml.
The generated XML file should be valid against the AuxiliarCtas_1_3.xsd schema. The following table shows the
mapping between XML attributes and Epicor values.

<AuxiliarCtas> Auxiliary chart of accounts that is
delivered as part of the Electronic
Accounting
<AuxiliarCtas/@Version> 1.3 Format version
<AuxiliarCtas/@RFC> Company.StateTaxId The RFC of the taxpayer sending data
<AuxiliarCtas/@Mes> End period specified as incoming The month corresponding to the end
parameter in the MM format period
<RepAuxFol/@Anio> Fiscal year in the YYYY format The year corresponding to the end
period
<RepAuxFol/@TipoSolicitud> 2-letter code specified as the Journal Type Journal type:
report's parameter
• AF - Control Act
Epicor ERP | 10.2.400 137


• FC - Audit
• DE - Returning
• CO - Compensation
<RepAuxFol/@NumOrden> A serial number assigned to the

Value of the Serial Number report's
report in case the Journal Type is AF
parameter in case <TipoSolicitud>= AF or
or FC
FC
<RepAuxFol/@NumTramite> A serial number assigned to the

Value of the Serial Number report's
report in case the Journal Type is DE
parameter in case <TipoSolicitud>= DE or
or CO
CO
<AuxiliarCtas/Cuenta> Each <Cuenta> element corresponds to Details of accounting balance

the GLJrnDtl records group by (required)
GLJrnDtl.GLAccount field (without
dynamic segments).
<Cuenta/@NumCta> GLJrnDtl.GLAccount Account or subaccount
<Cuenta/@DesCta> GLJrnDtl.GLAccount -> The name of the account
GLAccount.AccountDesc
<Cuenta/@SaldoIni> For account's opening balance refer to the The amount of the opening balance
Financial Management > General Ledger of account or sub-account in the
> Reports > Trial Balance MX report. selected period
<Cuenta/@SaldoFin> The amount of the closing balance
For account's closing balance refer to the
of account or sub-account in the
Financial Management > General Ledger
selected period
> Reports > Trial Balance MX report
<Cuenta/DetalleAux> Details of the movements of the

<DetalleAux> element corresponds to one
period for the Account
GLJrnDtl record
<DetalleAux/@Fecha> Registration Date of the Journal

GLJrnDtl.JEDate
<DetalleAux/@NumUnIdenPol> {CC} + GLJrnDtl.JournalNum + The unique number of the Journal

GLJrnDtl.JournalCode
{CC} =
• "IN" in case GLJrnHed.JournalCode ->
• "EG" in case GLJrnHed.JournalCode
-> JrnlCode.MXPolicy = 2;
• "DR" in case GLJrnHed.JournalCode
-> JrnCode.MXPolicy = 3.
<DetalleAux/@Concepto> GLJrnDtl.Description The concept of the transaction

<DetalleAux/@Debe> GLJrnDtl.DebitAmount The debit amount of the account for
the transaction
138 Epicor ERP | 10.2.400


<DetalleAux/@Haber> GLJrnDtl.CreditAmount The credit amount of the account for
the transaction
Account's Auxiliary-Selection Fields

Refer to the GL Journals MX Report Selection Fields section.
Create an Account's Auxiliary (Report F)

Refer to the Create a GL Journals MX Report section.
Withholding Tax Certificate MX Report
Use the Withholding Tax Certificate MX report to generate an .xml file with the information about withholding
tax certificates.
For each combination of supplier and retention code the application generates a separate XML file. The file is
named RetencionPago_{Supplier}_{RetentionCode}_{YYYYMMDDHHMMSS}.xml where:
• {Supplier} - tax ID of the supplier who is the recipient of the certificate
• {RetentionCode} - retention code provided by SAT
• {YYYYMMDDHHMMSS} - time stamp
Limitations:
1. The system cannot distinguish between transactions created today and then printed and transactions created
today and not printed. The report will show all transactions created today.
2. If you print a report for different periods that intersect, the system cannot process such situation correctly.
Transactions that were already printed will be shown as well.

<Retenciones> Withholding and payment
information
<Retenciones/@Version> 1.0 Format version
<Retenciones/@FolioInt> Not exposed ID of the document for internal
control
<Retenciones/@Sello> Empty string Digital seal for the electronic file.
The stamp must be expressed as
a string of text in Base64 format.
<Retenciones/@NumCert> Currently 20 "0" symbols display here The serial number of the certificate
of digital seal that protects the
electronic file, according to the
acknowledgment corresponding
to 20 positions awarded by the
SAT system
Epicor ERP | 10.2.400 139


<Retenciones/@Cert> Empty string The digital certificate seal that
protects the electronic file as text,
base64 format
<Retenciones/@FechaExp> Current date and time in format Date and time when the
YYYY-MM-DDThh:mm:ss+(-)hh:mm document was issued
<Retenciones/@CveRetenc> Retention code according to the
• TaxTran.APInvoiceNum -> SAT catalog
APInvHed.MXRetentionCode (new field)
in case TaxTran.APInvoiceNum <> ""
AND APInvHed.MXRetentionCode <>
"";
• "00" in other cases
<Retenciones/@DescRetenc> Not exposed Retention description

<Retenciones/Emisor> One <Emisor> node is created Issuer of the electronic document
<Emisor/@RFCEmisor> Company.StateTaxId Tax ID of the issuer
<Emisor/@NomDenRazSocE> Name of the issuer
Company.Name
<Emisor/@CURPE> Not exposed Registration key of the issuer

<Retenciones/Receptor> One <Receptor> node is created Receptor of the electronic
document
<Receptor/@Nacionalidad> The receptor's nationality
• Nacional in case the Supplier's country
ID = Company's country ID;
• Extranjero in other cases.
<Receptor/Nacional> The node is created if National receptor

<Receptor/@Nacionalidad> = Nacional
<Nacional/@RFCRecep> Vendor.TaxPayerID Supplier Tax ID
<Nacional/@NomDenRazSocR> Name of the taxpayer receiving
• Vendor.LegalName in case the value <> the document
Empty String.
• Vendor.Name in other cases.
<Nacional/@CURPR> Not exposed Registration key of the receptor

<Receptor/Extranjero> The node is created if Foreign receptor
<Receptor/@Nacionalidad> = Extranjero
<Extranjero/@NumRegIdTrib> Vendor.TaxPayerID Supplier Tax ID
<Extranjero/@NomDenRazSocR> Name of the taxpayer receiving
• Vendor.LegalName in case the value <> the document
Empty String.
• Vendor.Name in other cases.
<Retenciones/Periodo> One <Periodo> node is created Period that covers the document
<Periodo/@MesIni> Initial period specified as incoming The month corresponding to the
parameter initial period
140 Epicor ERP | 10.2.400


<Periodo/@MesFin> End period specified as incoming parameter The month corresponding to the
end period
<Periodo/@Ejerc> Fiscal year in format YYYY Fiscal year
<Retenciones/Totales> One <Totales> node is created Total amounts for the period
<Totales/@montoTotOperacion> Sum of -1* TaxTran.ReportableAmt of all Total transaction amount
selected rows for current Supplier and Tax
Code
<Totales/@montoTotGrav> Sum of -1 * TaxTran.TaxableAmt of all Total taxable amount
selected rows for current Supplier and Tax
Code
<Totales/@montoTotExent> {Total transaction amount} - {Total taxable Total exempt from the total
amount} transaction amount
<Totales/@montoTotRet> Sum of -1 * TaxTran.TaxAmt of all selected Tax amount. Sum of all tax
rows for current Supplier and Tax Code amounts from the ImpRetenidos
nodes
<Totales/ImpRetenidos> One node is created for each TaxTran Payment information
record. The node exposes information from
TaxTran.HeadNum -> CheckHed if it exists.
<ImpRetenidos/@BaseRet> -1 * TaxTran.TaxableAmt Taxable amount
<ImpRetenidos/@Impuesto> TaxTran.TaxCode -> SalesTax.MXTaxType Tax type:
(this code is specified in Company
• 01 - ISR
Configuration. To access the program,
navigate to System Setup> Company/Site • 02 - IVA
Maintenance and select Modules> All • 03 - IEPS
Modules> Localization> Digital Tax Receipts
tab.
<ImpRetenidos/@montoRet> -1 * TaxTran.TaxAmt Tax amount
Epicor ERP | 10.2.400 141


< ImpRetenidos/@TipoPagoRet> Type of the payment:
• "Pago definitivo" (Final payment) in
case Val(TaxTran.HeadNum) = 0 • Final payment
OR • Interim payment
{
Val(TaxTran.HeadNum) <> 0 AND
[
CheckHed.InvoiceNum = ""
OR
[CheckHed.InvoiceNum <> "" AND
CheckHed.InvoiceNum ->
APInvHed.InvoiceAmt less or equal to
CheckHed.CheckAmt]
]
};
• "Pago provisional" (Interim payment)
in case Val(TaxTran.HeadNum) <> 0
AND
[
CheckHed.InvoiceNum <> "" AND
CheckHed.InvoiceNum ->
APInvHed.InvoiceAmt greater than
CheckHed.CheckAmt
].
<Retenciones/Complemento> Not exposed Optional node for additional

information
<Retenciones/Addenda> Not exposed Optional node for extensions to
the format
Complete Steps Before You Create a Report
This section describes steps you need to complete before creating a withholding tax certificate.
1. Navigate to Financial Management > Accounts Payable > Setup > Tax Type and create a tax type.
The Collection Method must be set to Withholding.
2. Navigate to Financial Management > Accounts Payable > Setup > Tax Liability and create or select a tax
liability.
3. Add a withholding tax type to this liability.
4. Navigate to System Setup > Company/Site Maintenance > Company Configuration.

Your company should be properly configured to work with digital tax receipts as described in the Setup -
Digital Tax Receipt topics.
142 Epicor ERP | 10.2.400

5. On the Modules > All Modules > Localization > Digital Tax Receipts sheet, select the tax ID you created
and make sure it is assigned to MX tax type in the Tax Type Mapping grid. Refer to the Tax Type Mapping
section for details.
6. Navigate to Financial Management > Accounts Payable > Setup > Supplier and select a supplier.
7. On the Supplier - Mexico sheet specify a retention code.

You can leave this field blank if you do not need to specify this code for the supplier. Refer to the Setup -
Digital Tax Receipt - Supplier Maintenance topic for details.
8. Navigate to Financial Management > Accounts Payable > General Operations > Invoice Entry, create an
invoice and post it.
Note that if you specified a supplier retention code in step 7, it is displayed on the Header - Mexico sheet
in the Electronic Accounting pane and you can update it, if necessary. Otherwise the Retention code field
is blank.
9. Navigate to Financial Management > Accounts Payable > General Operations > Payment Entry, create a
payment and post it.
You can update the retention code in the Posted Invoice Update program, if necessary.
Now you can generate a Withholding Tax Certificate report as described in the following section.
Create a Withholding Tax Certificate MX Report
To create a withholding tax certificate:
1. Navigate to Withholding Tax Certificate MX.

Menu Path: Financial Management > General Ledger > Reports
Menu Path: Financial Management > Accounts Payable > Reports
2. In the Fiscal Year field define a fiscal year for the report.
3. In the Year Suffix field define a fiscal suffix for the report.
4. In the Starting Fiscal Period and Ending Fiscal Period fields define starting and ending periods to determine
which records to include.
5. Select the Print All check box if required.

• If the check box is selected, the application prints all transactions in the specified fiscal period.
• If the check box is cleared, the application prints only transactions entered later that the date of last
printing for selected periods.
6. Specify the output directory where the XML file will be generated.
Epicor ERP | 10.2.400 143

Additional information is available at the Education and
Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.

Mexico 102400

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mexico 102400

Uploaded by

Copyright:

Available Formats

Epicor ERP

Mexico Country Specific

Epicor ERP | 10.2.400 3

Create a Digital Tax Receipt Document Type....................................................................................20

4 Epicor ERP | 10.2.400

Create a Digital Tax Receipt AR Invoice.....................................................................................40

Epicor ERP | 10.2.400 5

Electronic CFDI Payment Supplement File Structure.................................................................101

6 Epicor ERP | 10.2.400

Mexico CSF Guide

Digital Tax Receipts

Cash Receipt with Payment Supplement

Epicor ERP | 10.2.400 7

Additional Post-Migration Steps

Remove CSF Mexico BPMs From Epicor ERP 10

Epicor 9 CSF Mexico contains the following BPM:

1. Navigate to Method Directives.

2. Click the Method Code button.

3. Select the Search by Directives option.

4. In the Directive Group field, search for the Mexico group.

5. Select this group and click the Search button.

6. Select the required method and click OK.

8 Epicor ERP | 10.2.400

Remove the LongDescription UD Field

Payment Method (SAT) Update

Payment Method (SAT) Update Fields

Fields for the current sheet are listed on this topic.

Run the Conversion Program

1. Navigate to Payment Method (SAT) Update.

3. Click the Submit button.

4. Exit Payment Method (SAT) Update.

Set Up CSF Default Settings on Country License Change

Epicor ERP | 10.2.400 9

1. Run Epicor ERP.

2. Navigate to Company Configuration.

4. Exit Company Configuration.

Setup - Mexico Localization

Code Type ID Description Long Description SAT Name or

10 Epicor ERP | 10.2.400

Code Type ID Description Long Description SAT Name or

Code Type ID Description Long Description SAT Name or

Load User Defined Codes

1. Navigate to Solution Workbench.

2. From the Actions menu, select the Install Solution command.

4. Select the Only Target Current Company check box.

6. Exit Solution Workbench.

Epicor ERP | 10.2.400 11

User Defined Codes Maintenance

Add UD Codes to MXProdServ Code Type

1. Navigate to User Defined Codes Maintenance.

3. Navigate to the Codes sheet.

4. From the New menu, select New UD Code.

5. In the Code field, enter the code ID.

6. In the Description field, enter the code description.

Add UD Codes to MXUOMCFDI Code Type

1. Navigate to User Defined Codes Maintenance.

3. Navigate to the Codes sheet.

4. From the New menu, select New UD Code.

5. In the Code field, enter the code ID.

6. In the Description field, enter the code description.

Add UD Codes to MXCountry Code Type

1. Navigate to User Defined Codes Maintenance.

12 Epicor ERP | 10.2.400

3. Navigate to the Codes sheet.