2017-07-28 | DOF 5492239

Added

Resolution modifying general provisions for handling information requests to financial entities supervised by the CNBV

The National Banking and Securities Commission modifies Article 9, fraction I to require credit institutions to submit passive operation statements in PDF format with specific integrity and editing restrictions, and additionally in XML format via a structured layout when requested. Annex 3 establishes the technical specifications for this XML layout, defining mandatory and optional fields such as account numbers, customer details, addresses, and transaction movements, along with their data types, lengths, and validation rules. The resolution enters into force the day after its publication in the Official Gazette, while the new Annex 3 follows the effective date set by a previous resolution from April 28, 2017.

Secretaria de Hacienda y Credito Publico logo

Mexico

Secretaria de Hacienda y Credito Publico

Click to view thumbnail

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: 28/07/2017

RESOLUTION that modifies the general provisions establishing the procedure for handling information and documentation requests formulated by competent authorities to financial entities subject to the supervision of the National Banking and Securities Commission, through it.

A seal with the National Coat of Arms is placed at the margin, which reads: United Mexican States.- Ministry of Finance and Public Credit.- National Banking and Securities Commission.

The National Banking and Securities Commission, based on Articles 4, fractions V, XXXVI and XXXVIII, 16, fraction I and 19 of the National Banking and Securities Commission Law; 97, 110 Bis 2, fraction IV, 115 and 142 of the Credit Institutions Law; 192, 212 and 399, fraction IV of the Securities Market Law; 44, 78, 129 and 133, fraction IV of the Credit Unions Law; 34, 122 Bis and 146, fraction IV, of the Popular Savings and Credit Law; 69, 70, 71, 72 and 120, fraction IV, of the Law to Regulate the Activities of Savings and Loan Cooperative Societies; 55, 87 Bis 2, fraction IV and 91 of the Investment Funds Law; 51-A, 87-D, 101 Bis 3, fraction IV and 95 of the General Law of Organizations and Auxiliary Credit Activities, and 45 of the Supervision Regulation of the National Banking and Securities Commission, published in the Official Gazette of the Federation on January 18, 2005, and

CONSIDERING

That it is necessary to specify in which media financial entities other than credit institutions must send the information requested by various fiscal, administrative and judicial authorities from the National Banking and Securities Commission in order to grant administrative facilities for the benefit of such entities, it has resolved to issue the following:

RESOLUTION THAT MODIFIES THE GENERAL PROVISIONS ESTABLISHING THE PROCEDURE FOR HANDLING INFORMATION AND DOCUMENTATION REQUESTS FORMULATED BY COMPETENT AUTHORITIES TO FINANCIAL ENTITIES SUBJECT TO THE SUPERVISION OF THE NATIONAL BANKING AND SECURITIES COMMISSION, THROUGH IT

SINGLE.- Article 9, fraction I, first paragraph is REFORMED; Article 9, fraction I, first paragraph, items a) to c) is ADDED; and Annex 3 of the "General Provisions establishing the procedure for handling information and documentation requests formulated by competent authorities to financial entities subject to the supervision of the National Banking and Securities Commission, through it", published in the Official Gazette of the Federation on November 9, 2009, modified by Resolutions published in said dissemination medium on October 11, 2010 and April 28, 2017, is SUBSTITUTED, to read as follows:

" ANNEXES 1 and 2

...

ANNEX 3

Characteristics and specifications for the sending of passive operation statements. "

" Article 9.-

...

I .

In case of Positive Response, they will send in paper to the Commission's offices the information and documentation in question, through a document signed by an attorney or legal representative, unless the authority requires it through other means. Regarding statements of Financial Entities, they will be sent in file in PDF (Portable Document Format) format and additionally, in the case of credit institutions in accordance with the characteristics and specifications indicated in Annex 3 of these provisions, when the authority itself so requests. The PDF format file must meet the following characteristics:

a)

