Welcome to the release notes for TRSuite version 21.01.0.23 Read these release notes thoroughly before you install the latest update, as they contain information the User Guide documentation may not cover. Release 21.01.0.23. and later requires a valid support license valid after 1^st of January 2023.

Please provide any feedback to: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

TRSUIT-134: SEI: Birthdate < 1.1.1900

If a person's birthday is before 01/01/1900, the "sfa:BirthInfo" tag is tacitly omitted from the FATCA XML due to a CRS rule. However, it is retained in the SEI-XML. The FTA carries out a check when importing the packages and determines: "The account holder's birthday from FATCA-XML does not match the account holder's birthday from SEI-XML. vs. 1899-XX-XX».

TRSuite now displays an warning after an excel import if the birth info was omitted. This allows the user to take the needed action (correct or remove the date entry).

 

TRSUIT-135: SEI: Organisation as Controlling Person

If an organization is designated as Controlling Person, the corresponding "ftc:SubstantialOwner" tag in the FATCA XML is implicitly omitted due to a rule. In the SEI-XML, on the other hand, he remains as a controlling person. The FTA carries out a check when importing the packages and determines: "SubstantialOwner from FATCA-XML does not match ControllingPerson from SEI-XML. Name: <company name>». In addition, there is a follow-up message, e.g. "The number of SubstantialOwners from FATCA-XML does not match the number of ControllingPersons from SEI-XML. Number of FATCA-XML 3 vs. number of SEI-XML 4"

TRSuite now displays an warning after an excel import if an element was omitted. This allows the user to take the needed action (correct or remove the date entry).

 

TRSUIT-141: FATCA: XLS Export

TRSUIT-145: CRS: XLS Export

Both modules (FATCA, CRS) now offer the option to export the current report into a XLS file (same format as known TRSuite templates). Currently only a single reporting FI is supported.

After selecting the export file path the data is exported into a XLS file. Data can now be corrected / added / removed and re-imported into TRSuite.

 

 

TRSUIT-109: CRS: AU CRS schema update

The AU specific transfer XML format has been updated and addresses new requirements concerning the content of the OECD-XML schema version 2.0. After updating to version 21.01 all exports will be done with the new schema version.

<bbdm:Message.Type.Text>crs.0002.lodge.request</bbdm:Message.Type.Text>

Loading OECD XML documents is possible for both versions. TRSuite detects the required version and loads the document accordingly.

 

TRSUIT-143: SEI: Several issues for update package

In case of an update package, the naming convention for delivery and information packages did not follow the ESTV standard. Now the following rules are properly implemented:

Delivery File

Fix: Da es sich um ein Update Delivery File handelt, muss der Filename zwingend um MM (-01) erweitert werden.

631.2-2021-US-2015-0000-0001-01.zip  (631.3-YYYY-US-AAAA-BBBB-TTTT-MM.zip)

Information Package

Bug: Die Information Packages, welche nicht updated wurden, tauchen auch im File auf.

FIX: Ein Update Delivery File darf nur Information Packages enthalten, welche updated wurden. Filename muss beibehalten werden und mit ‘-01’ ergänzt werden. In unserem Fall dürfen nur folgende Informations Packages enthalten sein:

631.2-2021-US-2015-0000-000046-01

631.2-2021-US-2015-0000-000047-01

631.2-2021-US-2015-0000-000052-01

 Inhalt der Information Packages

Fix: Auch die Filenamen müssen hier um ‘-01’ erweitert werden.

 631.2-2021-US-2015-0000-000046-01.pdf                     (631.3-YYYY-US-AAAA-BBBB-NNNNNN-MM.pdf)

631.2-2021-US-2015-0000-000046-01.xml                    (631.3-YYYY-US-AAAA-BBBB-NNNNNN-MM.xml)

631.2-2021-US-2015-0000-000046-FATCA-01.xml        (631.3-YYYY-US-AAAA-BBBB-NNNNNN-FATCA-MM.xml)

 

TRSUIT-147: FATCA/CRS: PDF Creation Protocol: line break if path is too long

The file path of the generated file name was not visible, if path elemen was to long > 100 chars. Now the name is properly formatted (line break).

 

TRSUIT-125: FATCA: Signatur validation multiple certificates

