Summary

  • Nine U.S. financial-regulatory bodies established joint data standards under the Financial Data Transparency Act (FDTA). Their final rule was published June 25, 2026 and took effect October 1, but it explicitly changed no existing reporting requirement at the effective date.
  • Seven implementing agencies must later adopt applicable standards for certain collections through their own rules. The joint framework names common identifiers such as the Legal Entity Identifier and date and currency formats, while allowing agency tailoring. A common dictionary does not by itself make separate filings interoperable.
  • GAO's May 2026 report described potential gains in analysis and reporting efficiency alongside legacy-system, coordination and transition costs. It preceded the final rule. The test now is each agency's dated implementation rule, its covered collections and the crosswalk from old fields to shared ones, not a claimed savings figure.

A rule went live. The forms stayed put.

The Securities and Exchange Commission's final-rule page states the unusual result plainly. The joint data standards were effective October 1. At that moment they changed no reporting requirement without further agency action. A filer still faced the forms it faced on September 30. The rule established common terms for regulators to use when they later change certain collections; it did not build a national upload button or make a filing submitted once appear in nine inboxes.

That distinction matters because the underlying problem is real. Businesses can report similar financial facts to different federal regulators in different ways. In GAO-26-108420, published May 14, the Government Accountability Office described potential benefits from standardised data: analysis across agencies, more timely supervision and less repeated work for reporting entities. It also described the bill for getting there: legacy systems at agencies, new governance and coordination, and adaptation and testing for filers. Those were prospects, not measured savings. GAO wrote while the August 2024 proposal was still being finalised. The joint rule arrived later, in June.

The full GAO report drew another boundary. The United States did not have a government-wide regulatory reporting system built on common standards. The FDTA was a financial-sector step, not a finished whole-of-government exchange. That is why the shiny phrase “submit once” is a poor description of October 1. Agencies can agree on what a field means before any one of them changes the form that asks for it.

Nine sign the dictionary; seven must edit the forms

The final rule published in the Federal Register came from nine institutions: the Office of the Comptroller of the Currency, Federal Reserve Board, Federal Deposit Insurance Corporation, National Credit Union Administration, Consumer Financial Protection Bureau, Federal Housing Finance Agency, Commodity Futures Trading Commission, SEC and Treasury. The FDTA separately directs seven of those agencies—the same list without the CFTC and Treasury—to issue agency-specific rules for certain information collections. Their adopted standards must take effect within two years of the joint rule's promulgation, subject to the law's terms. Participation in writing the common dictionary is not the same obligation as rewriting an individual collection.

What is in the dictionary? It specifies the ISO 17442 Legal Entity Identifier for a legal entity; a Unique Product Identifier for swaps and security-based swaps; a classification code for other financial instruments; ISO 8601 dates; U.S. postal state abbreviations; defined codes for countries and currencies. Its schema principles call for data that can be searched and read by machines, with documented meaning and nonproprietary or openly licensed formats where practicable. Those choices can reduce the confusion of one entity or date appearing under several labels. They do not tell an agency which old box on which form will be retired.

The rule also shows the politics hiding inside a technical standard. The agencies dropped a proposed joint identifier for financial instruments and specified a classification role for another code. They left room for an implementing agency to tailor a standard or adopt a different identifier where the statute permits it. Tailoring can spare smaller filers or an old system a costly forced conversion. If every agency makes a private exception without explaining its crosswalk, the original problem returns with nine official-looking dialects. A common vocabulary only becomes common in use.

The next decision is owned by each agency

This is the institutional bargain. A joint rule can establish semantic agreement among regulators without immediately changing what the public must submit. That protects filers from a surprise October conversion. It also moves the cost and discretion to seven later rulemaking desks. Each must identify the collections it covers, the identifiers and formats it will actually use, the exceptions it needs and the transition its reporting population can perform.

The GAO report is useful here because it separates promised efficiency from the work required to earn it. Modernising a database and testing a filing system are not ceremonial steps. If an agency asks for a common identifier but leaves its internal records unable to match it, the filer pays conversion cost and the regulator keeps the old silo. If one agency maps the same legal entity differently from another, the shared label loses its reason for being.

The public proof will be each implementing agency's dated final rule or applicable action, naming the covered collections and the chosen standard, followed by the actual reporting instructions and working crosswalks. An effective date for the joint dictionary is one receipt. A functioning path from an old field to a shared, machine-readable field is another. Washington has delivered the first and assigned ownership of the second. The filings will tell us whether those owners meet.

Sources