Guarantee the integrity of the document properties.

b)

Restrict document editing, which does not allow insertion, deletion, rotation and extraction of pages, or any other editing activity.

c)

Restrict the copying of text, images and other content from the document.

...

...

II . and III .

...

...

"

TRANSITORY

FIRST.- This Resolution will enter into force the day following its publication in the Official Gazette of the Federation.

SECOND.- Annex 3 will enter into force in accordance with what is provided in the second transitory article of the Resolution that modifies the General Provisions establishing the procedure for handling information and documentation requests formulated by competent authorities to financial entities subject to the supervision of the National Banking and Securities Commission, through it, published in the Official Gazette of the Federation on April 28, 2017.

Respectfully

Mexico City, July 21, 2017. - The President of the National Banking and Securities Commission, Jaime González Aguadé. - Rubric.

ANNEX 3

Characteristics and specifications for the sending of passive operation statements

Credit institutions must send to the Commission for the purposes referred to in Article 9, fraction I of these provisions, the statements through a layout, understood as a set of structured data containing the information of the statements and which will be provided in an XML (eXtensible Markup Language) format file. This information must correspond to that provided in the PDF format file.

LAYOUT FOR SENDING PASSIVE OPERATION STATEMENTS

No.

FIELD NAME

XML TAG

MANDATORINESS

DATA TYPE

LENGTH

FORMAT / MASK

BUSINESS RULES

1

ACCOUNT STATEMENT AUTHORITIES

<account_statement>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </account_statement> must be found.

1.1

INSTITUTION NAME

<institution_name>

Mandatory

Alphanumeric

1-150

N/A

VXSD: The field is mandatory.

VXSD: The minimum length is 1 character and the maximum is 150 characters.

VXSD: The field is alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </institution_name> must be found.

VXSD: Blank character strings are not accepted.

1.2

ACCOUNT NUMBER

<account_number>

Mandatory

Alphanumeric

1 - 18

Pattern: 999999999999999999

VXSD: The field is mandatory.

VXSD: The minimum length is 1 character and the maximum is 18.

VXSD: Only accepts the following characters: numbers 0-9.

Accepts leading zeros.

VXSD: The closing tag </account_number> must be found.

1.3

BRANCH

<branch>

Optional

Alphanumeric

1 - 8

Pattern: CCCCCCCC

Format: [A-Z 0-9]

VXSD: The field is optional.

VXSD: The minimum length is 1 character and maximum is 8.

VXSD: The field is alphanumeric.

VXSD: Only accepts characters of numbers 0-9 or letters A-Z. Accepts leading zeros. Underscore (_) and hyphen (-).

VXSD: The closing tag </branch> must be found.

VC31521R1: The branch key must correspond to the branch catalog sent by the entity to the Regulatory Body. The key must be the branch number of assignment or where the client's account or contract is located.

1.4.1

DATA IF THE NAME IS UNIFIED OR SEPARATED

<name_type>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </name_type> must be found.

1.4.1.2

UNIFIED NAME

<unified_name>

Optional

XML Tag

N/A

N/A

VXSD: If the <unified_name> tag does not exist, then the <separated_name> tag is mandatory. Both cannot exist.

VXSD: The closing tag </unified_name> must be found.

1.4.1.3

UNIFIED NAME DESCRIPTION

<name>

Mandatory

Alphanumeric

1-300

N/A

VXSD: The tag is mandatory if the <unified_name> tag is found within the <holder_name> tag.

VXSD: The minimum length is 1 character and maximum is 300.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </name> must be found.

1.4.2

SEPARATED NAME

<separated_name>

Mandatory

XML Tag

N/A

N/A

VXSD: If the <unified_name> tag does not exist, then the <separated_name> tag is mandatory. Both cannot exist.

VXSD: The closing tag </separated_name> must be found.

1.4.2.1

NAME(S)

<name>

Mandatory

Alphanumeric

