2025-11-27 | DOF 5774131Added
The resolution modifies the official format and business rules for reporting international fund transfers to align with ISO 20022 standards and include country/jurisdiction data. It updates field specifications for operation folios and renumbers layout fields 4 to 4.5 to capture detailed data on reporting persons, including physical and legal entities. Credit institutions are required to use the new MX format for operations performed on or after November 22, 2025, while maintaining MT format compatibility for prior operations.
If the document is presented incomplete on the right margin, it is because it contains tables that exceed the default width. If this is the case, click here to view it correctly.
DOF: 27/11/2025
RESOLUTION reforming the one that issues the official format for the reporting of international fund transfers in terms of the General Provisions referred to in Article 115 of the Credit Institutions Law
A seal with the National Coat of Arms is placed at the margin, which says: United Mexican States.- Treasury.- Ministry of Finance and Public Credit.-
Financial Intelligence Unit.- Mexico.
RESOLUTION REFORMING THE ONE THAT ISSUES THE OFFICIAL FORMAT FOR THE REPORTING OF INTERNATIONAL FUND TRANSFERS IN TERMS OF THE GENERAL PROVISIONS REFERRED TO IN ARTICLE 115 OF THE CREDIT INSTITUTIONS LAW, AS WELL AS THE INSTRUCTIONS FOR ITS COMPLETION.
OMAR REYES COLMENARES, Head of the Financial Intelligence Unit of the Ministry of Finance and Public Credit, based on the provisions of Article 115 of the Credit Institutions Law; Article 4 of the Federal Administrative Procedure Law; Article 35 of the General Provisions referred to in Article 115 of the Credit Institutions Law, and Articles 10, fractions I and VI of the Internal Regulations of the Ministry of Finance and Public Credit, and,
CONSIDERING
That credit institutions, in terms of Article 35 of the General Provisions referred to in Article 115 of the Credit Institutions Law, are obligated to remit monthly to the Ministry of Finance and Public Credit, through the National Banking and Securities Commission (Commission), a report for each international fund transfer that, individually, any of their clients or users has received or sent during the month being reported, for an amount equal to or greater than one thousand United States dollars or its equivalent in the foreign currency in which it is carried out, through electronic means and in the official format issued for such purposes by this Department.
That on July 4, 2013, the Resolution issuing the official format for the reporting of international fund transfers in terms of the General Provisions referred to in Article 115 of the Credit Institutions Law, as well as the instructions for its completion, was published in the Official Gazette of the Federation.
That on August 28, 2024, the reform to Article 35 of the General Provisions referred to in Article 115 of the Credit Institutions Law was published in the Official Gazette of the Federation to include in the international fund transfer report information regarding the countries or jurisdictions involved in international fund transfers, including those referred to in fraction X of Article 38 of said Provisions.
That due to global migration to achieve harmonized payment standards, SWIFT message types (MT format) were updated to the new ISO 20022 messages, establishing November 22, 2025, as the deadline for migration.
That in order to have information on the countries and jurisdictions involved in international fund transfers, as well as information on the SWIFT message type in accordance with ISO 20022 certification, it is necessary to modify the official format for the International Fund Transfer Report.
That after hearing the opinion of the National Banking and Securities Commission, issued via letter VSPP/220/32695/2025 dated November 10, 2025, I have deemed it appropriate to issue the following:
RESOLUTION REFORMING THE ONE THAT ISSUES THE OFFICIAL FORMAT FOR THE REPORTING OF INTERNATIONAL FUND TRANSFERS IN TERMS OF THE GENERAL PROVISIONS REFERRED TO IN ARTICLE 115 OF THE CREDIT INSTITUTIONS LAW, AS WELL AS THE INSTRUCTIONS FOR ITS COMPLETION
ARTICLE FIRST.- The length, format, and business rules of fields 3.1.1. CONSECUTIVE FOLIO OF THE OPERATION TO REPORT AND 3.1.2.1. FOLIO OF THE PREVIOUS OPERATION TO BE MODIFIED are modified to read as follows:
| FIELD NAME | XML LABEL | MANDATORINESS | DATA TYPE | LENGTH | FORMAT/MASK | BUSINESS RULES |
|---|---|---|---|---|---|---|
| 3.1.1. CONSECUTIVE FOLIO OF THE OPERATION TO REPORT | <folio_consecutivo> | Mandatory | Alphanumeric | 12 - 25 | Format: "year-swift-consecutive" Pattern: AAAA-MT999-999999999 (no leading zeros) or Pattern: AAAA-MXpacs.999-999999999 (no leading zeros) | VXSD: The field is mandatory for each operation. VXSD: The minimum length is 12 characters and the maximum is 25. VXSD: The field is alphanumeric. VXSD: For MT format operations, it follows the pattern AAAA-MT999-999999999 representing the year-swift-consecutive format, where: - AAAA must correspond to the year in which the operation is reported. - MT999 corresponds to the reported swift type (only applies to MT103 and MT202) - 999999999 corresponds to a consecutive number of operations per entity per year starting at 1 (no leading zeros). VXSD: For MX format operations, it follows the pattern AAAA-MXpacs.999-999999999 representing the year-swift-consecutive format, where: - AAAA must correspond to the year in which the operation is reported. - MXpacs.999 corresponds to the reported swift type (only applies to MXpacs.008 and MXpacs.009) - 999999999 corresponds to a consecutive number of operations per entity per year starting at 1 (no leading zeros). VXSD: The closing tag </folio_consecutivo> must be found. VC311R1: The consecutive number must start at 1 each year and increment by 1 for each operation reported during that year. VC311R2: Repeating a folio per entity is not allowed. Thus, if a modification is generated, a new folio is assigned to the modifying operation. VC311R3: The reported year must be valid and less than or equal to the year of sending the report containing the operation. VC311R4: For MT format operations, the MT999 field can only accept MT103 and MT202. VC311R5: For MX format operations, the MXpacs.999 field can only accept MXpacs.008 and MXpacs.009. VC311R6: The use of the MX format is only allowed for operations performed on or after November 22, 2025. |
| 3.1.2.1. FOLIO OF THE PREVIOUS OPERATION TO BE MODIFIED | <folio_previo> | Mandatory | Alphanumeric | 12-25 | Format: "year-swift-consecutive" Pattern: AAAA-MT999-999999999 (no leading zeros) or Pattern: AAAA-MXpacs.999-999999999 (no leading zeros) | VXSD: The field is mandatory if the <modificatorio> tag exists. VXSD: The minimum length is 12 and the maximum is 25. VXSD: The field is alphanumeric. VXSD: For MT format operations, it follows the pattern AAAA-MT999-999999999 representing the year-swift-consecutive format, where: - AAAA must correspond to the year in which the operation is reported. - MT999 corresponds to the reported swift type (only applies to MT103 and MT202) - 999999999 corresponds to a consecutive number of operations per entity per year starting at 1 (no leading zeros). VXSD: For MX format operations, it follows the pattern AAAA-MXpacs.999-999999999 representing the year-swift-consecutive format, where: - AAAA must correspond to the year in which the operation is reported. - MXpacs.999 corresponds to the reported swift type (only applies to MXpacs.008 and MXpacs.009) - 999999999 corresponds to a consecutive number of operations per entity per year starting at 1 (no leading zeros). VXSD: The closing tag </folio_previo> must be found. VC3121R1: The previous folio must correspond to an operation previously reported by the entity. VC3121R2: Each operation can only be modified once, so there must not be a modifying report to the same previous operation. If one exists, the record will be rejected. VC3121R3: The difference between the date of sending the modifying operation and the date of sending the operation to be modified must be less than or equal to 30 calendar days. VC3121R4: For MT format operations, the MT999 field can only accept MT103 and MT202. VC3121R5: For MX format operations, the MXpacs.999 field can only accept MXpacs.008 and MXpacs.009. VC3121R6: The use of the MX format is only allowed for operations performed on or after November 22, 2025. |
ARTICLE SECOND.- Fields 4 to 4.5 of the Layout are renumbered to read as follows:
| FIELD NAME | XML LABEL | MANDATORINESS | DATA TYPE | LENGTH | FORMAT/MASK | BUSINESS RULES |
|---|---|---|---|---|---|---|
| 3.1.6. DATA OF THE PERSON OR FIGURE TO REPORT | <persona> | Mandatory | XML Tag | N/A | N/A | VXSD: The tag is mandatory when the operation is a sending transfer (<transferencia_envio>) or receiving transfer (<transferencia_recepcion>), in case of vostro, the tag is optional. VXSD: The closing tag </persona> must be found. |
| 3.1.6.1. DATA OF TYPE OF PERSON OR FIGURE BEING REPORTED | <tipo_persona> | Mandatory | XML Tag | N/A | N/A | VXSD: The tag is mandatory if the <persona> tag exists. VXSD: The closing tag </tipo_persona> must be found. |
| 3.1.6.1.1. DATA OF THE PERSON BEING REPORTED WHEN IT IS A NATURAL PERSON | <persona_fisica> | Mandatory | XML Tag | N/A | N/A | VXSD: If the <persona_moral> tag does not exist, then the <persona_fisica> tag is mandatory. Both cannot exist at the same time. VXSD: The closing tag </persona_fisica> must be found. |
| 3.1.6.1.1.1. NAME(S) | <nombre> | Mandatory | Alphanumeric | 1 - 60 | N/A | VXSD: The field is mandatory if the <persona_fisica> tag exists. VXSD: The minimum length is 1 character and the maximum is 60. VXSD: The field is alphanumeric. VXSD: It only accepts the following characters: letters A-Z (uppercase and without accents or diacritics), letter Ñ, space ( ), apostrophe ('), period (.). Note: Parentheses are not included in permitted characters. VXSD: The closing tag </nombre> must be found. VXSD: Blank character strings are not accepted. |
| 3.1.6.1.1.2. PATERNAL SURNAME | <apellido_paterno> | Mandatory | Alphanumeric | 1 - 60 | N/A | VXSD: The field is mandatory if the <persona_fisica> tag exists. VXSD: The minimum length is 1 character and the maximum is 60. VXSD: The field is alphanumeric. VXSD: It only accepts the following characters: letters A-Z (uppercase and without accents or diacritics), letter Ñ, space ( ), apostrophe ('), period (.). Note: Parentheses are not included in permitted characters. VXSD: The closing tag </apellido_paterno> must be found. VXSD: Blank character strings are not accepted. VC316112R1: In case the reported person does not have a Paternal Surname, four Xs (XXXX) must be captured. VC316112R2: If the "Maternal Surname" field was filled with four Xs (XXXX), the "Paternal Surname" field must be different from this value. |
| 3.1.6.1.1.3. MATERNAL SURNAME | <apellido_materno> | Mandatory | Alphanumeric | 1 - 60 | N/A | VXSD: The field is mandatory if the <persona_fisica> tag exists. VXSD: The minimum length is 1 character and the maximum is 60. VXSD: The field is alphanumeric. VXSD: It only accepts the following characters: letters A-Z (uppercase and without accents or diacritics), letter Ñ, space ( ), apostrophe ('), period (.). Note: Parentheses are not included in permitted characters. VXSD: The closing tag </apellido_materno> must be found. VXSD: Blank character strings are not accepted. VC316113R1: In case the reported person does not have a Maternal Surname, four Xs (XXXX) must be captured. VC316113R2: If the "Paternal Surname" field was filled with four Xs (XXXX), the "Maternal Surname" field must be different from this value. |
| 3.1.6.1.1.4. DATE OF BIRTH | <fecha_nacimiento> | Mandatory | Numeric | 8 | Pattern: AAAAMMDD | VXSD: The length is 8 characters. VXSD: The field is numeric and follows the pattern AAAAMMDD representing the date format, where: - AAAA corresponds to the 4-digit year. - MM corresponds to the 2-digit month. - DD corresponds to the 2-digit day. VXSD: The closing tag </fecha_nacimiento> must be found. In case of not having the data, it does not need to be included in the report without invalidating rule VC316114R3. VC316114R1: The date must be valid, meaning it must have a year less than or equal to the year in which the report is received, a valid month between 01-12, a valid day corresponding to the indicated month. VC316114R2: The date must be less than the date of receipt of the report. VC316114R3: The field is mandatory only when the RFC or CURP is not available, providing the 3 if they are available. VC316114R4: If more than one field is provided (Date of Birth, RFC, or CURP), the date reported in these fields must match; if different, the operation will be rejected. |
| 3.1.6.1.1.5. UNIQUE KEY OF POPULATION REGISTRY (CURP) | <curp> | Mandatory | Alphanumeric | 18 | Format: AAAAAAAAAAAAAAAA AA Pattern: LLLLAAMMDDGEFCCC99; where, L=(A-Z) letter, AA=year, MM=month, DD=day, G=M or H, EF=Federative Entity CC=(A-Z) letters 99=(0-9) number | VXSD: The length is 18 characters. VXSD: The field is alphanumeric and follows the pattern LLLLAAMMDDGEFCCC99 representing the format where: - LLLL Letters corresponding to the first two letters of the paternal surname, the first letter of the maternal surname, and the first letter of the name. - AA corresponds to the 2-digit birth year. - MM corresponds to the 2-digit birth month. - DD corresponds to the 2-digit birth day. - G Gender (H=man, M=woman). - EF Federative Entity in two characters. Permitted characters A-Z. - CCC Letters corresponding to the second consonant of the paternal surname, the second consonant of the maternal surname, and the second consonant of the name. Permitted characters A-Z. - 99 Numbers assigned by the authority as a consecutive number. VXSD: The closing tag </curp> must be found. In case of not having the data, it does not need to be included in the report without invalidating rule VC316115R1. VC316115R1: This field is optional as long as RFC or date of birth is available, providing the 3 if they are available. It is mandatory when neither Date of Birth nor RFC is available. VC316115R2: If more than one field is provided (Date of Birth, RFC, or CURP), the date reported in these fields must match; if different, the operation will be rejected. |
| 3.1.6.1.1.6. FEDERAL TAXPAYER REGISTRY KEY WITH HOMOCODE (RFC) | <rfc> | Mandatory | Alphanumeric | 13 | Pattern: LLLLAAMMDDXXX; where, L=(A-Z) letter or characters & or Ñ, AA=year, MM=month, DD=day, X=alphanumeric. | VXSD: The length is 13 characters. VXSD: The field is alphanumeric and follows the pattern LLLLAAMMDDXXX representing the format where: - LLLL Letters in uppercase, without accents or diacritics from A-Z corresponding to the first two letters of the paternal surname, the first letter of the maternal surname, and the first letter of the name. Characters & or Ñ can be included. - AA corresponds to the 2-digit birth year. - MM corresponds to the 2-digit birth month. - DD corresponds to the 2-digit birth day. - XXX Characters representing the homocode, which can be letters A-Z (uppercase, without accents and without diacritics) or numbers. VXSD: Only RFC will be considered when the Homocode is included. VXSD: The closing tag </rfc> must be found. In case of not having the data, it does not need to be included in the report without invalidating rule VC316116R1. VC316116R1: This field is optional as long as CURP or date of birth is available, providing the 3 if they are available. It is mandatory when neither Date of Birth nor CURP is available. VC316116R2: If more than one field is provided (Date of Birth, RFC, or CURP), the date reported in these fields must match; if different, the operation will be rejected. |
| 3.1.6.1.1.7. COUNTRY OF BIRTH KEY | <pais_nacimiento> | Optional | Alphabetic | 2 | Format: AA | VXSD: The length is 2 characters. VXSD: The field is alphabetic. VXSD: It only accepts the following characters: letters A-Z. VXSD: The closing tag </pais_nacimiento> must be found. In case of not having the data, it does not need to be included in the report. VC316117R1: The field key must be according to the COUNTRY CATALOG provided by the UIF. |
| 3.1.6.1.1.8. NATIONALITY COUNTRY KEY | <pais_nacionalidad> | Mandatory | Alphabetic | 2 | Format: AA | VXSD: The field is mandatory if the <persona_fisica> tag exists. VXSD: The minimum length is 2 characters. VXSD: The field is alphabetic. VXSD: It only accepts the following characters: letters A-Z. VXSD: The closing tag </pais_nacionalidad> must be found. VC316118R1: The field key must be according to the COUNTRY CATALOG provided by the UIF. |
| 3.1.6.1.1.9. ECONOMIC ACTIVITY KEY, OCCUPATION, PROFESSION, ACTIVITY OR BUSINESS TRADE THAT THE NATURAL PERSON IS DEDICATED TO AT THE TIME OF PERFORMING THE OPERATION | <actividad_economica> | Mandatory | Alphanumeric | 7 | Pattern: 9999999 | VXSD: The field is mandatory if the <persona_fisica> tag exists. VXSD: The length is 7 characters. VXSD: The field is alphanumeric. VXSD: It only accepts characters 0-9. VXSD: The closing tag </actividad_economica> must be found. VC316119R1: The field key must be according to the ECONOMIC ACTIVITY, OCCUPATION, PROFESSION, ACTIVITY OR BUSINESS TRADE THAT THE NATURAL PERSON IS DEDICATED TO AT THE TIME OF PERFORMING THE OPERATION CATALOG provided by the UIF. |
| 3.1.6.1.2. DATA OF THE PERSON BEING REPORTED WHEN IT IS A LEGAL ENTITY | <persona_moral> | Mandatory | XML Tag | N/A | N/A | VXSD: If the <persona_fisica> tag does not exist, then the <persona_moral> tag is mandatory. Both cannot exist at the same time. VXSD: The closing tag </persona_moral> must be found. Both cannot exist at the same time. VXSD: The closing tag </persona_moral> must be found. |
| 3.1.6.1.2.1. DENOMINATION OR CORPORATE NAME | <razon_social> | Mandatory | Alphanumeric | 1-90 | N/A | VXSD: Mandatory if the <persona_moral> tag exists. VXSD: The minimum length is 1 character and the maximum is 90. VXSD: The field is alphanumeric. VXSD: It only accepts the following characters: letters A-Z (uppercase and without accents or diacritics), letter Ñ, numbers 0-9, space ( ), hash (#), hyphen (-), period (.), &, comma (,), underscore (_), @, apostrophe ('). Note: Parentheses are not included in permitted characters. VXSD: The closing tag </razon_social> must be found. VXSD: Blank character strings are not accepted. |
| 3.1.6.1.2.2. DATE OF CONSTITUTION | <fecha_constitucion> | Mandatory | Numeric | 8 | Pattern: AAAAMMDD | VXSD: The length is 8 characters. VXSD: The field is numeric and follows the pattern AAAAMMDD representing the date format, where: - AAAA corresponds to the 4-digit year. - MM corresponds to the 2-digit month. - DD corresponds to the 2-digit day. VXSD: The closing tag </fecha_constitucion> must be found. In case of not having the data, it does not need to be included in the report without invalidating rule VC316122R3. VC316122R1: The date must be valid, meaning it must have a year less than or equal to the year in which the report is received, a valid month between 01-12, a valid day corresponding to the indicated month. VC316122R2: The date must be less than the date of receipt of the report. VC316122R3: The field is mandatory only when the RFC is not available, providing the 2 if they are available. |
| 3.1.6.1.2.3. FEDERAL TAXPAYER REGISTRY KEY WITH HOMOCODE (RFC) | <rfc> | Mandatory | Alphanumeric | 12 | Pattern: LLLAAMMDDXXX; where, L=(A-Z) letter, AA=year, MM=month DD=day, X=alphanumeric. | VXSD: The length is 12 characters. VXSD: The field is alphanumeric and follows the pattern LLLAAMMDDCCC representing the format where: - LLL Letters in uppercase, without accents or diacritics from A-Z. - AA corresponds to the 2-digit birth year. - MM corresponds to the 2-digit birth month. - DD corresponds to the 2-digit birth day. - CCC Characters representing the homocode, which can be letters A-Z (uppercase, without accents and without diacritics) or numbers. VXSD: Only RFC will be considered when the Homocode is included. VXSD: The closing tag </rfc> must be found. In case of not having the data, it does not need to be included in the report without invalidating rule VC316123R1. VC316123R1: This field is optional as long as Date of Constitution is available, providing the 2 if they are available. It is mandatory when Date of Constitution is not available. |
| 3.1.6.1.2.4. NATIONALITY COUNTRY KEY | <pais_nacionalidad> | Mandatory | Alphabetic | 2 | Format: AA | VXSD: Mandatory if the <persona_moral> tag exists. VXSD: The minimum length is 2 characters. VXSD: The field is alphabetic. VXSD: It only accepts the following characters: letters A-Z. VXSD: The closing tag must be found. VC316124R1: The field key must be according to the COUNTRY CATALOG provided by the UIF. |
| 3.1.6.1.2.5. COMMERCIAL TRADE KEY, ACTIVITY OR CORPORATE OBJECTIVE | <giro_mercantil> | Mandatory | Alphanumeric | 7 | N/A | VXSD: Mandatory if the <persona_moral> tag exists. VXSD: The length is 7 characters. VXSD: The field is alphanumeric. VXSD: It only accepts characters 0-9. VXSD: The closing tag </giro_mercantil> must be found. VC316125R1: The field key must be according to the COMMERCIAL TRADE, ACTIVITY OR CORPORATE OBJECTIVE CATALOG provided by the UIF. |
| 3.1.6.1.2.6. NAME OF THE |
ADMINISTRATOR,
DIRECTOR, GENERAL MANAGER
OR
LEGAL REPRESENTATIVE
WHO, WITH THEIR SIGNATURE,
CAN OBLIGATE THE
LEGAL ENTITY FOR
PURPOSES OF
OPENING AN
ACCOUNT, ENTERING
INTO A CONTRACT OR
CARRYING OUT THE
OPERATION
<apoderado_legal>
Mandatory
Alphanumeric
1 - 180
N/A
VXSD: It is Mandatory if the
label <persona_moral> exists.
VXSD: The minimum length is 1
character and maximum 180.
VXSD: The field is alphanumeric.
VXSD: It only accepts the
following characters: letters A-Z
(uppercase and without accents or umlauts),
letter Ñ, space ( ), apostrophe ('), period
(.). Note. Parentheses are not included
in allowed characters. VXSD: The
closing tag </apoderado_legal> must be found.
VXSD: Blank character strings are not accepted.
3.1.6.2.
DATA
ON
ADDRESS
<domicilio>Mandatory
XML Tag
N/A
N/A
VXSD:
The label
is
mandatory
if
the label <persona> is found.
VXSD:
The closing tag
</domicilio> must be found.
3.1.6.2.1. DATA
IF
THE
ADDRESS
IS NATIONAL
<nacional>Mandatory
XML Tag
N/A
N/A
VXSD:
If the label
<extranjero> does not
exist, then
the label <nacional> is mandatory.
Both
cannot exist
at the same time.
VXSD:
The closing tag
</nacional> must be found.
3.1.6.2.1.1. DATA
IF
THE
ADDRESS
IS UNIFIED OR
IS SEPARATE
<tipo_domicilio>
Mandatory
XML Tag
N/A
N/A
VXSD:
The label
is
mandatory
if
the label <nacional> exists.
VXSD:
The closing tag
</tipo_domicilio> must be found.
3.1.6.2.1.1.1. DATA
ON
UNIFIED
ADDRESS
<unificado>Mandatory
XML Tag
N/A
N/A
VXSD:
If the label
<separado> does not
exist, then
the label <unificado> is mandatory.
Both cannot exist
at the same time.
VXSD:
The closing tag
</unificado> must be found.
3.1.6.2.1.1.1.1 UNIFIED
ADDRESS
<domicilio_unificado>
Mandatory
Alphanumeric
1-300
N/A
VXSD: The label is mandatory if the
label is found.
VXSD: It only accepts the
following characters: letters A-Z
(uppercase and without accents or umlauts),
letter Ñ, numbers 0-9, space ( ),
hash (#), hyphen (-), period (.),
comma (,), apostrophe ('), colon (:),
slash (/). Note. Parentheses are not
included in allowed characters.
VXSD: The closing tag must be found.
VXSD: Blank character strings are not accepted.
3.1.6.2.1.1.1.2. CITY OR
POPULATION
<ciudad_poblacion>
Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <unificado> is found.
VXSD:
It only accepts
the
following characters:
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ, numbers
0-9,
space
( ),
hash (#),
hyphen (-),
period (.),
comma
(,),
apostrophe
('),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</ciudad_poblacion> must be found.
VXSD:
Blank character strings are not
accepted.
3.1.6.2.1.1.1.3. POSTAL
CODE
<codigo_postal>
Mandatory
Alphanumeric
5
N/A
VXSD:
The label
is
mandatory
if
the label <unificado> is found.
VXSD:
The length is
of
5 characters.
VXSD: It only accepts
the
characters
0-9 or the character
X.
VXSD:
The closing tag
</codigo_postal> must be found.
VC 316 21113R1:
In case of not having
it,
it will be filled
with
the value XXXX..
3.1.6.2.1.1.2.
SEPARATE
ADDRESS
<separado>Mandatory
XML Tag
N/A
N/A
VXSD:
If the label
<unificado> does not
exist, then
the label <separado> is mandatory.
Both cannot exist
at the same time.
VXSD:
The closing tag
</separado> must be found.
3.1.6.2.1.1.2.1. KEY
OF
FEDERAL ENTITY
<entidad_federativa>
Mandatory
Alphanumeric
2
N/A
VXSD: The label is mandatory if the
label <separado> is found.
VXSD: The closing tag must be found.
</entidad_federativa>.
VC 316 21121R1: The key of the field
must correspond to the catalog of
SEPOMEX Federal Entities Catalog.
3.1.6.2.1.1.2.2.
POSTAL CODE
<codigo_postal>
Mandatory
Alphanumeric
5
N/A
VXSD: The label is mandatory if the
label <separado> is found.
VXSD: The length is 5 characters.
VXSD: It only accepts the
characters 0-9. VXSD: The closing tag must be
found.</codigo_postal>.
3.1.6.2.1.1.2.3.
CITY OR
POPULATION
<ciudad_poblacion>
Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD: The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD: The closing tag must be found
</ciudad_poblacion>.
VXSD:
Blank character strings are not
accepted.
3.1.6.2.1.1.2.4.
KEY OF
DELEGATION
OR
MUNICIPALITY
<delegacion_municipio>
Mandatory
Alphanumeric
5
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD:
The closing tag
</delegacion_municipio> must be found.
VC 316 21124R1: The key
of the field
must correspond
to the
Delegation or
Municipality Catalog
SEPOMEX.
VC 316 21124R2:
The
delegation or
municipality reported must
belong
to
the federal entity
specified
in
the field
3.1.6.2.1.1.2.1.
(<entidad_federativa>),
that is,
the two
first digits
of the key of
delegation or
municipality must
coincide
with the key
of
federal entity.
3.1.6.2.1.1.2.5.
NEIGHBORHOOD
<colonia>Mandatory
Alphanumeric
1 - 40
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD: The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</colonia> must be found.
VXSD:
Blank character strings are not
accepted.
VC31621125R1:
In case
of not having
it,
it will be filled with the
value XXXX..
3.1.6.2.1.1.2.6.
STREET,
AVENUE
OR LANE
<calle>Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD:
The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following characters letters A-Z
(uppercase and without accents or umlauts),
letter Ñ, numbers 0-9, space ( ),
colon (:), slash (/). Note. The
parentheses are not included in allowed
characters.
VXSD: The closing tag must be found
</calle>.
VXSD: Blank character strings are not accepted.
3.1.6.2.1.1.2.7
EXTERNAL
NUMBER
<numero_exterior>
Mandatory
Alphanumeric
1-40
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD: The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</numero_exterior> must be found.
VXSD: Blank character strings are not
accepted.
3.1.6.2.1.1.2.8
INTERNAL
NUMBER
<numero_interior>
Optional
Alphanumeric
1-40
N/A
VXSD:
The minimum length
is
of 1
character and
maximum
of 40.
VXSD:
It only accepts the
following characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</numero_interior> must be found.
In case
of not having
the data,
it does not
need to be included in the report.
3.1.6.2.2.
DATA
IF
THE
ADDRESS
IS
FOREIGN
<extranjero>Mandatory
XML Tag
N/A
N/A
VXSD:
If the label
<nacional> does not
exist, then
the label <extranjero> is mandatory.
Both cannot exist
at the same time. VXSD:
The closing tag must be found
</extranjero>.
3.1.6.2.2.1. KEY OF
COUNTRY
WHERE THE
ADDRESS
IS
LOCATED
<pais>Mandatory
Alphabetic
2
Format: AA
VXSD:
Mandatory if the label
<extranjero> exists.
VXSD:
The length
is
of 2 characters.
VXSD:
The field is
alphabetic.
VXSD:
It only accepts
the
following
characters:
letters
A-Z.
VXSD:
The closing tag
</pais> must be found.
VC 316 221R1:
The key
of the
field must
be according to the CATALOG
OF
COUNTRY
provided
by
the UIF.
3.1.6.2.2.2.
DATA
IF
THE
ADDRESS
IS
UNIFIED OR
IS SEPARATE
<tipo_domicilio>
Mandatory
XML Tag
N/A
N/A
VXSD:
The label
is
mandatory
if
the label <extranjero> exists.
VXSD:
The closing tag
</tipo_domicilio> must be found.
3.1.6.2.2.2.1.
UNIFIED
ADDRESS
<unificado>Mandatory
XML Tag
N/A
N/A
VXSD:
If the label
<separado> does not
exist, then
the label <unificado> is mandatory.
Both cannot exist
at the same time.
VXSD:
The closing tag
</unificado> must be found.
3.1.6.2.2.2.1.1.
UNIFIED
ADDRESS
<domicilio_unificado>
Mandatory
Alphanumeric
1-300
N/A
VXSD:
The label
is
mandatory
if
the label <unificado> is found.
VXSD:
It only accepts
the
following characters:
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ, numbers
0-9,
space
( ),
hash (#),
hyphen (-),
period (.),
comma
(,),
apostrophe
('),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</domicilio_unificado> must be found.
VXSD: Blank character strings are not
accepted.
3.1.6.2.2.2.1.2.
CITY OR
POPULATION
<ciudad_poblacion>
Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <unificado> is found.
VXSD:
It only accepts
the
following characters:
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ, numbers
0-9,
space
( ),
hash (#),
hyphen (-),
period (.),
comma
(,),
apostrophe
('),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</ciudad_poblacion> must be found.
VXSD: Blank character strings are not
accepted.
3.1.6.2.2.2.1.3. POSTAL
CODE
<codigo_postal>
Optional
Alphanumeric
4-12
N/A
VXSD: The minimum length is 4
characters and maximum 12.
VXSD: It only accepts the
characters 0-9 and letters A-Z (uppercase
and without accents or umlauts).
VXSD: The closing tag must be found
</codigo_postal>. In case of
not having the data, it does not need to
be included in the report.
3.1.6.2.2.2.2. SEPARATE
ADDRESS
<separado>Mandatory
XML Tag
N/A
N/A
VXSD: If the label
<unificado> does not exist, then the label
<separado> is mandatory. Both cannot exist
at the same time. VXSD: The closing tag
</separado> must be found.
3.1.6.2.2.2.2.1. STATE,
PROVINCE,
DEPARTMENT
OR
POLITICAL DIVISION
SIMILAR THAT
CORRESPONDS
<estado_provincia>
Mandatory
Alphanumeric
1-70
N/A
VXSD: The label is mandatory if the
label <separado> is found.
VXSD: The minimum length is 1
character and maximum 70.
VXSD: It only accepts the
following characters letters A-Z,
letter Ñ, numbers 0-9, space ( ),
comma (,), period (.). Note. Parentheses
are not included in allowed characters.
VXSD: The closing tag must be found
</estado_provincia>.
VXSD: Blank character strings are not
accepted.
3.1.6.2.2.2.2.2. POSTAL
CODE
<codigo_postal>
Optional
Alphanumeric
4-12
N/A
VXSD:
The minimum length is
of 4
characters
and
maximum
of 12.
VXSD:
It only accepts the
characters
0-9 and
letters
A-Z
(uppercase
and
without
accents
or
umlauts).
VXSD:
The closing tag
</codigo_postal> must be found.
In case
of
not having the data,
it does not need to
be included in the
report.
3.1.6.2.2.2.2.3.
CITY OR
POPULATION
<ciudad_poblacion>
Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD:
The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/). Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</ciudad_poblacion> must be found.
VXSD:
Blank character strings are not
accepted.
3.1.6.2.2.2.2.4. NEIGHBORHOOD
<colonia>Mandatory
Alphanumeric
1 - 40
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD: The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</colonia> must be found.
VXSD:
Blank character strings are not
accepted.
VC31622224R1:
In case
of not having
it,
it will be filled with the
value XXXX.
3.1.6.2.2.2.2.5. STREET,
AVENUE
OR LANE
<calle>Mandatory
Alphanumeric
1-70
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD: The minimum length
is
of 1
character and
maximum
of
VXSD:
It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</calle> must be found.
VXSD: Blank character strings are not
accepted.
3.1.6.2.2.2.2.6.
EXTERNAL
NUMBER
<numero_exterior>
Mandatory
Alphanumeric
1-40
N/A
VXSD:
The label
is
mandatory
if
the label <separado> is found.
VXSD:
The minimum length
is
of 1
character and
maximum
of
VXSD: It only accepts
the
following
characters
letters
A-Z
(uppercase
and
without
accents
or
umlauts),
letter Ñ,
numbers
0-9,
space (
),
comma
(,),
period (.),
colon
(:),
slash
(/). Note.
Parentheses
are not
included
in
allowed
characters.
VXSD: The closing tag
</numero_exterior> must be found.
VXSD: Blank character strings are not
accepted.
3.1.6.2.2.2.2.7.
INTERNAL
NUMBER
<numero_interior>
Optional
Alphanumeric
1-40
N/A
VXSD:
The minimum length
is
of 1
character and
maximum
of 40.
VXSD:
It only accepts the
following characters
letters
A-Z,
letter Ñ,
numbers
0-9,
space
( ),
comma (,),
period (.),
colon
(:),
slash
(/).
Note.
Parentheses
are not
included
in allowed
characters.
VXSD:
The closing tag
</numero_interior> must be found.
In case
of
not having the data,
it does not need to
be included in the
report.
3.1.6.3.
DATA
ON
TELEPHONE NUMBER
<telefono>Optional
XML Tag
N/A
N/A
VXSD:
The closing tag
</telefono> must be found.
In case
of not
having
the data,
it does not
need to be included
in the report.
3.1.6.3.1. TELEPHONE
NUMBER
<numero_telefono>
Mandatory
Numeric
10-12
Format:
Region Code +
telephone
number
VXSD:
Mandatory if the label
<telefono> exists.
VXSD:
The minimum length
is
of 10
characters
and
maximum
of 12.
VXSD:
The field is
numeric.
VXSD:
It only accepts the
following characters
0-9.
VXSD:
The closing tag
</numero_telefono> must be found.
3.1.6.3.2. KEY OF
COUNTRY
<clave_pais>
Optional
Alphabetic
2
N/A
VXSD:
The length is of 2 characters.
VXSD:
The field is
alphabetic.
VXSD: It only accepts
the
following
characters:
letters
A-Z.
VXSD:
The closing tag
</clave_pais> must be found.
In case
of not
having
the data, it does not need to
be included
in the report.
VC31632R1:
The key
of the
field must
be according to the
CATALOG OF COUNTRY
provided
by
the UIF.
3.1.6.3.3. EXTENSION
NUMBER
<extension>Optional
Alphanumeric
1 - 6
N/A
VXSD:
The minimum length
is
of 1
character and
the
maximum
of 6.
VXSD:
The field is
alphanumeric.
VXSD:
It only accepts the
following
characters
0-9.
(Accepts 0's at
the beginning).
VXSD:
The closing tag
</extension> must be found.
In case
of not
having
the data,
it does not need to be included
in the report.
3.1.6.4. EMAIL
ADDRESS
<correo_electronico>
Optional
Alphanumeric
5 - 60
Pattern:
([A-Z][0-9].-')+@([A-Z][0-9].-')
VXSD:
The minimum length
is
of 5
characters
and
maximum
of 60.
VXSD:
The following characters are accepted:
letters
A-Z,
numbers
0-9,
hyphen
(-),
period (.),
underscore
(_) and
apostrophe
(').
It is mandatory to have
the character
@
and
at least
one letter, a period and
another
letter after @,
for example, a@a.a.
Note.
Parentheses
are not
included
among the
allowed
characters.
VXSD:
The closing tag
</correo_electronico> must be found.
In case
of not having
the data,
it does not need to be included
in the report.
3.1.6.5. ADVANCED
ELECTRONIC
SIGNATURE
SERIAL NUMBER
<fiel>Optional
Numeric
21
N/A
VXSD: The length is 21 characters.
VXSD: It only accepts the
characters 0-9.
VXSD: The closing tag must be found
</fiel>. In case of not having
the data, it does not need to be included in the
report.
ARTICLE THIRD.- FIELD 3.1.7 COUNTRIES OR JURISDICTIONS INVOLVED IN THE OPERATION TO
BE REPORTED IS ADDED to read as follows:
FIELD NAME
XML TAG
MANDATORINESS
DATA TYPE
LENGTH
FORMAT/
MASK
BUSINESS RULES
3.1.7. COUNTRIES OR
JURISDICTIONS
INVOLVED IN THE
OPERATION TO
BE REPORTED
<paises_involucrados>
Mandatory
Alphabetic
1-100
Pattern:
XXX/YYY/ZZZ
VXSD: The field is mandatory if the label
<operacion> exists.
VXSD: The minimum length is 1
character and maximum 100.
VXSD: The field is alphabetic.
VXSD: The closing tag must be found
</paises_involucrados>.
VXSD: It only accepts the following
characters: letters A-Z (uppercase and
without accents or umlauts), letter Ñ, space (
), apostrophe ('), period (.), hyphen (-),
underscore (_), ampersand (&), slash (/).
Note. Parentheses are not included in
allowed characters.
VC317R1: Blank character strings are not
allowed.
VC317R2: Succession of
3 or more identical characters is not
allowed.
VC317R3: The list of jurisdictions
referred to in paragraphs a), b) and c) of
fraction X of the 38th of the GCP, can
be consulted in the sections
described as GAFI Public Lists
and Lists of preferential tax regimes
and Lists of preferential tax regimes
provided for in Article 9 of the
Transitory Provisions of the Income Tax
Law located in the following electronic link: https://
www.gob.mx/uif/documentos/internacion
al-337953?idiom=es
VC317R4: The field must contain
at least 2 jurisdictions
related to the operation
according to the following pattern:
XXX/YYY/ZZZ
Where:
XXX: jurisdiction or country of origin.
YYY: jurisdiction or country intermediary or
correspondent.
ZZZ: jurisdiction or country destination.
TRANSITORY PROVISIONS
FIRST.- This Resolution shall enter into force the day after its publication in the Official Journal of the Federation.
SECOND.- The Commission will make available to credit institutions, in electronic version through the SITI system, the
official format referred to in this Resolution.
THIRD.- Entities will begin to send to the Unit, through the Commission, the updated format starting from December 1
of 2025.
FOURTH.- In order for credit institutions to update the automated systems referred to in the 51st of the
Provisions, field 3.1.7 will be considered mandatory starting from March 1, 2026.
Mexico City, November 11, 2025.- The Head of the Financial Intelligence Unit of the Ministry of Finance and
Public Credit, Omar Reyes Colmenares.- Signature.
In the document you are viewing, there may be text, characters or objects that do not display correctly due to conversion to HTML format, so we recommend always taking the digitized image of the DOF or the PDF file of the edition as a reference. The content, form and scope of published documents are the strict responsibility of their issuer.
SEARCH
BY DATE
Do Mo Tu We Th Fr Sa
INDICATORS
Exchange Rate and Rates as of 08/22/2026
UDIS
8.805261
See more
SURVEYS
Did you like the new look of the Official Journal of the Federation website?
No
Yes
Official Journal of the Federation
Río Amazonas No. 62, Col. Cuauhtémoc, C.P. 06500, Mexico City Tel. (55) 5093-3200, where you can access our service menu
Electronic address: dof.gob.mx
113
LEGAL NOTICE | SOME RIGHTS RESERVED © 2026
More like this from SHCP
SHCP published 20 documents in the last 30 days. We email you each new one the day it's published.