Cyprus DAC2/CRS Filing: The 13 December Cut-Off and XSD v3.0
The Cyprus Tax Department will take its DAC2/CRS file submission service offline from 14 December 2026 to 17 January 2027 while it moves from XSD Schema v2.0 to XSD Schema v3.0. Its press release of 20 November 2026 sets a hard edge for Cyprus DAC2/CRS filing: reporting financial institutions can submit files on the current v2.0 schema up to and including 13 December 2026, and from 18 January 2027 all DAC2/CRS file submissions will be based on v3.0.
The earlier date carries the risk. A late return, correction or deletion still sitting in a v2.0 queue after 13 December cannot be filed for five weeks, and when the service reopens it has to be rebuilt in a schema that requires data elements the v2.0 file never carried.
Related reading: GMSG CRS Reporting: Austria’s XSD v3.0 Switch on 8 January 2027
Cyprus DAC2/CRS filing dates around the schema switch
- 20 November 2026: Tax Department press release announcing the suspension.
- Up to and including 13 December 2026: last day for files on XSD Schema v2.0.
- 14 December 2026 to 17 January 2027: DAC2/CRS file submission service suspended.
- 18 January 2027: service back; all DAC2/CRS file submissions on XSD Schema v3.0.
- 30 June following the reporting year: annual reporting deadline stated in the May 2017 edition of the Ministry of Finance guidance notes, moving to the next working day when 30 June falls on a weekend or bank holiday; the Tax Department’s current edition of the notes should be checked before relying on it for the 2027 cycle.
13 December 2026 is a Sunday, so the last working day inside the v2.0 window is Friday 11 December. The notice does not say whether uploads are accepted that weekend, and a Sunday upload leaves no working day to act on a rejection before Monday 14 December.
The right-hand column below is my reading of the notice’s “all DAC2/CRS file submissions” wording, which carries no exception for earlier reporting periods.
| File | Submitted by 13 December 2026 | Submitted from 18 January 2027 |
|---|---|---|
| Late initial return for calendar year 2025 | XSD v2.0 | XSD v3.0 |
| Correction or deletion of a 2025 or earlier record | XSD v2.0 | XSD v3.0 |
| Initial return for calendar year 2026 | Not a complete calendar-year 2026 return: the annual reporting period ends on 31 December 2026 | XSD v3.0 |
What the Tax Department notice covers, and where it is silent
The notice runs to three sentences. It names one service, gives one reason (the transition between two schema versions) and sets a suspension window with a cut-off date on each side. It cites no legal provision.
The Ministry of Finance’s May 2017 guidance describes the original Cyprus DAC2/CRS framework, including Law 60(I)/2016 and CRS Decree 161/2016 for exchanges with non-EU partner jurisdictions. The current framework also includes Law 38(I)/2026, which secondary summaries report as published in the Official Gazette on 27 March 2026 and applying retroactively from 1 January 2026, with few exceptions. Those summaries describe it as bringing e-money institutions and e-money products into the Cyprus CRS rules.
Nothing in the notice touches the annual reporting deadline. Under the May 2017 guidance notes, information for a reporting period ending 31 December is due to the Tax Department by 30 June of the following year. On that rule the return for calendar year 2026 falls due by 30 June 2027. That date is a calculation from the 2017 guidance, and EY’s summary of Law 38(I)/2026 gives the same date for the first crypto-asset reports.
The notice also leaves the technical package unaddressed. It links to no v3.0 XSD, national user guide, validation rule list or test environment, and it does not name the schema’s owner. The version numbers match the OECD’s CRS XML Schema: version 2.0 is the schema in the OECD’s June 2019 user guide, used for all exchanges from 1 January 2021; version 3.0 is the amended schema in the OECD’s October 2024 user guide, written for the CRS as updated in 2023. The OECD specification is the likely basis of Cyprus’s v3.0, but the notice does not confirm that, and whether Cyprus’s own validator accepts every value the OECD allows is not established; national rules would follow in Tax Department documentation.
Other administrations have paired the same switch with their own file rules. Our coverage of the BZSt CRS schema v3.0 switch in Germany and of Poland’s CRS-1(4) schema shows how much national detail can sit on top of the OECD file.
What XSD v3.0 adds to each account report
The new elements come from the 2023 CRS amendments. For EU institutions the same data points arrive through Council Directive (EU) 2023/2226 (DAC8), which amended Annex I of Directive 2011/16/EU, the reporting and due diligence annex that DAC2 (Directive 2014/107/EU) inserted. Article 2 of DAC8 required Member States to apply its provisions from 1 January 2026, with later dates for a small number of provisions.
| v3.0 element | What it reports | OECD values |
|---|---|---|
| AccountType | Type of Financial Account | CRS1101 Depository, CRS1102 Custodial, CRS1103 Cash Value Insurance or Annuity Contract, CRS1104 Debt or Equity Interest in an Investment Entity |
| DDProcedure | Preexisting or New Account | CRS1201 New, CRS1202 Preexisting |
| SelfCert (account holder) | Whether a valid self-certification was provided | CRS901 true, CRS902 false |
| SelfCert (controlling person) | The same, for each controlling person who is a Reportable Person | CRS1001 true, CRS1002 false |
| JointAccount and Number | Whether the account is joint, and the number of joint holders | Number as an integer |
| CtrlgPersonType | Role of each controlling person, now a validation element and repeatable | CRS801 to CRS813 |
| EquityInterestType | Role of an equity interest holder in an Investment Entity that is a legal arrangement | CRS401 to CRS410 |
| AcctNumberType (optional) | Account number type, with a new e-money value | OECD606 Specified Electronic Money Product |
The OECD guide treats AccountType, DDProcedure and the account holder SelfCert as validation elements, and states that validation elements must be present for all data records in a file, with the receiver free to reject a file where they are missing. A v2.0 generator that only swaps the namespace and sets the root version attribute to “3.0” will therefore produce records that fail schema validation.
Back-year corrections after 18 January 2027
The notice draws its line by submission date, so a correction to a 2024 or 2025 record filed after the service reopens goes in on v3.0. Two rules in the OECD guide shape that file. A correction completely replaces the previous version of a record and must carry a new, unique DocRefID.
Its CorrDocRefID must reference the latest DocRefID for the record being corrected or deleted. Where there has been no intervening correction, that reference may be the identifier originally submitted under v2.0. A message should also carry either new records or corrections and deletions, and the guide advises against mixing the two.
A correction that is ready before 13 December can still go in on v2.0. After that, the OECD schema anticipates the case: AccountType, DDProcedure, SelfCert, CtrlgPersonType and the controlling person SelfCert each have a “not reported” value (CRS1100, CRS1200, CRS900, CRS800 and CRS1000), which the guide describes as a transitional measure to support interoperability with the previous schema version, particularly for corrections. The Cyprus notice does not say whether the Tax Department’s v3.0 validation accepts those values in a correction to a period before 2026; that answer belongs in its v3.0 technical documentation.
First-time filers and accounts brought in by DAC8
DAC8 widened the population. Its amendments bring entities that hold electronic money or central bank digital currencies for customers within the Depository Institution definition, and the OECD v3.0 schema adds the OECD606 value for Specified Electronic Money Products. For accounts treated as Financial Accounts solely because of DAC8, an account maintained as of 31 December 2025 is generally pre-existing, while an account opened from 1 January 2026 is generally new. However, Annex I, Section VIII(C)(9)(b), also classifies subsequently opened accounts as pre-existing where all four specified conditions concerning an existing account relationship, account aggregation, AML/KYC reliance and customer-information requirements are met. Institutions must apply that exception before mapping DDProcedure to CRS1202 (pre-existing) or CRS1201 (new).
An institution whose first reportable year is 2026 will ordinarily make its first filing from 18 January 2027, because the annual reporting period ends on 31 December 2026. Registration is separate from XML submission. The suspension notice speaks only of file submission and says nothing about registration requests between 14 December and 17 January.
The ATO’s route from CRS specification v1.1 to schema v3.0 shows the same switch outside the EU, where DAC8 does not apply.
Frequently Asked Questions
Does the suspension also stop FATCA submissions to the Tax Department?
The notice names only the DAC2/CRS file submission service and the move between CRS schema versions; it does not mention FATCA. It therefore does not establish whether FATCA XML submissions remain available during the suspension. Dual filers should confirm FATCA availability directly with the Tax Department.
A v2.0 file goes in on 11 December and comes back rejected after 13 December. Can it be resubmitted on v2.0?
The notice gives no grace period. It accepts v2.0 files up to and including 13 December 2026 and bases all submissions from 18 January 2027 on v3.0, so on its wording the corrected file has to be rebuilt in v3.0. It does not say whether a rejection notice can even issue while the service is suspended.
Can the 2026 return use the OECD “not reported” values for data the institution has not collected yet?
The OECD frames those values as a transitional link to the previous schema version. Separately, the transitional rule that DAC8 added as Section XI of Annex I to Directive 2011/16/EU requires controlling person roles and equity interest roles for accounts maintained as of 31 December 2025 only where that information is in the institution’s electronically searchable data, for reporting periods ending by the second calendar year after that date; the OECD guide carries the same relief. The Cyprus notice says nothing on how its v3.0 validation treats “not reported” codes in a 2026 return.
Related Articles
- GMSG CRS Reporting: Austria’s XSD v3.0 Switch on 8 January 2027: Austria’s cut-over dates, nil reports and FinanzOnline error codes.
- BZSt CRS Reporting: The Schema v3.0 Switch and Saint-Martin Refile: Germany’s move to CRS schema v3.0 under Newsletter 04/2026.
- CRS-1(4) Schema: Poland’s New CRS Form From 1 December 2026: the Polish national schema with the new self-certification, role, account type and joint account fields.
- Australian CRS Reporting: ATO Specification v1.1 to Schema v3.0: ATO lodgement rules and the 2027 schema v3.0 switch.
- EU Tax Simplification Package 2026: What the DAC Recast Means for DAC6, DAC7 and CESOP Reporting: the Commission’s proposed recast of the Directive on Administrative Cooperation.
Sources and References
- Tax Department, Republic of Cyprus, “Temporary Suspension of DAC2/CRS File Submission Service”, press release, 20 November 2026: gov.cy
- Republic of Cyprus, Ministry of Finance, “Automatic Exchange of Financial Account Information: Guidance Notes”, May 2017 (hosted by the OECD): Cyprus guidance notes (PDF)
- EY Cyprus, “Tax Legi April 2026” (secondary summary of Law 38(I)/2026, Official Gazette 27 March 2026): EY
- Council Directive (EU) 2023/2226 of 17 October 2023 amending Directive 2011/16/EU (DAC8), OJ L, 2023/2226, 24.10.2023: EUR-Lex
- Council Directive 2014/107/EU of 9 December 2014 amending Directive 2011/16/EU (DAC2), OJ L 359, 16.12.2014: EUR-Lex
- Council Directive 2011/16/EU of 15 February 2011 on administrative cooperation in the field of taxation, OJ L 64, 11.3.2011: EUR-Lex
- OECD (2024), Amended Common Reporting Standard XML Schema: User Guide for Tax Administrations, Version 4.0, October 2024 (CRS schema version 3.0): OECD
- OECD (2019), Common Reporting Standard XML Schema: User Guide for Tax Administrations, Version 3.0, June 2019 (CRS schema version 2.0): OECD (PDF)
Clearing the Cyprus v2.0 queue before 13 December
Late 2025 returns and any correction or deletion already prepared on v2.0 have until 13 December 2026, and Friday 11 December is the last working day to upload them. Any DAC2/CRS file submitted from Monday 18 January 2027 must use XSD v3.0, including returns covering calendar year 2026. On the May 2017 guidance-note rule the 2026 return falls due by 30 June 2027. Institutions should complete and validate their AccountType, DDProcedure and SelfCert mapping before their first v3.0 submission.
Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.
