Nothing is uploaded.This page has no endpoint behind it. The dictionary is bundled with the page and the check is a function that runs on your machine, so your register is never transmitted or stored. Open your browser’s network tab and watch.
Drop your register here
The filed xBRL-CSV package, or the CSVs behind it. Files are recognised by name - B_05.02.csv and the like.
What it checks, and what it does not.
Every rule below is read out of the official EBA reporting dictionary that ships inside Treica - module 1.1.0, in force from 2025-03-31 - rather than from a hand-written list. All 15 tables and all 120 columns.
- Structure
- Every column against the official EBA dictionary: headers that name no column in the standard, columns the file does not carry, and rows whose field count does not match the header - the quiet damage an unquoted comma in a company name does to every column after it.
- Coded values
- Each coded cell against that column's own code list from the dictionary, not against our idea of it. A coded column carrying the word behind the code is the most common single reason a submission comes back.
- Identifiers and formats
- LEIs with ISO 7064 check digits rather than length alone, ISO 3166 countries, ISO 4217 currencies, yyyy-mm-dd dates and numeric cells. A locale date is read as a different day; a mistyped LEI passes a length check and fails at the authority.
- Keys
- Empty primary-key cells and two rows sharing one identity. A blank key does not fail a value check - it breaks row identity, and the parser rejects the submission rather than naming a cell.
- The rules between tables
- The referential rules the dictionary carries, R1 to R22. A subcontractor in B_05.02 whose provider is not in B_05.01, an arrangement whose contract reference is in no B_02.01 row, a function referenced by nothing. This is the layer a format validator does not have.
- Supervisory risk
- Warnings that pass validation and still read as gaps: one provider entered under two identification codes, which reports a fraction of your real concentration; a provider declared with no supply chain at all; a criticality assessment with no reasons recorded.
What it cannot tell you. Whether your register is complete - a table you did not upload is not a table reported as empty, and the result says which ones those were. Whether a judgement is right: nothing here can decide if a function is genuinely critical. And whether your authority will accept the filing. Treica is software; it does not provide legal or regulatory advice.
If you would rather not maintain the file at all, that is what the product does: the register is generated from a connected record rather than kept as a document, so these checks run continuously instead of once a year. The warning tier is where you record your position against each warning so it becomes evidence of active management.