Prior to version 21.0.1.23 a signatur validation failed, if the signatur contains > 1 certificate. This has now been fixed.

 

TRSUIT-132: CRS: Ireland Validator uses wrong country code

 Prior to version 21.0.1.23 the Ireland country validator uses IR instead of IE default country code. This has now been fixed.

 

TRSUIT-133: CRS: Split by tax residence fails if CP has a TIN List

 Prior to version 21.0.1.23 the split and save function failed, in case the controlling person has > 1 TIN. Now the controlling person is properly exported to all required country reports.

 

TRSUIT-137: CRS: Missing Message Type is not validated

 Prior to version 21.0.1.23 a missing message type does not generate an warning message when validating the report. This has now been fixed.

 

TRSUIT-138: CRS: IE check for valid character

Specific characters needs to omitted in case reporting to IE tax authority. Version 21.01.0.23 offers the option to replace those forbidden character.

 

 

 

 

 

 

Welcome to the release notes for TRSuite version 20.05. Read these release notes thoroughly before you install the latest update, as they contain information the User Guide documentation may not cover. Release 20.05. and later requires a valid support license valid after 1^st of May 2020.

Please provide any feedback to: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

TRSUIT-42: SEI FATCA Information Delivery v1.3 (Improvement)

The "Technical Specification and User Guide for Financial Institutions according to FATCA IGA 2" [hereafter: «User Guide»] has been updated and addresses new requirements from the IRS concerning the content of the FATCA-XML file (CARRef-Element in accordance with the FATCA XML scheme V2.0, cf. chapter 4.5.3 of the user guide). The general rule is that financial institutions concerned have to take into account the requirements of the IRS for the FATCA-XML that are valid at the time the file is delivered to the FTA.

TRSuite Version 20.05 implements all changes as described in version 1.3 of the User Guide. Further the software validates the reports against all important business and validation rules for SEI XML and FATCA XML as described in Business & Validation Rules FTA (PDF, 197 kB, 19.05.2020)

 

TRSUIT-57: SEI FATCA: NPE in case of 0.0.1900 birth date format (Bug)

In case the invalid birth date 0.0.1900 was entered into the excel template the import failed with a "Null Pointer Exception". This error condition is now handled correctly and the user is informed about the incorrect data.

 

TRSUIT-58 CRS: Adress element getting duplicated during export (Bug)

In case an address element was a combination of a free and fix address element the data was duplicated during the XML export. If only free or fix address element was used the data was exported without any issue.

Export of address data is now correct and no duplicate data element is produced.

 

TRSUIT-59: MO CRS: Update to XML v1.3

Macao reporting schema is updated to version 1.3 (since version 20.05.0.4)

 

TRSUIT-62: SEI FATCA: Support for Cover Letter (New Feature)

Since version 20.05 it is possible to add a cover letter to the generated delivery package. Simply select or enter the path to the relevant file and it will added automatically. If the delivery file is split due to size or account number restrictions the cover letter is added to each generated delivery file.

 

TRSUIT-61: SEI Reporting Pool Report Data Extractor (New Feature)

In case the FTA request further information about pool report data regarding threshold, the FI needs to send a excel file with specific data as described below.

To support financial institutes generating such a report we implemented a little tool (pool extractor) to extract the relevant information from pre-existing pool reports. As not all data is available in the pool report, there is still a major manual task to complete the data. The data is missing, because within the pool report there is no data available regarding above/below threshold data.

The flow looks like:

1.    Collect all your relevant pool report in one folder (Reports Root Folder)

2.    The tool collects all XML files within the defined folder, extracts the data and generates a enclosure.xlsx file (or as named by the user) in the root folder.
3.    Manually complete the data

 

TRSUIT-64: SEI Reporting Pool Report Data Extractor fails for FATCA XML 1.0/1.1 (Bug)

The extraction process failed for reports generated in year 2014/2015 in the old FATCA XML 1.0 or 1.2 format. Since version 20.05.0.1 also the extraction of the old formats is supported.

 

TRSUIT-63: IDES: IRS Response extraction fails with no error

The validation of the working directory failed during the extraction process of an IRS response. The process aborted without further notification. This is fixed for version 20.05.0.1.

 

TRSUIT-77: SEI: Support for Sponsor in Excel-Template

