GMSG CRS Reporting: Austria’s XSD v3.0 Switch on 8 January 2027

RegReportingDesk card: BMF, Federal Ministry of Finance, Austria

Austrian GMSG CRS reporting switches to version 3.0 of the OECD’s CRS XML schema on 8 January 2027. The Federal Ministry of Finance (BMF) has set out the cut-over in an information sheet on the new schema and in its technical guide “Allgemeine Informationen GMSG” for CRS XSD v3.0, dated 5 November 2026. FinanzOnline accepts version 2.0 files only until 21 December 2026, takes no GMSG transmissions at all from 22 December 2026 to 7 January 2027, and rejects version 2.0 files from 8 January 2027.

The schema change arrives in the same cycle as a change in the law. The Betrugsbekaempfungsgesetz 2025 Teil Daten (BGBl. I Nr. 96/2025) amended the Gemeinsamer Meldestandard-Gesetz (GMSG) with effect from 1 January 2026 to carry the EU’s DAC8 amendments to the Common Reporting Standard. Reporting financial institutions now report the account type, whether an account is new or preexisting, joint-account holders, self-certification status and the roles of controlling persons, and they file a nil report when they maintain no reportable accounts. The report for reporting period 2026, due by the end of July 2027, is the first file that has to carry all of it.

Under the BMF’s rule on errors, any error rejects the whole message, and the new validation codes tie payment codes and account-number types to the account type. A mapping gap in one account report blocks every other account in the same file.

Related reading: BZSt CRS Reporting: The Schema v3.0 Switch and Saint-Martin Refile

GMSG CRS reporting dates for the XSD v3.0 switch

  • 1 January 2026: the GMSG amendments listed in Section 117(7), including the revised reporting obligations, entered into force and apply to reporting period 2026. The amendment to Section 92 has a separate commencement date of 10 July 2027 under Section 117(8).
  • 31 March 2026: registration deadline under Section 1a GMSG for institutions that were already reporting financial institutions on 31 December 2025 (passed).
  • 21 December 2026: last day to transmit version 2.0 files through FinanzOnline, including resubmissions of rejected version 2.0 files.
  • 22 December 2026 to 7 January 2027 inclusive: GMSG transmission through FinanzOnline is unavailable.
  • 8 January 2027: version 3.0 only. Version 2.0 files are rejected with an error, version 3.0 test submissions become possible, and corrections, deletions and cancellations of previously transmitted data must use version 3.0.
  • 2 August 2027: Section 4(1) GMSG sets the end of July as the deadline for the reporting period 2026 report, nil reports included. 31 July 2027 is a Saturday, and Section 108(3) of the Federal Fiscal Code (BAO) moves a deadline that ends on a Saturday to the next day that is not a Saturday, Sunday, public holiday, Good Friday or 24 December, here Monday 2 August 2027. The roll-over follows from Section 4(1) treating the report as a tax return. The BMF guide itself refers to 31 July and does not mention the roll-over, so a file sent by Friday 30 July 2027 avoids the question.

The BMF’s information sheet adds a warning for filings made in 2026: because every correction or late submission from 8 January 2027 has to be built in the new schema, it asks institutions to take particular care over the accuracy and completeness of what they send before the cut-over, and to check the transmission protocols in their FinanzOnline messages regularly so that rejected files are spotted in time.

The GMSG was enacted as Article 4 of BGBl. I Nr. 116/2015. Section 1 sets out its two channels: exchanges with other EU Member States under Directive 2011/16/EU on administrative cooperation in the field of taxation (DAC), and exchanges with non-EU states under the global standard for automatic exchange of financial account information and the multilateral competent authority agreement. The rules sit in the statute itself: reporting duties in Sections 3 to 6, due diligence in Sections 7 to 53 and definitions in Sections 54 to 106.

The 2026 changes come from Article 2 of the Betrugsbekaempfungsgesetz 2025 Teil Daten, promulgated on 23 December 2025. Article 1 of the same act created a separate federal law on automatic exchange of information on reportable crypto-assets, the crypto strand of DAC8 that our CARF and DAC8 reporting guide for Luxembourg covers from the Luxembourg side. Section 117(7) GMSG puts the amended Sections 1, 1a, 3, 4, 4a, 5, 5a and 6 (among others) into force on 1 January 2026.

