HOW TO USE THIS GUIDE
This is a living guide, updated as each agency publishes its FDTA implementation rules. Bookmark it.
The CFO’s Complete Guide to the Financial Data Transparency Act (FDTA): What It Is, What It Requires, and What Comes Next
The FDTA has moved from legislation to implementation. Nine federal agencies have adopted a joint final rule, and for CFOs and compliance leaders, the implications depend on what each agency brings within scope next.
The Financial Data Transparency Act (FDTA) has moved from legislation to implementation. Nine federal agencies have adopted a joint final rule establishing common identifiers and principles intended to make certain financial regulatory data machine-readable, consistently defined and more interoperable across agencies. The joint rule establishes a foundation rather than immediate filing requirements. The formats and standards applicable to information collections will be determined through subsequent agency-specific rulemaking or other agency action.
For CFOs and compliance leaders, the implications will depend on which information collections each agency brings within scope and how the standards are applied. Public companies, banks, credit unions, housing-finance entities, consumer-finance firms, derivatives-market participants and municipal issuers could be affected in different ways. This guide explains what the joint rule establishes, what remains undecided, and how organizations can prepare without moving ahead of the regulations.
At first glance, the FDTA may look like a minor technical update: a joint rulemaking, a set of common data standards, and an acronym most finance professionals have not yet had to act on. But that view misses the real story.
This guide explains the full picture: where the FDTA came from, what the joint final rule requires, what it means for each type of regulated company, and what CFOs and compliance leaders need to do as the agency-specific implementation phase begins. This blog will be updated as each agency publishes its own implementation rules. Make sure to bookmark it.
What Is the FDTA and Why Did It Happen
The Financial Data Transparency Act was enacted on December 23, 2022, as Title LVIII of the James M. Inhofe National Defense Authorization Act for Fiscal Year 2023. It directed the covered agencies to jointly establish data standards for certain collections of financial regulatory information.
THE CORE PROBLEM: FRAGMENTATION
The SEC has EDGAR. The FDIC has its call report system. The FHFA has its own formats. Each agency evolved its reporting requirements independently, and the result is that the same organization reporting to multiple regulators is doing the same job multiple times, in multiple languages, to incompatible systems. The data that arrived at each agency could not be compared with data at any other.
This was more than an efficiency problem. When each agency collected data in a different format, regulators and investors could not easily connect the dots across the financial system. The 2008 crisis showed why that missing cross-agency view mattered.
The trigger that made Congress act was a convergence of pressures: the post-pandemic explosion of digital financial services, the acceleration of AI-driven investment analysis that required clean machine-readable data, and the growing recognition, crystallized in GAO reports and Congressional testimony, that the U.S. was falling behind countries like the Netherlands, the Nordic nations, and Australia that had already implemented unified government-to-business data standards.
The FDTA’s mandate was direct: common data standards, applicable across agencies, making financial regulatory data interoperable, machine-readable, and comparable. Congress required the agencies to publish proposed joint standards within 18 months of enactment and final standards within two years. The CFTC was not one of the agencies originally specified in the Act. The Treasury designated it as an additional covered agency on May 3, 2024, bringing the number of agencies participating in the joint rulemaking to nine.
How It Evolved: From Concept to Final Rule
2008–2020 | The Fragmentation Problem Becomes Undeniable The financial crisis of 2008 exposed what regulators could not see because data could not flow across agency lines. The Dodd-Frank Act created the Office of Financial Research to try to synthesize cross-agency financial intelligence, but the OFR could not solve a data architecture problem that predated it and sat upstream of everything it received. Meanwhile, XBRL is quietly being mandated by one agency at a time, and the story starts earlier than most finance professionals realize. Bank Call Reports were the first major US implementation: the FFIEC Central Data Repository began accepting XBRL-tagged data from banks in 2005, four years before the SEC required it for public company filings in 2009. FERC followed with electric utility filings in 2021. But these were parallel mandates built on parallel tracks, no shared taxonomy, no interoperability, no mechanism for data to flow between them. That structural disconnect is precisely what the FDTA was designed to fix. |
2022 | Congress Establishes the Framework The FDTA established a coordinated process for developing data standards across federal financial agencies covered in the Act. It specified properties that should be satisfied such as machine-readability, consistent semantic definitions, open licensing and interoperability, while leaving the agencies to determine the appropriate identifiers, classifiers and reporting formats. |
2023–2024 | Consultation and Proposed Rule Beginning in March 2023, the agencies consulted other federal bodies, data-standard organizations and public stakeholders. On August 22, 2024, the agencies published a joint Notice of Proposed Rulemaking and invited public comment on the proposed standards. Respondents expressed different views on common identifiers, reporting formats, implementation costs, and the flexibility agencies should retain. XBRL US argued that XBRL provided the semantic framework needed to satisfy the FDTA’s objectives, while other participants recommended alternative standards or a technology-neutral approach. |
2025–2026 | Review and Finalization The agencies reviewed the public comments and continued meeting with stakeholders before completing the rule. The SEC issued its final-rule release on May 21, 2026, and the joint final rule was published in the Federal Register on June 25, 2026. It becomes effective on October 1, 2026, but does not change any existing reporting requirements without further agency action. The FDTA’s first phase is complete. Now the implementation phase begins. |
Now | Agency-Specific Implementation Begins The joint-rule phase involved seven agencies such as the OCC, Federal Reserve Board, FDIC, NCUA, CFPB, FHFA, and SEC, with a discretionary power to CFTC and Treasury to implement joint-rules. The FDTA specifically requires implementing agencies except CFTC and Treasury to adopt applicable data standards for certain information collections through agency-specific rulemaking. The CFTC and Treasury are not statutorily required to issue comparable implementation rules, although they may adopt the joint standards for their collections at their discretion. Each implementing agency will determine which information collections are affected and how the joint standards should be applied, taking account of feasibility, implementation burden and the need to minimize disruption. The standards adopted through the required agency-specific rules must take effect no later than two years after promulgation of the joint final rule, although the detailed requirements and collection-specific compliance dates remain to be determined. |
What the Joint Rule Actually Requires
Pillar Two taxation sounds intimidating. GloBE Information Returns, QDMTT calculations, jurisdiction-specific XML schemas, OECD Pillar Two model rules applied differently in every filing jurisdiction. None of that complexity lands on your team. Here is exactly what the process looks like from your side.
1
COMMON IDENTIFIERS
First, the rule establishes common identifiers and classifiers to be used where applicable — the building blocks that ensure different agencies label the same entity consistently.
2
DATA FORMAT PRINCIPLES
Second, it establishes principles for data-transmission and schema-and-taxonomy formats. The rule remains technology neutral. It does not mandate XBRL, although agencies may select XBRL where appropriate.
3
IMPLEMENTATION PHASE
Third, it initiates the agency-specific implementation phase. Seven implementing agencies will determine which information collections are covered and how the applicable standards will be introduced.
The Seven Common Identifiers Established by the Rule
ISO 17442
Legal Entity Identifier (LEI)
ISO 4914
Unique Product Identifier (UPI)
ISO 10962
Classification of Financial Instruments (CFI)
ISO 8601
Date formats
USPS Standards
US state and postal abbreviations
GENC
Geopolitical Entities, Names, and Codes
ISO 4217
Currency codes
WHAT THIS MEANS PRACTICALLY
No organization needs to change its filings because of the joint rule alone. But every organization reporting to one or more of these agencies needs to assess whether its current reporting infrastructure can absorb the transition, and begin that assessment now, before individual agency deadlines arrive with limited lead time.
What It Means for Your Organization Type
Public Companies Filing with the SEC
Public companies are already familiar with structured data mandates. The SEC adopted Inline XBRL (iXBRL) requirements in 2018, with phased compliance beginning in 2019 depending on filer type. The FDTA joint rule does not change current SEC filing requirements. The SEC must undertake agency-specific implementation to determine which additional information collections are covered, and which applicable data standards or formats will be used. Public companies should nevertheless expect continued attention to the consistency and usability of their structured data. An important consideration is data quality. The XBRL US Data Quality Committee approved version 30 of its validation rules in June 2026. Although DQC rules are industry-developed validation checks rather than SEC or FDTA requirements, they can help identify tagging errors and inconsistencies. Organizations should therefore look beyond minimum technical compliance and assess whether their XBRL tagging supports accurate interpretation and comparison as structured-data practices continue to evolve.
Banks and Financial Institutions Filing with the OCC, Federal Reserve, FDIC, and NCUA
Banks are not starting from an unstructured-reporting environment. The FFIEC’s Central Data Repository, introduced in 2005, uses XBRL-based taxonomies and data exchange for Call Report information. This predates the SEC’s mandatory XBRL phase-in, although individual banks generally submit their data through regulatory reporting software rather than preparing XBRL filings directly. Under the FDTA, the OCC, Federal Reserve Board and FDIC must determine how the joint standards apply to covered information collections. The NCUA will separately determine how the standards apply to covered credit-union information collections. Future rules could increase consistency in identifiers, definitions, metadata, and reporting formats across banking regulators. However, the affected collections and technical requirements will not be known until the agencies complete their implementation processes. Banks should therefore assess their regulatory data governance and the consistency of information supplied across different reports, but they should not assume that the FDTA requires an immediate replacement of their current Call Report systems.
Related Structured Reporting Context: Utilities and Energy Companies Filing with FERC
The Federal Energy Regulatory Commission is not one of the agencies covered by the FDTA, and its structured data requirements arise from separate legislation and FERC rulemaking. Utilities should therefore not treat their existing FERC filing obligations as FDTA requirements. FERC’s use of XBRL-based electronic forms is nevertheless a useful example of structured regulatory reporting. Companies filing with both FERC and an FDTA implementing agency may be able to reuse aspects of their data-governance, validation and reporting processes. However, the two regulatory frameworks remain legally and technically separate.
Mortgage Lenders and Housing Finance Companies Filing with the FHFA
The FHFA is one of the seven agencies required to implement the FDTA standards. Its direct regulatory population includes Fannie Mae, Freddie Mac, the Federal Home Loan Banks, and the Federal Home Loan Banks’ Office of Finance. The FHFA will determine through its implementation process which information collections are covered and how the applicable data standards will be applied. Mortgage lenders, servicers, and other counterparties are not automatically subject to the FDTA merely because they provide information to an FHFA-regulated entity. They could experience indirect effects if Fannie Mae, Freddie Mac or the Federal Home Loan Banks subsequently revise their data requirements, but those effects are not mandated by the joint rule and should not be presented as certain.
Derivatives Traders Filing with the CFTC and SEC
The joint rule adopts the Unique Product Identifier under ISO 4914 as the common identifier for swaps and security-based swaps where applicable. However, the rule does not itself change existing derivatives-reporting obligations or require firms to submit new information. The CFTC participated in developing the joint standards after being designated by the Treasury in 2024. Unlike the seven statutory implementing agencies, however, the CFTC is not required to issue an agency-specific FDTA implementation rule. It may choose to apply the standards to its information collections at its discretion. The SEC is a required implementing agency and regulates security-based swaps. Any effect on SEC-regulated security-based-swap reporting will depend on subsequent SEC action. Derivatives-market participants should therefore monitor the relevant regulator rather than assume that the joint rule has already changed their reporting requirements.
Consumer Finance Companies Filing with the CFPB
The CFPB is one of the seven agencies required to implement the FDTA standards. Its future rulemaking will determine which information collections are covered, which entities are affected and how the applicable standards will be introduced. The joint rule does not alter the confidentiality or public-disclosure status of information collected by the CFPB. Banks and nonbank financial companies subject to CFPB reporting should inventory their recurring submissions and monitor the Bureau’s implementation activity. However, system changes should be based on collection-specific requirements once proposed, rather than an assumption that every CFPB data collection will be standardized in the same way.
Municipal-Securities Market Participants
The Municipal Securities Rulemaking Board is not one of the nine agencies that participated in the FDTA in joint rulemaking. It is a self-regulatory organization overseen by the SEC, and the FDTA directs the SEC to establish data standards for information submitted to the MSRB. The joint rule does not change the EMMA submission requirements. The affected submissions, technical formats, and implementation dates will depend on subsequent SEC and MSRB action. Municipal issuers, obligated persons, broker-dealers, and municipal advisors should monitor both SEC and MSRB developments. Until specific requirements are adopted, existing disclosure and submission obligations remain unchanged.
The CFO’s New Mandate
The FDTA final rule is, at its deepest level, a statement about what financial data is for. It is not a record of what happened. It is structured intelligence, machine-readable, comparable, and actionable, something that regulators, investors, and counterparties will use to evaluate your company automatically and continuously.
That reframes what a CFO is responsible for in ways that most finance leaders have not yet fully absorbed.
The Evolution of the CFO Role
Ten years ago, the CFO’s mandate centered on financial stewardship: closing the books accurately, managing costs, and overseeing treasury. Five years ago, it expanded into strategic leadership: shaping the company’s narrative, driving data-informed decisions, and taking a seat at the M&A table. Today, the mandate has expanded again. The CFO is the organization’s chief data integrity officer, responsible for the quality, consistency, and machine-readability of every number the company submits to every regulator.
EXPECTATION FROM CFO
The near-term priority is measured readiness. Finance leaders should identify the regulators and recurring information collections relevant to their organizations, assign responsibility for monitoring agency developments and assess whether existing data-governance processes can support more consistent identifiers, definitions and metadata.
Preparation should involve finance, compliance, legal, technology and data-governance teams. Organizations can take low-regret steps to improve data ownership, lineage and validation, while postponing collection-specific technology investments until proposed requirements provide sufficient detail.
The Statistics Reflect This Shift
85%
of globally report compliance requirements have become more complex in 3 years (PwC 2025 Global Compliance Survey)
64%
of CEOs cite the regulatory environment as inhibiting their ability to reinvent their business model to at least a moderate extent (PwC 27th Annual Global CEO Survey)
$17.1M
median settlement for securities class actions involving accounting allegations in 2025 (NERA Economic Consulting 2025)
$43.5M
average settlement across 35 settled accounting-related class action cases in 2025 (NERA Economic Consulting 2025)
The FDTA makes these figures more consequential. As its interoperability framework eventually enables automatic comparisons between data submitted to different agencies, cross-agency inconsistencies will no longer be merely internal audit findings; they will become regulatory signals.
The CFO is no longer just closing the books. They are the organization’s chief data integrity officer responsible for the quality and machine-readability of every number submitted to every regulator.
What the Expanded CFO Mandate Now Includes
1
Data governance across all regulatory filings
Not just the 10-K and 10-Q but there are several other regulatory reports covered within the scope through agency specific implementation. The CFO needs a complete, documented map of where financial data goes, in what format, under whose ownership, and with what validation process.
2
Technology infrastructure ownership
Every agency-specific implementation rule will require software capable of producing regulatory reports in machine-readable format using the appropriate taxonomy. Organizations relying on manual processes or legacy single-agency tools will face compounding costs as each agency’s rules arrive.
3
Cross-agency data consistency
If the same revenue figure appears in your SEC 10-K and in a CFPB supervisory submission filed six weeks later with a reconciling difference, because different teams used different methodologies. The FDTA’s interoperability framework will eventually surface that discrepancy. Data governance is no longer purely an internal quality control question.
4
Proactive engagement with implementation timelines
The joint rule is complete. The agency-specific rules are coming. CFOs need to monitor each agency’s rulemaking calendar and build the implementation timeline into their compliance roadmap now, not when a final rule drops with a 12-month deadline.
The Path to Standard Business Reporting
The FDTA could contribute to a longer-term movement toward Standard Business Reporting, as discussed by XBRL US and the U.S. Government Accountability Office. SBR is a framework in which organizations submit financial data in a structured format so that it can be reused across relevant regulatory recipients.
GAO 2026 REPORT: POTENTIAL BENEFITS OF STANDARD BUSINESS REPORTING
“Improve the quality and efficiency of data analysis by regulators”
“Improve oversight and more timely identification of compliance concerns”
“Reduce reporting entities’ burden by making financial reports across multiple regulatory agencies more efficient”
The Netherlands and Australia have implemented national SBR programs. The Nordic countries have developed coordinated digital-reporting initiatives, including Nordic Smart Government and Business. The FDTA may represent an initial US step toward similar standardization, but it does not itself establish an SBR system.
For CFOs who have long managed the redundancy of submitting the same financial data to multiple agencies in different formats, SBR illustrates a possible longer-term benefit of greater standardization. Preparing for future collection-specific requirements may involve improving data quality, consistent tagging, and structured data capabilities.
Agency Implementation Tracker
LIVING SECTION: UPDATED AS RULES ARE PUBLISHED
This section is updated as each agency publishes its FDTA-specific implementation rules. Bookmark this page and check back as developments occur. Last updated: July 2026.
Agency | Regulated Population | FDTA Status | Next Expected Step |
SEC | Public companies, investment companies and other SEC-reporting entities | Joint rule adopted; required implementing agency. Existing filing requirements remain unchanged. | Agency-specific rulemaking; covered collections, formats and dates TBD. |
MSRB under SEC | Municipal issuers, obligated persons, broker-dealers and municipal advisers | Not a joint-rule agency. The SEC must establish standards for information submitted to the MSRB. | SEC rulemaking and related MSRB action; timeline TBD. |
OCC | National banks and federal savings associations | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; scope and timing TBD. |
Federal Reserve | Bank holding companies, state member banks and other supervised institutions | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; scope and timing TBD. |
FDIC | State non-member banks and other supervised institutions | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; scope and timing TBD. |
NCUA | Federally insured credit unions and other NCUA-reporting entities | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; scope and timing TBD. |
CFPB | Banks and nonbank financial companies subject to CFPB reporting | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; affected collections and entities TBD. |
FHFA | Fannie Mae, Freddie Mac, FHLBanks and Office of Finance | Joint rule adopted; required implementing agency. | Agency-specific rulemaking; affected collections and entities TBD. |
CFTC | Swap dealers and other CFTC-reporting entities | Joint rule adopted; discretionary — not required. | Monitor for any discretionary CFTC action. |
Treasury | Entities reporting under relevant Treasury-administered programmes | Joint rule adopted; separate implementation is discretionary. | Monitor for any discretionary Treasury action. |
Last updated: July 2026
Where DataTracks Fits In
DataTracks has spent over 20 years building the infrastructure that FDTA requires, not as a future capability, but as the operational foundation of everything the company already delivers.
FOR SEC FILERS: RAINBOW DataTracks Rainbow produces SEC filings in multiple formats, including XBRL, Inline XBRL and XML, according to the requirements applicable to each filing. It also supports validation using relevant XBRL US DQC rules. Its integration with upstream systems, collaborative content-editing and review workflows, EDGAR-direct submission and automatic taxonomy updates provides an established structured-reporting foundation that may help filers adapt as the SEC develops its collection-specific FDTA requirements. | FOR FERC FILERS: GLACIER DataTracks Glacier is already operating in the FDTA environment. As Order No. 917 transitions EQR filing to XBRL-CSV, Glacier filers will have the structured data infrastructure the FDTA builds upon already in place. |
FOR GLOBAL TAX FILERS DataTracks’ native FATCA, CRS, CbCR, and BEPS reporting capabilities demonstrate its experience with structured, machine-readable data across multiple jurisdictions. Although these reporting regimes are separate from the FDTA, they draw on related capabilities in data preparation, validation and regulatory submission that may become increasingly relevant as US agencies implement collection-specific standards. | FOR MULTI-AGENCY FILERS DataTracks’ managed service model addresses the cross-agency data consistency challenge the FDTA will eventually make visible. A single compliance partner with oversight across your SEC, FERC, and global tax filings is better positioned to identify and resolve cross-agency inconsistencies before they become regulatory signals. |
The FDTA does not ask organizations to become structured data experts overnight. It establishes the direction: machine-readable, interoperable, consistently formatted regulatory data, with XBRL well-positioned as the standard that meets those requirements across many agency contexts. As each agency’s implementation rules take shape, organizations with structured reporting infrastructure already in place will absorb the transition far more efficiently than those starting from scratch. DataTracks is that infrastructure.
Four Actions CFOs Should Take Now
1
Map your full regulatory reporting footprint
Identify every federal agency to which your organization is obligated to report, and reports that require a change in scope and format as per the updated standards. This is your FDTA exposure map. Most CFOs do not have this documented in one place.
2
Engage your technology vendors on FDTA readiness
Ask your reporting software providers directly: what is your roadmap for each agency’s FDTA implementation rule? If they can’t give a clear answer, that’s an answer in itself.
3
Monitor agency-specific rulemaking calendars
Bookmark the Agency Implementation Tracker above and return as each agency publishes its proposals. Alternatively, work with a compliance partner who tracks regulatory developments on your behalf.
4
Consider briefing your board
For organizations likely to be materially affected, the FDTA may warrant board-level visibility as agency-specific requirements emerge. The discussion can cover regulatory data governance, potential technology implications, and the longer-term possibility of more standardized cross-agency reporting. The timing and depth of the briefing should reflect the organization’s likely exposure and materiality.
KEY TAKEAWAYS
✓ The FDTA Joint Data Standards Final Rule was published in the Federal Register on June 25, 2026, and becomes effective October 1, 2026
✓ XBRL could be suited to the FDTA’s objectives and already in use across several regulatory contexts, though each agency’s implementation rule will determine the exact format required for its regulated population
✓ The joint rule covers common filers with reporting obligations to multiple regulators. For example, public companies (SEC), banks (SEC, OCC, Federal Reserve, FDIC, NCUA), mortgage lenders (FHFA), derivatives traders (CFTC and SEC), and consumer finance companies (CFPB)
✓ The joint rule sets the foundation, agency-specific implementation rules are next, each with its own compliance timeline
✓ The CFO mandate must consider data integrity, cross-agency consistency, and structured reporting infrastructure governance
✓ Organizations with an infrastructure to report in multiple formats are structurally ahead of those relying on manual or legacy tools
KEY TAKEAWAYS
Ready to assess your FDTA?
DataTracks has spent 20 years building the structured reporting infrastructure the FDTA requires. Talk to a compliance specialist about your multi-agency filing obligations.