1 - 60

N/A

VXSD: The field is mandatory.

VXSD: The minimum length is 1 character and maximum is 60.

VXSD: The field is alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </name> must be found.

VXSD: Blank character strings are not accepted.

1.4.2.2

FIRST LAST NAME

<first_last_name>

Optional

Alphanumeric

1 - 60

N/A

VXSD: The field is optional.

VXSD: The minimum length is 1 character and maximum is 60.

VXSD: The field is alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </first_last_name> must be found.

1.4.2.3

SECOND LAST NAME

<second_last_name>

Optional

Alphanumeric

1 - 60

N/A

VXSD: The field is optional.

VXSD: The minimum length is 1 character and maximum is 60.

VXSD: The field is alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </second_last_name> must be found.

1.5

CLABE ACCOUNT NUMBER

<clabe_account_number>

Optional

Alphanumeric

18

Pattern: 999999999999999999

VXSD: The length is 18 characters.

VXSD: The field is alphanumeric.

VXSD: Only accepts the following characters: Numbers 0-9.

Accepts leading zeros.

VXSD: The closing tag </clabe_account_number> must be found.

1.6

CUSTOMER NUMBER

<customer_number>

Optional

Alphanumeric

1-18

N/A

VXSD: The minimum length is 1 character and the maximum is 18.

VXSD: The field is alphanumeric.

VXSD: Only accepts the following characters: Numbers 0-9.

Accepts leading zeros.

VXSD: The closing tag </customer_number> must be found.

1.7

UNIQUE POPULATION REGISTRY KEY

<curp>

Optional

Alphanumeric

18

Format: AAAAAAAAAAAAAAAAAA

Pattern: LLLLAAMMDDGEFCCC99; where, L=(A-Z) letter, AA=year, MM=month, DD=day, G=M or H, EF=Federal Entity CCC= (A-Z) letters 99=(0-9) number

VXSD: The length is 18 characters.

VXSD: The field is alphanumeric and follows the pattern LLLLAAMMDDGEFCCC99 which represents the format where:

  • LLLL Letters in uppercase, without accents or diaeresis from A-Z corresponding to the first two letters of the paternal last name, the first letter of the maternal last name and the first letter of the name.

  • AA corresponds to the birth year in two digits.

  • MM birth month in two digits.

  • DD birth day in two digits.

  • G Gender (H=man, M=woman).

  • EF Federal Entity in two characters. Allowed characters from A-Z.

  • CCC Letters corresponding to the second consonant of the paternal last name, the second consonant of the maternal last name and the second consonant of the name. Allowed characters from A-Z.

  • 99 numbers assigned by the authority as a sequence.

VXSD: Consider the validations cited in the "Normative Instruction for the Assignment of the Unique Population Registry Key", issued by the General Directorate of the National Registry of Population and Personal Identification, issued by the Ministry of the Interior.

VXSD: The closing tag </curp> must be found. If the data is not available, it does not need to be included.

1.8

FEDERAL TAXPAYER REGISTRY

<rfc>

Optional

Alphanumeric

12 - 13

Pattern: LLLLAAMMDDXXX (Individual) or LLLAAMMDDXXX (Legal Entity).

VXSD: The length is 12 to 13 characters; 12 for Legal Entities and 13 for Individuals.

VXSD: For Individuals, the field is alphanumeric and follows the pattern LLLLAAMMDDXXX which represents the format where:

  • LLLL Letters in uppercase, without accents or diaeresis, from A-Z (including Ñ and &) corresponding to the first two letters of the paternal last name, the first letter of the maternal last name and the first letter of the name.

  • AA corresponds to the birth year in two digits.

  • MM birth month in two digits.

  • DD birth day in two digits.

  • XXX Characters representing the homoclave. They can be letters from A-Z, including Ñ (uppercase, without accents and without diaeresis) or numbers.