On the EU side, Council Directive (EU) 2023/2226 (DAC8) amended the CRS rules in Annex I of the DAC and required Member States to apply them from 1 January 2026. Council Directive (EU) 2025/872 later replaced Article 8(3a) of the DAC, the provision that defines the financial account information exchanged under the CRS. The BMF’s information sheet cites Article 8(3a) points (e) to (g) of that version when it sets out the revised payment definitions.

Two status points matter for anyone building a file. Section 4(1) GMSG treats the report as a tax return (Abgabenerklaerung). The BMF’s technical guide, by contrast, describes itself as programming support and refers readers to the GMSG and the GMSG guidelines (GMSG-R) for the substantive rules. The XSD tells you how a data point is encoded; Section 3 GMSG tells you which data points the institution owes. The BMF guide links each new version 3.0 element to the Section 3 item that requires it, which gives a usable map from schema field to legal source.

The BMF download page also qualifies the 2027 package: it is published on the basis of the EU requirements currently available, and those requirements remain subject to ongoing EU adjustments. The BMF’s document-version log is the place where later changes to the guide, the error-code list, the specifications and the sample files are recorded.

Who files: reporting financial institutions and their FinanzOnline transmitters

The obligation sits with the reporting financial institution. The BMF guide restates the four categories of financial institution: custodial institution, depository institution, investment entity and specified insurance company (Verwahrinstitut, Einlageninstitut, Investmentunternehmen, spezifizierte Versicherungsgesellschaft). The GMSG defines each in Sections 54 to 61 and lists the non-reporting financial institutions from Section 62. Under Section 3(1a) GMSG the report goes to the Large Taxpayers Office (Finanzamt fuer Grossbetriebe).

DAC8 widened the depository perimeter. The amended DAC definition of depository institution covers entities that hold e-money or central bank digital currencies for the benefit of customers, and Section 72 GMSG now counts as a depository account an account or notional account that represents all e-money held for a customer. Section 87 GMSG then excludes such an e-money account where the customer’s 90-day rolling average balance or value does not exceed USD 10,000 on any day of the calendar year. Exceeding that threshold ends the Section 87 no. 5a GMSG exclusion for the account, and the account is reportable where the other GMSG conditions for a reportable account are also met, including the relevant account-holder and due-diligence requirements. For a reportable specified electronic money product, CRS schema version 3.0 provides AcctNumberType OECD606.

Since 1 January 2026, Section 1a GMSG has required each reporting financial institution to register electronically with the competent tax office without being asked. Institutions that were already reporting on 31 December 2025 had until 31 March 2026; others register within one month of starting the activity, and deregister within one month after the licence lapses or the liquidation is final.

The institution and the party that presses send can be different. The national wrapper’s Info_Daten block carries two nine-digit tax numbers: Fastnr_Fon_Tn for the FinanzOnline participant that transmits the file, and Fastnr_Fi for the reporting financial institution. Several error codes test how those numbers flow into the OECD part of the message:

  • SendingCompanyIN in MessageSpec must repeat Fastnr_Fon_Tn (ERR-DAC2-100006).
  • ReportingFI must carry exactly one IN element of type TIN holding Fastnr_Fi (ERR-DAC2-100008), and ResCountryCode for the ReportingFI must be AT exactly once (ERR-DAC2-100010).
  • TransmittingCountry must be AT (ERR-DAC2-100009).

The BMF guide describes Fastnr_Fon_Tn as the tax number of the FinanzOnline participant (the transmitter), Fastnr_Fi as that of the financial institution, and SendingCompanyIN as the transmitter’s data. On that reading, a service provider that transmits for a client puts its own tax number in Fastnr_Fon_Tn and SendingCompanyIN and the client’s tax number in Fastnr_Fi and the ReportingFI IN. If the tax number in Fastnr_Fon_Tn is not assigned to the FinanzOnline participant, the file fails with ERR-F-003 and FinanzOnline cannot attribute it to anyone, which means a NOK protocol and no processing at all.

What the CRS XSD v3.0 package changes in each account report

The BMF guide summarises nine changes taken from version 3 of the OECD schema. Five add data elements that Section 3 GMSG now requires; the others extend code lists, change a cardinality or redefine payments. The table maps each element to its legal basis as the BMF cites it.

