What a report package is
A filing is rarely one file. An xBRL-CSV return is a folder of CSV tables and JSON. An Inline XBRL annual report can come with images and style sheets. Before 2023 each regulator described its own zip layout, so software had to be told where to look.
Report Package 1.0 fixes that. In XBRL International’s words it is “a single container for XBRL reports to reside in”, which lets compliant tools “identify, process and present enclosed reports automatically”.
An example: inside an EBA leverage ratio return
Open the EBA’s public sample for the COREP leverage ratio module and you find the layout the standard describes, with the EBA’s own naming on top.
- The one top-level folder
- DUMMYLEI123456789012.CON_FR_COREP040100_COREPLR_2026-12-31_20260108131530603: the firm, country, framework and version, module, reference date and creation time
- META-INF/reportPackage.json
- One line that matters: documentType https://xbrl.org/report-package/2023, the plain zip kind used for CSV
- reports/report.json
- Says this is xBRL-CSV and which EBA module it follows (corep_lr.json in framework 4.2)
- reports/parameters.csv and FilingIndicators.csv
- Who is reporting (entity rs:DUMMYLEI123456789012.CON), the reference date, euro, precision, and which templates are filed
- The rest of reports/
- 10 CSV tables, one per template, such as c_47.00.csv
This zip follows Report Package 1.0, so the report is in reports/, and report.json there says how to read it. No guessing, no EBA-only unpacking code.
What the package label saysShowHide
{ "documentInfo": { "documentType": "https://xbrl.org/report-package/2023" } }From the EBA’s public sample package, as served by Line4 Check. The figures are dummy values.
.xbri, .xbr or .zip: the three kinds
The file extension tells software, and people, what is inside before anything is opened. The extensions .xbr and .xbri MUST be lowercase.
Who uses report packages
The EBA moved its xBRL-CSV package onto the standard in version 5.4 of its filing rules (June 2024), and its rules v5.9 say the package “respects the Report Package 1.0”, with a reportPackage.json of fixed content. Every EBA report with a reference date from 31 March 2026 must be xBRL-CSV, so every EBA return now travels as a report package.
ESMA’s ESEF Reporting Manual (October 2025) recommends that issuers prepare annual financial reports as Report Package 1.0 (guidance 2.6.1) and name them {base}-{date}-{version}-{lang}.xbri (guidance 2.6.3), with .zip still accepted and national rules taking precedence. ESMA also proposed in May 2024 to replace the ESEF rules’ reference to taxonomy packages with one to report packages.
What it means for supervisors
A report package is the first thing a collection platform checks and the cheapest to get right. Is it a zip? Is there one top-level folder, named as the rules say? Does reportPackage.json declare the right kind? Is there a reports folder with exactly one report in it? Each answer should come back to the firm on arrival, in plain words, before any taxonomy is loaded.
If you write your own submission rules, point to Report Package 1.0 rather than describing a zip layout of your own. Software built for EBA and ESEF filing already produces it, and you can then accept XBRL-XML, Inline XBRL and xBRL-CSV through one front door.
Where AI fits, and where people decide
Package errors are dull, and they stop a filing before a single number is read. AI can read a rejected zip, see that the folder was renamed or the reports folder is missing, and tell the firm exactly what to change.
Whether a package is valid is still a fixed check against the specification and your filing rules. The same zip gets the same answer every time, and the answer is kept with the filing.
- 1Do your filing rules point to Report Package 1.0, or describe a zip layout of your own?
- 2Which kinds do you accept: .xbri, .xbr, .zip, or all three?
- 3Is the top-level folder name rule written down, with an example?
- 4Do package errors reach the firm in plain words on arrival, before validation?
- 5Count last cycle’s rejections that were package errors, not data errors.
Where Line4 fits
Line4 is SupTech software for financial regulators. It collects returns in XBRL, Excel and CSV by portal, API or MCP, validates them against your taxonomies and rules at the point of submission (see XBRL software for regulators), and puts AI to work reading them, with supervisors making every decision. If you work with a standard we have not yet run in production, we will say so plainly and show you how we would approach it.
Questions
What is an XBRL report package?
A zip file holding one or more XBRL, Inline XBRL, xBRL-CSV or xBRL-JSON reports in a standard layout: a single top-level folder, a reports folder, and a META-INF/reportPackage.json saying which kind of package it is. It is defined by XBRL International’s Report Package 1.0, a Recommendation since 22 September 2023.
What is the difference between .xbri, .xbr and .zip?
An .xbri package holds one Inline XBRL report, an .xbr package holds one XBRL-XML report, and a .zip package is unconstrained: it is the one used for xBRL-CSV and xBRL-JSON, and for more than one report. The kind is also declared in reportPackage.json as a documentType.
Is reportPackage.json required?
Under Report Package 1.0 it is a SHOULD, not a MUST: a package should include it. The EBA’s filing rules go further and say the META-INF folder contains one reportPackage.json with fixed content.
Does the EBA use report packages?
Yes. Since version 5.4 of its filing rules (June 2024) the EBA’s xBRL-CSV package follows Report Package 1.0. The zip is named ReportSubject_Country_FrameworkCodeModuleVersion_Module_ReferenceDate_CreationTimestamp.zip and its one root folder has the same name. From the 31 March 2026 reference date every EBA report must be xBRL-CSV.
Does ESEF require report packages?
ESMA’s ESEF Reporting Manual (October 2025) recommends Report Package 1.0 and the .xbri file name pattern {base}-{date}-{version}-{lang}.xbri. .zip files are still accepted, and the naming rules of national authorities take precedence.
What is the difference between a report package and a taxonomy package?
A taxonomy package carries a taxonomy, with its entry points and a catalog, so software can load it offline. A report package carries a filing. A report package may also be a valid taxonomy package, which is how an Inline XBRL report can travel with its own extension taxonomy.
Can Line4 Check read report packages?
Yes. Line4 Check reads EBA xBRL-CSV report packages (.zip) and XBRL-XML instances in the browser, finds the module from report.json, and runs the EBA’s filing rules and validation rules without uploading the file.
Are report packages used outside Europe?
Not that we could find. In the US, the SEC’s EDGAR system takes Inline XBRL as separate files attached to the submission: a filer needs only one Inline XBRL document, and since the 2018 rule change a submission can carry more than one. The EDGAR XBRL Guide (November 2026) and EDGAR Filer Manual Volume II (September 2026) do not mention report packages or .xbri files. Line4 Check reads both shapes: a packaged EBA xBRL-CSV .zip and a single XBRL instance.
- XBRL International: Report Package 1.0 (Recommendation, 22 September 2023, errata to 11 March 2025)
- XBRL International: Report Packages specification finalised (30 September 2023)
- EBA: XBRL Filing Rules v5.9 (26 June 2026)
- EBA: hotfix for reporting framework 4.1, xBRL-CSV from March 2026 (4 July 2025)
- SEC: Inline XBRL (last reviewed 17 January 2025)
- SEC: EDGAR XBRL Guide (November 2026)
- SEC: EDGAR Filer Manual Volume II, chapter 6 (September 2026)
- EBA: Reporting framework 4.2
- ESMA: ESEF Reporting Manual (October 2025)
