FDTA and the SEC
Of all FDTA agencies, the SEC enters the implementation phase with the strongest structured data foundation. That does not mean public companies are ready. Here is what the waiting period requires.
Where the SEC Stands
Of all agencies covered by the FDTA, the SEC enters the implementation phase with the strongest foundation. In 2005 the Commission established a voluntary XBRL filing programme for corporate financial statements. Those voluntary programmes were made mandatory in 2009. In 2018, the Commission adopted rules requiring operating company financial information to be submitted in Inline XBRL, a format that is both human-readable and machine-readable. Since then, the mandate has expanded steadily: cover pages, cybersecurity disclosures, insider trading arrangements. Today, the SEC is arguably the most XBRL-advanced regulator among the nine FDTA agencies.
Being furthest along, though, is not the same as finished. The SEC still needs to align with the other eight agencies on a common reporting framework, which is the FDTA’s central purpose. Section 16 Forms 3, 4, and 5 are currently submitted via a web form and generated as XML. Converting them to full XBRL is a logical next step as implementation unfolds. The SEC may also turn its attention to strengthening the audit of machine-readable data already in the system, moving from producing structured data to actively assuring its quality. For public companies, that last point carries the most immediate weight.
2005 SEC voluntary XBRL programme launched for corporate financial statements | 2009 XBRL filing made mandatory for all operating company periodic reports | 2018 Inline XBRL adopted, single human-readable and machine-readable document | 43/55 Forms now requiring machine-readable data under relevant statutory provisions (June 2026) |
How Long Will the SEC’s Rule Actually Take
The FDTA final rule takes effect on October 1, 2026, but will not impact reporting requirements until it is applied by the agencies in the context of issuing or updating specific reporting requirements over the next two years. No agency-specific FDTA rulemaking has yet been proposed. The actual schedule will depend on each agency’s regulatory priorities, capacity, and the pace of stakeholder engagement.
Industry practitioners who have watched SEC rulemaking cycles for close to two decades will tell you that agency-specific rules of this complexity typically take two to four years from joint rule adoption to a proposed rule, and the timeline can still compress through pilot programmes, clarifications, and refinements. The formal compliance deadline and the operational reality are rarely the same date.
The most important observation is behavioral. Most finance teams wait for final guidelines before acting. That posture consistently produces worse outcomes. The companies that participate in consultations, respond to comment periods, and engage in pilot programmes are the ones that shape the questions, and therefore know the answers before the mandate lands. The waiting period is preparation time.
THE SEC IS ALREADY WATCHING
Under the FDTA, the Commission is required to submit a semi-annual report to Congress every 180 days through December 2029, covering how machine-readable data is being used internally and publicly. The June 2026 report confirms that the SEC’s Division of Enforcement used machine-readable data to bring charges against four public companies in October 2024 for cybersecurity disclosure violations, noting that the alleged violations would have been “significantly more difficult to detect” without structured data analysis.
SEC staff tools are actively comparing filings across periods, flagging custom tags, and generating comment letters to individual issuers on their XBRL tagging. The agency-specific FDTA implementation rule formalizes that scrutiny. It does not introduce it.
Why Your Current XBRL Quality Matters Now
The FDTA’s interoperability goal means regulators will eventually compare structured data submitted across agencies automatically. Before that happens, the SEC is already raising the quality bar through specific public observations.
The most persistent failure point in XBRL filings is custom extensions. Companies extend the standard taxonomy when no standard element fits a specific line item, which is legitimate. The problem is extensions used where a standard element already exists, inconsistent tagging of the same disclosure across reporting periods, and dimensions applied to the wrong axis. These appear in filings that passed EDGAR’s technical validation without any error.
TWO SPECIFIC AREAS THE SEC HAS FLAGGED PUBLICLY
1
NONINTEREST INCOME TAGGING ERRORS
The SEC’s Division of Economic and Risk Analysis completed an assessment of bank holding companies’ tagging practice for noninterest income in Forms 10-K. Staff observed inappropriate use of custom elements to tag noninterest income line items within the scope of Topic 606, where standard elements already exist, and inconsistent application of tags between line items on the income statement and identical items disclosed in the note.
2
CONSOLIDATED ENTITIES AXIS
DQC Rule 0245, currently under public review with comments due September 30, 2026, addresses the inappropriate use of the ConsolidatedEntitiesAxis in the statement section of a filing, a misapplication the committee considers widespread enough to warrant a dedicated rule.
DQC VERSION 30 EFFECTIVE SEPTEMBER 1, 2026
Version 30 was approved in June 2026. There are now 196 automated rules. The version 30 updates focus on accuracy, not on blocking filings. Areas targeted:
- Incorrect use of ScenarioAdjustmentMember for Accounting Standard Updates
- Inappropriate use of TransactionTypeAxis with market method members
- Capitalized Software Costs, Domestic Income Tax Items, and Segment Information tagging
- New IFRS rule on combined total concepts in the Statement of Operating Activities
The consistent direction across every DQC round: the gap between technically valid and substantively accurate is the target. In the environment the FDTA is building, that gap becomes visible to regulators, investors, and counterparties at the same time.
A filing that passes EDGAR validation is not the same as a filing that passes regulatory scrutiny. In a higher-scrutiny environment, that gap becomes visible.
Three Things to Do Right Now
1
Three Things to Do Right Now
Ask your reporting software provider to run a sample document under the applicable standards today. If they cannot show you a working output, that is an answer. If you have genuine doubt about their capability, begin assessing alternatives before a deadline forces the decision.
2
Map every agency you report to
Most CFOs do not have a single document listing every federal agency their organization reports to, every form that agency receives, and each agency’s FDTA implementation timeline. Build it. DataTracks can help you produce a company-specific version: forms, checklists, and timelines mapped to your actual filing obligations.
3
Review your XBRL for quality, not just technical validity
Filings prepared with legacy tools generally pass EDGAR validation. That is a lower bar than it appears. A quality review assesses the accuracy and consistency of tagging decisions across periods. What typically surfaces: unnecessary extensions, inappropriate elements or dimensions, and a fragmented reporting process with different vendors handling different forms and separate tools for HTML and XBRL preparation. That fragmentation is the operational risk the FDTA’s interoperability framework will make visible across agency lines.
What to Watch and How Rainbow Is Built for This
The SEC’s agency-specific FDTA rule has not been proposed yet. Specific milestones to track:
- The SEC’s rulemaking calendar for its agency-specific FDTA rule. The first proposed rule is the signal that the preparation window is closing.
- DQC updates beyond version 30. Version 31 is in public review, with comments on Consolidated Entities Axis and related rules due September 30, 2026.
- The SEC’s structured disclosure team quality observations published periodically. These flag where examiner attention is moving before a formal rule follows.
DataTracks Rainbow is built for multi-output regulatory environments. Under the UK’s Multi-Target Document framework, Rainbow already produces UKSEF tags for the Financial Conduct Authority and UK FRS tags for Companies House from a single workflow. When the SEC’s agency-specific FDTA rule arrives, Rainbow incorporates the new taxonomy and validation rules into that same workflow. Customers provide any newly required data and review the mappings. They do not adopt a new process.
SINGLE-SOURCE, MULTI-OUTPUT
Rainbow prepares and maintains common content once, applying different sections, taxonomies and tags for each regulatory output. No duplicate data entry, no reconciliation risk between parallel processes.
DQC VALIDATION BUILT IN
Rainbow validates against XBRL US DQC rules including version 30, surfacing accuracy issues before submission, not after EDGAR returns a comment letter.
COLLABORATIVE REVIEW WORKFLOW
Multiple users across finance, compliance, and legal review and approve within Rainbow. No version-control issues from spreadsheet handoffs between teams.
TAXONOMY AUTO-UPDATES
When the SEC publishes updated taxonomies or validation rules as part of its FDTA implementation, Rainbow incorporates them automatically. Customers do not install updates manually.
KEY TAKEAWAYS
✓ The FDTA joint rule is effective October 1, 2026. The SEC’s agency-specific implementation rule has not yet been proposed.
✓ The SEC is already using machine-readable data to identify enforcement targets, compare filings across periods, and issue comment letters on XBRL tagging quality.
✓ 43 of 55 forms under relevant statutory provisions now require machine-readable data. The remaining 12 are the FDTA implementation phase’s primary target.
✓ The most common XBRL quality problems are custom extensions used where standard elements exist, and inconsistent tagging of the same disclosure across reporting periods.
✓ DQC Version 30, effective September 1, 2026, adds 196 automated accuracy rules covering ASU tagging, capitalized software, segment information, and IFRS 18.
✓ Rainbow is already built for multi-output regulatory environments and incorporates new taxonomies and validation rules without requiring customers to change their process.
Ready to review your XBRL quality before the SEC’s scrutiny increases?
DataTracks Rainbow is built for the multi-output, higher-scrutiny regulatory environment the FDTA is building. Talk to a compliance specialist about your current filing quality and FDTA readiness.