Element in v3.0 What it records Values GMSG basis cited by the BMF
AccountType (1..1) Type of financial account CRS1101 depository, CRS1102 custodial, CRS1103 cash value insurance or annuity contract, CRS1104 debt or equity interest in an investment entity; CRS1100 not reported Section 3(2) no. 1
DDProcedure (1..1) New or preexisting account CRS1201 new, CRS1202 preexisting; CRS1200 not reported Section 3(2) no. 1
JointAccount with Number (0..1) Joint account and number of joint holders Integer count Section 3(1) no. 3
SelfCert (account holder) Whether the holder provided a valid self-certification CRS901 true, CRS902 false; CRS900 not reported Section 3(1) no. 1 lit. f
SelfCert (controlling person) Same question for each reportable controlling person CRS1001 true, CRS1002 false; CRS1000 not reported Section 3(1) no. 2 lit. e sublit. gg
CtrlgPersonType (now 1..n) Role or roles of each controlling person CRS801 to CRS813; CRS800 not reported Section 3(1) no. 2 lit. e sublit. ff
EquityInterestType Role or roles of an equity interest holder in an investment entity that is a legal arrangement CRS401 to CRS410 Section 3(4) no. 2
AcctNumberType OECD606 Specified Electronic Money Product New enumeration value No Section 3 item cited

The ninth change is definitional. The payment codes stay as they were (CRS501 dividends, CRS502 interest, CRS503 gross proceeds or redemptions, CRS504 other), but the BMF maps them to the account types under the revised Article 8(3a): dividends, interest and other income on custodial accounts use CRS501, CRS502 or CRS504 and their proceeds use CRS503; interest on depository accounts uses CRS502; proceeds or redemptions on cash value insurance and annuity contracts and on debt or equity interests in investment entities use CRS503. The validation codes below also admit CRS504 for those two account types.

The “not reported” values and the electronically searchable data relief

Each new mandatory element has a “not reported” value (CRS800, CRS900, CRS1000, CRS1100, CRS1200). The OECD’s Amended CRS XML Schema User Guide describes each one as a transitional measure that facilitates interoperability with the previous version of the schema, with corrections named as the main case. The BMF adds two statements. Citing information from the OECD Global Forum, it says that information the new schema makes mandatory but that is not available is reported with the matching “not reported” value, so CRS800 in the case of CtrlgPersonType. For DDProcedure, the BMF says CRS1200 may be needed in exceptional cases to keep interoperability with earlier schema versions, especially in corrections.

Section 6(4) GMSG gives the substantive relief that sits behind the role codes. For each reportable account that an institution maintained on 31 December 2025, and for reporting periods ending by 31 December 2027, the roles by virtue of which a reportable person is a controlling person or an equity interest holder have to be reported only if that information is available in the institution’s electronically searchable data. Read this way, the codes record unavailability and leave untouched what Section 3 requires an institution to collect. A new 2026 account sent with CRS900 or CRS1200 is a data gap the institution should be able to explain, which is a different position from the role-data relief that Section 6(4) grants for older accounts.

One naming trap catches people searching for the OECD document: the user guide that describes CRS schema version 3.0 is itself “Version 4.0” of the guide, dated October 2024. The BMF links to the OECD’s publication page for the guide and the XSD.

Validation in v3.0: the account type decides what else is allowed

The BMF’s information sheet lists seven validations from the OECD’s CRS Status Message XML Schema user guide (version 3.0) and says they must be implemented for transmissions and for exchanges between states. The OECD guide itself describes its agreed record validations as a recommendation for exchanges between tax administrations; for FinanzOnline filings, the BMF guide’s rule that every error rejects the whole report is the operative one. The BMF error-code list dated 30 September 2026 carries them as ERR-DAC2 codes, together with two new checks on new accounts.

Code Rule
ERR-DAC2-60017 AcctNumberType OECD606 (Specified Electronic Money Product) requires AccountType CRS1101 (depository)
ERR-DAC2-60018 AcctNumberType OECD601 (IBAN) requires AccountType CRS1101
ERR-DAC2-60019 If EquityInterestType is given, AccountType must be CRS1104
ERR-DAC2-60020 AccountType CRS1103 (cash value insurance or annuity contract) allows only AcctNumberType OECD605
ERR-DAC2-60021 AccountType CRS1101 allows only payment type CRS502 (interest)
ERR-DAC2-60022 AccountType CRS1104 allows only payment types CRS503 or CRS504
ERR-DAC2-60023 AccountType CRS1103 allows only payment types CRS503 or CRS504
ERR-DAC2-60101 TIN is mandatory for new accounts (DDProcedure CRS1201), as the BMF list words it; Section 6(2) GMSG separately exempts jurisdictions that issue no TIN
ERR-DAC2-60102 Birth date is mandatory for new accounts (DDProcedure CRS1201), as the BMF list words it; the statutory birth-date item concerns natural persons

