FINRA explains U4 API address handling for registered and unregistered offices

FINRA has notified developers of an October change in the way Form U4 application-programming-interface submissions handle office-location addresses. In a 5 October developer bulletin, the US broker-dealer regulator said that locations with an existing Branch CRD identifier will be treated differently from unregistered offices when address values arrive through the firmAssociations.officeLocations field. It asked firms to test the change in FINRA's quality-assurance environment and said production rollout was planned for the end of October 2026.[1][2]

For registered locations, including the main office and branches with a Branch CRD number, the system is to ignore address values supplied in the Form U4 submission and retain the registered address already on record. FINRA said the earlier behavior could result in a location marked with bdMainOfficeIndicator receiving the firm's main-office address. The change is therefore an important data-governance fix: a personnel registration submission should not quietly overwrite the authoritative address attached to a separately registered branch.[1]

For an unregistered office location without a Branch CRD number, the opposite treatment applies. FINRA says a new address submitted through the U4 location field will be accepted and saved, and a firm may edit such an address. That difference means a brokerage's registration integrations cannot assume all location objects are updated through the same process. The relevant system should identify the office type before determining whether an incoming address can be written to FINRA's records.[1]

Form U4 API: location-specific behavior

Form U4 is the uniform registration application for securities-industry individuals. Addresses in that process help link representatives to offices and supervision arrangements, but their presence does not independently establish that a location is a licensed branch. Similarly, the change to an API field does not alter a person's qualification examinations, customer-disclosure requirements or the substantive definition of a branch office. Those obligations must be evaluated under their own rules, not inferred from whether an address was accepted by a data interface.[1]

FINRA's announcement specified end-of-October production deployment as a plan, not a documented completion time. The publicly accessible bulletin does not, by itself, establish that every member integration has been updated or that every production change was successful by 31 October. Firms should test registered-main-office and unregistered-location examples in the stated QA environment, then reconcile actual production responses before treating the change as implemented in their internal registration databases.[1]

FINRA's October developer note distinguishes registered locations, where supplied U4 API addresses will be ignored in favour of the existing registered address, from unregistered locations, where new addresses can be accepted and edited. It said the change was scheduled to enter production at the end of October 2026. That schedule has now passed: without a separate production-release confirmation, the notice supports the announced rule and planned deployment, not an independently verified current API state. Firms should validate submissions in test and production against the relevant branch CRD references before relying on automated address changes.[1]

The direct impact falls on broker-dealer compliance and technology teams, especially those that generate U4 submissions automatically from human-resources or branch-management systems. A silent overwrite or ignored address could undermine the quality of internal office records if the receiving behavior is misunderstood. A sound control compares the expected authoritative location identifier, the field submitted, the FINRA response and the resulting registered address. This is a precise registration-data maintenance change, not a new financial-services licence or a change to where customers may trade.[1]

Report an error or submit an update