Check your Register of Information before you file it.
Drop in the xBRL-CSV report package you are about to submit — or, if you have not built one yet, a single template straight out of your spreadsheet. This checks it against the fifteen templates of Implementing Regulation (EU) 2024/2956: keys that cannot be empty, columns that must hold one of the regulation's own codes, and references that have to resolve between templates. Those three account for most rejections.
Most checkers want the finished package, which is no use while you are still assembling one. A loose CSV is recognised by the columns it carries, so it does not matter what your spreadsheet called the file.
The file stays on your machine. It is read in your browser. Nothing is uploaded, nothing is stored, and we never see it. Your Register lists your providers and what you pay them, so it should not have to leave your laptop to be checked.
Nothing to hand? Download a sample package and drop it back in. It is a real export with real faults in it, so the check has something to find.
What this checks
- Every key column is filled, because the templates join on them.
- Every coded column holds one of the regulation's own values, not a phrase that reads correctly.
- Every reference resolves: an arrangement cited in B_02.02 exists in B_02.01, a provider used anywhere is described in B_05.01, a function is defined in B_06.01.
- Which of the fifteen templates the package actually contains.
The columns and code lists come from the EBA's own reporting framework 4.0 technical package. What it does not do is run your supervisor's full taxonomy validation, so a clean result here means the structure is sound, not that the filing is accepted. The 15 templates and 120 columns it knows about are the ones the implementing regulation defines.