Reference

Supported countries

TRSuite produces reports for the OECD Common Reporting Standard (CRS), IRS FATCA and the OECD Crypto-Asset Reporting Framework (CARF). What "supported" means differs by jurisdiction: for some it is the plain OECD schema, for others a national schema and a ready-to-upload delivery package. This page lists, per standard and per jurisdiction, the level TRSuite reaches, the current status and any restriction worth knowing before you rely on it.

Last updated 9 November 2026

TRSuite produces reports for the OECD Common Reporting Standard (CRS), IRS FATCA and the OECD Crypto-Asset Reporting Framework (CARF). What "supported" means differs by jurisdiction: for some it is the plain OECD schema, for others a national schema and a ready-to-upload delivery package. This page lists, per standard and per jurisdiction, the level TRSuite reaches, the current status and any restriction worth knowing before you rely on it.

TRSuite writes OECD CRS XML 2.0 and 3.0 and reads CRS XML 1.0, 2.0 and 3.0. FATCA is written as IRS FATCA XML 2.0 and 2.0.1, CARF as OECD CARF XML 1.5 (CARF XML 1.0 files can still be opened). Data can be entered in the application or imported from the supplied Excel templates: generic CRS, FATCA and CARF workbooks plus the Hong Kong, Macau and Swiss SEI variants. Where a taxpayer identification number of a natural person was issued by one of the following countries, TRSuite checks its format and, where the national algorithm has one, its check digit: AT, BE, BG, CH, CY, DE, DK, EE, ES, FI, FR, GB, HR, HU, IE, IT, LT, LU, NL, PL, PT, SE and SI. For CZ, GR, LV, MT, RO and SK only the structure is checked, because the European Commission does not publish their check digits. A Danish number that fails only the modulus 11 check is reported as a note, since numbers issued from 2007 may legitimately fail it; a Cypriot TIN of a natural person must start with 0, 6 or 9. Identification numbers of entities are checked with the national algorithm only where it also covers entities: CH, NL, PL, PT and SI.

How to read this page

TRSuite can support a jurisdiction at up to four levels, each building on the one before it. A row may name several levels.

  1. Generic OECD schema — the report is produced against the plain schema of the standard (OECD CRS, OECD CARF or IRS FATCA), with no country-specific fields or rules. Most jurisdictions in the list below also carry country presets: default currency, identifier conventions and file naming.
  2. Country validation rules — TRSuite additionally applies the jurisdiction's own rules (message header requirements, identifier formats, TIN formats, mandatory fields, character restrictions) before the report is exported. Rows marked Basic country rules carry a small subset only; the cell says which. Where an authority only recommends something, TRSuite shows a note instead of an error; notes do not make a report invalid.
  3. National format — the jurisdiction defines its own XML schema or additional header elements, and TRSuite produces that national format directly.
  4. Transmission package — TRSuite also builds the file or files ready for the jurisdiction's upload channel (naming convention, compression, signing, encryption, sender metadata), not just the report XML.

On export, every report is validated against the XML schema of the selected version; the OECD XML export also warns when the written file exceeds the file size limit of the selected country.

Corrections, deletions and late filings for reporting periods before 2026 can be exported in CRS XML 3.0: when a CRS XML 1.0 or 2.0 file for such a period is loaded, TRSuite fills the empty CRS 3.0 mandatory fields with the "not reported" codes the OECD allows for those periods and shows a note; existing values are kept. The same applies to Excel workbooks and saved work files; the entry forms do not pre-fill.

Status is one of: Available (in the current release), Restricted (available, but the authority currently rejects the produced file or channel; update in preparation), In preparation (being built), Planned (scheduled, no date committed).

OECD CRS

