TIN-Requirements FATCA CRS

The document outlines TIN validation requirements for CRS/FATCA One, confirming full compliance with OECD standards and key features like duplicate detection and multi-company support.

Functional Requirements
Functional Requirement	Type	Compliance Level	Comments
TIN Formats
Validate all TIN formats from OECD jurisdictions	Required	T - Fully complies
Maintain updated TIN formats for OECD jurisdictions.	Required	T - Fully complies
Include the formats of new jurisdictions according to the OECD	Required	T - Fully complies
What does the tool do when it is a non-OECD country?			System will only validate OECD and US TIN formats.
Reporter for the regulator DGI
Multi-company management	Required	T - Fully complies
Management screen with preloaded reporting parameters	Required	T - Fully complies
Customer information file upload (detail the structure of the upload template)	Required	T - Fully complies	Excel format file with information fields to be filled in according to regulation
Validation of clue fields to generate alerts - CRS: Home Address vs. Tax Jurisdiction (PN/PJ) - FATCA: Country of birth, nationality, primary residential address vs tax jurisdiction, Are you a US citizen or resident vs tax jurisdiction) (PN) country of incorporation vs tax jurisdiction (PJ)	Required	T - Fully complies
Detect if a customer has the same TIN in two different jurisdictions (PN/PJ)	Required	T - Fully complies
Detect if two or more customers have the same TIN in the same jurisdiction (PN/PJ)	Required	T - Fully complies
Detect customers with sequential (123456789) or repeated (000000000, 111111111) TIN (PN/PJ)	Required	T - Fully complies
Detect inconsistencies in the data (e.g.: invalid characters, double spaces, letter "ñ").	Required	T - Fully complies
Ability to make corrections to data in the tool	Desirable	T - Fully complies
Ability to provide exception to data inconsistency with supervisor approval	Required	T - Fully complies
Generation of an Excel file with the inconsistencies to send to users for correction.	Required	T - Fully complies
Being able to rerun the customer information file at the request of users	Required	T - Fully complies
To be able to generate a file of the corrections made in the tool so that they can also be made in the core of the bank.	Desirable	T - Fully complies
To have a screen for validating the TIN format directly in the tool and indicating the correct format according to the jurisdiction.	Required	T - Fully complies
Ability to process high volume of customers and accounts to be reported on	Required	T - Fully complies
Generation of XML reports to upload to the DGI portal.	Required	T - Fully complies
Sending of reports to the DGI automatically.	Desirable	N - Does not comply	We do not have a direct connection to the DGI, however the system delivers the XML file ready to be uploaded to the DGI portal.
Maintain historical records of the corrections made in the tool.	Desirable	T - Fully complies
Maintain history of all report files generated in XML format.	Required	T - Fully complies

Face-to-face and digital onboarding and updating of existing customer data
Mechanism for validation of the TIN formats in the different bank platforms (interface)	Required	T - Fully complies
Validation of clue fields to generate alerts - CRS: Home Address vs. Tax Jurisdiction (PN/PJ) - FATCA: country of birth, nationality, primary residential address vs tax jurisdiction, Are you a US citizen or resident vs tax jurisdiction) (PN) country of incorporation vs tax jurisdiction (PJ) (interface)	Required	T - Fully complies
To have a screen for validating the TIN format directly in the tool and indicating the correct format according to the jurisdiction.	Required	T - Fully complies