Upload a FATCA or CRS XML file and select the reporting type and jurisdiction. The tool validates against the correct XSD schema and reports any errors — line-by-line, with the specific rule that failed.
Validate your XML file
What this tool checks
- Well-formedness — the file is a valid XML document (correctly nested tags, proper encoding, no unclosed elements)
- Schema validation — the file conforms to the XSD for the selected report type and jurisdiction
- Namespace check — the root element's namespace matches the expected namespace for the schema
- Element ordering — child elements appear in the sequence the XSD requires
- Enumeration values — coded fields contain only the values the XSD permits
- Data types and patterns — GIIN format, ITDREIN length, date formats, numeric ranges
Supported schemas
| Report type | Jurisdiction | Schema |
|---|---|---|
| FATCA 1 | India | Form61B.xsd (Ver 1.3) |
| FATCA 1 | Germany | dip.xsd (BZSt) |
| FATCA 1 | Luxembourg | AEOI_FATCA_V3.0.xsd |
| FATCA 1 | United Kingdom | uk_aeoi_submission_v2.0.xsd |
| FATCA 1 | Canada | T619_PartXVIII.xsd |
| FATCA 1 | Global | OECD FATCA v1 |
| FATCA 2 | Global (IDES) | FatcaXML_v2.0.1.xsd |
| CRS | Global | CrsXML_v3.0.xsd |
Why validate before submission
Filing a non-compliant XML file wastes time — the submission is rejected, and depending on the jurisdiction, may count against your compliance record. Validation catches the errors that cause most rejections:
- IDES alert codes — for FATCA 2 submissions, IDES returns alert codes that indicate specific schema failures. Fixing them before submission avoids re-filing cycles.
- ITDREIN length errors — for India Form 61B, a short ITDREIN second segment (under 6 characters) causes rejection.
- Missing TIN — for legal entities in most jurisdictions, a TIN element is mandatory.
- Wrong ConstitutionType — for India, using
Ifor a company instead ofCfails validation. - Element ordering — XSDs use
xs:sequence, which requires elements in a specific order. Out-of-order elements fail validation even when data is correct.
Common validation errors and fixes
Namespace mismatch
You selected a report type whose expected namespace doesn't match the file's root namespace. Check that the file was generated for the correct framework.
ITDREIN too short
For India FATCA 1, the ITDREIN must be 16 characters — 10-character PAN followed by a 6-character code (e.g., AAACN1234Z.CB1012).
Missing TIN for legal entity
US-resident legal entities require a TIN element in the AccountHolder section. Add <TIN TinIssueCountry="US">...</TIN>.
Invalid ReportType code
For Form 61B, use 01 for FATCA and 02 for CRS. Other values fail enumeration.
Wrong ConstitutionType
Use C for Company, I for Individual. Mismatched codes fail enumeration even when structurally correct.
Need to validate at scale?
The tool above validates one file at a time. For batch validation — hundreds of XML files, multiple jurisdictions, with audit trails — see our FATCA Reporting Services and CRS Reporting Services.
Related tools
- GIIN Lookup — verify any GIIN against the live IRS FFI List
- Download Templates — free Excel templates with test data
- FATCA Reporting Services
- CRS Reporting Services
Frequently asked questions
Is this XML validator free?
Yes. There's no signup and no limit on how many files you validate.
Do you store my uploaded XML file?
No. Uploaded files are processed in memory and discarded immediately after validation. Nothing is retained on disk or in any database.
Which schema versions do you validate against?
We validate against the current published versions of each schema — updated automatically when the IRS, OECD, or a local authority publishes a new release.
Can you validate FATCA Model 1 and Model 2?
Yes. FATCA 2 (IDES) uses the OECD FATCA v2.0 schema. FATCA 1 jurisdictions use their own national schemas — choose the specific jurisdiction for the correct schema.
What if my file fails validation?
The tool returns the exact errors with line numbers. Common fixes are listed above. If you can't resolve an error, contact us — we can help diagnose the schema rule that's failing.
Can I validate multiple files at once?
The free tool handles one file at a time. For batch validation, see our FATCA Reporting Services.
Does the tool check business rules, or just schema?
The tool validates against the XSD schema and checks well-formedness, element order, data types, patterns, and enumerations. Business rules that aren't part of the XSD (e.g., jurisdiction-specific cross-field rules) are handled in our paid platform.