Get a demo Create free account →
Documentation · EBA reporting

EBA XBRL Converter.

Turning an Excel return into a validated XBRL-CSV package, and understanding what the validation is telling you.

Manual Regulatory Reporting → EBA XBRL Converter · Version 2.0 · 2 screenshots REGREP · Issued January 2026
NoteThis guide assumes you know how to sign in, navigate the Solutions menu, complete Settings and work with sessions. Those are covered in the Getting Started guide and are not repeated here.

What this module does

Regulators want XBRL. Firms work in Excel. This module bridges the two: you upload a completed EBA reporting template as a spreadsheet, and it validates the contents and produces an XBRL-CSV package for submission.

It supports all 51 EBA reporting templates up to framework version 4.2, and works with templates downloaded from the built-in library or taken directly from the EBA website.

Solutions → Regulatory Reporting → EBA XBRL Converter.

Getting the right template

The converter
Figure 1 — The converter.
  1. 1Configuration — the parameters describing your file.
  2. 2Upload and conversion.
  3. 3The template library, with the framework version of each and a download icon.
ImportantThe template version you select in Configuration must match the version of the file you are uploading. A v4.0 file converted as v4.2 will fail validation in ways that are difficult to diagnose, because the errors will point at the data rather than at the mismatch.

Download a template from the library, or use one from the EBA. Either works, provided the structure matches what you tell the converter it is.

Configuration

FieldWhat to set
TemplateThe EBA template your file corresponds to.
Template VersionThe framework version of the file. Confirm which version your competent authority requires for the reporting period.
Level ScopeSolo or Consolidated.
Reporting CurrencyThe currency the return is denominated in.
Reporting DateThe reference date of the return.
Base LanguageThe language of the output.
Base CurrencyThe primary currency used in the output.

Advanced configuration

Advanced Configuration holds two groups of settings. The decimal settings control number formatting; the export settings change what the converter is willing to produce.

Advanced Configuration
Figure 2 — Advanced Configuration.
  1. 1Parameter.csv settings — decimal precision by value type.
  2. 2Export settings.
  3. 3Bypass Errors — see section 5 before using this.
SettingWhat it does
Decimals IntegerPrecision for whole numbers such as counts and units — normally 0.
Decimals MonetaryPrecision for currency amounts — normally 2.
Decimals PercentagePrecision for rates and ratios.
Decimals DecimalPrecision for general decimal values that are neither currency nor percentages.
Add 0 in exported CSVFills blank fields with zero, so the output has a complete data structure.
Export columns as ""Wraps values in double quotation marks, keeping the file readable across regional settings.
Bypass ErrorsGenerates a package despite hard validation failures. See section 5.
NoteThese selections are written into the Parameter.csv file inside the package, so they form part of what you submit.

Uploading and reading the validation

Upload the completed template in .xlsx format and select START CONVERSION. The converter runs a dual-layer check — the Excel parameters, and the JSON schema behind the framework — and reports what it found in three tiers.

TierWhat it meansWhat to do
Info — field entitlementValues were found in cells outside the template's designated input fields. The data is not necessarily wrong, but it is somewhere the template does not expect it.Check whether working notes or stray values have been left in the sheet, and clear them.
Warning — non-critical inconsistencyData that looks inconsistent but does not breach a hard constraint of the framework or the schema.Review each one. A warning you understand and accept is fine; a warning you cannot explain usually indicates a real problem.
Error — hard validation gateThe data contradicts EBA guidelines or fails schema validation. The converter treats the file as non-compliant and will not generate a package.Fix the data. This is the tier that stops submission of an invalid return.

Download the CSV notification file for the full list with the specific reason for each item.

Bypass Errors

Important

Bypass Errors disables the hard validation gate. With it enabled, the converter produces a package from data that has failed EBA or schema validation — data it has already assessed as non-compliant.

The gate exists to stop an invalid return reaching a regulator. Turning it off removes that protection, and the resulting file carries no marking to say it was produced this way.

When it is legitimate

  • Producing a file for internal testing or for a system integration test, where it will never be submitted.

  • Reproducing a specific failure for REGREP support.

  • A case where you have established with your competent authority that the validation rule is wrong or does not apply, and they have agreed to receive the file.

If you use it

  1. Establish first that the error is genuinely not a data problem. Assume it is until you have shown otherwise.

  2. Get the decision approved by someone senior enough to answer for it, and record the approval.

  3. Save the CSV error log alongside the generated package as evidence of exactly what was overridden.

  4. Mark the file clearly in your own records as error-bypassed. The file itself does not say so.

  5. Turn the setting off again immediately.

NoteAccess to this module — and therefore to this setting — is granted through Team Management → Access Management. It is worth reviewing who holds it. See the Administration guide.

Producing the package

Once validation is clear — or the bypass has been consciously applied — the conversion completes and the package downloads automatically. If the download does not start, a manual download option remains on screen.

  1. Confirm the template and version match your file.

  2. Set the scope, currency, reporting date and language.

  3. Set the decimal precision your authority expects.

  4. Upload the file and start the conversion.

  5. Review every Info, Warning and Error item; download the CSV log.

  6. Correct the source spreadsheet and re-run until the errors are resolved.

  7. Download the package and file it through your authority's portal.

  8. Keep the source spreadsheet, the CSV validation log and the package together — that set is your evidence of what was submitted and that it validated.

Troubleshooting

SymptomLikely cause and fix
Errors across the whole fileUsually a template or version mismatch rather than bad data. Check both before investigating individual cells.
Info items on an apparently clean sheetValues in unentitled cells — often working notes, totals added by hand, or leftover content in hidden rows.
Numbers appear with the wrong precisionCheck the decimal settings in Advanced Configuration; they are written into the package.
The file will not uploadOnly .xlsx is accepted. Re-save from Excel if the file came from another tool.
The download does not startUse the manual download option on screen.
The authority rejects a package that validated hereCheck the framework version against what they require for the period, and the reporting date and scope.

Document control

VersionDateChange
2.0January 2026Rewritten and brought up to date — the previous version was flagged in the manual index as needing revision. Navigation moves to the Getting Started guide. Documents the Configuration panel and the template library as they now appear, the Advanced Configuration decimal and export settings, and the three validation tiers as a decision table. Adds a full section on Bypass Errors covering when its use is legitimate, the approval and evidence it warrants, and the fact that the generated file carries no marking. Adds a production workflow and troubleshooting.
1.0—Original XBRL manual, marked in the index as requiring update.

REGREP is an independent software provider. This manual describes how to operate the platform and is not legal, tax or regulatory advice. Confirm scope, thresholds and submission dates with your competent authority before you file.

Other guides

The rest of the documentation set.

All documentation →