The mechanics rather than the rules: how source data becomes a validated submission file, what a validation report is telling you, which formats come out, and what happens to the data you put in.
The other pillars answer what a framework requires. This one answers how the file actually gets made. Every REGREP module runs the same shape of work: source data arrives in the format your systems already produce, it is mapped to the reporting model for the framework and the taxonomy version in force, it is validated against the published rules before anything is submitted, and it is exported in the format the authority accepts. Most of what practitioners need to know sits in the joins between those steps.
So this pillar collects the operational material — conversion tutorials worked end to end, guidance on reading a validation report and acting on it, reference datasets such as taxpayer identification number structures, and a maintained catalogue of the frameworks and output formats we support. It also covers the questions that come before a first upload: what a test run does, what is retained afterwards, where data is processed, and how deletion works. Every record cites its source and carries the date it was last reviewed, and platform behaviour that changes is recorded in the changelog against an immutable framework version rather than quietly amended.
Two habits save the most time. The first is treating validation as the working step rather than the final gate — a validation report read early tells you which source fields are wrong while there is still time to fix them at source. The second is keeping the mapping stable: source layouts that change every period turn a solved problem into a recurring one.
Nothing here replaces the framework rules themselves, and no output is submitted on your behalf. When you want the wider picture of what the platform does and how data is handled, the capability and security pages carry it in full.
What each area covers, and where the full detail lives.
Looking for the rules rather than the mechanics? Framework obligations sit in the tax transparency, operational resilience, prudential reporting and digital assets pillars.
Everything published under this pillar, newest first.
Reviewed submission dates across every framework we support, shown in each deadline’s local timezone with the official source attached. Guidance only — always confirm the current date with your national competent authority.
Convert, validate and export — with the validation report in front of you before anything is submitted to an authority.
