The XBRL US Database contains 10+ years of as-reported data from public companies reporting to the Securities and Exchange Commission (SEC), and utilities reporting to the Federal Energy Regulatory Commission (FERC). All data is continuously updated directly from the regulator. XBRL data from other reporting domains will be added soon.
Power User, Sole Practitioner and all Organizational XBRL US Members* can use this resource with:
- the XBRL API in any programming language or with free tools and templates,
- direct access with SQL (also available here)
- or with snapshots posted to a qualified AWS account.
This Postgres resource mirrors the structure of the XBRL Standard so that an XBRL instance document and associated schema can be loaded and stored. This structure makes it very flexible for use in any XBRL data collection environment.
Reported data, full XBRL reports (instances), and associated schema are recorded in the database, along with document name, filing date, and submission-related data (such as whether it’s a restatement). Data reported in any XBRL format (iXBRL, JSON, CSV or XML) can be stored in the database. Additional metadata is included to streamline and improve the efficiency of your own data management.
*Power Users and the primary contact of any organizational member can get credentials for SQL access.
All XBRL data in the instance, the associated schema, and information about the XBRL documents (name, filing date, whether it’s a restatement and other submission-related detail) is recorded in the database.
In addition the following factual data is added to the database:
Fact Hash: Every fact reported in an XBRL format is assigned an identifier. The identifier or hash is based on the context of the fact. Facts with identical contexts will have the same hash. The hash does not include the value of the fact, so restated facts will have the same hash. This hash makes it possible to identify where the same information has been reported across multiple reports.
Ultimus Index: This is a number sequence associated with each fact. This sequence indicates when the fact was reported relative to the same fact in other reports. A value of 1 for example means that this is the latest fact reported. If the value was 2 it means the same fact has been reported in a more current report. In theory the fact value should be the same but can be different due to changes across reports, such as a restatement.
Fiscal and Calendar Year: This is the Fiscal or Calendar year when a fact was reported in the format YYYY. This data is calculated by looking at the date associated with the fact data and the financial period end for the reporting entity. Every fact is assigned a fiscal year and a calendar year. A fact reported with a date of 2017-12-31 with a period end of 09-30 will have a fiscal year of 2018 and a calendar year of 2017.
Fiscal and Calendar Period: This is the fiscal or Calendar period when a fact was reported. These can be in the format 1Q, 2Q, 3Q, 4Q, Y, 3QCUM, 1H, 2H. This data is calculated by looking at the date associated with the fact data and the financial period end for the reporting entity. Most facts are assigned a fiscal period and a calendar period. Facts with durations that do not fit into the assigned period types (such s 3 years) are not assigned a period type. A quarterly fact reported with an end date of 2017-06-30 with a period end of 2017-06-30 will have a fiscal period of 4Q and a calendar period of 2Q.