VXSD: For Legal Entities, the field is alphanumeric and follows the pattern LLLAAMMDDXXX which represents the format where:

  • LLL Letters in uppercase, without accents or diaeresis from A-Z corresponding to the letters of the legal name of the Legal Entity.

  • AA corresponds to the year of constitution in two digits.

  • MM corresponds to the month of constitution in two digits.

  • DD corresponds to the day of constitution in two digits.

  • XXX Characters representing the homoclave. They can be letters from A-Z (uppercase, without accents and without diaeresis) or numbers.

-VXSD: The closing tag </rfc> must be found. If the data is not available, it does not need to be included in the report.

1.9

ACCOUNT TYPE

<account_type>

Optional

Alphanumeric

1-180

N/A

VXSD: The minimum length is 1 character and maximum is 180.

VXSD: The field is alphanumeric.

VXSD: VXSD: Use UTF-8 encoding.

VXSD: The closing tag </account_type> must be found.

VXSD: Blank character strings are not accepted.

1.10

CURRENCY

<currency>

Mandatory

Alphabetic

3

Pattern: LLL

VXSD: The field is mandatory.

VXSD: The length is 3 characters.

VXSD: The field is alphabetic.

VXSD: Only accepts uppercase characters from A-Z, where L corresponds to a letter.

VXSD: The closing tag </currency> must be found.

VC31511112R1: The key must correspond to the CURRENCY OR CURRENCY CATALOG provided by the UIF.

2

ADDRESS

<address>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </address> must be found.

2.1

DATA IF THE ADDRESS IS UNIFIED OR SEPARATED

<address_type>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </address_type> must be found.

2.1.1

UNIFIED ADDRESS

<unified>

Optional

XML Tag

N/A

N/A

VXSD: If the <separated> tag does not exist, then the <unified> tag is mandatory. Both cannot exist.

VXSD: The closing tag </unified> must be found.

2.1.1.1

UNIFIED ADDRESS DESCRIPTION

<unified_address>

Mandatory

Alphanumeric

1-500

N/A

VXSD: The tag is mandatory if the <unified> tag is found within the <address> tag.

VXSD: The minimum length is 1 character and maximum is 500.

VXSD: VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </unified_address> must be found.

2.1.2

SEPARATED ADDRESS

<separated>

Mandatory

XML Tag

N/A

N/A

VXSD: If the <unified> tag does not exist, then the <separated> tag is mandatory. Both cannot exist.

VXSD: The closing tag </separated> must be found.

2.1.2.1

FEDERAL ENTITY KEY

<federal_entity>

Mandatory

Alphanumeric

2

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address> tag.

VXSD: The length is 2 characters.

VXSD: The closing tag </federal_entity> must be found.

VC421121R1: The field key must correspond to the SEPOMEX Federal Entities Catalog.

2.1.2.2

ZIP CODE

<zip_code>

Mandatory

Alphanumeric

5

Pattern: 99999

VXSD: The tag is mandatory if the <separated> tag is found within the <address> tag.

VXSD: The length is 5 characters.

VXSD: Only accepts characters 0-9.

VXSD: The closing tag </zip_code> must be found.

2.1.2.3

CITY OR TOWN

<city_town>

Mandatory

Alphanumeric

1-70

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address> tag.

VXSD: The minimum length is 1 character and maximum is 70.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </city_town> must be found.

2.1.2.4

DELEGATION OR MUNICIPALITY KEY

<delegation_municipality>

Mandatory

Alphanumeric

1 - 150

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address> tag.

VXSD: Use UTF-8 encoding.

VXSD: The length is 1 to 150 characters.

VXSD: The closing tag </delegation_municipality> must be found.

2.1.2.5

NEIGHBORHOOD

<neighborhood>

Mandatory

Alphanumeric

1 - 70

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address> tag.

VXSD: The minimum length is 1 character and maximum is 70.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </neighborhood> must be found.

2.1.2.6