Read together, the codes make AccountType the key field of the account report. A custodial account whose number happens to be an IBAN cannot be sent with AcctNumberType OECD601, because 60018 reserves the IBAN type for depository accounts. A depository account with anything other than interest in its Payment block fails 60021. An insurance or annuity contract sent with any account number type other than OECD605 fails 60020. All seven are new in the September 2026 error-code list, and AccountType itself is a new element in version 3.0.

The two new-account checks differ from TIN validation in kind. The BMF error-code list words ERR-DAC2-60101 as “the TIN is mandatory for new accounts (DDProcedure=CRS1201)” and 60102 as the same for the birth date, and its TWOK table places them with the other ERR-DAC2 codes. They sit alongside the statute, which is narrower: Section 3(1) GMSG requires a birth date only for natural persons (and for controlling persons), and Section 6(2) provides that a TIN is not reported where the residence jurisdiction does not issue one. How the checks treat those cases is not stated in the BMF documents and should be confirmed with the BMF before the first version 3.0 production file.

Checks on whether a TIN is valid are handled differently. The BMF currently points institutions to the EU’s TIN-on-the-Web service for checking TIN structure, and says that if the tax authority starts validating TINs itself, invalid or faulty TINs will be flagged as notices in the transmission protocol, with no rejection of the GMSG report.

Nil reports (CRS703) from reporting period 2026

Section 4(1) GMSG, as amended, requires a reporting financial institution to transmit a report even when it maintains no reportable accounts in the reporting period, and calls that report a Nullmeldung. The BMF guide makes it concrete: nil reports are mandatory from reporting period 2026, the value CRS703 in MessageTypeIndic is accepted from reporting period 2026 onwards, and the nil report is an XML file in the same national format as any other GMSG report.

The BMF sample nil file shows the structure:

  • the Crs_National wrapper with Info_Daten (both tax numbers and the version number);
  • MessageSpec with TransmittingCountry AT, ReceivingCountry AT, MessageType CRS, MessageTypeIndic CRS703 and ReportingPeriod 2026-12-31;
  • a ReportingFI block with name, address, the institution’s tax number as IN and a DocSpec with DocTypeIndic OECD1;
  • an empty ReportingGroup element.

The empty ReportingGroup is deliberate. The BMF guide requires exactly one ReportingGroup in every transmission even when there are no AccountReport elements, and the OECD user guide makes AccountReport mandatory except where CRS703 signals that there is nothing to report. The new code ERR-DAC2-100018 rejects a CRS703 message that contains an AccountReport.

Both country fields carry AT, so the nil report is a single file to the Austrian authority covering the institution as a whole, with no separate message for each partner jurisdiction. It follows the same end-of-July deadline as an ordinary report under Section 4(1) GMSG, which puts the last day for the first one at 2 August 2027 because 31 July 2027 is a Saturday (Section 108(3) BAO). A message that does not state CRS701, CRS702 or CRS703 as its MessageTypeIndic is rejected in full.

The sample also shows the BMF’s naming pattern for the nil report’s DocRefId (AT_20261231_9999_FI_NIL_1_AT). The guide presents it as an example; the binding requirements for a DocRefId are global uniqueness and the length limit discussed below.

Submission through FinanzOnline: the national wrapper, identifiers and file limits

The BMF has adapted its national schema to Crs_National_v3.0 (namespace urn:oecd:ties:nationalcrs:v3), which imports CrsXML_v3.0.xsd and adds the Info_Daten block. The specifications package on the BMF’s bank detail page contains the version 3.0 XSDs including Crs_National_v3.0.xsd, and a separate archive contains sample files for version 3.0 and the nil report. For other jurisdictions running the same OECD schema change, see our notes on the Australian CRS reporting specification and its move to schema v3.0 and on Poland’s CRS-1(4) schema. The Info_Daten wrapper and the tax-number checks described here are specific to FinanzOnline.