A new excel template supports the import of a sponsor entity since version 20.05.0.4

 

TRSUIT-79: SEI: File and Folder Naming wrong year used

When generating delivery artifacts with version 20.05.0.4 a wrong file name is generated. Instead of the dossier year the FACTA-Reporting year is used. This is fixed for version 20.05.0.5

 

TRSUIT-81: FATCA: NIL-Report splitting by FI

Since version 20.5.0.7 also NIL Reports are taken into consideration when splitting collected FATCA data by reporting FI.

 

TRSUIT-83: FATCA:Support for Notification schema update v. 2.5

BASE-FATCA-NOTIFICATION-2.5 - Base schema for common data elements and data types related to FATCA notifications. Referenced by all main notifications schemas.

• Updates (from prior version):
• RecordLevelErrorCd datatype changed from enumerated list of 4-digit values to 5 character string

FATCA-FILE-ERROR-NOTIFICATION-2.5 - Main schema that describes various types of file level error notifications.
FATCA-VALID-FILE-NOTIFICATION-2.5 - Main schema for the valid file notifications.

• FATCA Report Notification XML Samples_2.5.xml :
• FileErrorNotificationSample_2.5.xml
• FieldLevelErrorNotification_2.5.xml
• RecordLevelErrorNotification_2.5.xml
• ValidFileNotification_2.5.xml

https://www.irs.gov/businesses/corporations/fatca-xml-schemas-and-business-rules-for-form-8966

 

TRSUIT-84: SEI: Fix for "Missing Ressource Exception"

Missing ressource bundel konfiguration key for "Legal Entity" leads to:

      java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key legalEntity

The key is now added.

Also a workaround is available using a temporary license key (please contact This email address is being protected from spambots. You need JavaScript enabled to view it. to receive such a key):

Enter the temporary license key, restart TRSuite -> Three additional fields are visible in the "Settings" tab of the SEI module:

Enter any value in the field "Legal Entity" and save the general informations (the value is stored in the windows registry)

Finally re-enter your origin license key and restart the application. Now the generation of the delivery file(s) should run without problems.

 

 

TRSUIT-86: SEI: Creating SEI work item fails with IllegalAnnotationsException

Saving a TRSuite-Work Item for a SEI-Report failed without further notice due to a missing XML-Element mapping. This issue is fixed with patch 20.05.0.8.

Further a success/fail message is displayed to the user after the export.

 

 

TRSUIT-88: SEI: Updated requirements for the information delivery

Patch 20.05.0.9 brings support for the updated "Credentials Exchange (v1.3) - Information Delivery" pdf form.

As a workaround the pdf can be manually exchanged in the <INSTALLATION_PATH>\TRSuite\app\resources\sei folder, but needs to be named "SEISYS_FATCAInformationDelivery_CredentialForm_v1.2.pdf"

 

 

TRSUIT-86: CRS: Albanian Country Validator

Since Version 20.05.0.9 a new country validator for Albania (AL) alllows the complaiant generation of message- and document reference IDs according the AL-specific definition:

MSG-RefID: AL<YEAR><TIN><10-digit-RUNNING-NUMBER>

DOC-RefID for Reporting FIs: AL<YEAR><TIN>FI<10-digit-RUNNING-NUMBER>

DOC-RefID for Account Reports: AL<YEAR><TIN>AR<10-digit-RUNNING-NUMBER>

 

 

 

 

 

 

 

 

 

Welcome to the release notes for TRSuite version 20.11. Read these release notes thoroughly before you install the latest update, as they contain information the User Guide documentation may not cover. Release 20.11. and later requires a valid support license valid after 1^st of November 2020.

Please provide any feedback to: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

TRSUIT-88: CRS: Update schema v2.0

The OECD CRS XML specification has been updated (v3.0) and addresses new requirements concerning the content of the OECD-XML schema version 2.0. TRSuite Version 20.11 implements all changes as described in version 3.0 of the User Guide. Further, the software validates the reports against the new schema version 2.0.

To enable the new format, the user needs to configure the CRS version in the CRS Common Configuration section of the CRS module. After setting the version to 2.0 all exports will be done with the new schema version.

Loading OECD XML documents is possible for both versions. TRSuite detects the required version and loads the document accordingly.

 

