SEC ·

SEC adopts FDTA joint data standards for financial regulatory reporting

Regulatory-reporting and data teams at SEC-reporting entities must plan migration to the FDTA common identifiers and machine-readable formats ahead of the agency-specific rulemakings that will set binding collection requirements

Change
On 8 June 2026, the U.S. Securities and Exchange Commission (SEC) adopted a final rule establishing joint data standards under the Financial Data Transparency Act of 2022, setting common identifiers and machine-readable submission formats for data reported to certain US financial regulatory agencies; eight other federal agencies are adopting the same standards, with agency-specific rulemaking to follow.
Why it matters
The joint standards establish common identifiers for entities, geographic locations, dates, and certain products and currencies, plus a principles-based standard for data transmission and schema/taxonomy formats. The SEC frames this as the first FDTA step, with separate agency-specific rulemaking to follow that will set the standards applying to individual data collections. Because the same joint standards are being adopted across nine agencies — the SEC, Federal Reserve, CFTC, CFPB, Treasury, FDIC, FHFA, NCUA and OCC — entities reporting to more than one of these regulators face a common-format migration rather than divergent per-agency formats. The binding reporting-format obligations and timelines arrive through the forthcoming agency-specific rules.
Implications
  • Regulatory-reporting and data-management teams at SEC-reporting entities must map current submission formats to the FDTA common identifiers (entity, location, date, product, currency) and machine-readable schema/taxonomy requirements, or face rework when the agency-specific collections transition to the joint standards.
  • Entities reporting to multiple of the nine FDTA-adopting agencies must plan a single coordinated migration to the common standards across those reporting lines, or carry the duplicate divergent-format pipelines the rule is intended to eliminate.
  • Compliance and technology teams must track the SEC's forthcoming agency-specific FDTA rulemaking, since this rule sets the common format but the binding collection-level requirements and compliance dates arrive in the separate rules the SEC has flagged will follow.
Who is affected
  • Regulatory-reporting and data-management teams at SEC-reporting entities
  • Entities reporting to multiple of the nine FDTA-adopting US agencies
  • Compliance and technology teams responsible for regulatory data submission
What to watch
  • SEC agency-specific FDTA rulemaking: the joint standards are set, but the SEC has stated binding, collection-level standards and compliance dates will arrive in separate rulemaking to follow — watch for those proposals and their effective dates.
View on SEC
Clarify this change

Grounded in this brief and its source — your questions stay private.

Continue asking every change your own questions.

You asked:

Upgrade to Pro for unlimited Clarify across every brief.

Pro includes

Implications — what this change may force you to review
Who is affected — which people, workflows, or obligations are touched
What to watch — dates, deadlines, and triggers that matter next
Real-time alerts — delivered when a decision-forcing change is published
Clarify with AI — ask what this change means for you

$29/month · Founding rate, locked for life. Cancel anytime.

Continue asking this change your own questions.

You asked:

Create a free account to keep the conversation going.

Pro includes

Implications — what this change may force you to review
Who is affected — which people, workflows, or obligations are touched
What to watch — dates, deadlines, and triggers that matter next
Real-time alerts — delivered when a decision-forcing change is published
Clarify with AI — ask what this change means for you

Free account: no card, ever. Pro trial: $29/month after 14 days, no card to start, cancel anytime.