Info_Daten, MessageRefId and DocRefId

Info_Daten holds Fastnr_Fon_Tn and Fastnr_Fi (exactly nine digits each) and Vers, a version number in the pattern NN.NN starting at 01.00. On top of the schema check, the error-code list runs uncoded checks for a missing or invalid version number and for the structure and reuse of the MessageRefId.

The MessageRefId follows a national structure that the version 3.0 change leaves untouched: the first nine characters are the institution’s Fastnr_Fi, followed by AT, a year of 2016 or later, and an individual value of one to eight alphanumeric characters, for a maximum of 23 characters. The BMF’s example is 091234567AT2026999. A MessageRefId may be used for one transmission only, corrections included. Length violations are caught during schema validation and reject the complete file.

Field lengths are otherwise unchanged from version 2.0: most elements and some attributes are capped at 200 characters, AddressFree, Warning and Contact at 4,000. The DocRefId is the exception that needs care. The BMF guide says the DocRefId has been adjusted to 170 characters, while the text of ERR-DAC2-80001 in the error-code list describes an invalid DocRefId as one longer than 200 characters. A generator that stays within 170 characters satisfies both documents. Each DocRefId must be unique across all of the institution’s transmissions; the only permitted repeat is the ReportingFI DocRefId resent with DocTypeIndic OECD0.

The 4,000-account limit and the one-ReportingFI rule

A message may contain at most 4,000 AccountReport elements; above that, ERR-DAC2-100004 rejects the whole transmission. Larger populations are split into several initial messages, each with its own MessageRefId and the same Fastnr_Fon_Tn, Fastnr_Fi, SendingCompanyIN and IN. The first message carries the ReportingFI with DocTypeIndic OECD1; every later one carries the same ReportingFI with OECD0. The same pattern applies when account reports are sent late for a ReportingFI already created in the period.

ERR-DAC2-100015 enforces the underlying rule: one ReportingFI record per reporting period and Fastnr_Fi. A second file for the same period that uses OECD1 in the ReportingFI is rejected. Other structural checks sit alongside it: one ReportingGroup per message (ERR-DAC2-60007), one reporting period per message (ERR-DAC2-80012), a ReportingPeriod in the form YYYY-12-31 (ERR-DAC2-100005), and no data for future reporting years.

Residence codes, extraterritorial areas and undocumented accounts

Under the OECD validation behind ERR-DAC2-60011, at least one ResCountryCode of the relevant individual account holder or controlling person must match the message’s ReceivingCountry; it is not necessary for every residence code to match. Under validation 60012, at least one residence code of the entity account holder or of its controlling persons must match ReceivingCountry. The BMF list words its 60011 and 60012 rules without the “at least one” qualifier, and section 2.1.9 of the BMF guide says that the ResCountryCode of an individual account holder or controlling person must always correspond to the ReceivingCountry, so how FinanzOnline treats an individual with a second residence code that does not match is a point to confirm with the BMF before the first version 3.0 production file. The BMF guide lists the ISO codes to use for extraterritorial areas: Saint-Martin takes MF and Saint-Barthelemy BL, while Guadeloupe, French Guiana, Martinique, Reunion and Mayotte take FR; Bonaire, Sint Eustatius and Saba take BQ, Aruba AW, Curacao CW and Sint Maarten SX; the Canary Islands take ES, Gibraltar GI, the Azores and Madeira PT, and the Aland Islands FI.

Undocumented accounts go to Austria. For a pre-existing individual account subject to Section 15 GMSG, a hold-mail instruction or c/o address can lead to undocumented-account reporting only where no other address or relevant indicia (Section 12 items 1 to 5) are identified, the required paper-record search (Section 19) finds no indicia, and attempts to obtain a self-certification or documentary evidence are unsuccessful. Section 15 then requires the institution to report the account to the competent tax office as an undocumented account, in a report under Section 4. Section 4.2.14 of the BMF guide gives the XML encoding for these accounts, including ReceivingCountry AT and placeholder values in the address and name fields.

Protocols and error codes: OK, NOK and TWOK

Every transmission is checked, and the BMF states the consequence plainly: each error rejects the entire report, none of the data in it is accepted, and after correcting the faulty data the institution has to repeat the whole transmission. The result arrives as a transmission protocol in FinanzOnline (messages, Databox), in one of three forms.

