TRSuite 26.03 is a major release for the reporting year 2026. It writes CRS XML 3.0 and 2.0, FATCA XML 2.0.1 and CARF XML 1.5, extends the country rules of more than 30 jurisdictions to the current specifications of their tax authorities, adds national formats for Luxembourg (CRS_LUX V3.0), Uruguay (Doméstico 3.0), Canada (Part XIX 2028V1) and Curaçao (FC XML 2.2), and contains a large number of corrections to validation, import, export and delivery. Several of the new checks can report findings on files that passed without a message in earlier versions. Please read the section "Upgrade Notes" before you install the update.
Regulatory Changes
OECD – CRS (all jurisdictions)
- Duplicate DocRefIds within a file are now reported; before, duplicates passed unnoticed. The rule that "Resent Data" (OECD0) is only allowed on the Reporting FI is now checked for every jurisdiction. TRSUIT-225
- OECD correction rules: validation now checks CorrMessageRefId in the Message Spec (80007) or Doc Spec (80006), a CorrDocRefId on new data (80004), the deletion of a Reporting FI without its account reports (80009), a resent Reporting FI without corrected account reports, and the mixing of test and production records (50010/50011). Pool Report, a repeated Reporting Group and the name type OECD201 are reported for all countries (60010, 60007, 60004). TRSUIT-227
- The Corresponding Message Reference ID of the General tab is no longer copied into every Doc Spec (only Finland/TAXFI keeps it there). TRSUIT-227
- Forbidden character sequences: the sequences
--,/*and&#are now rejected in every text field of a CRS report, because tax authorities reject such files through their threat detection; the message names the element, its path and the DocRefId. Before, only Macau, Malaysia and Aruba checked selected fields. TRSUIT-227 - A negative account balance is now reported for every jurisdiction (OECD status 60002). TRSUIT-227
- Notes instead of errors: recommendations of a tax authority (for example for Singapore, Hong Kong, Macau, China or the Cook Islands) no longer count as errors. "Validate" shows "No errors found" and lists the notes separately; the Reporting FI form marks an entry as invalid only for real errors. TRSUIT-227
- File size limit: the OECD XML export now warns when the written file exceeds the limit of the selected country (Germany 100 MB, Macau 100 MB, Cayman Islands 150 MB, Luxembourg 60 MB until 31 December 2026 and 250 MB from 1 January 2027, China and Finland 100 MB); the configuration shows "no limit" instead of -1. TRSUIT-227
- Reporting FI: the residence country code and the tax identification number of the Reporting FI are now checked for jurisdictions without a jurisdiction-specific rule as well. If no country is selected on the configuration tab, the generic OECD validator is used instead of skipping the Reporting FI checks silently. TRSUIT-225 TRSUIT-222
- Entity tax numbers are no longer run through the check meant for individuals; only Switzerland, Poland, Portugal, Slovenia and the Netherlands, which have an organisation number format, check an entity's tax number. This removes false "invalid tax number" findings on organisations. TRSUIT-225
- Character checks (forbidden sequences, character sets) now also cover attribute values, for example the name type. Messages of the schema check are always shown in English. TRSUIT-225
- Character set validation (Switzerland, Italy, Ireland, Albania) was rebuilt: large reports are checked noticeably faster, every field with a disallowed character is reported in one pass, and numbers, dates and coded values are no longer mistaken for free text. TRSUIT-225
- Empty values: an element that is empty or contains only spaces is reported as a note when the report is exported as CRS XML 2.0 or 3.0, because the export leaves such elements out; if the element is mandatory, the schema check reports it as missing. A TIN consisting only of spaces is no longer checked against the EU TIN rules. TRSUIT-227
- Earlier reporting years in CRS XML 3.0: when a CRS XML 1.0 or 2.0 file, an Excel workbook or a work file saved with an earlier version carries a reporting period before 2026, TRSuite fills the empty CRS 3.0 mandatory fields with the "not reported" codes the OECD allows for those periods (CRS900, CRS1000, CRS1100, CRS1200, CRS800 for controlling persons without a type) and shows a note with the number of fields. Existing values are kept; the entry forms do not pre-fill. Corrections, deletions and late filings for earlier years can thus be exported in CRS XML 3.0 directly. TRSUIT-227
- CRS XML 2.0 export: the controlling person type CRS800 (CRS 3.0 only) is no longer written; before, the file failed the schema check. Data from a 2601 workbook or a CRS XML 3.0 file no longer stops a 2.0 or national-format export when it contains the account number type OECD606, the controlling person types CRS800/CRS819 or the residence "multiple"; these values are mapped (OECD606 becomes OECD605 "Other") or left out. TRSUIT-227 TRSUIT-224
- Sponsor, intermediary and pool reports are now kept when a file is converted between the CRS XML versions (loading an older file, exporting 2.0). TRSUIT-224
- The CRS configuration offers OECD CRS XML 2.0 and 3.0 only; a configuration saved with 1.0 switches to 3.0 when loaded and shows a note. TRSUIT-227
- The controlling person category CRS819, reserved for Finland's national format, is no longer offered for other countries; a report with this type is rejected with a clear message in every OECD export (menu, split export, command line, ATO BBDM) and in the exports to Canada Part XIX and Curaçao FC XML. Export such a report as TAXFI or change the type. TRSUIT-226 TRSUIT-224
- The Uruguayan domestic-format fields (average account balance, pre-existing account, top account holder) no longer appear in the standard OECD CRS export, where they were not valid; they remain in the work file and in the Uruguayan domestic export. TRSUIT-226
- Internal placeholder entries ("MULTI", "OECD") have been removed from all country selection lists. TRSUIT-226
- A validation run no longer stops with just the word "null" when a required field is missing; the message names what is missing. An account report without a document specification is reported instead of being silently accepted. TRSUIT-225
EU TIN check (CRS, FATCA, CARF)
- The format check now follows version 7.00 of the European Commission's TIN algorithm specification. Taxpayer identification numbers of natural persons issued by Czechia, Greece, Latvia, Malta, Romania and Slovakia are now checked for their structure (the Commission does not publish their check digits); until now these numbers were not checked at all. Finnish personal identity codes with the century signs A–F and U–Y (issued since 2023) are accepted; the 13-digit German tax number is accepted in addition to the 11-digit tax identification number. A Danish CPR number that fails only the modulus 11 check is reported as a note. TRSUIT-225
- Corrections: a valid Polish PESEL number with check digit 0 is no longer rejected; the French check reads all three check digits; the list of blocked UK National Insurance prefixes has been extended; the accepted characters for Cyprus and Ireland are corrected, Cypriot TINs of individuals start with 0, 6 or 9; the German digit-frequency rule is applied correctly; separators (spaces, dots, dashes, slashes, plus signs) are treated consistently for all countries. TRSUIT-225
- The Swiss TIN check (AHVN13) now actually checks the number instead of always reporting it as correct, and accepts the Swiss business identification number (UID) for organisations; the UK TIN check, which never ran before, now runs. TRSUIT-225
Albania
- The GovTalk file wraps the OECD message with the namespace of the exported file, escapes special characters in password and institution name correctly, and the export is validated against CRS XML 1.0; values that exist only from CRS 2.0/3.0 are reported. The upload verifies the server certificate, waits up to 60 seconds for the answer, and reads the response as UTF-8; responses containing a DOCTYPE declaration are rejected. TRSUIT-228 TRSUIT-227
Australia – ATO
- The BBDM export uses the ATO services crs.0002.lodge.request (CRS XML 2.0) and crs.0003.lodge.request (CRS XML 3.0) instead of the deprecated crs.0001; CRS XML 1.0 can no longer be exported to BBDM. The CRS content is checked against the CRS schema before the file is written, the export dialog asks for the sender identifier type (ABN or TAN), and the file no longer contains an xsi:schemaLocation attribute. BBDM files name "BRIFS GMBH" as software producer. TRSUIT-227 TRSUIT-224
- ATO validation rules (VR.ATO.CRS numbers in every message): Sending Company IN and Reporting FI IN as ABN, TFN or GIIN, MessageRefId and DocRefIds relative to the reporting period and the receiving country, one CrsBody, uninhabited jurisdictions and external territories, undocumented accounts and AU residence, dates of birth, timestamp and reporting period. For CRS XML 3.0 the new ATO 2027 rules are checked; from 1 January 2027 a CRS XML 2.0 file is reported as an error, until then a note explains the cutover. Characters outside ASCII are reported – those the ATO converts itself as a warning, all others as an error. TRSUIT-227
- CSV conversion (BBDM): an organisation with account holder type CRS101 was written twice, the first time without its controlling persons; it is now written once. Country codes are also accepted in lower case, an invalid code is skipped on its own, and an account balance or payment amount that is not a valid number stops the conversion with a message naming column, record number and customer ID. A file that cannot be loaded is reported and skipped instead of stopping the batch. TRSUIT-224
- The DocRefId check no longer stops partway through a file; a missing Sending Company IN is reported by name. No false alarm VR.ATO.CRS.000013 at the second boundary. TRSUIT-225 TRSUIT-227
Austria – FinanzOnline
- Validation now rejects nil reports (CRS703), checks the FinanzOnline MessageRefId format (tax number of the FI + AT + year + 1–8 characters), birth dates between 1900 and the current year, and empty values that FinanzOnline rejects. The 4,000-account-holder limit is counted across the whole message, and the checks for controlling persons and for a disallowed name type also apply to organisations. TRSUIT-227 TRSUIT-225
- The national export and "Validate" check Info_Daten against the report (9-digit Fastnr_Fon_Tn/Fastnr_Fi, Sending Company IN = Fastnr_Fon_Tn, Reporting FI IN = Fastnr_Fi); the national file is not written if this check finds errors. Validation findings are shown in the Error Viewer instead of a message dialog. TRSUIT-227 TRSUIT-228
- Login, upload, databox and download run in the background with connection and response timeouts; the FinanzOnline session identifier and the uploaded report content are no longer shown or logged. TRSUIT-228
Bahamas – Competent Authority
- Bahamas can now be selected on the CRS configuration tab (presets BS/BSD). Validation applies the rules of the AEOI Portal User Guide 2026: reporting period 31 December, nil filings (CRS703) only as a domestic filing, Reporting FI resident in the Bahamas, DocRefIds starting with BS and without spaces, tax residence matching the receiving country, no nationality, date of birth range, and the undocumented-account flag for domestic filings. TRSUIT-222 TRSUIT-227
- From 1 January 2027 a message that is not in CRS XML 3.0 is reported as an error, because the AEOI Portal no longer accepts CRS 2.0 from that date; until then a CRS XML 3.0 message receives a warning that the portal still validates against schema 2.0. TRSUIT-227
Bermuda
- Validation now follows the 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. TRSUIT-227
British Virgin Islands – BVIFARS
- The validator now applies the checks of the BVIFARS portal (User Guide 10.0.1, section 3.11): transmitting country and Reporting FI residence VG, nil reports and undocumented accounts only in domestic filings, DocRefIds of non-domestic filings starting with
VG, no spaces and no duplicates in DocRefIds, document types per message type, no CorrMessageRefId, tax residence matching the receiving country, no nationality, date of birth after 1900, no negative balances and one reporting group per file. Earlier versions only preset country and currency. TRSUIT-222
Canada – CRA Part XIX
- The Part XIX export supports the CRA format 2028V1 (Amended CRS) with all CRS 3.0 fields; the target schema is preselected from the taxation year. The official CRA schema package 2026 (version 1.26) replaces the earlier copy. TRSUIT-227
- A trust without a business number can be reported with its trust account number as Reporting FI identification number; the T619 transmitter record accepts the transmitter account number, the RepID or both. TRSUIT-227
- DocRefIds are checked for duplicates, taxation year and business number (CRA EFV 440–453, 495, 513); generated IDs use the BN RZ of the filer account number, and the export stops with a message if neither a filer account number nor a Reporting FI IN is available. Validation checks the slip DocRefId, the Reporting FI residence and the Canadian SIN/ITN. TRSUIT-227 TRSUIT-224
- For a party with several residence countries the TIN is written under the residence country that issued it; a TIN without issuing country counts as the residence TIN when there is exactly one residence country. Empty contact and blank fields are no longer written, amounts always carry two decimals, and the export warns about the CRA file size limits. TRSUIT-224 TRSUIT-227
- Open, Save and Save As now work and store the T619 and Part XIX data in a work file; "Generate Delivery Package" is disabled because the return is uploaded through the CRA's filing service. Stored transmitter information is migrated automatically. TRSUIT-228
Cayman Islands – DITC
- Document type OECD0 (Resent Data) for the Reporting FI is accepted, as the DITC portal requires for every file that corrects or deletes account reports; earlier versions reported such a file as invalid. The DocRefId check (
KY+ reporting year + receiving country) now has effect; reporting years after 2029 are accepted. TRSUIT-222 - Validation checks the DITC portal rules: no CRS703 file (use the CRS Filing Declaration), Reporting FI IN issued by KY, no CorrDocRefId on a resent Reporting FI, receiving country KY only for undocumented accounts, tax residence matching the receiving country, and the DocRefId structure. Generated DocRefIds use a 10-character unique part, and the MessageRefId contains the FI Number. TRSUIT-227
Chile
- Chile no longer pre-selects the undocumented CLM/CLF/CLA reference ID patterns; the generic OECD rules apply. A note reminds that institutions without reportable accounts must still file DJ 1958. TRSUIT-227
China – STA (CNCRS)
- "Validate" now checks: the button used to report "No errors found" without checking anything. It now checks the file against the CNCRS schema and the STA rules on residence country, names, placeholder birth dates, corrections (document type, no mixing of new data and corrections or of test and production data, CorrDocRefId), nil reports, account balances, uniqueness of DocRefIds, the forbidden sequences
--,/*,&#and the MessageRefId format. TRSUIT-225 TRSUIT-227 - Nil reports (CRS703) can be created; the MessageRefId and file name use the year of submission (reporting period + 1) and P/N for pre-existing/new accounts, as required by the STA. TRSUIT-227
- Controlling persons entered in the China module were lost when the account report was saved, and only type, TIN and birth data were loaded; they are now saved and loaded completely. The place of birth is taken from the city field, and empty blocks are no longer written. In the Excel import every individual receives the TIN of its own line, unknown codes for gender, ID type and account holder type are reported, and skipped organisation lines are counted. TRSUIT-224 TRSUIT-226
Cook Islands – IGOR
- Validation applies IGOR rules 1 (Reporting FI resident in CK), 5 (no name type OECD201 for organisations), 8 (date of birth, also for controlling persons) and 9 (whitespace-only TINs), rejects test values OECD10–OECD13, DocRefIds differing only in letter case and the Reporting FI of a correction, and requires one ReportingGroup per CrsBody. A Transmitting Country other than CK and mixed messages are notes. TRSUIT-227
Costa Rica – DGT
- Validation no longer rejects Message and Document Reference IDs in other formats – the DGT prescribes none. Account holders and controlling persons not resident in one of the 89 active exchange partners of the DGT (list of 1 July 2026), individuals without a TIN, a reporting period other than 31 December and nil reports (which the DGT expects in the SIIF portal) are shown as notes. The Reporting FI DocRefId check no longer depends on an earlier run. TRSUIT-227 TRSUIT-225
Curaçao – MDES
- The module now creates FC XML 2.2 (namespace urn:fatcacrs:ties:v2), the only version accepted by the MDES portal since 1 February 2021, and validates the file against the official schema. The "Recalcitrant" flag has been removed, because FC XML 2.2 no longer contains it. FC XML 2.0 files and older work files can still be opened; the Excel import accepts templates marked 2.0 or 2.2. TRSUIT-227
- The module has its own validation of the MDES rules (Message Reference ID and DocRefIds with CW and the tax year, correction rules, nil report document types, mandatory fields, prohibited character sequences); "Validate CRS" checks account reports and Reporting FIs again. Generated IDs contain the tax year, and an export with a sponsor no longer writes each account twice. TRSUIT-227
- Updating an account report no longer drops additional TINs, residence countries, substantial owners or controlling persons; "Clear list" checks for organisations in use; write errors are reported. TRSUIT-228
Finland – Vero (TAXFI)
- The account type "not reported" (CRS1100) no longer produces an invalid file, the Nationality element is no longer written (rejected by Ilmoitin.fi since June 2026), one controlling person type is written per person with a warning about further types, account balances always carry two decimals, and a malformed contact entry is reported instead of being left out. TRSUIT-227
- Validation applies the Ilmoitin.fi checks: Business ID check digit and match with the MessageRefId, mandatory contact, CorrMessageRefId in Message Spec and Doc Spec for corrections, nil return rules, IN type of the Reporting FI, date of birth, name type OECD207, TIN length and the dummy value 000000000. TRSUIT-227
France – DGFiP
- Filings for New Caledonia, Saint-Martin and Saint-Barthélemy are no longer rejected. The validator checks the rules of the cahier des charges v3.7 (SIREN/IDSP, MessageRefId and DocRefId format, Warning 1–4, no GIIN for French INs, residence code of the Reporting FI, birth date, undocumented accounts,
#); invalid TINs are shown as notes. TRSUIT-227
Germany – BZSt
- BZSt/ELMA export removed: the BZSt stopped accepting ELMA-based CRS submissions at the end of November 2025. German reporting financial institutions create the plain OECD CRS XML file with the German validation rules and upload it through the mass data upload of the BZSt online portal. Automated transmission through the DIP interface needs a DIP envelope, which TRSuite does not produce. TRSUIT-227
- BZSt content rules: Sending Company IN as 13 digits, tax number in the 13-digit ELSTER format (legacy formats are a note until 31 December 2026 and an error afterwards), all residence codes of the Reporting FI = DE, no test data, account DocRefId built with the Reporting FI's tax number, undocumented accounts with DE, no nationality, birth date between 1900 and the reporting year, at most 20,000 account reports per file (new default), field lengths 170/200/4000, and a note if the Reporting FI carries more than one IN. TRSUIT-225 TRSUIT-227
- Record description 3.0 (BMF, 14 January 2026): the reporting period must end on 31 December, the reporting year in MessageRefId and DocRefIds must match, one CrsBody per file, one type per controlling person; from 1 January 2027 only schema 3.0 is accepted, before that date a 3.0 file gets a note. TRSUIT-227
- Cancellation deliveries (Stornolieferung) are supported: message type CRS702, the MessageRefId of each cancelled delivery as Corresponding Message Reference ID, the Reporting FI repeated with OECD0 and its original DocRefId, no account reports. Validation accepts this form for Germany only and checks the referenced MessageRefIds. TRSUIT-227
Guernsey – IGOR
- The country list showed "Gournsey"; the GIIN pattern is no longer suggested as TIN rule. Validation accepts messages mixing new data and corrections, reports the Transmitting Country only as a note, and rejects test document types, DocRefIds that differ only in letter case, and a Reporting FI with new data next to corrected account reports. TRSUIT-222 TRSUIT-227
- CRS XML 3.0 messages are checked against the draft Guernsey CRS Guidance Notes v2 (30 September 2026): from reporting period 2026 the "not reported" codes are errors, CRS800 is accepted in 2026 and 2027 only for pre-existing accounts; account type cross-checks; a joint account must have more than one holder; notes for a missing or placeholder date of birth and the Remediation Disclosure Package. From 1 January 2027 a message that is not in CRS XML 3.0 is an error. The rules will be reviewed against the final version of the Guidance Notes. TRSUIT-227
- IGOR requests have a time limit and run in the background; a rejected deletion of a Reporting FI is reported with the answer of the server. TRSUIT-224 TRSUIT-228
Hong Kong – IRD
- The check for undocumented accounts was inverted and reported every correctly filled Hong Kong address as an error. The option to check TINs and require DocRefIds was silently ignored; both checks now run. TRSUIT-225
- Validation checks the character sequences prohibited by the IRD user guide, compares the MessageRefId with the IRD file name format (note), reports DocRefIds longer than 40 characters and IDs that differ only in letter case, and distinguishes the controlling person messages 60016 and 60005. MessageRefIds generated within the same second get an incrementing sequence number. The recommended file size limit is 200 MB. TRSUIT-227
- The controlling person form no longer offers a self-certification, and entries with more than one controlling person type are reported – the IRD schema v2.0 cannot carry them. Older work files are converted in memory without a temporary file. A payment in one of the five currencies added with CRS 3.0 (BYN, MRU, STN, UYW, VES) is reported instead of being dropped silently. TRSUIT-228 TRSUIT-225
Ireland – Revenue
- Selecting Ireland now suggests EUR (was GBP). The validator checks the Revenue limits of 30 MB / 20,000 records and shows notes for
#, the Revenue reference ID pattern and controlling persons in several jurisdictions. TRSUIT-222 TRSUIT-227
Isle of Man – Income Tax Division
- Selecting the Isle of Man now suggests GBP (was EUR). Validation applies the Isle of Man validation table for CRS schema 3.0 (GN53, Industry Advisory Notice of 18 December 2025): "not reported" codes rejected from 2026, account number type/account type/payment types must match, no CorrMessageRefId, DocRefIds starting with the GIIN or the tax reference number followed by a full stop, unique Reporting FI names, no undocumented organisation accounts, pool reports or test document types. The default file size limit is 124 MB. TRSUIT-222 TRSUIT-227
Israel – ITA
- The DocRefId convention follows the ITA technical instructions (33 characters, six-digit sequence number; previously nine digits). IDs generated by earlier versions are not changed. Notes are shown when the MessageRefId is not 24 or the DocRefId not 33 characters long. The receiving country check no longer depends on the transmitting country. TRSUIT-227 TRSUIT-225
Italy – Agenzia delle Entrate
- Substitute communications (CRS701 with CorrMessageRefId) are no longer flagged as errors. The validator checks the rules of the Agenzia delle Entrate (MessageRefId/DocRefId format, codice fiscale of the sender, dates without time zone, characters in names, empty TINs); TINs of other states are reported as notes. TRSUIT-227
Jersey – Revenue Jersey
- Corrections and deletions (OECD2/OECD3) require the Corresponding Message Reference ID in the message header; "Correct Report" moves the MessageRefId of the loaded report into it. Validation checks the practical guidance v10.0: MessageRefId/DocRefId starting with JE + year + JE, TIN also for controlling persons and entities with NOTIN as the only placeholder, no Nationality, no empty elements, date of birth range, City also with a free-text address, and the account type/payment cross-checks. A missing date of birth is a note. TRSUIT-227
Liechtenstein – STV
- With CRS version 2.0 selected, the command-line export also writes CRS XML 2.0. The Liechtenstein Tax Administration accepts CRS XML 2.0 until 30 November 2026; validation shows this as a note and reports an error from 1 December 2026. TRSUIT-227
- Validation checks the STV additional specification of 14 April 2026: 7-digit reporting office number as Sending Company IN, Reporting FI residence LI and PEID, no spaces or special characters in MessageRefId/DocRefId, one document type per message, no fields of spaces only. An IN without issuing country is a note; a file with receiving country LI and accounts not resident there is noted (one file per final receiving country). TRSUIT-227
Luxembourg – ACD
- The AEOI export can create files in the new ACD format CRS_LUX V3.0 (OECD CRS 3.0), mandatory from 1 January 2027 and accepted on the ACD pre-validation platform from 12 October 2026. A new "Schema" selection offers V3.0 and V2.0 (V2.0 preselected until 31 December 2026); the target environment – Production (P) or pre-validation (T) – is added to the file name as required by the ACD. CRS 3.0 data is kept in the V3.0 file, and the file is checked against the ACD schema before it is saved. AEOI files in V3.0 can be opened again. TRSUIT-227
- The export splits a report by destination country as described in the ACD user manual, gives each copy its own DocRefId, maps overseas territories to the destination codes required by the ACD, creates ZeroReports (CRS703), checks the ACD rules before writing (forbidden elements, account number length, reporting period, closed accounts, whitespace, identifier structure), and stops with a clear message for a sponsor, intermediary, pool report, more than one Reporting FI, or values that CRS_LUX V3.0 does not define. The transmitting and receiving country are always Luxembourg; CRS_LUX V2.0 files no longer contain the Sending Company IN or Uruguay-specific account fields. TRSUIT-225 TRSUIT-227 TRSUIT-226
- A work file or OECD file in schema 1.0 or 3.0 can be used as the source; the export file name no longer depends on the Windows regional settings. TRSUIT-225
Macau – DSF
- The target schema version must be set explicitly; a report that relied on the silent default 1.3 needs the version selected. Each version is validated against its own schema (before, 1.1 and 1.2 were checked against 1.3), and values that only version 1.4 permits are reported for lower target versions. TRSUIT-226 TRSUIT-225
- Validation checks the DSF status message catalogue: MessageRefId matching the file name format and Return Year (50107/50122), Return Year range, birth dates from 1900 (60014), values of spaces only (55014), duplicate elements (60101), lengths of FI name, reference IDs and free-text addresses (5 lines of 150 characters), the joint account number (1.4), and the residence country of every organisation. The export reports a file name that differs from the MessageRefId and files above 100 MB. TRSUIT-227 TRSUIT-226
- The TIN/DocRefId option now has effect; a message about a missing corrected message reference names the right field; an account holder without last name no longer shows "null"; a payment in a CRS 3.0 currency (BYN, MRU, STN, UYW, VES) is reported; all equity interest types are kept; a rejected account report shows the reason. TRSUIT-225 TRSUIT-228
- Delivery: the authority's encryption certificate can be selected as X.509 (.crt, .cer, .pem) or PKCS#7 (.p7b, .p7c); if the file contains several certificates, the one intended for encryption is used. The package is created in the background with a cancellable progress window; the private-key password is saved when you leave the field. TRSUIT-228 TRSUIT-224
Malaysia – IRBM (HiDEF)
- The MessageRefId check accepts both forms used in the IRBM's published examples – 22 characters and 26 characters with the reporting year; TRSuite continues to generate the 22-character form. The MyCRSID is checked as 8 digits in the Sending Company IN as well; DocRefIds with sequence number 0000/000000 are rejected. TRSUIT-212 TRSUIT-227
- The delivery tab no longer reports success for an incomplete HiDEF package; missing sender metadata, deselected steps or missing package parts are errors. The sequence number dialog accepts 0001–9999. The package is created in the background; "Check Configuration" no longer writes test key files into the working directory. TRSUIT-227 TRSUIT-228
Malta
- A note is shown when the Sending Company IN is not the 9-digit Malta income tax number. TRSUIT-227
San Marino
- TRSuite checks the rules of the Guida pratica v2.0 (country codes SM, CRS701 only with OECD1, empty TIN/IN elements, Passive NFE coding) and proposes the file name required by Regulation 20/2015. TRSUIT-227
Seychelles – SRC
- The IN of the Reporting FI is optional. TRSUIT-227
Singapore – IRAS
- Reporting FI DocRefId: the three-digit number at the end (
<year><tax reference number>FI<nnn>) is now entered when the DocRefIds are reset, with 001 preset; IRAS defines it as the version of the Reporting FI element within the reporting year. Earlier versions always wrote 001. TRSUIT-222 - Validation follows the IRAS error list and the XML Schema User Guide 4.0.1: transitional codes CRS900–CRS1200 rejected from reporting year 2027 and CRS800 from 2029, dates of birth between 1900 and the reporting year, nil returns only for Trustee-Documented Trusts, Reporting FI resident in SG, accounts with more than one jurisdiction of residence or more than one controlling person reported as errors (IRAS requires a separate account report for each), TIN and IN issuing countries matching the residence country. A missing TIN with the reason code allowed by IRAS is no longer an error; placeholder values are reported; reason codes IRAS101–IRAS104 are not checked as TINs. TRSUIT-227 TRSUIT-225
- The jurisdiction list follows the IRAS list for reporting year 2025; Antigua and Barbuda and Curaçao are accepted only for corrections of earlier years. The character
#is an error, because IRAS rejects returns containing it (write#03-12as03-12). The default file size limit is 5 MB until 31 December 2026 and 50 MB from 1 January 2027. TRSUIT-227
Switzerland – FTA (CRS)
- ESTV test submissions: the new menu item "Generate CH test archive ..." converts all document types to the test codes OECD10–OECD13 and names the encrypted archive
Test_<file>.zip, as the ESTV AEOI portal requires. Both archive functions derive the archive name from the document types in the file, refuse files that mix test and production codes, and warn about a production archive whose name starts with "Test". TRSUIT-227 - The bundled ESTV certificate used to encrypt the CRS archive has been replaced by the current one (CN
encryptor.estv.admin.ch, valid until 4 February 2027); the previous one had expired in April 2022. TRSUIT-222 - The character check reported every amount such as
1000.00as a "CRMT" error (introduced with 26.02); the exception list works again, and the check for three identical characters in a row has been removed because the ESTV does not require it. The character "¤" is reported as not permitted. TRSUIT-225 TRSUIT-227 - DocRefIds of up to 200 characters are accepted; the ESTV rules 60017–60023 for CRS XML 3.0 (account type matrix) are applied; an undocumented account needs an individual account holder resident only in CH (98203); controlling persons are checked like account holders (structured address 98104, plausible date of birth 60014); the account report/CRS703 rule applies to every part of a message; a correction (CRS702) of only the Reporting FI no longer needs account reports. TRSUIT-227 TRSUIT-225
United Kingdom – HMRC
- The United Kingdom can now be selected on the CRS configuration tab (presets GB/GBP, receiving country GB). TRSuite checks the HMRC rules for the OECD Amended CRS XML schema (mandatory from 1 January 2027): schema version 3.0, the ISO-8859-1 character set and the transitional "not reported" codes by reporting year; notes for NANUM, undocumented accounts, UK-resident account holders and missing dates of birth on new accounts. TRSUIT-222 TRSUIT-227
Uruguay – DGI
- The report can be created in the DGI domestic schema Doméstico 3.0 (mandatory from 2 January 2027); the export takes the version from the CRS configuration (3.0 → Doméstico 3.0, otherwise 2.2), is validated against the DGI schema, and no longer writes DormantAccount and Nationality. The delivery tab lets you choose the schema used to validate the signed report. "Split & Save" and the command-line export write the domestic format. TRSUIT-227
- Validation checks the DGI rules: account average, RUC as Sending Company IN, mandatory TIN/IN, TIN types, Transmitting Country UY (98001), residence equal to receiving country (98034/98060), identification type of organisations (98048–98050), name types (98059), CorrMessageRefId rules (98007–98009), the MessageRefId format
UYAAAAZZ.RUC.NNNNNNNNN(50008), and rejects sponsors, intermediaries and pool reports. TRSUIT-227 - The message type CRS708 (total update of a previous report) and undocumented accounts with receiving country YY can be reported in the domestic format; the NIL report is written in the domestic format; the delivery checks the RUC of the signing certificate (98000). Other countries reject CRS708 and YY with a clear message. TRSUIT-227
- The nine-digit identifier of DocRefId and MessageRefId was drawn at random for every record, so duplicates could occur (DGI error 80000); identifiers are now consecutive and cannot repeat within one run. A RUC longer than 12 characters is rejected instead of being truncated. TRSUIT-222 TRSUIT-224
- Delivery: the authority's certificate can be selected as X.509 or PKCS#7; an unreadable certificate or report, and a failure to copy the finished package to the upload folder, are reported instead of "Processing successful". TRSUIT-228 TRSUIT-224
USA – IRS FATCA / IDES
- New IRS encryption certificate: TRSuite ships with the IRS certificate that replaced the previous one on 24 September 2026 (valid until 31 March 2027). TRSuite warns when the certificate has expired or expires within 30 days – when the IDES module is opened, under "Validate" and before a transmission archive is created. TRSUIT-222 TRSUIT-228
- SFTP connection checks the server key: on the first connection to a server a dialog shows the key type and the SHA-256 and MD5 fingerprint; after confirmation the key is stored per server name and port and checked on every further connection. A changed key is refused with a warning ("Replace stored key" only after the change is confirmed by the IRS). Without a user interface an unknown or changed key is always refused. The suggested test gateway is
test.fatcaidesgateway.com; transfers through an HTTP proxy without authentication work again, a proxy with authentication is reported as unsupported. The read timeout is now separate from the connection timeout (master data field "ReadTimeout [ms]"). TRSUIT-224 - DocRefIds: sponsor and intermediary now get their own DocRefId per reporting FI (a shared one was a duplicate the IRS rejects); duplicates are reported for every element including sponsor and intermediary; a CorrDocRefId that matches a DocRefId of the same file is reported; messages name the affected element. If the reporting FI has no GIIN, the sponsor DocRefId is built from the GIIN of the sponsor. A DocRefId that does not start with the GIIN is a warning instead of an error; DocRefIds shorter than 21 characters and reporting periods in a future year are errors; the Timestamp is written without fractions of seconds. TRSUIT-225 TRSUIT-222 TRSUIT-227
- Validation rejects
--,/*and&#in the report data (IRS Publication 5124) and warns about characters outside the recommended set in reference IDs. IRS recommendations are shown as notes; a Reporting FI without GIIN no longer aborts the validation. "Check" also validates NIL reports when the report contains no account or pool reports. TRSUIT-227 TRSUIT-228 - Target version 2.0 and codes of 2.0.1: with target version FATCA XML 2.0, validation now reports values that only FATCA XML 2.0.1 defines (country code
XX, currencies BYN, MRU, STN, UYW, VED, VES) as errors with the affected element; before, the export failed at the schema check without a prior message. TRSUIT-224 - Excel export: a successful export shows a confirmation with the file name. If the report contains several reporting FIs, a dialog warns before the export that only the first reporting FI is written to the workbook (Continue/Cancel); exporting several reporting FIs into one workbook is planned for a later release. The same applies to the Excel export of the CRS module. TRSUIT-228
- IDES: the sender metadata declare FileFormatCd and BinaryEncodingSchemeCd correctly; before a transmission archive is created, the document types are checked against the target gateway (test types for production are rejected, production types for test need a confirmation). Creating a transmission archive and extracting an IRS response run in the background and can be cancelled; a run uses the configuration as it was when it started; key material is removed even if a run fails. An invalid signature of a received file is reported. TRSUIT-227 TRSUIT-228 TRSUIT-224
- "Wrap Non-XML": every wrapped file, including
.txt, is embedded Base64-encoded, so its content arrives byte for byte (before, the text of a.txtfile lost forbidden sequences silently); the IDES metadata declare the real format (PDF, TXT, RTF or JPG) and BASE64. Choosing the source file as target is rejected; a partly written wrapper file is removed after an error. Note: according to the IRS, a FATCA Report (RPT) must be an XML file; wrapped non-XML files are intended for other communication types between tax authorities and the IRS. TRSUIT-224 - Excel: the "Pool_Report" sheet is now imported, also for a return of pool reports only; a workbook naming both a sponsor and an intermediary reports that the sponsor was not imported; the export writes the organisation name instead of the name type; Batch Void also voids 2.0.1 files; the NIL report from Excel reports write errors. A company that is Reporting FI, sponsor and intermediary at once is kept as three entries when the file is reopened. The workbook created from an IRS notification with a record error group shows each reporting FI above its error rows. TRSUIT-222 TRSUIT-228 TRSUIT-226 TRSUIT-224
- Entry screens: right-click menus act on the clicked row; switching entries or tabs no longer loses unsaved pool or NIL reports; invalid reports are no longer added silently; "Clear list" checks for organisations in use; "Clear list" of payments marks the report as changed; "Generate DocRefIDs" names the IDs it could not generate for filers from "XX" and keeps existing ones. TRSUIT-228
- The outdated Excel templates
FATCA_Basic_1902.xlsmandFATCA_Basic_2601.xlsmare no longer installed inresources\xls; use the template bundle FATCA_2601 from the download page. TRSUIT-228
Switzerland – FTA (SEI, FATCA group requests)
- The Excel import takes the reporting period from the year of the workbook, imports the account holder type, no longer stops on a document without account, and no longer deletes existing packages without asking (append or replace; duplicate dossier numbers are reported). An import that produces no information package reports "Excel Import Failed" with the reasons instead of a partial success, and a cancelled import no longer points to a package folder. TRSUIT-224 TRSUIT-228
- An update package for a dossier number above 99 can be created; the limit of 99 applies to the update number. The table of contents of the merged PDF documentation continues on additional pages (it listed at most 20 documents). IRS warnings no longer mark a package as partial. The import warns when the stored delivery password cannot be read on this computer. TRSUIT-224 TRSUIT-227 TRSUIT-228
- Saving keeps the previous file on error, cancelling "Save As" no longer causes an error, an unreadable work file is reported, and the module is unlocked again after an unexpected error. "Show FATCA" opens FATCA XML 2.0.1 files. TRSUIT-228
- Customer-specific extension: a dossier with missing files no longer stops the whole copy run; "CANCEL COPY" cancels; the archive password is no longer stored in plain text; metadata values with special characters are written as well-formed XML. TRSUIT-228
OECD – CARF
- TRSuite creates and validates CARF XML 1.5 (OECD schema of September 2025); CARF XML 1.0 files can still be opened and are exported as 1.5; the load dialog recognises 1.5 files. Amounts are reported with two decimals, numbers of units may have decimals, numbers of transactions must be whole numbers; amounts above 2,147,483,647 are kept exactly. Other Nexus accepts every nexus value (CARF901–CARF907). Nil reports (CARF703) and nexus-only reports can be exported; the Sending Entity IN is optional. New DocRefIDs follow the CARF pattern (country code, reporting year, unique identifier). TRSUIT-227 TRSUIT-228
- CARF Finland: the Ilmoitin.fi checks of the Finnish Tax Administration (CARF/DAC8 guidance 1.0H) are applied: Finnish MessageRefID/DocRefID formats, one Crypto Users record per crypto asset and transaction type (split automatically by "Generate DocRef-IDs"), timestamp with milliseconds, file name = MessageRefID. New: FICARF nil report (FICARF703) and a checker for FICARF files created by your trading system. TRSUIT-227
- CARF Liechtenstein: new validator configuration following the STV additional XML specification of 4 February 2026 – reference IDs LI + year + receiving country + "." + unique part, PEID as SendingEntityIN and RCASP TIN, RCASP resident in LI, one document type per message, no nil reports, reporting periods from 2026. TRSUIT-227
- Validation: duplicate DocRefIDs and self-referencing corrections; number of transactions for all transaction types; new option "EU TIN Check" (off by default; entity TINs only for CH, PL, PT, SI, NL); unknown TINs as NOTIN with unknown="true"; birth date 1900-01-01 for an individual RCASP; deleting an RCASP requires its Crypto Users to be deleted; no mixing of test and production document types; a CARF701 message without crypto users needs an OtherNexus (60011); the RCASP must be resident in the transmitting country (60005); date of birth before 1900 or after the reporting period (60007); the same CorrDocRefID twice (80011); an OtherNexus weaker than the Nexus (60010, note); mandatory fields of spaces only count as missing; "Type of controlling person not set" is reported instead of being lost. Existing CARF data may show new messages. TRSUIT-228 TRSUIT-227
- Export and work file: Nationality is no longer written to CARF XML (not to be reported per the User Guide),
unknown="false"is no longer written, the export enforces the maximum file size and number of Crypto Users from the configuration, writes only schema-valid files and never overwrites an existing file with an invalid one; "Save TRWI" no longer saves an empty work item on error. The work file keeps all data the export deliberately leaves out (Nationality, timestamp, incomplete entries, the selected document type) and values containing--,/*,&#or several spaces; a foreign XML file in "Open TRWI"/"Load XML" is reported. TRSUIT-227 TRSUIT-228 - Editors: invalid transaction input is reported instead of stored as 0; accented and CJK names are written correctly; a birth place is only written when entered; multiple controlling person types and TINs per party are kept on XML load and in Excel; the District field is saved; default country and currency of the configuration are entered when a field is empty; the message type descriptions show the OECD wording; the TIN/IIN tables are higher. Auto-save uses one file per running instance; new entries created while the search filter is active no longer disappear; "Validate" no longer shows findings of deleted entries. TRSUIT-228 TRSUIT-227 TRSUIT-209
- The Excel "Check Data" macro accepts decimal Number of Units (up to 6 decimals) and Amount (up to 2 decimals); the demo TINs of the sample workbook are valid. TRSUIT-227 TRSUIT-228
New Features
- Error viewer with "Go to entry": validation in the CRS and FATCA modules and in the country modules (Hong Kong, Macau, China, Curaçao, Austria, Canada) opens the same error viewer as CARF; each message shows the affected entry in an "Entry" column, and a double-click, "Go to entry" or "GO TO ENTRY" switches to the tab and selects the row. Every error viewer has a "Clear list" button and a severity filter ("All / Errors and warnings / Errors only"); loading or creating a new report clears the list of the previous one. TRSUIT-228
- Validation before export: the OECD XML exports of the CRS module (including NIL report, split exports and the Swiss archives) and the CARF XML export run the business-rule validation before writing. If it reports errors, a dialog asks "Export anyway" or "Cancel" (default); "Cancel" writes no file and opens the error viewer. If the export passes with notes only, the success message shows their number and "Show notes" opens them. TRSUIT-228
- Excel export on the 2601 templates: the CRS export writes the 2601 workbook including the CRS 3.0 elements (Self-Certification, DD Procedure, Account Type, Equity Interest Type, Joint Account, controlling person Self-Certification) and one "CP to Previous" row per additional controlling person type; the FATCA export uses the same 2601 data dictionary as the import and writes the current FATCA_Basic_2601 workbook with document type and schema version. Exported workbooks can be imported again without loss. TRSUIT-214 TRSUIT-223 TRSUIT-228
- Long-running tasks in the background: IDES transmission archives, FinanzOnline, the Malaysia and Macau delivery packages, IGOR requests, the TAXFI/FC XML/BBDM exports and the split exports now run in the background with a progress message and a single summary; the window stays responsive and a run can be cancelled. TRSUIT-228
- Running numbers: one common dialog for every running-number prompt (Reporting FI, account, message); the suggested value always has the required number of digits, cancelling always stops the ID generation, and the split export asks for the number for Malaysia, Finland and Albania as well. TRSUIT-228
- Message dialogs with many validation messages no longer grow beyond the screen: long messages are shown in a scrollable, copyable text field, and a dialog opens at most 800 pixels high. TRSUIT-228
- New address for the update check: TRSuite contacts
https://update.trsuite.chfor the update check and the licence check at start-up (earlier versions usedupdate.section11.chandwww.section11.chover HTTP). The connection is encrypted, and the check logs in to a proxy with the user and password from the master data. The start-up checks run in the background with time limits, so TRSuite starts normally without network access. TRSUIT-222 TRSUIT-228 - The suggested reporting periods in the CRS, FATCA, Macau, SEI, CARF, China, Curaçao, Hong Kong and Luxembourg modules extend to 2030. TRSUIT-228 TRSUIT-225
Improvements
- Error viewer: every entry has a tooltip with the full message text, broken into lines at element, path and DocRefId, so long messages can be read without widening the window. TRSUIT-228
- Excel templates (CRS 2601, HK, MO, CARF): "Check Data" validates country codes against the country list of the workbook and accepts the account number type as label or code; the drop-down lists include OECD606, CRS800, reporting period 2030 and the CRS 3.0 lists in all CRS variants and the multi-FI template; the Macau templates offer OECD606 (schema 1.4); the tax residence fields accept several countries as a comma-separated list (e.g. FR,NL); the country lists contain the Uruguay-only code YY; drop-down lists of three sample files that had shifted to the neighbouring column are corrected; the AC02 column is labelled "Account Number Type"; the template ZIP files contain the Excel user guide as PDF. TRSUIT-222 TRSUIT-227
- Excel import: numbers of 12 or more digits are imported completely instead of in exponent notation; amounts are read from the cell value, and amounts with more than two decimals are reported when rounded; codes and labels are both accepted for account number type, name type, account holder type and controlling person type; yes/no fields accept 1/0; unknown codes are reported with sheet, row and field instead of being dropped; an invalid code in a comma-separated country list no longer drops the valid codes after it; invalid amounts are reported with field name and cell (never with the value); check boxes and TRUE/FALSE cells are read; the account reports keep the order of the workbook; a workbook that does not fit, does not exist or cannot be read leaves the current report unchanged; the workbook is no longer locked after the import; the bundled CRS templates with DocRefIDs import without a custom configuration; an unreadable dictionary sheet stops the import with a clear message; entries below line 228 of a custom data dictionary are read. TRSUIT-224 TRSUIT-226
- Exporting a report with more than about 12,000 account reports to Excel no longer fails, and very large delivery files (several hundred megabytes) no longer need a multiple of their size in memory. TRSUIT-224
- Country modules open faster (the data dictionary is no longer read completely on every open), CARF handles large reports much faster, and the Log File Viewer reads in the background and shows the last 5,000 lines. TRSUIT-228
- Unused controls removed: the "Data Science" button, the "Dashboard (Status)" field in the master data, the CARF "Data Filter" options and "Clear RCASP Information", and the "Export CNCRS XML ..." menu item. TRSUIT-228
- Splash screen, About dialog, licence messages and installer show the company name BRIFS GmbH and link to https://www.trsuite.ch; the installer shows the end-user licence agreement from the program package. TRSUIT-228
- Exiting TRSuite always runs the shutdown steps (for example stopping the CARF auto-save). Starting without a licence key no longer writes error stack traces to the log. TRSUIT-228 TRSUIT-222
- "Generate Template" in the configuration tabs reports gaps in the data dictionary instead of failing silently. TRSUIT-224
Bug Fixes
- CRS configuration: the "Configuration Sheet" list is empty and disabled as long as no Excel configuration file is selected; before, it showed a stored sheet name without a file. Without a configuration file the import recognises the delivered workbooks on its own. TRSUIT-228
- Exports report errors: an export to a locked or write-protected file could report success because the check ran on the older file; a write error is now reported and the existing file left untouched (CRS in all versions, Austria, China, Curaçao, Hong Kong, Macau, FC XML, Canada, BBDM, Uruguay). A failed export never leaves an incomplete file behind, an encryption error no longer produces an empty Swiss archive, and the Excel export stops with a message when the template cannot be copied to the target file. TRSUIT-224 TRSUIT-228
- XML export: values containing "CDATA" and control characters are escaped or removed consistently in every export (the file was not valid XML before); the control character U+0085 is removed like the others; no character references such as
	are written any more. The sequences&#,--and/*are removed from values in every export, including attribute values; if this or the removal of an invalid control character would change an identifier (DocRefId, CorrDocRefId, MessageRefId, CorrMessageRefId, account number, Sending Company IN and similar), the export stops before writing the file and names the element. Other values are written without these sequences, and the export shows a warning instead of finishing silently. An error while writing an organisation IN stops the export instead of leaving a file without the IN. TRSUIT-224 - Split & Save failed with an internal error whenever a party had a date or country of birth or an account carried joint-account data; it now uses the same DocRefId rules as the regular export and names each file after its own MessageRefID. TRSUIT-226 TRSUIT-228
- CRS entry screens: a new account that was not yet added with "ADD TO LIST" is added when you select another row and confirm; switching tabs no longer discards an account report being entered; all equity interest types and all controlling person types of a loaded report are kept (additional types in the tooltip); the message type and the controlling person type no longer appear set while being empty after a tab switch; invalid input is reported and kept; "Correct Report" and "Generate Doc Ref IDs" change nothing when a running-number dialog is cancelled; "Create Documentation" reports a missing or read-only target folder. TRSUIT-228
- Validate, Save or Print no longer change the document type or corrected message reference of the loaded report; reports with several reporting groups are loaded completely with a notice; a failed XML, Excel, TAXFI or CNCRS import leaves the current report unchanged; an unreadable XML or work file is reported with file name and cause, and "Save" no longer overwrites it. TRSUIT-228
- Running numbers wider than the DocRefId format lost their leading digits, so two reports could receive the same DocRefId; the number is now always written in full (also SEI serial numbers and the Canada slip DocRefId). TRSUIT-222
- PDF documentation: creating the documentation no longer stops on names outside the Latin alphabet; both a free-format and a structured address are printed; "null" no longer appears in file names or FI lists; amounts in a currency Java does not know (e.g. UYW) are shown with the currency code; a PDF that cannot be written is reported. TRSUIT-224 TRSUIT-226
- A new installation defaults to CRS XML 3.0. Country code lists entered as "DE, CH" keep their order. The generic CRS configuration no longer offers the reference ID rules of the national modules. Work files in CRS XML 1.0 with the type CRS819 can be opened again. TRSUIT-228 TRSUIT-224
- Command line: CRS XML 3.0 is written exactly like in the CRS module; the Excel step reads the workbook like the application, so the CRS 3.0 fields are no longer lost and the generated XML is schema-valid; configurations with a reference ID rule that needs a running number are rejected with a message. TRSUIT-224
- Licence check: if the minimum support date cannot be read, TRSuite no longer accepts every support licence. The connection test in the master data reports unknown HTTP status codes. The IDES receiver field no longer shows "000000.00000.TA.00-1" for countries without an ISO numeric code. TRSUIT-228
Security & Dependencies
- Stored passwords: passwords in configuration and work files (IDES, Macau, Malaysia, Uruguay, Albania, master data proxy, Swiss SEI, customer-specific extension) and in the user settings (FinanzOnline PIN, IGOR API key) are stored encrypted and bound to your Windows user account; existing files are read as before and converted on the next save. "Reset" in the IDES module no longer clears the password fields; the IGOR API key is masked. TRSUIT-224 TRSUIT-228
- Proxy credentials from the master data are sent only to the configured proxy server; previously they were also sent to any web server that asked for a login. TRSUIT-224
- "Accept all certificates" applies only to the connections it is meant for (connection test, update check, IGOR, Albania upload) instead of relaxing every HTTPS connection of the program. TRSUIT-224
- SFTP host key verification for IDES (see "USA – IRS FATCA / IDES"). TRSUIT-224
- Signing: if signing fails, no unsigned file is left at the target path; an invalid signature of a received IDES file is reported. TRSUIT-224
- XML files are read with a restricted parser configuration in all modules; document type declarations and external references are not processed. TRSUIT-224
- Certificates of tax authorities (Macau, Uruguay) are chosen by key usage when a file contains several certificates. TRSUIT-224
- The FinanzOnline session identifier and the uploaded report content are no longer logged. TRSUIT-228
- Library updates: Jackson 2.18.12 (closes CVE-2026-89407, CVE-2026-89425, CVE-2026-91776 and CVE-2026-91777 of the 2.18 line). CVE-2026-110879 (polymorphic type handling in jackson-databind, no fixed version published yet) does not affect TRSuite, which uses no polymorphic deserialisation; the VEX document states the assessment. The SBOM and VEX published with this release list every component. TRSUIT-222
- Internal cleanup: a large amount of unreachable code (about 136,000 lines of generated model classes, unused validator copies, copied library classes for JDOM and ControlsFX, the copied proxy detection library) has been removed; TRSuite uses the released library versions. No effect on how reports are created, checked or exported. TRSUIT-225 TRSUIT-226 TRSUIT-228 TRSUIT-224
Upgrade Notes
- Minimum support licence: TRSuite 26.03 requires a support licence valid until 1 October 2026 or later. TRSUIT-222
- Firewall and proxy: if a firewall or proxy restricts the outbound connections of TRSuite, approve
update.trsuite.chon port 443 (HTTPS). Keep the entries forupdate.section11.chandwww.section11.ch(port 80) as long as you run versions up to 26.02.0.2. Without access, TRSuite works as before but cannot notify you about new versions. If your proxy replaces TLS certificates, the update check needs "Accept all Certificates" on the Masterdata tab. The default address of "Test Connection" is nowhttps://update.trsuite.ch. - Proxy detection: "Auto Detect" in the master data uses the proxy settings of Windows and no longer evaluates PAC scripts or WPAD. If your proxy is distributed only by a PAC script or WPAD, enter host and port by hand. A proxy already entered continues to work. If "authentication required" is set, host and port must be entered. TRSUIT-224
- IDES – SFTP host key: after the update the first connection to each IDES server shows the confirmation dialog once per Windows user. The IRS does not publish the fingerprint of the IDES gateway: make this first connection from your trusted company network, check the server name shown in the dialog and note the fingerprint; all workstations must see the same fingerprint for the same server. The keys are stored in
known_hostsunderAppData\Local\TRSuite\app. If you run IDES transfers from the command line or a scheduled job, confirm the key in the user interface first with the Windows user that runs the job, otherwise the first run after the update is refused. The procedure is described in the IDES guide, chapter "SFTP Host Key Verification". - IDES – certificate: if you entered a certificate file manually under "Path to IRS Public Key" after the IRS key change of 24 September 2026, you can remove that entry, because the bundled certificate is the current one. TRSUIT-222
- Stored passwords and your Windows account: passwords are protected with a key bound to your Windows user account. A configuration file saved by another Windows user or on another computer no longer carries a readable password; enter it again and save the file. This also applies to command-line runs under a service account: save the configuration under that account, or enter the password in plain text in the file – it is accepted and replaced on the next save. If Windows can no longer provide the key (for example after an administrator reset the account password, or after the profile was moved or restored), TRSuite creates a new key, informs you once at start-up and remains usable; the stored passwords appear empty and must be entered again. TRSUIT-224
- Log file: TRSuite writes its log to
%USERPROFILE%\AppData\Local\TRSuite\app\logs\trsuite.logat level INFO (previously a fixed folder on drive C at level DEBUG). Update monitoring or support scripts that point at the old location. TRSUIT-228 - Data dictionaries v1902 (
CRS_TRSuite_DataDictionary_v1902.xlsx,FATCA_TRSuite_DataDictionary_v1902.xlsx) are no longer shipped. If a configuration (application or command line) points to one of them, change the path to the v2601 file in the same folder; the sheets CRS_1902_* and FATCA_1902_* exist there as well. CRS workbooks in the old fixed-column format (1702/1704) are rejected with a message. TRSUIT-228 TRSUIT-224 - Excel templates: download the current 2601/2602 template bundles from the download page; the drop-down lists, "Check Data" and the CRS 3.0 fields described above are only available in these workbooks. The outdated FATCA templates in
resources\xlsof the installation are no longer installed. - New validation findings on existing data: many jurisdictions now apply rules of their tax authority that earlier versions did not check (among others British Virgin Islands, Bahamas, Bermuda, Cayman Islands, Guernsey, Jersey, Isle of Man, Liechtenstein, Germany, Austria, Switzerland, Singapore, Australia, France, Italy, China, Curaçao, Uruguay, CARF, EU TIN check for CZ/GR/LV/MT/RO/SK, Swiss AHVN13/UID, UK National Insurance prefixes). Files that validated without a message before may now show findings; every error corresponds to a rule that would have led to a rejection by the portal. Please validate existing reports again before the next submission and check findings against the source data.
- Cayman Islands: files whose DocRefIds do not start with
KY, the reporting year and the receiving country are reported as invalid; TRSuite generates this format with the DocRefId ruleCRS_KY_FI, which the Cayman validator preselects. Check the rule on the configuration tab if you see the new message. - Germany: the menu item "Germany (DE) → Export DE BZSt XML" no longer exists; use the OECD XML export with the German validator and the mass data upload of the BZSt online portal. The default number of account reports per file is 20,000.
- Luxembourg: the new "Schema" selection (V3.0/V2.0) is preselected by date. If you use a sponsor, an intermediary, a pool report or more than one Reporting FI, check the export message; the earlier version accepted these files but silently left out data. Overseas territories are written with the destination codes required by the ACD.
- Uruguay: with CRS version 3.0 in the CRS configuration the export writes Doméstico 3.0, which the DGI accepts only from 2 January 2027; select 2.0 for submissions before that date. A MessageRefId that does not follow the DGI format is reported (50008).
- Macau: the target schema version must be selected explicitly before a report can be exported or checked.
- Curaçao: the "Recalcitrant" field no longer exists; recalcitrant FATCA account holders are reported with the FATCA account holder type.
- Canada: generated DocRefIds use the BN RZ of the filer account number instead of the Reporting FI IN; the 2028V1 format is preselected for taxation year 2027 and later.
- Australia: the BBDM export asks for the sender identifier type (ABN or TAN); from 1 January 2027 a CRS XML 2.0 file is reported as an error.
- CARF: CARF XML 1.0 files can still be opened, the export writes version 1.5 only; amounts are written with two decimals. Existing CARF data may show new validation messages (date of birth range, duplicate CorrDocRefID, OtherNexus, blank mandatory fields). The CARF Excel macros require the current CARF_2602 template.
- Corresponding Message Reference ID: the value of the General tab is no longer copied into every Doc Spec (only Finland/TAXFI). The OECD XML export now warns when a file exceeds the country's file size limit.
- Command line: CRS XML 3.0 is written like in the CRS module (empty elements are left out) and Excel workbooks are read like in the application; the result can differ from 26.02. Uruguay reports are written in the DGI domestic format.
Known Limitations
- National formats based on CRS 3.0 for Austria, China and Hong Kong are pending until the respective authorities publish their 3.0 schemas; Hong Kong's IRD schema v2.0 cannot carry the controlling person self-certification or more than one controlling person type. The generic OECD report in 3.0 is not affected.
- Isle of Man (GN53 rules), Luxembourg (CRS_LUX V3.0) and Canada (Part XIX 2028V1) are implemented from the published specifications; a test submission to the authority's test environment has not yet been made. The Guernsey rules follow the draft Guidance Notes v2 and will be reviewed against the final version; the Bahamas rules await the Competent Authority's confirmation of the first reporting period for schema 3.0; the Malaysia MessageRefId rule accepts both published forms until the IRBM answers; the United Kingdom rules are subject to a pending HMRC query.
- China: "Validate" does not yet cover the complete national rule set; the confirmation message names the checks that were run.
- Singapore: accounts with more than one jurisdiction of residence or more than one controlling person are reported as errors; TRSuite does not yet split them into separate account reports automatically.
- Luxembourg: with schema V2.0 selected, fields that exist only in CRS XML 3.0 are left out of the file.
- IDES: SFTP through a proxy that requires authentication is not supported.
- FATCA Form 8966: with a test licence, "Check" still validates against the production document types, while the export correctly writes test document types.
- Germany: the DIP interface of the BZSt (automated transmission with a DIP envelope) is not supported; use the mass data upload of the online portal.