Interview with Ben Ouseph, Head of US Operations, DataTracks
The following interview examines the Financial Data Transparency Act (FDTA) and what its transition from legislation to implementation means for CFOs, compliance leaders, and organizations subject to financial regulatory reporting. Ben Ouseph, Head of US Operations at DataTracks, explains the June 2026 joint final rule, the common data standards being established across nine federal agencies, and how the FDTA relates to existing structured-data requirements such as XBRL.
Congress set a clear goal for the FDTA: shared data standards that make financial regulatory data machine-readable and comparable, whichever agency receives it. The law gave the agencies 18 months to propose joint standards and two years to finalize them. The agencies issued the proposal in August 2024 and the final rule in June 2026.
Ouseph also outlines which organizations and filings could be affected, what remains undecided as agencies develop their own implementation requirements, and the practical steps companies can take now to assess data quality, strengthen governance, identify reporting gaps, and prepare for potential technology, operational, and compliance costs ahead of the 2028 implementation horizon.
1. What is the FDTA, and why does it matter to CFOs and compliance leaders?
The Financial Data Transparency Act (FDTA) modernizes financial regulatory reporting by establishing common data standards across federal agencies. Its goal is to make regulatory information more consistent and interoperable, reducing the confusion caused by different reporting formats and definitions.
For CFOs and compliance leaders, FDTA has important implications. Companies that standardize their reporting can expose inconsistencies across financial statements, regulatory submissions, and internal systems. Data quality, governance, and accountability have always mattered, but they now carry more weight than before.
2. What federal agencies are involved and what standards did they establish in the June 2026 joint final rule?
The June 2026 joint final rule set common data standards for financial regulatory information across nine federal agencies: the SEC, Federal Reserve, OCC, FHFA, NCUA, CFPB, FDIC, CFTC, and the Treasury Department.
The standards include the Legal Entity Identifier (LEI), the Unique Product Identifier (UPI) for swaps and security-based swaps, and the Classification of Financial Instruments (CFI) for classifying other financial instruments, along with standards for currencies, dates, and geographic locations.
Of note, the joint final rule does not mandate a single reporting technology, such as XBRL, across all agencies. Individual agencies may use XBRL or other qualifying formats when implementing the joint standards.
Nine agencies participated in the joint rule, but only seven are specifically required to conduct agency-specific implementation rulemakings. Treasury and the CFTC may do so at their discretion.
3. What organizations and types of regulatory filings could be affected?
The FDTA may affect public companies, banks, credit unions, investment firms, consumer and housing finance companies, and issuers of municipal securities.
SEC disclosures, bank regulatory reports, credit union submissions, housing-finance reporting, and municipal securities disclosures submitted through the Municipal Securities Rulemaking Board are among the potentially affected filings.
But the specifics will vary by organization type and by the agency requiring the filing. CFOs should look at their current reporting obligations and keep track of which types of information will be standardized under the act. The FDTA focuses on standardizing existing regulatory data rather than imposing new information-collection requirements. The joint rule itself does not change current reporting obligations; implementation requires further agency action.
4. How does the FDTA affect today’s XBRL and other structured-data requirements?
The FDTA builds on today’s structured-data reporting initiatives, including the SEC’s Inline XBRL requirements and XBRL-based bank regulatory reporting. But it does not replace those requirements or mandate XBRL as a universal reporting format. Instead, it establishes common standards to improve consistency and interoperability across federal agencies.
XBRL supports machine-readable financial information, standardized definitions, and automated validation, so it can be expected to play an important role in reporting.
Companies already using structured reporting technologies may have an advantage, but the real advantage will go to organizations that do extensive research and closely track developments, since government agencies can set their own technical specifications. What is right for one agency might not be right for another.
5. What is still undecided, and how can companies keep track of the latest developments?
These are among FDTA’s biggest unanswered questions: which filings will change, what technical formats agencies will require, and when organizations must comply. Although the joint rule establishes common standards, individual agencies must determine how those standards apply to their reporting programs.
CFOs should keep a close eye on the Federal Register, agency rulemaking calendars, proposed new regulations, and technical guidance from their relevant regulators. They should also work with reporting software providers to stay ahead of planned updates and changing costs.
6. What should CFOs and compliance teams do now to assess their readiness?
CFOs can get started by making an inventory of their regulatory filings, reporting systems, data sources, and internal responsibilities. They should track how all information moves from source systems into regulatory submissions, including transformations, reconciliations, and validation procedures. It is especially important to track information that appears in multiple filings, where inconsistent definitions or calculations could create reporting risks.
Organizations should also evaluate whether existing technology can accommodate machine-readable formats and new identifiers. Compliance with rules that have yet to be finalized is not the immediate objective. Identifying weak spots that could complicate future implementation is.
7. What operational challenges and costs should organizations anticipate?
Some organizations will find that inconsistent data definitions, fragmented reporting systems, and manual processes pose bigger challenges than the filings themselves. There may be costs associated with software upgrades, systems integration, data mapping, validation, employee training, or external vendor support.
Companies that report to multiple agencies face more complexity, as do smaller organizations that rely entirely on spreadsheets or legacy systems.
CFOs should develop preliminary cost scenarios based on which agencies they report to, identify operational dependencies, and refine budgets as regulators release more detailed guidance.
8. What is the implementation timeline, and which milestones matter most?
The FDTA was enacted on December 23, 2022. It was followed by proposed joint standards on August 22, 2024. The joint final rule was published on June 25, 2026, and became effective on October 1, 2026.
The FDTA requires applicable agency-specific data standards to take effect within two years of the final joint rule’s promulgation, creating a June 2028 implementation horizon. However, each agency will set its own requirements and compliance dates, so organizations should maintain agency-specific implementation plans rather than assume there will be a single, universal deadline.
9. What is the single most important step a CFO can take today to prepare?
Mapping the organization’s regulatory reporting environment, including its filings, data sources, systems, and responsible personnel, is the most important initial step. CFOs need a clear picture of how information moves from source systems through internal calculations, reconciliations, and approvals before being sent to regulators.
Inconsistent definitions, duplicated processes, manual workarounds and data validation weaknesses must first be exposed to be remedied.
With a clear picture of the reporting environment, organizations can evaluate their exposure to future FDTA requirements and prioritize improvements based on actual risk. The immediate priority should be understanding, standardizing and establishing control over the data the organization already reports, not rushing out to buy new technology.
Sponsored Feature