Protocol When it is issued What it tells you
OK No error code in the whole report The BMF has taken over the report in full
NOK ERR-F-001 to ERR-F-003: Fastnr_Fon_Tn or Fastnr_Fi invalid or missing, or the tax number not assigned to the FinanzOnline participant The file cannot be attributed; nothing is processed and the corrected file must be resent
TWOK No ERR-F code, at least one ERR-DAC2 code The code plus a DocRefId or an XPath pointing at the faulty part, where the error level allows a pointer

Some TWOK errors carry no pointer because they arise at a level where none is possible; the BMF’s example is ERR-DAC2-100005, a ReportingPeriod that is not YYYY-12-31. The BMF publishes sample OK, NOK and TWOK protocol files, including TWOK samples with a DocRefId and with an XPath, on its bank detail page.

The BMF’s document-version log (Stand 30 September 2026) records the error-code list as revised for the nil report and the version 3.0 schema and lists the codes it describes as newly included, among them ERR-DAC2-100018, 60013, 60008 to 60010, 60017 to 60023, 60101, 60102 and 50012, together with 60005, 60016 and 50009. For those last three the list is not a record of first introduction: the log’s earlier, undated entry adapting the error-code list to the version 2.0 schema already names 60016 as a new code (the matching guide entry is dated 23 December 2020), and an entry of 12 May 2017 records changes to ERR-DAC2-60005 and 60006 and the deletion of ERR-DAC2-50009. The OECD CRS Status Message XML Schema User Guide (version 3.0) includes the account-type validations 60017 to 60023, which the BMF carries as ERR-DAC2 rules; the current BMF error-code list remains the reference for domestic validations and protocol classification. The guide’s own description of TWOK refers to codes between ERR-DAC2-60004 and ERR-DAC2-100017, a range narrower than the codes in the list’s TWOK table, so a protocol parser should follow the list.

Resubmitting after a rejection

The BMF guide speaks with two voices on identifiers. Its error-code section says the MessageRefId and DocRefIds of a rejected message can be reused. Its protocol section says that after correcting the listed records the whole report is transmitted with a new MessageRefId, which must be unique and used only once, and the error-code list rejects a MessageRefId that was already transmitted (ERR-DAC2-50009). A fresh MessageRefId on every resubmission satisfies both passages, so building the resubmission step that way is consistent with the BMF text until it is aligned.

Corrections, deletions and late accounts after 8 January 2027

The cut-over applies to history as well. From 8 January 2027, corrections, deletions and cancellations of data transmitted earlier have to be sent in the new schema, and a file rejected under version 2.0 that misses the 21 December 2026 window is resent in version 3.0. A correction to a 2025 account report originally filed in version 2.0 therefore has to fill the version 3.0 mandatory elements, the case the OECD’s description of the “not reported” values names first.

The correction mechanics themselves are unchanged in the guide:

  • MessageTypeIndic CRS702, with DocTypeIndic OECD2 for a correction and OECD3 for a deletion; a message never mixes new records with corrections (ERR-DAC2-80010).
  • The ReportingFI is always included; it carries OECD0 and its existing DocRefId when it has not changed.
  • A corrected AccountReport is sent complete, with every unchanged child element; AccountReports that are not being corrected are left out.
  • CorrDocRefId points to the DocRefId of the immediately preceding version of the record. A correction of a correction that points back to the initial record is not allowed, and the BMF asks for corrections to be sent in chronological order.
  • A child element such as one controlling person is deleted by resending the whole AccountReport as OECD2 without that child. A ReportingFI can be deleted only after all its AccountReports have been deleted (ERR-DAC2-80009).
  • In the BMF’s example of an account with controlling persons in two Member States, a correction to one controlling person goes to both states, even though nothing changed for the controlling person reported to the second.

Corrections and deletions remain possible after 31 July and in later years. Late account reports for a period follow the split-message pattern: a new initial message (CRS701) with the existing ReportingFI as OECD0 and only the additional AccountReports.

Frequently Asked Questions

Can we test version 3.0 files in FinanzOnline before 8 January 2027?

The BMF says version 3.0 reports can be tested through FinanzOnline from 8 January 2027, the same day the new schema goes live for production. Before that date, the published specifications package (with Crs_National_v3.0.xsd) and the version 3.0 sample files are what is available for checking files against the schema locally, and the error-code list documents the business rules that FinanzOnline applies on top of the schema.

