EBA template code explorer
Framework 4.2 has 52 template workbooks, but only 31 of them ask you to enter a code. Those 31 carry 474 coded fields across 126 reports, drawing on 168 code lists. Pick a template and see exactly which fields need a code, and which values each will accept.
EBA Reporting Framework 4.2 · 474 coded fields · 126 reports · 168 code lists · runs offline
Explore a template
Runs in your browser · nothing uploadedStart with the template. Templates with no coded fields are marked, so you can see at a glance that there is nothing to look up rather than searching for something that is not there.
eba_ namespace prefix, which the converter adds. Check against the EBA taxonomy for the release you are filing.
Knowing the code is not the same as producing valid XBRL. The converter maps your data to the taxonomy, applies the code lists and validates before submission — with a free tier to start.
Create free account →Most of the work is in a few templates
Coded fields are not spread evenly. Knowing where they cluster tells you where the mapping effort actually goes.
Need no codes at all
FRTBCOREP, LRCOREP and NSFRCOREP among them. No coded selections are required, so there is nothing to map and nothing to get wrong. Confirming that is as useful as finding a code.
The heaviest single template
OFCOREP carries 14 reports with coded inputs, 40 coded fields, 27 distinct code lists and over 1,300 permitted values. If a mapping project runs late, this is usually where.
Dense for its size
11 reports with coded inputs, 41 coded fields and 21 code lists. The register of information is code-heavy relative to its footprint, which is why free-text entry causes so many rejections.
Shared across templates
The same code list is reused across modules, so a value learned once carries. The explorer shows which templates and reports each list is used in, which is how you find the rest of the places a mapping decision lands.
Reviewed 21 August 2026 · source: EBA Reporting Framework 4.2 workbooks and DPM glossary · Source: EBA Reporting Framework 4.2 template workbooks and DPM glossary export as supplied · compiled 19 August 2026
What this tool does
It doesResolve fields to values
- Lists every coded field in a template, with its report, column and column code.
- Shows the permitted values for the code list behind each field.
- Marks templates that require no coded selections, so you can stop looking.
- Searches across field labels, report codes and code list names at once.
- Runs entirely offline against an embedded copy of the data.
It does notValidate anything
- Apply the EBA validation rules. A valid code in the wrong context still fails.
- Tell you which templates your firm must submit. That is a scoping question.
- Cover releases other than 4.2 as supplied here.
- Show whether a code was withdrawn in a later release — the glossary export carries no end-of-life data.
- Produce a file. It is a reference, not a converter.
A correct code in the wrong place still gets rejected
Code lists constrain what a field will accept; the validation rules constrain what the combination of fields must add up to. This tool answers the first question completely and the second not at all. Passing here means the value exists in the taxonomy, not that the return will be accepted.
Nothing you search here leaves your browser
The dataset is embedded in the page and every lookup runs on your own machine. No query is sent to REGREP, and nothing is logged.
That is deliberate. Which templates you are mapping says a good deal about your firm.
About coded fields
Why do only 31 of 52 templates appear?
Because the other 21 require no coded selections. Every input is a monetary amount, a date, a count or free text, so there is no code list to consult. The explorer marks them rather than hiding them, since confirming that a template needs no codes is itself a useful answer during a mapping exercise.
What is the eba_ prefix?
The namespace prefix the taxonomy uses, as in eba_qAS:qx2004. Codes are shown here without it for readability; the converter adds it when producing XBRL. If you are hand-editing a file, the prefixed form is what belongs in the instance document.
Does a valid code mean the return will pass?
No. A code list governs what a single field will accept. The EBA validation rules govern the relationships between fields, and a value that is individually valid can still breach a rule about totals, consistency or applicability. This tool covers the first and not the second.
Why is the same code list used by several templates?
Because the DPM is dimensional: a concept such as accounting standard or currency is defined once and referenced wherever it is needed. That is helpful for consistency, and it means a mapping decision taken for one template usually applies to several. The explorer shows which templates and reports each list appears in.
Which release does this cover?
Framework 4.2, from the workbooks and glossary supplied for this build. Codes and lists change between releases, and the glossary export records when an item was introduced but never when it was withdrawn, so nothing here should be assumed to hold for an earlier or later release without checking the taxonomy for that release.
Do you store what I search for?
No. The data is embedded in the page and every lookup happens in your browser. Nothing is transmitted, logged or persisted.
Finding the code is the easy half of a mapping project.
Create a free account and take your data through mapping, code lists and validation into submission-ready XBRL.
No card required · free tier on core modules · nothing stored from this tool