Applies to: AEOI
|Warning: Please be aware that there might be small differences between your project implementation and the screenshots and information in this article, however, the overall functionality remains the same.|
To create a CRS Filing based on a XML Upload, first go to the Menu Button on the left hand side.
Then go to Manage Filings and Create Filing.
Each Financial Institution must decide between a Manually entered filing and a filing completed through XML upload.
In this module, we will concentrate on supplying data through XML data uploads, hence the CRS XML Upload Filing option should be selected.
Each Filing must have Filing Name, Filing Type and Period End Date. Click Create Button.
To Complete the XML Filing
Click on the Filing Name to Complete (In this example it is CRS XML Filing 18)
After selecting a Filing, select Upload Data to automatically populate the filing from an XML file by clicking on Upload Data on the right hand side.
You will now browse for the XML file you wish to upload.
Select the file and click on Open.
Once the selected file uploads, the system automatically virus scans the file and rejects it if a virus is found. If no virus is found, the file is stored for offline processing. The FI user is informed that they will be notified in due course of the outcome of their submission. At this point, the FI user has completed the process and can logout.
As XML files can be very large and contain large quantities of data, their processing is handled offline so as not to impact system performance. The XML file is placed in a “queue” for processing, from where a background server picks up the XML file and performs the following processing steps:
The XML file is first fully validated against the relevant XSD (XML Schema Definition) file that is published by the OECD for CRS or CbC. If any XML errors are found, the processing stops, and the errors are recorded. A notification email will automatically be sent to the FI notifying them of the failed submission.
Data Extraction & Further Validation
If the XML file passes the XML validation, the system extracts the data from the XML file and enters the data into the Vizor CRS or CbC data model. At this point additional validation rules are executed:
- For CbC filings, the only additional validation on top of the XSD validation will be to ensure the reference ID is unique
If any validation errors are discovered, the errors are recorded and the processing stops. A notification email will automatically be sent to the FI notifying them of the failed submission.
If the two sets of validation performed above result in no errors with the XML data, then the filing is automatically submitted. In this scenario, the FI user is notified by email that their filing has passed all validation rules and has been accepted by the system. The successfully submitted filing moves from the “Draft Filings” area of the system to the “Submission History” area (this section is described later in this document).
If any validation rules fail in either of the two processing steps above, then the FI user is notified by email that there are validation failures. For security purposes, the nature of the validation errors are not contained within the email. The FI user must now log into the Portal application to view the detail of the validation failures. These errors are accessible to the FI user by clicking on the errors icon next to the filing in the “Draft Filings” screen.
Last review date: 28th February 2023
Author: Alan Joyce
Warning: When working with Vizor Builder or any aspect of Vizor Software configuration including individual configuration files, please note that significant problems can occur when performing modifications or additions to existing configuration incorrectly. it is highly recommended that a backup of any project or related file is readily available when making any configuration adjustments. In addition, any modifications made to configuration or project files should be carefully tested before being deployed to any live environment. In addition, changes to projects or configuration files should be made by trained and certified personnel in the use of Vizor Software. If further advice is needed on making any configuration changes involving Vizor Software, a customer support representative should be consulted.
Article is closed for comments.