CountryCodeSupportStatusRestrictionsUser guide
AlbaniaALTransmission package · Basic country rulesAvailableCharacter set check. The export is checked against CRS XML 1.0, and values that exist only from CRS XML 2.0 or 3.0 (for example account number type OECD606 or controlling person type CRS800) are reported. Signed GovTalk submission to the tax administration.–
Antigua and BarbudaAGGeneric OECD schemaAvailableCountry presets only (default currency, identifier and file naming conventions); no country validation rules.–
ArubaAWCountry validation rulesAvailableDelivery to DIMP through the MDES portal as plain OECD XML, schema 2.0 (select CRS version 2.0). Reference IDs are generated and checked in the DIMP form AW + reporting year + registration number of the delivering institution. No schedule for schema 3.0 published by DIMP.–
AustraliaAUNational format · Country validation rulesAvailableBBDM envelope for the ATO services crs.0002 (CRS XML 2.0) and crs.0003 (CRS XML 3.0); the CRS content is checked against the CRS schema before the envelope is written, and the sender identifier (ABN or TAN) is selectable. Validation covers the ATO CRS validation rules (2021 v1.4 and the draft 2027 rules), including ABN/TFN/GIIN checks, the reference ID format, restricted country codes, the CRS 3.0 consistency rules and the ATO rule for characters outside ASCII. Hard cutover to CRS 3.0 on 2027-01-01: from that date a CRS 2.0 file is reported as an error. The 2027 rules follow the ATO's draft specification and will be updated when it is final.–
AustriaATNational format · Country validation rulesAvailableGMSG/BMF format wraps OECD CRS 1.0 and 2.0; schema 3.0 mandatory from 2027-01-08 (national package due Nov 2026), update in preparation. Validation applies the FinanzOnline rules (no nil reports, MessageRefId format, dates of birth, empty or blank values); the national export checks the Info_Daten tax numbers against the report and is not written if that check finds errors (notes do not stop it).CRS Austria
BahamasBSCountry validation rulesAvailableValidation follows the AEOI Portal User Guide 2026: reporting period 31 December, nil filings (CRS703) only as domestic filings, Reporting FI resident in the Bahamas, DocRefIds starting with BS and without spaces, residence in the receiving country, no nationality, date of birth range, undocumented-account flag for domestic filings. The AEOI Portal validates against CRS XML 2.0 until 2026-12-31 (select CRS version 2.0; a CRS XML 3.0 file before that date is shown as a warning); from 2027-01-01 it accepts only CRS XML 3.0 and CRS 2.0 is no longer accepted (reported as an error). The Competent Authority's FAQs refer to reporting period 2027 for schema 3.0, so a CRS XML 3.0 file for reporting period 2026 is shown with a note to confirm with the Competent Authority. No test environment. First Amended CRS exchanges 2028.–
BelizeBZGeneric OECD schemaAvailablePlain OECD schema. Belize has not signed the CRS MCAA Addendum as of 2026-08. Country validation rules planned.–
BermudaBMCountry validation rulesAvailableValidation follows the Bermuda Tax Information Reporting Portal User Guide v8.0 (CRS body, account reports, DocRefId prefix and spaces, test values, nil reports, nationality, date of birth, tax residence, repeated payment types, undocumented-account flag); missing dates of birth and TINs are shown as notes.–
British Virgin IslandsVGCountry validation rulesAvailableValidation follows the BVIFARS User Guide 10.0.1: Transmitting Country and Reporting FI VG, nil filings (CRS703) only domestic, undocumented-account flag for domestic filings, DocRefIds starting with VG for non-domestic filings and without spaces, residence in the receiving country, no nationality, date of birth range.–
CanadaCANational format · Country validation rulesAvailablePart XIX return in the CRA formats 2026V2 (official CRA schema package 2026, version 1.26) and 2028V1 (Amended CRS, taxation year 2027 onwards, with the CRS 3.0 fields); the target format is preselected from the taxation year and can be changed. The 2028V1 format may still change until the underlying legislation receives Royal Assent. CRA checks on document reference IDs (duplicates, taxation year, business number), filer account number (RZ program), reporting FI resident in Canada, SIN and file size. A TIN without issuing country is written as the residence TIN when the party has exactly one residence country; otherwise a note is shown. Trusts can be reported with their trust account number; the T619 transmitter record accepts the transmitter account number, the RepID or both.CRS Canada
Cayman IslandsKYCountry validation rulesAvailableValidation follows the DITC Portal User Guide: CRS701/702 only (a nil return is made with the CRS Filing Declaration), Reporting FI IN issued by KY, OECD0 (resend) accepted for the reporting FI in corrections, receiving country KY only for undocumented accounts, residence in the receiving country, DocRefId format with reporting year, receiving country, FI Number and a unique part of up to 10 characters; generated IDs follow that format. File size limit 150 MB. Reporting for 2026 is due in v3.0 by 2027-06-30.–
ChileCLGeneric OECD schemaAvailableTRSuite does not produce a file that can be filed with the SII: the SII collects CRS data through the sworn statement DJ 1958, which is filed through the SII's own form or in the SII's own column format, not as OECD XML. The OECD XML produced by TRSuite can serve as the data basis for DJ 1958. No country-specific reference ID formats. A note reminds that institutions without reportable accounts must still file DJ 1958.–
ChinaCNNational format · Basic country rulesAvailableCNCRS format wraps OECD CRS 1.0. "Validate" checks the CNCRS schema and selected STA rules (residence code, names, placeholder date of birth, Message Reference ID format with the year of submission and the P/N indicator, prohibited character sequences, corrections and the separation of new, corrected and test data, nil reports, account balances, unique DocRefIds within the report); nil reports (CRS703) can be created. Not the complete STA rule set. CRS 3.0 pending; no national CRS 3.0 schema published.–
Cook IslandsCKCountry validation rulesAvailableValidation follows the IGOR rules: Reporting FI resident in CK, no name type OECD201 for organisations, date of birth also for controlling persons, one ReportingGroup per CrsBody, no whitespace-only TINs, no test document types (OECD10–OECD13), no DocRefIds differing only in letter case, and the Reporting FI of a correction must be present; messages mixing new and corrected data are rejected. A Transmitting Country other than CK is only a note. IGOR portal API for reporting FI administration only; no report upload.–
Costa RicaCRCountry validation rulesAvailableMessage header, DocSpec, account holder and controlling person checks. Reference IDs are generated in the TRSuite format but not checked against a pattern (the DGT prescribes none). Notes only, not blocking the file: residence outside the 89 active exchange partners published by the DGT (list of 1 July 2026), individuals without a TIN, a reporting period other than 31 December, and nil reports (CRS703). The DGT expects a nil report through the SIIF portal, not as an XML file, and requires the exported file to be signed and encrypted with the Ministry's own tool before upload — neither step is part of TRSuite.–
CuraçaoCWNational format · Country validation rulesAvailableWrites the combined FATCA/CRS format FC XML 2.2, the version the MDES portal accepts, and validates it against the official schema; FC XML 2.0 files and older work files can still be opened. Validation of the MDES delivery rules (IDs with CW and the tax year, correction and Nil Report rules, mandatory fields, prohibited character sequences); generated IDs follow the MDES format. The CRIB number format itself is not checked. No CRS 3.0 path yet.–
CyprusCYGeneric OECD schemaAvailableCountry presets only (default currency, identifier and file naming conventions); no country validation rules. TINs of individuals are checked as described above.–
FinlandFINational format · Country validation rulesAvailableTAXFI format v1.0 and v2.0. Validation follows the Ilmoitin.fi rules (Business ID with check digit, contact, CorrMessageRefId in corrections, nil return, IN type, name type, TIN, date of birth). From 2027-01-01 the Finnish Tax Administration replaces TAXFI with the OECD CRS XML 3.0 schema, first for reporting year 2026; update in preparation.–
FranceFRCountry validation rulesAvailableValidation follows the DGFiP rules of cahier des charges v3.7: identifiers (SIREN/IDSP), MessageRefId and DocRefId format, mandatory Warning value, no GIIN for French identification numbers, residence code of the Reporting FI, date of birth, undocumented accounts and the character #; filings for New Caledonia, Saint-Martin and Saint-Barthélemy (FR/NC/MF/BL) are accepted. Invalid TINs are shown as notes, as the DGFiP does not reject them.–
GermanyDECountry validation rulesAvailableNo national format: the report is the plain OECD XML, uploaded through the mass data upload of the BZSt online portal (as required there, without a DIP envelope). TRSuite does not support the automated DIP interface, which needs the DIP envelope (dip:dip) around the report. The former BZSt ELMA export was removed, because the BZSt closed ELMA for CRS at the end of Nov 2025. Schema 3.0 mandatory from 2027-01-01; the BZSt accepts schema 2.0 for productive submissions until 2026-12-31. Validation also applies the BZSt record description for schema 3.0 (Federal Ministry of Finance, 14 Jan 2026): reporting period ending 31 December, reporting year in the MessageRefId and DocRefIds, one CrsBody, one controlling person type per controlling person, schema 3.0 only from 2027-01-01. Cancellation deliveries (Stornolieferung) are supported: message type CRS702 with the MessageRefIds of the cancelled deliveries in the header and only the Reporting FI (OECD0), no account reports. Validation applies the BZSt content rules of the CRS communication manual part 4 (13-digit ELSTER tax number: a Sending Company IN or reporting FI IN in a legacy format is a note until 2026-12-31 and an error from 2027-01-01; a note if the reporting FI carries more than one IN; no test data, DocRefId with the tax number, undocumented accounts, names, date of birth, nationality, at most 20,000 account reports, field lengths, file size limit 100 MB).–
GuernseyGGCountry validation rulesAvailableValidation follows the IGOR XML Reporting Guide: messages mixing new and corrected data are accepted, the Transmitting Country is only a note, test document types (OECD10–OECD13) and DocRefIds that differ only in letter case are rejected. From 2027-01-01 only CRS XML 3.0 can be submitted, for every reporting year including corrections, voids and additions for prior years (draft Guernsey CRS Guidance Notes v2, section 5.11.4); a CRS 2.0 file from that date is reported as an error, a CRS XML 3.0 file before that date receives a note (accepted once IGOR has adopted schema 3.0). CRS XML 3.0 messages are checked against the draft Guidance Notes v2: "not reported" codes are errors from reporting period 2026 (CRS800 only for pre-existing accounts in 2026–2027), the account type must match the account number type, equity interest type and payment types, and a joint account needs more than one holder; notes for a missing date of birth and for the Remediation Disclosure Package of corrections. IGOR portal API for reporting FI administration; no report upload.–
Hong KongHKNational format · Country validation rulesAvailableIRD AEOI schema v2.0 only; under the current Bill the Amended CRS applies from 2028. Validation includes the prohibited character sequences of the IRD user guide, DocRefIds of at most 40 characters and duplicates that differ only in letter case; a Message Reference ID outside the IRD file name format is shown as a note. Generated Message Reference IDs carry a sequence number (00–99), so two files created in the same second no longer collide. Recommended file size limit 200 MB. Manual upload to the IRD portal; no transmission package.CRS Hong Kong
IrelandIECountry validation rulesAvailableValidation follows the Revenue rules: file size limit 30 MB, 20,000 account reports; notes for the character #, the Revenue reference ID pattern and controlling persons resident in several jurisdictions. Character set check with a tool to replace invalid characters.–
Isle of ManIMCountry validation rulesAvailableValidation follows the ITD validation table for CRS schema 3.0 (GN53 and Industry Advisory Notice of 18 December 2025): "not reported" codes rejected from reporting period 2026, account type and payment cross-checks, no CorrMessageRefId, DocRefIds starting with the GIIN or the Isle of Man tax reference followed by a full stop, unique Reporting FI names, no pool reports or test document types, file size limit 124 MB. The authority accepts v3.0 only from 2026-10-01; TRSuite writes v3.0.–
IsraelILBasic country rulesAvailablePlain OECD CRS XML. Message header checks, with notes when the MessageRefId is not 24 or a DocRefId not 33 characters long, as in the ITA technical guidelines.–
ItalyITCountry validation rulesAvailableValidation follows the Agenzia delle Entrate Istruzioni v2.3: MessageRefId/DocRefId format, codice fiscale of the sender, dates without time zone, character set in names, no empty TIN elements; substitute communications (CRS701 with CorrMessageRefId) are accepted. Findings on TINs issued by other states are shown as notes only, since the Agenzia only warns about them (for Czechia, Greece, Latvia, Malta, Romania and Slovakia only the structure is checked, see above).–
JapanJPGeneric OECD schemaAvailableCountry presets only (default country and currency); no country validation rules.–
JerseyJECountry validation rulesAvailableValidation follows the Jersey CRS practical guidance v10.0: reference IDs starting with JE + year of the data + JE, CorrMessageRefId required on corrections (OECD2/3) and filled in by "Correct Report", TIN also for controlling persons and entity account holders with NOTIN as the only placeholder, no Nationality, no empty elements, date of birth and account type rules.–
LiechtensteinLICountry validation rulesAvailableValidation follows the STV additional specification of 14 April 2026 (7-digit reporting office number, Reporting FI resident in LI with PEID (an IN issued by LI must be the PEID, an IN without issuing country is only a note), one document type per message, no spaces or special characters in reference IDs, no blank fields); the export carries the required schemaLocation. A file with receiving country LI where an account is not resident in Liechtenstein is shown as a note, since the STV expects one file per final receiving country. The STV accepts v2.0 until 2026-11-30 and v3.0 thereafter: select CRS version 2.0 in the configuration for a v2.0 export; the validation shows a note until 30 November 2026 and an error from 1 December 2026.–
LuxembourgLUNational format · Country validation rulesAvailableACD formats CRS_LUX V2.0 (OECD CRS 2.0, until 2026-12-31) and CRS_LUX V3.0 (OECD CRS 3.0, mandatory from 2027-01-01, ACD pre-validation from 2026-10-12), selectable per export together with the production or test environment. Files are checked against the ACD rules before they are written (V3.0 also against the ACD schema); ZeroReports (CRS703) and overseas-territory destination codes are supported; sponsor, intermediary, pool reports, nationality and name type OECD201 are rejected. File size limit 60 MB until 2026-12-31, 250 MB from 2027-01-01. Manual upload to the ACD portal; no transmission package.CRS Luxembourg
MacauMONational format · Transmission package · Country validation rulesAvailableDSF AEOI v1.1 to v1.4, selectable per report; v1.4 carries the CRS 3.0 content and is valid from 2027-01-01. Validation covers the DSF status message error catalogue (Message Reference ID and file name, Return Year, date of birth range, blank values, duplicate elements, name and reference ID lengths, residence country of organisations); the export reports a file name that differs from the Message Reference ID and files above 100 MB.CRS Macau
MalaysiaMYTransmission package · Country validation rulesAvailableNo national format; the report is the plain OECD XML. MyCRSID checked as 8 digits throughout. The Message Reference ID is accepted in both forms used in the IRBM's examples (22 characters, or 26 characters with the reporting year); TRSuite generates the 22-character form. HiDEF/CTS delivery package, created only when it is complete (sender metadata, all packaging steps). Schema 3.0 applies from 2027-01-01.CRS Malaysia
MaltaMTGeneric OECD schemaAvailableCountry presets only (default currency, identifier and file naming conventions); the Sending Company IN is checked for the 9-digit Malta income tax number (note only). No other country validation rules.–
MauritiusMUGeneric OECD schemaAvailableNo country presets and no country validation rules.–
San MarinoSMCountry validation rulesAvailableValidation follows the Guida pratica per l'invio dei flussi dati CRS v2.0: Transmitting and Receiving Country SM, CRS701 only with OECD1, no blank TIN or IN elements (a TIN without an issuing country is a note), and Passive NFE coding notes. On export TRSuite proposes the file name required by Regulation 20/2015.–
SeychellesSCCountry validation rulesAvailableAccount holder, individual and controlling person checks against the reportable jurisdiction list of Statutory Instrument 54 of 2026, Schedule 5 (89 jurisdictions, reporting year 2025). The IN of the reporting FI is optional, as in the regulations ("if any").–
SingaporeSGCountry validation rulesAvailableValidation follows the IRAS CRS error code list and the IRAS XML Schema User Guide 4.0.1 (transitional codes by reporting year, date of birth, nil returns only for Trustee-Documented Trusts, Reporting FI resident in SG, TIN issuing country, undocumented accounts); a missing TIN with a valid IRAS reason code is accepted, and the reason codes IRAS101–IRAS104 are not checked as TINs. The jurisdiction list follows the IRAS list for reporting year 2025 (updated 2 February 2026); Antigua and Barbuda and Curaçao are accepted only for corrections of reporting years before 2023 and 2025 respectively. The character # is rejected, as IRAS does not accept it in a CRS return (write unit numbers such as #03-12 as 03-12). IRAS requires one account report per jurisdiction of residence and per controlling person; TRSuite does not split such accounts, so they must be entered as separate account reports. CRS 3.0 applies from 2027-01-01, when the file size limit rises from 5 MB to 50 MB.–
SwitzerlandCHTransmission package · Country validation rulesAvailableEncrypted CRS archive for the ESTV. Validation follows the ESTV technical guidance: message header, reporting FI, party and character set checks, DocRefIds of up to 200 characters, the account type rules 60017 to 60023 for CRS 3.0, undocumented accounts, address and date of birth of controlling persons. A correction (CRS702) of only the reporting FI needs no account reports. Test submissions: a separate menu item writes the ESTV test archive (test document types, archive name starting with Test); a production archive whose name starts with Test is shown with a warning, because the ESTV treats it as a test submission. File size limit 100 MB.–
United KingdomGBCountry validation rulesAvailableHMRC accepts CRS returns only on the OECD Amended CRS XML schema 3.0 from 2027-01-01, including returns for earlier years. TRSuite checks the HMRC rules for the schema version, the transitional "not reported" codes by reporting year and the ISO-8859-1 character set, with notes for accounts without account number, undocumented and UK-resident account holders. HMRC has not published reference ID or file size rules; the OECD defaults apply. HMRC's own combined CRS/FATCA schema, valid until 2026-12-31, is not supported and will not be; FATCA is reported separately in the IRS schema (see FATCA below).–
UruguayUYNational format · Transmission package · Country validation rulesAvailableDoméstico format in schema 2.2 (OECD CRS 2.0) and 3.0 (OECD CRS 3.0, mandatory from 2027-01-02), chosen from the CRS version of the configuration, including the message type CRS708 (total update of a previous report, "reliquidación total"); the export is checked against the DGI domestic schema. OECD files of all other countries reject CRS708 with a clear message. Validation follows the DGI rules (account average, RUC as Sending Company IN, TIN requirements and types, residence against the receiving country, identification type of organisations, the reference to the previous report for a total update, no sponsor, intermediary or pool report). Archivo and Archivo cifrado delivery packages with schema selection. From 2027 the DGI accepts reports and corrections from 1 March to 31 May, followed by 30 days for corrections only. Undocumented-account files with receiving country YY in the DGI domestic format are supported; the MessageRefId is checked against the DGI format, and CRS708 can also be selected in the Excel templates.–
VanuatuVUGeneric OECD schemaAvailableCountry presets only (default currency, identifier and file naming conventions); no country validation rules.–