An e-money account opened in February 2026 became reportable only because of DAC8. Is it new or preexisting for DDProcedure?

The BMF answered a related question from the Austrian Economic Chamber: for accounts that become reportable only through the DAC8 changes, the opening date from 1 January 2026 is relevant, so such an account opened on 31 December 2025 counts as preexisting and one opened on or after 1 January 2026 as new. For accounts that were already reportable before, Sections 79 and 80 GMSG continue to decide. On that reading a February 2026 account is CRS1201, which brings in the checks of ERR-DAC2-60101 and 60102 as the error-code list words them.

A passive NFE is resident in one Member State; two of its controlling persons live there too and a third lives in another Member State. How many messages do we send?

One per receiving state. The BMF’s worked example has an entity in state B with two controlling persons in state B and one in state C. The message to state C carries one AccountReport with holder type CRS101 and the state C controlling person. The message to state B carries two AccountReports: one with holder type CRS103 and no controlling persons, and one with CRS101 and the two state B controlling persons. ControllingPerson is rejected with CRS102 or CRS103 (ERR-DAC2-60005) and required with CRS101 (ERR-DAC2-60006).

We need to correct both 2024 and 2025 data in early 2027. Can one correction message cover both?

No. A message may contain data for one reporting period only (ERR-DAC2-80012), and every CorrDocRefId in a correction must refer to the ReportingPeriod stated in that message. Two periods mean two CRS702 messages, each with its own MessageRefId, and from 8 January 2027 both are built in version 3.0.

Does ERR-DAC2-60101 reject a new account whose holder is resident in a state that issues no TINs?

The BMF documents do not say. Section 6(2) GMSG still provides that a TIN is not reported where the residence state does not issue one, while the error-code list states the 60101 rule without an exception. The point stays open until the BMF clarifies how the check treats that case, and institutions with such account holders can put the question to the BMF before their first version 3.0 production file.

We file a nil report for 2026 and later find a reportable account. How do we add it?

The guide does not cover this sequence explicitly. Its late-submission pattern is a new CRS701 initial message with the existing ReportingFI as OECD0 plus the additional AccountReports, and ERR-DAC2-100015 allows only one ReportingFI record per period and Fastnr_Fi. Whether a ReportingFI first created in a CRS703 message counts as that record, and how the nil report itself is treated afterwards, is a question for the BMF before the file is sent.

Key Takeaways

  • Any file, correction or resubmission still pending in version 2.0 has to be transmitted by 21 December 2026; after that it waits for 8 January 2027 and is rebuilt in version 3.0.
  • Assign AccountType to every reportable account before mapping payments and account-number types: ERR-DAC2-60017 to 60023 validate both against it.
  • Every reporting financial institution with no reportable accounts in 2026 needs a CRS703 file with an empty ReportingGroup. Section 4(1) GMSG sets the end of July 2027; Saturday 31 July moves to Monday 2 August 2027 under Section 108(3) BAO, while the BMF guide refers to 31 July, so a file sent by Friday 30 July 2027 avoids the question.
  • For accounts flagged CRS1201, report the TIN information the GMSG requires, subject to the Section 6(2) exception where the residence jurisdiction issues no TINs; birth-date reporting concerns natural persons. Confirm with the BMF how 60101 and 60102 treat those cases.
  • Cap generated DocRefIds at 170 characters and issue a new MessageRefId for every transmission, resubmissions included.
  • Log a reason for each “not reported” value: Section 6(4) GMSG relieves role data only for accounts maintained on 31 December 2025 and reporting periods ending by 31 December 2027.
  • Check the BMF document-version log before each production run: the 2027 package is published subject to further EU adjustments.

