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
- — 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.
- — 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
- — 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.