DEVELOPMENT US GAAP Financial Reporting
Taxonomy

Public Review and Comment

The Development US GAAP Financial Reporting Taxonomy (Development Taxonomy) is the FASB’s day-to-day working taxonomy and includes proposed changes since the last annual release.

We encourage all interested parties to review and comment on the ‘Development Taxonomy’. To encourage feedback, the FASB Taxonomy Online Review and Comment System (TORCS) is operational throughout the year. All comments are tracked and reviewed for potential inclusion in a subsequent taxonomy release. All comments are acknowledged when received but it is not possible to respond directly to individual comments. We have included guidance for using the taxonomy viewer/commenting tool.
 

Guidelines for Providing Comments

Individuals providing comments on the taxonomies are required to register with a “user name” and email address. Please note that all comments will be visible to other registered users. In order to process comments, commentators should (1) describe the issue clearly, (2) provide examples and/or frequency of occurrence, and (3) provide a recommendation.

Please note: Individuals submitting more than 10 comments related to the same issue should not use this system as it delays the processing of the comments. Individuals who wish to provide more than 10 comments related to the same issue should send them directly to xbrlweb@fasb.org.

Changes in the Development Taxonomy are identified by a Change Note (CN). The CN identifies the year-month of the change in the Change Date part (cn-part:ChangeDate). For example, “2017-05,” refers to a change made in May 2017 and identifies the nature of the change with the following (parts have added spaces in this document to assist in readability):
  • Taxonomy Version: identifies in which version of the Taxonomy the change was made.
  • Change Date: identifies the year and month the change was made in the Taxonomy.
  • Modified References: identifies by value of true that the change applies to a reference.
  • Modified Labels: identifies whether the change applies to a Standard, Period Start, Period End, or Total label.
  • Source: identifies whether a change note is based on an ASU, topical project, or other sources.
  • Source Name: identifies which ASU or TIG an element is related.
  • Source ASU Number: identifies the number of the ASU on which the change is based.
  • New Element: identifies by value of true that the change is because of the addition of an element.
  • Modified Documentation: identifies by value of true that the change applies to a documentation label (definition).
  • Previous Documentation: identifies the previous documentation label when the change applies to a documentation label (definition).
  • Deprecated Date: identifies the date when the element is deprecated.
  • Deprecated Label: identifies the reason for the deprecation and possible replacement elements, if applicable.
  • Element Deprecated: identifies by value of true that the change applies to deprecation of an element.
  • Modified Deprecated Label: identifies by value of true that the change applies to a change in a deprecation label.
  • Modified Balance Type: identifies by value of true that the change applies to a balance type
“Shared Searches” are included to facilitate discovery of the changes. After applying the “Shared Search” and selecting “Highlight Matches” from the status bar at the bottom of the screen, the filter highlights the networks containing changes with pale yellow. Each element that has been modified or added will be highlighted with bright yellow. All items meeting the filter criteria will be listed in the search pane.

The Development Taxonomy includes all proposed changes since the last annual release except for certain proposed ASU changes, which are managed separately as ASU Taxonomy Changes. See ASU Taxonomy Changes Page. ASU Taxonomy Changes are merged into the Development Taxonomy at the later of a completed public review period or the anticipated annual taxonomy release that covers the ASU effective date. Periodic release notes will be provided for the Development Taxonomy as a “snapshot” of changes since the last periodic release notes.


THE TAXONOMIES AND SUPPORTING MATERIALS PROVIDED THROUGH THESE LINKS ARE FOR REVIEW PURPOSES ONLY AND ARE NOT TO BE USED OR RELIED UPON FOR ANY PURPOSES OTHER THAN FOR THIS REVIEW AND COMMENT. YOUR USE OF THE TAXONOMIES FOR THESE PURPOSES SHALL BE SUBJECT TO THE TERMS AND CONDITIONS LOCATED AT THE INITIAL LINK TO THE TAXONOMIES.
 

Taxonomy (XBRL)

What's New—XBRL

SEC Announces EDGAR System Upgrade: 2017 GAAP Taxonomy No Longer Supported (June 12, 2019)
FASB Adds Taxonomy Entry Points to Address FAST Act Updates in the 2019 DEI Taxonomy (June 11, 2019)
FASB Staff Issues Proposed Taxonomy Improvements for a Proposed Accounting Standards Update on Codification Amendments in Response to the SEC's Disclosure Update and Simplification Initiative and for a Proposed Accounting Standards Update Simplifying the Accounting for Income Taxes (Topic 740) (May 23, 2019)
FASB Staff Issues Proposed Taxonomy Improvements for a Proposed Accounting Standards Update (Revised), Income Taxes (Topic 740): Disclosure Framework—Changes to the Disclosure Requirement for Income Taxes, for Comment and Incorporates Taxonomy Improvements for Final Accounting Standards into the Development Taxonomy (April 30, 2019)
SEC Accepts 2019 GAAP Financial Reporting Taxonomy and SEC Reporting Taxonomy (March 12, 2019)
FASB Staff Issues Update to Frequently Asked Questions about the U.S. GAAP Financial Reporting Taxonomy and a Final Taxonomy Implementation Guide on Financial Instruments—Debt Securities (March 6, 2019)
FASB Staff Issues Proposed Taxonomy Improvements for a Proposed Accounting Standards Update on Targeted Tranisition Relief for Topic 326, Financial Instruments—Credit Losses and a Proposed Accounting Standards Update on Business Combinations (Topic 805): Revenue from Contracts with Customers—Recognizing an Assumed Liability (February 14, 2019)
Video: The XBRL Data User Perspective
Video: The GAAP Taxonomy: Why It’s Important