Every year, the REQ is required to be submitted by every subject person / obliged entity to the FIAU, typically around the time of March / April of the year, covering the period of the previous financial year.
The REQ has come a long way since the inception of KYCMATIC and has been altered by the regulator many times, at times even when a few weeks before the deadline, which no doubt can prove to be challenging.
Nevertheless, we have designed an REQ architecture that can adapt to change with ease, therefore abiding by the last minute changes that may be provided by the regulator - which is something we would perform and communicate to all subject persons / obliged entities when the changes would have been done.
Needless to say, what would not be able to be provided in a timely manner would be new data touch points. Therefore, if for example the regulator simply alters a question to capture information on entities who are PEP from within the EU to global, then this change is done with ease. On the other hand, if the regulator creates a new question, or alters an existing questions which requires new fields for data to be captured, this would be handled differently and may not necessary be in time for the REQ submission.
Selecting the 'Questionnaire' menu item shall direct the user (provided that the current user has the necessary privileges to access this module) to a screen similar to the above figure whereby a list of questionnaires would be have been previously generated - therefore being able to keep a record of all REQ's which had been generated previously. Here, you shall also be able to identify what REQs had been saved (submitted) compared to REQ's which have been started but not as yet submitted.
The difference in the 'Status' here implies that a user may start an REQ, review the information being exported and if required go back into KYCMATIC and update the information, provided this needs to be updated. Inevitably, once submitted, the REQ Data is 'locked' and would be kept to represent the REQ when it had been generated.
Creating a new REQ requires the user to select the 'Generate Report' button, which shall direct the user to a screen similar to the above figure whereby the user may select the report type, the integrations/environment on which the source data must be associated with and finally the reporting period, which by default is pre loaded with the dates of the previous financial year.
Once the 'Generate Report' button is again selected from the above, the report would execute and alter the screen to look similar to the figure provided below.
Once the report is generated, the user shall be able to review the different section (typically similar to what is shown in the actual REQ issued by the regulator) on the left, which will show the respective question and question numbers on the right. Since the data is being reviewed, assuming data would be changed from KYCMATIC, selecting the 'Update System Generated Values' button shall re-execute the report and updated the information being provided.
Once the REQ values are to your liking, the next step would be to select the 'View Report' button which shall direct you to a screen showing the REQ report in a 'PDF' format.
Once you are reviewing the report as shown in the figure above, you may be able to print the report to PDF to keep a hard copy (although you are able to access this from the initial screen at any time you require) as well as Submit the report, saving a state of all REQ data and therefore keeping a history of all REQ's which you would have generated.