STREET, AVENUE OR WAY

<street>

Mandatory

Alphanumeric

1-70

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address_type> tag.

VXSD: The minimum length is 1 character and maximum is 70.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </street> must be found.

2.1.2.7

EXTERIOR NUMBER

<exterior_number>

Mandatory

Alphanumeric

1-40

N/A

VXSD: The tag is mandatory if the <separated> tag is found within the <address_type> tag.

VXSD: The minimum length is 1 character and maximum is 40.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </exterior_number> must be found.

2.1.2.8

INTERIOR NUMBER

<interior_number>

Optional

Alphanumeric

1-40

N/A

VXSD: The minimum length is 1 character and maximum is 40.

VXSD: Use UTF-8 encoding.

VXSD: Blank character strings are not accepted.

VXSD: The closing tag </interior_number> must be found. If the data is not available, it does not need to be included in the report.

3

BANKING PRODUCTS ASSOCIATED WITH THE ACCOUNT OR CONTRACT

<associated_banking_products>

Optional

XML Tag

N/A

N/A

VXSD: If the tag exists, the closing tag </associated_banking_products> must be found.

VC3R1: The tag is mandatory if there are banking products associated with the account or contract. If there are no associated banking products, it should not be included.

3.1

DATA OF THE BANKING PRODUCT ASSOCIATED WITH THE ACCOUNT OR CONTRACT

<associated_banking_product>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory if the <associated_banking_products> tag exists (at least one operation must be included).

VXSD: The closing tag </associated_banking_product> must be found.

VC31R1: There must be a <associated_banking_product> tag for each product listed.

3.1.1

ACCOUNT NUMBER

<account_number>

Mandatory

Alphanumeric

1 - 18

Pattern: 999999999999999999

VXSD: The field is mandatory for each associated banking product.

VXSD: The minimum length is 1 character and the maximum is 18.

VXSD: Numbers 0-9. Accepts leading zeros.

VXSD: The closing tag </account_number> must be found.

3.1.2

PRODUCT DESCRIPTION

<product_description>

Mandatory

Alphanumeric

1-150

N/A

VXSD: The field is mandatory for each associated banking product.

VXSD: The minimum length is 1 character and maximum is 150.

VXSD: The field is alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </product_description> must be found.

4

PERIOD COVERED BY THE INFORMATION

<information_period>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </information_period> must be found.

4.1

PERIOD START DATE

<period_start_date>

Mandatory

Numeric

8

Pattern: YYYY-MM-DD

VXSD: The length is 8 characters.

VXSD: The field is numeric and follows the pattern YYYY-MM-DD which represents the date format, where:

  • YYYY corresponds to the year in 4 digits.

  • MM month in two digits.

  • DD day in two digits.

VXSD: The closing tag </period_start_date> must be found.

VC31611114R1: The date must be valid, that is, a valid month between 01-12, a valid day between 01-31 corresponding to the indicated month.

4.2

PERIOD END DATE

<period_end_date>

Mandatory

Numeric

8

Pattern: YYYY-MM-DD

VXSD: The length is 8 characters.

VXSD: The field is numeric and follows the pattern YYYY-MM-DD which represents the date format, where:

  • YYYY corresponds to the year in 4 digits.

  • MM month in two digits.

  • DD day in two digits.

VXSD: The closing tag </period_end_date> must be found.

VC31611114R1: VC31611114R1: The date must be valid, that is, a valid month between 01-12, a valid day between 01-31 corresponding to the indicated month.

5

DETAIL OF THE TRANSACTIONS

<transactions>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </transactions> must be found.

5.1

TRANSACTION DETAIL

<transaction>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory if the <transactions> tag exists (at least one transaction must be included).

VXSD: The closing tag </transaction> must be found.

VC31R1: There must be a <transaction> tag for each operation reported.

5.1.1

TRANSACTION DATE

<transaction_date>

Mandatory

Numeric