Sources and References

  • BMF, Allgemeine Informationen GMSG (CRS XSD v3.0 ab 2027), Stand 5 November 2026: BMF technical guide (PDF)
  • BMF, Information ueber das neue CRS-XSD-Schema Version 3.0 ab 2027 (Gemeinsamer Meldestandard): BMF information sheet (PDF)
  • BMF, Fehlercodeverzeichnis GMSG ab Jaenner 2027, Stand 30 September 2026: BMF error-code list (PDF)
  • BMF, Dokumentenversion GMSG ab Jaenner 2027, Stand 30 September 2026: BMF document-version log (PDF)
  • BMF, Detailinformationen fuer Banken (GMSG downloads, specifications, samples and protocol examples): BMF bank detail page
  • BMF, Umsetzungsfragen DAC8 Implementierung: BMF DAC8 implementation questions
  • Gemeinsamer Meldestandard-Gesetz (GMSG), original text, BGBl. I Nr. 116/2015, Article 4: RIS (PDF)
  • Betrugsbekaempfungsgesetz 2025 Teil Daten, BGBl. I Nr. 96/2025 (Article 2 amends the GMSG): RIS
  • GMSG Section 3 (Allgemeine Meldepflichten), consolidated version from 1 January 2026: RIS
  • GMSG Section 4 (Zeitpunkt, Form und Uebermittlung der Meldung), consolidated version from 1 January 2026: RIS
  • GMSG Section 6 (Entfall von Meldepflichten), consolidated version from 1 January 2026: RIS
  • GMSG Section 15 (Postlagerungsauftrag, c/o-Adresse): RIS
  • GMSG Section 117 (Inkrafttreten), subsections 7 and 8: RIS
  • Bundesabgabenordnung (BAO) Section 108 (Fristen): RIS
  • OECD, Common Reporting Standard Status Message XML Schema User Guide (June 2025), record validations 60011 to 60023: OECD (PDF)
  • GMSG Section 1a (registration and deregistration): RIS
  • GMSG Section 72 (definition of depository account): RIS
  • GMSG Section 87 (Ausgenommenes Konto), consolidated version from 1 January 2026: RIS
  • Council Directive 2011/16/EU on administrative cooperation in the field of taxation: EUR-Lex
  • Council Directive (EU) 2023/2226 of 17 October 2023 (DAC8): EUR-Lex
  • Council Directive (EU) 2025/872 of 14 April 2025 amending Directive 2011/16/EU: EUR-Lex
  • OECD (2024), Amended Common Reporting Standard XML Schema: User Guide for Tax Administrations, Version 4.0, October 2024: OECD (PDF)

Before 21 December 2026: closing the version 2.0 window

The calendar leaves one decision for December. Anything that still has to go out in version 2.0, whether a late account report, a correction or the resubmission of a rejected file, has to be transmitted through FinanzOnline by 21 December 2026, and a rejection that arrives after that date can only be answered with a version 3.0 file. FinanzOnline reopens for GMSG files on 8 January 2027, and the first full version 3.0 report for reporting period 2026, nil reports included, is due by 2 August 2027 (the end-of-July deadline of Section 4(1) GMSG, moved from Saturday 31 July by Section 108(3) BAO).

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.

Similar Posts

  • Luxembourg-Viet Nam Tax Treaty: Information Exchange Rules From 2027

    The protocol amending the Luxembourg-Viet Nam tax treaty entered into force on 14 April 2026, according to the entry-into-force notice published in Memorial A No. 506 on 23 October 2026. Signed in Hanoi on 4 May 2023, the protocol deletes Article 27 of the 1996 double taxation convention, the exchange-of-information article, and replaces it with…

  • CBAM Indirect Emissions: What the DG TAXUD Study Means for Importers

    Get CBAM indirect emissions wrong and the error does not show up as a rejected file. It shows up later, as a number on a CBAM declaration that you cannot defend, or as a default value you paid for because the supplier data never arrived. The Carbon Border Adjustment Mechanism has moved from its quiet…

  • VAT Reverse Charge Extension: Articles 199a and 199b to June 2030

    On 1 October 2026 the European Commission adopted COM(2026) 515, a proposal for a Council directive that would let Member States keep using two VAT anti-fraud tools until 30 June 2030: the optional reverse charge mechanism in Article 199a of the VAT Directive and the Quick Reaction Mechanism (QRM) in Article 199b. Under the Directive…

  • BZSt CRS Reporting: The Schema v3.0 Switch and Saint-Martin Refile

    On 9 September 2026 the Bundeszentralamt fuer Steuern (BZSt) issued CRS Newsletter 04/2026, and it carries four items relevant to BZSt CRS reporting. The Federal Ministry of Finance has published an English translation of the BMF-Schreiben that fixes the officially prescribed dataset and interface; the BMF-Schreiben dated 14 January 2026 requires version 2.0 for transmissions…