Not listed? The table names the jurisdictions for which TRSuite carries something of its own. It is not the list of jurisdictions you can report for. Any authority that accepts the plain OECD CRS XML can be served at the Generic OECD schema level today, whether or not it appears above: you select the default profile, TRSuite writes CRS 2.0 or 3.0 and validates it against the OECD schema, and you follow the authority's own identifier and naming conventions yourself. See the CRS module guide for how the generic path works.

FATCA

FATCA reporting is generic: one IRS schema for all jurisdictions, with no country-specific rule sets. Two countries add a channel of their own. For the United Kingdom, HMRC accepts FATCA reports in the IRS schema, separately from CRS, from 1 January 2027; its combined CRS/FATCA schema is not supported.

CountryCodeSupportStatusRestrictionsUser guide
United States (IRS)USGeneric IRS schema · Transmission packageAvailableFATCA XML 2.0 and 2.0.1, chosen from the version attribute of the file. Validation includes the IRS rules for the prohibited character sequences, DocRefIds of at least 21 characters and reporting periods in a future year; a DocRefId that does not start with the GIIN is shown as a warning (IRS best practice). With target version 2.0, values that only FATCA XML 2.0.1 defines (country code XX, currencies BYN, MRU, STN, UYW, VED, VES) are reported as errors. IDES package with sender metadata 1.1 to 1.3 (FileFormatCd XML and BinaryEncodingSchemeCd NONE for FATCA XML; the real file format and BASE64 for files wrapped with "Wrap Non-XML") and SFTP transfer with host key verification; before the archive is created, the document types are checked against the target IDES gateway (test data is not sent to production).FATCA, IDES
SwitzerlandCHTransmission package · Country validation rulesAvailableSEI group requests to the ESTV, written as FATCA XML 2.0.1. A customer-specific archiving and upload extension exists and is available on request.SEI Switzerland
CuraçaoCWNational format · Country validation rulesAvailableOne combined FATCA and CRS file (FC XML 2.2); see the Curaçao row in the CRS table.–