8

Pattern: YYYY-MM-DD

VXSD: The length is 8 characters.

VXSD: The field is numeric and follows the pattern YYYY-MM-DD which represents the date format, where:

  • YYYY corresponds to the year in 4 digits.

  • MM month in two digits.

  • DD day in two digits.

VXSD: The closing tag </transaction_date> must be found.

VC31611114R1: The date must be valid, that is, a valid month between 01-12, a valid day between 01-31 corresponding to the indicated month.

5.1.2

CONCEPT/DESCRIPTION

<description>

Mandatory

Alphanumeric

1-200

N/A

VXSD: The minimum length is 1 character and the maximum is 200.

VXSD: The field is Alphanumeric.

VXSD: Use UTF-8 encoding.

VXSD: The closing tag </description> must be found.

5.1.3

SERIAL/REFERENCE

<reference>

Optional

Numeric

1-18

Pattern: 999999999999999999

VXSD: The minimum length is 1 character and the maximum is 18.

VXSD: Only accepts the following characters: letters A-Z (without accents or diaeresis), numbers 0-9.

VXSD: The closing tag </reference> must be found.

5.1.4

CREDIT/DEPOSIT

<deposit>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: If the <charge> tag does not exist, then the <deposit> tag is mandatory. Both cannot exist.

VXSD: The minimum length is 4

characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum of 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </deposito> must be found.

5.1.5

WITHDRAWAL/CHARGE

<cargo>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: If the <deposito> tag does not exist, then the <cargo> tag is mandatory. Both cannot exist.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </cargo> must be found.

5.1.6

NEW BALANCE (AFTER THE MOVEMENT)

<nuevo_saldo>

Optional

Numeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </nuevo_saldo> must be found.

6

OPERATIONS SUMMARY

<resumen_operaciones>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </resumen_operaciones> must be found.

6.1

INITIAL BALANCE

<saldo_inicial>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </saldo_inicial> must be found.

6.2

NUMBER OF DEPOSITS/CREDITS MADE

<numero_depositos>

Optional

Numeric

1-6

Pattern: 999999

VXSD: The length is 6 characters.

VXSD: It only accepts characters from 0-9.

VXSD: The closing tag </numero_depositos> must be found. If the data is not available, it does not need to be included.

6.3

TOTAL AMOUNT DEPOSITED/CREDITED

<monto_total_depositado>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </monto_total_depositado> must be found.

6.4

NUMBER OF WITHDRAWALS/CHARGES MADE

<numero_retiros>

Optional

Numeric

1-6

Pattern: 99999

VXSD: The length is 6 characters.

VXSD: It only accepts characters from 0-9.

VXSD: The closing tag </numero_retiros> must be found. If the data is not available, it does not need to be included.

6.5

TOTAL AMOUNT WITHDRAWN/CHARGED

<monto_total_retirado>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: The field is numeric with decimals. It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </monto_total_retirado> must be found.

6.6

FINAL BALANCE

<saldo_final>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </saldo_final> must be found.

6.7

TOTAL FEES

<monto_total_comisiones>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </monto_total_comisiones> must be found.

7

YIELD SUMMARY

<resumen_rendimientos>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory.

VXSD: The closing tag </resumen_rendimientos> must be found.

7.1

AVERAGE BALANCE

<saldo_promedio>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The field is mandatory.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </saldo_promedio> must be found.

7.2

DAYS OF THE AVERAGE

<dias_del_promedio>

Mandatory

Numeric

2

Pattern: 99

VXSD: The minimum length is 1 character and the maximum is 2.

VXSD: It only accepts characters from 0-9.

VXSD: The closing tag </dias_del_promedio> must be found.

7.3

ANNUAL GROSS RATE

<tasa_bruta_anual>

Mandatory

Alphanumeric

4

Format: 1 integer position, decimal point (explicit), 2 decimal positions

