Every product in this category demos the same way: a dashboard, a green tick, a submission button. The differences that matter are underneath, and they are the same four things whatever the regulator and whatever the return. This page is those four, in the order they bite, so a demo can be steered at the parts that will actually hurt in month three rather than the parts that look good in month one.
Collecting the data from systems that were not built to give it
The return wants figures in the regulator's shape, and the business keeps them in the core system's shape. Everything else in the category is downstream of how the gap is crossed: an export somebody edits, a mapping somebody maintains, or a feed nobody touches. Ask which, and ask who owns the mapping when the core system is upgraded. That answer predicts more about the next two years than any feature list.
Applying the form's rules, including the ones that change
Forms are versioned and the rules move. What matters is not that a product supports the current version but how quickly it supports the next one, and whether your data has to be reshaped when it lands. A product whose validations are configuration ages differently from one whose validations are code. This is worth an explicit question because both look identical in a demo of the current form.
Keeping the evidence a figure rests on
A number in a return is only as defensible as the working behind it, and the moment anybody queries it the question is what the figure was derived from and who checked it. A solution that stores the submitted file and nothing else has solved the easy half. The useful test: can it show, for a figure filed eighteen months ago, the source extract and the person who approved it, without anybody going to a backup.
Proving what was filed and when
The submission receipt, the version submitted, the date, the person. This is the part every product claims and the part worth testing hardest, because it is the one an examiner asks for and the one that is most often a folder on a shared drive with a naming convention. If the answer to what was filed on this date is a search of somebody's mailbox, the product is not doing this.
Questions people ask about regulatory reporting solutions
Do we need a dedicated product at all?
Below a handful of returns a year, a spreadsheet and a calendar genuinely work. The point at which they stop is usually when the person who built the spreadsheet leaves.
How do we compare two of these fairly?
Run both against a return you have already filed and compare their output to what you actually submitted. A demo on the vendor's data compares nothing.
What is the most common thing missed in selection?
Who maintains the mapping when the source system changes. It is nobody's favourite question and it is the one that decides the running cost.