TRSUIT-92: SEI: Provided password is overwritten during package generation (Bug)

Any entered password was overwritten during the generation of the transmission archive(s). This has now been fixed and a password provided by the user is used for all generated archives.

 

TRSUIT-93: SEI: Coverletter requires dedicate zip-File

Until version 20.05, the cover letter has been placed within each generated transmission archive. Since version 20.11.0.0 a single dedicated ZIP-file is generated with the cover letter as content.

 

TRSUIT-94: SEI/FATCA: Document Reference ID capital letters only

Since version 20.11 the document reference IDs are generated in capital letters only.

 

TRSUIT-94: CRS: Albania Country Extension

Version 20.11 now supports CRS reporting for Albania. This covers a specific country validator, the XML signing, the generation of the required GovTalk XML-File and the HTTP post request to send the data to the local tax authority.

Workflow:

• Generate default OECD CRS XML using TRSuite with AL country validator
• Select the file as input for the “Sign & Submit” dialog
• Configure Private Key, Working Directory and GovTalk-Details
• "Generate XML" -> Upload File prefilled with the generated fiel
• Configure Target-URL
• "Upload" generated GovTalk XML file
• Verify response: stored in the Working Directory: GovTalkResponse_<YYYMMDDHHmm>.xml

 

TRSUIT-97: FATCA/IDES: IRS certificate update

The IRS has published a new public key replacing the existing key on December 13, 2020. TRSuite version 20.11.0.1 includes the latest key.

After December 13, if you don't upgrade to the latest TRSuite version, you need to download the new IRS Public Key from IDES support homepage and configure it manually in the IDES configuration screeen to file your FATCA Reports.

 

TRSUIT-99: SEI: Update Serial Number validation checks wrong Value

Previous version of TRSuite did validate the whole dossier number, not just the update part (2-digits). This is fixes in version 20.11.0.1.

In case you are using an older version, the error can be ignored in case the shown number is a two-digit value.

 

 

 

 

 

Welcome to the release notes for TRSuite version 20.03. Read these release notes thoroughly before you install the latest update, as they contain information the User Guide documentation may not cover. Release 20.03. and later requires a valid support license valid after 1^st of March 2020.

Please provide any feedback to: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Bug: HK Module: Excel Import: empty Controlling Person generates error during import (TRSUIT-51)

If the Excel-Datasource contains any empty Controlling Person for an organisation the import process reports errors (can be ignored). Since version 20.03 the import runs without errors.

 

Improvement: IDES Module: Validation, if working directory is accessible (TRSUIT-14), improved error message (TRSUIT-27)

Additional check for IDES configuration validation and processing: if working directory is not accessible / writeable a proper error message is shown. In previous versions the processing stopped with a cryptic error message.

 

Improvement: IDES Module: Save HCTA processing option

In case the user enables the "Encrypt AES key with public key of HCTA" stepp during the transmission archive creation, the step remains enabled next time the application is started.

 

Bug: SEI Module / FATCA: FilerCategory and AccountClosed should not be used for 2014/15

If FATCA reports are generated for reporting year 2014 / 2015 the both elements FilerCategory and AccountClosed should not be included for tax years 2014 and 2015, but is required for 2016 and later years (source: https://www.irs.gov/pub/irs-pdf/p5124.pdf).

 If the Reporting Period is 2014 or 2015 TRSuite does not generate the two elements within the FATCA XML report.

 

Bug: SEI Module: SEI File size splitting, last delivery package not written

If the last package exceeds the max file size and requires splitting the last delivery package is not properly created. Fixed since 20.03.0.0

 

Improvement: FATCA Reporting for SG: Adapt changes for SG Reporting

With effect from 1 April 2020, Reporting SGFIs must submit all FATCA returns, including nil returns (if applicable), electronically to IRAS via the “Submit CRS or FATCA Return” e-Service at IRAS’ myTax Portal. The Supplementary Guide provides additional guidance on how the information for certain data elements must be presented for the purpose of FATCA reporting to IRAS via myTax Portal with effect from 1 April 2020. (source: SG new supplementary XML guide).

Since version 20.03.0.0 TRsuite supports the described requirements. Once the transmitting country is set to SG, the specific ruleset for SG reporting is active. Automatically the receiving country is set to SG and the message reference ID is generated according the new guide.