VXSD: The minimum length is 3 characters (1 integer of 1 digit, 1 point and 1 decimal) and the maximum is 4 (1 integer of 2 digits, 1 point and 1 decimal). The first 2 positions will be used for the integers and the last one for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .0.

VXSD: The closing tag </tasa_bruta_anual> must be found.

7.4

TAXABLE AVERAGE BALANCE

<saldo_promedio_gravable>

Optional

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </saldo_promedio_gravable> must be found.

7.5

INTERESTS IN FAVOR

<intereses_a_favor>

Optional

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </intereses_a_favor> must be found.

7.6

ISR WITHHELD

<isr_retenido>

Optional

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </isr_retenido> must be found.

8

FEES OF THE PERIOD

<comisiones_del_periodo>

Optional

XML Tag

N/A

N/A

VXSD: If the tag exists, its closing tag </comisiones_del_periodo> must be found.

VC3R1: The tag is mandatory if there are fees in the period of the account statement. If there are no fees, it should not be included.

8.1

PERIOD FEE

<comision>

Mandatory

XML Tag

N/A

N/A

VXSD: The tag is mandatory if the <comisiones_del_periodo> tag exists (at least one operation must be included).

VXSD: The closing tag </comision> must be found.

VC31R1: There must be a <comision> tag for each fee reported.

8.1.1

DATE

<fecha>

Mandatory

Numeric

8

Pattern: YYYY-MM-DD

VXSD: The tag is mandatory if the <comision> tag exists.

VXSD: The length is 8 characters.

VXSD: The field is numeric and follows the YYYY-MM-DD pattern which represents the date format, where:

  • YYYY corresponds to the year in 4 digits.
  • MM month in two digits.
  • DD day in two digits

VXSD: The closing tag </fecha> must be found.

The date must be valid, that is, a valid month between 01-12, a valid day between 01-31 corresponding to the indicated month.

8.1.2

CONCEPT

<concepto>

Mandatory

Alphanumeric

1-200

N/A

VXSD: The tag is mandatory if the <comision> tag exists.

VXSD: The minimum length is 1 character and the maximum is 200.

VXSD: VXSD: Use UTF-8 encoding.

VXSD: The closing tag </concepto> must be found.

8.1.3

AMOUNT

<monto>

Mandatory

Alphanumeric

4 - 17

Format: 14 integer positions, decimal point (explicit), 2 decimal positions

VXSD: The tag is mandatory if the <comision> tag exists.

VXSD: The minimum length is 4 characters (1 integer of 1 digit, 1 point and 2 decimals) and the maximum is 17 (1 integer of 14 digits, 1 point and 2 decimals). The first 14 positions will be used for the integers and the last 2 for the decimals, separating the fractions with a point.

VXSD: It is mandatory to specify the decimals, even when the fractional amount is .00.

VXSD: The closing tag </monto> must be found.

8.1.4

REFERENCE

<referencia>

Optional

Alphanumeric

1-18

N/A

VXSD: The tag is optional if the <comision> tag exists.

VXSD: The minimum length is 1 character and the maximum is 18.

VXSD: It only accepts the following characters: letters from A-Z (without accents or umlauts), numbers from 0-9. Accepts leading zeros.

VXSD: The closing tag </referencia> must be found.


In the document you are viewing, there may be text, characters or objects that are not displayed 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 the published documents are the strict responsibility of their issuer.

INQUIRY

BY DATE

Su Mo Tu We Th Fr Sa

INDICATORS

Exchange Rate and Rates as of 29/08/2026

UDIS

8.809369

See more

SURVEYS

Did you like the new look of the Official Gazette of the Federation website?

No

Yes

Official Gazette 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 menu of services

Electronic address: dof.gob.mx

113

LEGAL NOTICE | SOME RIGHTS RESERVED © 2026

More like this from SHCP

SHCP published 14 documents in the last 30 days. We email you each new one the day it's published.

Share