About filings.xbrl.org

filings.xbrl.org is a repository of Inline XBRL filings. The repository currently contains filings that have been prepared under the following filing systems:

filings.xbrl.org was originally created in order to:

The repository has subsequently been expanded to cover other filing systems.

What information is available?

For each filing we provide:

What is it for?

All new regulatory filing arrangements take some time to settle in. The ESEF filing mandate represents a significant change for European public companies and PIEs and because of the federated structures involved in ESEF, there will undoubtedly need to be improvements made throughout the information supply chain.

XBRL International hopes that making this information more readily accessible will help ensure that these improvements will happen as quickly as possible, and in particular to help:

Why the focus on ESEF?

We expect that the ESEF mandate will be closely studied by other regulators around the world as corporate reporting (including ESG reporting) shifts to a digital-first approach.

Missing filings

Although we aim to include as many filings as possible, the repository is not complete.

In some cases, technical errors in a filing prevent us from providing the viewer and xBRL-JSON outputs. In other cases, the format of the filing is such that we cannot automatically determine the LEI and filing date to which it relates, and the filing will be excluded from the index altogether.


The filings database is also available via an API at https://filings.xbrl.org/api/filings. The API uses the JSON-API standard.

At present there is no documentation for the API, and it is subject to change without notice.


Some filings in this repository can be slow to open in a browser. This is typically because the Inline XBRL report has been created using automated PDF-to-HTML conversion software. Such software produces a document which faithfully reproduces the appearance of a PDF document, but the resulting HTML is often extremely inefficient, leading to large file sizes and slow rendering times.

We expect this to improve over time, as software improves, and preparers start to target the Inline XBRL format directly, rather than converting from PDF.

Index structure

The index is structured by company identifier (typically LEI), then reporting date, filing system and country. In some cases there are multiple reports within that structure. This is typically due to reports being provided in multiple languages, but it may also be due to the submission of amended reports. Where there are multiple reports, these are put into separate, numbered sub-directories. We do not attempt to capture the relationship between such sets of reports, as data collection authorities do not make this information available in a consistent manner.

Nothing should be inferred from the numbers assigned to the reports; they reflect the order in which they were added to the index, which may not match the order in which they were filed.


The language(s) shown for a filing is based on the tagging of any text facts within the report.

Report dates

The date shown for a filing is inferred from the facts tagged within the report.


We use hashes to uniquely identify reports with in the index. This allows us to detect where the same filing is submitted to multiple authorities, and cross-link them. It also allows us to reliably avoid adding duplicate filings.

We use a SHA-256 hash. We generally show the first eight hexadecimal digits of the hash, with the full 64-digit hash is available in a mouse-over.

"Added" date

The "added" column shows the date on which the filing was added to our index. Although we try to keep our index as up-to-date as possible, there may be a significant delay between a filing being submitted to the collection authority and it being added to our index.

Validation errors and warnings

Many of the filings in the index have validation errors and warnings.

Validation errors indicate that the report does not conform to the relevant XBRL specifications and as such cannot be expected to open reliably if at all in XBRL software. For now, we have chosen to include these filings where possible in order to assist with identifying and fixing the problems.

Validation warnings are generally a result of failing to comply with XBRL Formula Rules defined in the ESEF taxonomy.

Please note that for ESEF filings, beyond applying the XBRL Formula Rules defined in the ESEF taxonomy, we have not attempted to validate rules in the ESEF Reporting Manual, or any country-specific rules that may be applicable.


Filings are sourced from the relevant data collection authority. In the case of ESEF reports, this is the Officially Appointed Mechanism (OAM) for the country in which it was filed. See the Filing Sources for a list of the sources that we use.

Missing data

Unfortunately, there are a number of countries where ESEF filings are not made available in a way that allows us to reliably discover and download them, or where we have not been able to locate a source at all. These countries include:

If you can help us access data for these countries, please get in touch.

Mailing list

If you would like to stay informed of new developments in the repository, or would like to suggest and discuss potential new features, please join our filings.xbrl.org mailing list.


This service uses the Arelle Inline XBRL Viewer The xBRL-JSON outputs are provided by the Arelle XBRL processor. We are very grateful to Workiva for their support of these open source projects.

Terms of use

At present, there are no restrictions on the ways that the data can be used.


If you have any questions about the contents of this repository, please contact filings@xbrl.org.