Enquire Now
Home › Knowledge Base › CRS XML Schema v3.0 vs v2.0

OECD CRS XML Schema v3.0 vs v2.0 — New Fields, SelfCert Boolean & Migration Checklist

The complete side-by-side reference for the CRS 2.0 schema transition. Every new field, every changed element, every operational impact — with the migration path.

CRS Reporting Validate XML
On this page

Why CRS XML Schema v3.0 Matters

The OECD's amended Common Reporting Standard (CRS 2.0) introduced a significantly enhanced XML schema — CrsXML_v3.0.xsd — which replaces the legacy v2.0 schema. The transition is mandatory for most jurisdictions from the 2026 reporting year, with the first filings due in 2027.

FIs that continue to submit v2.0 XML to jurisdictions that have adopted v3.0 will have their files rejected at the portal. Every reporting financial institution must update its data pipelines, self-certification workflows, and XML generation tools.

Timeline pressure: The UK, Luxembourg, Ireland, and several other EU jurisdictions have already confirmed 2026 as the first reporting year under CRS v3.0. Cayman, Switzerland, and Canada follow in 2027. Waiting until 2027 to begin migration is a compliance risk.

Field-by-Field Comparison: v2.0 vs v3.0

XML Element / Feature Legacy CRS Schema v2.0 New OECD CRS XML Schema v3.0 Operational Impact for FFIs How Novus Compliance Handles It
Root Schema Version version="2.0"
CrsXML_v2.0.xsd		 version="3.0"
CrsXML_v3.0.xsd		 Tax authority portals reject legacy v2.0 XML headers once the CRS 2.0 mandate takes effect. Dedicated CRS v3.0 Data Preparation engine generating compliant v3.0 XML.
Self-Certification Indicator (SelfCert) Not reported in XML (assumed implicitly) Mandatory Boolean Flag for both Account Holders & Controlling Persons Institutions must explicitly declare whether a valid self-certification is held on file for every reportable record. Pre-built SelfCert columns in the Novus Excel template with instant row-level validation.
Account Lifecycle Status Not differentiated in XML Pre-existing vs. New Account Flag Must explicitly report whether each financial account was opened before or after the cut-off date. Automatically maps account lifecycle status to the required CRS v3.0 XML element.
Joint Account Metadata No structured joint count tag Joint Account Flag + Joint Holder Count Requires a Boolean indicator for joint accounts plus an integer count of total joint holders. Auto-validates joint account flags against the integer count of holders in your spreadsheet.
Financial Account Category Not required in standard CRS v2.0 Mandatory Account Type Enumeration Must classify accounts as Depository, Custodial, Equity/Debt Interest, Cash Value Insurance, or E-Money. Validates account type codes against the official OECD CRS v3.0 XSD enumeration list.
Controlling Person Roles (CtrlgPersonType) Single role per Controlling Person Multiple Roles Supported (CRS801–CRS813) Where an individual holds multiple ownership/control roles, all applicable roles must be reported in XML. Supports multi-role Controlling Person mapping without duplicating account structures.
Dual Tax Residency & Tie-Breaker Rules Relied on single treaty tie-breaker residency All Tax Residencies Reportable Prohibits relying solely on tax treaty tie-breaker rules to exclude a second tax residence on self-certifications. Supports multiple <ResCountryCode> and <TIN> pairs per Account Holder or Controlling Person.
E-Money & Digital Currencies Largely excluded Specified E-Money Products & CBDCs Included Brings Electronic Money Institutions (EMIs), digital wallets, and CBDC providers into mandatory CRS v3.0 scope. Includes tailored Excel-to-XML templates for both traditional banks/funds and E-Money fintechs.

Migration Checklist: v2.0 → v3.0

  1. Update your root schema declaration. Any file with version="2.0" will be rejected by portals that have migrated to v3.0.
  2. Add SelfCert flags. Every reportable account holder and controlling person must have an explicit boolean value indicating whether a valid self-certification is on file.
  3. Classify every account by type. Depository, Custodial, Equity/Debt, Cash Value Insurance, or E-Money — no exceptions.
  4. Map multi-role controlling persons. If one person is both a beneficial owner and a settlor, both roles must appear in the XML.
  5. Report all tax residencies. Do not rely on treaty tie-breaker rules to exclude second residencies. Report every <ResCountryCode> on the self-cert.
  6. Add joint account metadata. Boolean flag + integer count of joint holders.
  7. Update your self-certification forms. CRS 2.0 requires self-certs at or before account opening with strengthened reasonableness checks.
  8. Validate against the v3.0 XSD. Use our free XML validation tool to catch schema errors before filing.
Looking for a template? Download our CRS v3.0 Excel template from the Download Templates page. It includes pre-built columns for every new v3.0 field.

Frequently asked questions

When does CRS XML Schema v3.0 become mandatory?

Depends on the jurisdiction. UK, Luxembourg, and Ireland adopt v3.0 for the 2026 reporting year. Cayman, Switzerland, and Canada adopt it for 2027. Check your specific jurisdiction's guidance for the exact date.

What happens if I file v2.0 XML to a v3.0 jurisdiction?

The filing portal will reject the file at upload. In most cases, you will receive a schema version mismatch error and will need to regenerate the file with the correct root schema declaration.

Can I use one Excel template for both v2.0 and v3.0?

No. The new fields (SelfCert, Account Type, Joint Holder Count, Multi-Role Controlling Person) require additional columns. Download our dedicated CRS v3.0 template from the Download Templates page.

Does Novus Compliance support both v2.0 and v3.0 output?

Yes. Our CRS Reporting engine can generate both v2.0 and v3.0 XML depending on the target jurisdiction and reporting year. Contact us to confirm which version is enabled for your account.