Free tool · XML validation
Validate FATCA & CRS XML before the regulator does.
Upload a FATCA or CRS file and check it against the exact XSD it will be judged by. Every error comes back with its line number and the rule that failed.
- FATCA 2.0 · IDES
- CRS v3.0
- 6 local FATCA schemas
- Never stored
01What it checks
The same rules the portal applies.
Validation runs the official XSD with every import resolved locally, so the result is what the schema says, not an approximation.
-
01 / Check
Well-formedness
The file is a valid XML document: tags nested and closed, encoding correct.
-
02 / Check
Namespace
The root namespace matches the report type you chose, so a CRS file isn’t judged as FATCA.
-
03 / Check
Element order
Schemas use
xs:sequence: elements out of order fail even when the data is right. -
04 / Check
Enumerations
Coded fields such as
DocTypeIndiccontain only the values the schema allows. -
05 / Check
Types & patterns
Dates, numbers, lengths and patterns like GIIN and country-code formats.
-
06 / Check
Required elements
Mandatory elements are present, with the cardinality the schema demands.
02Supported schemas
Eight schemas, one upload.
Not sure which to pick? If you report to the IRS through IDES, choose FATCA 2. If you report to a local authority, choose FATCA 1 and your jurisdiction.
| Report type | Jurisdiction | Schema |
|---|---|---|
| FATCA 1 | India | Form61B.xsd (Ver 1.3) |
| FATCA 1 | United Kingdom | uk_aeoi_submission_v2.0.xsd |
| FATCA 1 | Luxembourg | AEOI_FATCA_V3.0.xsd |
| FATCA 1 | Canada | T619_PartXVIII.xsd |
| FATCA 1 | Germany | dip.xsd (BZSt DIP) |
| FATCA 1 | Global | FatcaXML_v2.0.1.xsd |
| FATCA 2 | IRS (IDES) | FatcaXML_v2.0.1.xsd |
| CRS | OECD (CRS 2.0) | CrsXML_v3.0.xsd |
03Common errors
The errors behind most rejections.
-
Namespace mismatch
The report type you selected doesn’t match the file’s root namespace. Check the file was generated for the right framework, then pick that type.
-
ITDREIN length (India)
The ITDREIN must be 16 characters:
XXXXXXXXXX.YZNNN, the 10-character PAN or TAN, a dot, then a 5-character suffix, for exampleAAACN1234Z.CB001. -
Missing TIN for a legal entity
US-resident legal entities need a TIN in the AccountHolder section, for example
<TIN issuedBy="US">…</TIN>. -
Invalid ReportType (Form 61B)
Use
01for FATCA and02for CRS; any other value fails the enumeration. -
Wrong ConstitutionType (Form 61B)
Use
Cfor a company andIonly for an individual. Mismatched codes fail even when the structure is right. -
Test vs. production DocTypeIndic
FATCA11–FATCA14andOECD10–OECD13mark test data. Production files useFATCA1–FATCA4orOECD0–OECD3.
Need a clean starting point? Our Excel templates follow each schema’s fields.
Download templatesFAQ
Frequently asked questions
Something else? Ask our team
Is this XML validator free?
Yes. There’s no sign-up. To keep it fast for everyone, each visitor can validate up to 30 files every 10 minutes.
Do you store my XML file?
No. The file is parsed from the server’s temporary upload and discarded when the check finishes. Nothing from the file is written to disk, a database or logs.
Which schema versions do you validate against?
FATCA 2 (IDES) and the global FATCA 1 option use FatcaXML_v2.0.1.xsd; CRS uses the OECD CrsXML_v3.0.xsd. The local FATCA 1 schemas are listed in the table above.
Can you validate FATCA Model 1 and Model 2 files?
Yes. Model 2 files go to the IRS through IDES and use the IRS FATCA 2.0 schema; choose FATCA 2. Model 1 jurisdictions use their own schemas; choose FATCA 1 and your jurisdiction.
Does the tool check business rules or just the schema?
The schema: well-formedness, element order, data types, patterns and enumerations. Business rules outside the XSD, such as jurisdiction-specific cross-field rules, are checked in the Novus platform.
What if my file fails?
Each error shows its line number and the rule that failed. The common errors above cover most rejections; if you’re stuck, contact us and we’ll help you read the rule.
Can I validate many files at once?
The free tool checks one file at a time. For batch validation across entities and jurisdictions, with an audit trail, see the Novus platform.
Validating one file at a time? Validate every filing.
Novus validates input, business rules and the XSD before any file is produced, for every entity and jurisdiction you report.