CARF

CARF reporting is generic. TRSuite writes OECD CARF XML 1.5 for every jurisdiction, with the OECD identifier and naming conventions. Country rules: Finland and Liechtenstein (see below). When each jurisdiction expects the first CARF reports, and which of them TRSuite covers, is shown on First CARF filing deadlines.

CountryCodeSupportStatusRestrictionsUser guide
All jurisdictions–Generic OECD schemaAvailableWrites and validates OECD CARF XML 1.5 (OECD, September 2025), including nil reports (CARF703) and reports that only state the nexus of the service provider; CARF XML 1.0 files can still be opened and are exported as version 1.5. Amounts are reported with two decimal places; units may have decimals for every transaction kind. New document reference IDs follow the CARF pattern (country code, reporting year, unique identifier). Validation also covers the remaining rules of the OECD CARF User Guide: an unknown TIN must be flagged NOTIN, the birth date of an individual Reporting Crypto-Asset Service Provider defaults to 1900-01-01 when none is entered, deleting a service provider requires its Crypto Users to be deleted too, test and production document types may not be mixed, and Nationality is no longer written to the file. The service provider must be resident in the transmitting country (OECD status 60005), a CARF701 message without Crypto Users needs an OtherNexus (status 60011), and a corrected report keeps the DocRefID of a resent service provider. Optional EU TIN check for individuals and, for CH, NL, PL, PT and SI, for entities. Mandatory fields that contain only spaces are reported as missing. Country rules: Finland and Liechtenstein (see below).CARF
FinlandFICountry validation rulesAvailableValidation follows the CARF/DAC8 technical guidance 1.0H of the Finnish Tax Administration (Ilmoitin.fi checks): Finnish MessageRefID and DocRefID formats with running numbers, file name = MessageRefID, one Crypto Users record per crypto asset and transaction type (split automatically when DocRefIDs are generated), timestamp with milliseconds, 100 MB limit. TRSuite also creates the FICARF nil report (FICARF703) and checks FICARF files created by the provider's trading system before upload; the full FICARF return itself comes from the trading system.CARF
LiechtensteinLICountry validation rulesAvailableValidation follows the STV additional XML specification CARF of 4 February 2026: PEID as SendingEntityIN and RCASP TIN, RCASP resident in LI, reference IDs LI + year + receiving country + "." + unique part (generated by TRSuite), one document type per message, no nil reports (CARF703), reporting periods from 2026, no fields consisting of spaces only and no "##"; one file per receiving country is recommended (note).CARF

