Resources › Guide

xBRL-CSV, explained simply

When it comes to the DORA Register of Information, regulators don't want a spreadsheet you designed yourself. They want a precise, machine-readable package in a format called xBRL-CSV. Here's what that means in plain terms.

What is xBRL-CSV?

xBRL is the international standard for structured regulatory reporting. The CSV flavour keeps the data in plain CSV files (easy for machines to parse and validate) while a small set of metadata files tell the supervisor how to interpret them against the official ESA taxonomy. In short: standard files, standard meaning, zero ambiguity.

What's inside a valid package?

• A META-INF folder and a report.json describing the report and taxonomy version;
• Parameters and filing indicators declaring which templates are reported;
• One CSV per template, with columns named to the official convention (e.g. c0010) and values drawn from the taxonomy's closed lists;
• The whole thing zipped and named to the ESA convention.

Why hand-made files get rejected

Every detail is checked: a wrong column code, a value outside a closed list, an invalid LEI, or a mismatched taxonomy version will fail the authority's quality checks. Excel gives you none of these guardrails, which is why so many first submissions bounce.

The reliable way to produce it

Generate the package from validated data, against the taxonomy in force, and replay the regulators' checks before you file. That's exactly what Obligia does: it produces the official xBRL-CSV package automatically, so you never assemble it by hand.

Generate my package   Avoid rejection ›

General information, not regulatory advice; responsibility for submission remains with the entity.