Known limitations (all CRS jurisdictions)

Every CRS report, whatever the jurisdiction, is checked against the rules of the OECD CRS XML User Guide v4.0 and the CRS status message schema that apply to all authorities: DocRefId uniqueness within the file, OECD0 (resend) for the reporting FI only, the correction rules (CorrMessageRefId and CorrDocRefId, deleting a reporting FI, mixing test and production data), no Pool Report, one ReportingGroup per CrsBody, no name type OECD201, no negative account balance and the prohibited character sequences --, /* and &# in element values and attributes. The following gaps remain:

  • Uniqueness of MessageRefId and DocRefId against earlier submissions cannot be checked from a single file; TRSuite generates unique IDs, IDs entered by hand are your responsibility.
  • The rule that an account holder must be resident in the receiving country (OECD status message 60011) is checked only for the jurisdictions that require it, because in a domestic report the receiving country is the reporting jurisdiction itself.
  • The file size warning is given for the OECD XML export and the Macau and Canada exports; "Split & Save", command-line and the other national-format exports do not warn.

Contact

This page is reviewed and updated with every TRSuite release. Regulatory dates are those published by the authorities at the date above; check the authority's own site before you rely on one.

Missing a jurisdiction, or found something here that no longer matches the application? Write to support@section11.ch.