Automating Operations: Who Has to Register as an Operations Professional

Updated October 2026. First published April 2024.

The first version of this post said firms should balance automation with human talent. That's true, and it won't help anyone staff a desk. Here is something more useful. FINRA's registration rules already count defining, approving, and validating operations systems as operations work, and they say who has to be qualified to approve it.

The Rule

FINRA Rule 1220(b)(3) requires three groups of people to register as Operations Professionals:

• senior management with direct responsibility over the covered functions;
• people that senior management designates as supervisors, managers, or others who approve or authorize work in a covered function;
• people with authority to materially commit the firm's capital, or to commit the firm to material contracts, as part of a covered function.

The covered functions read like a map of the back office. They include client onboarding; collection, sweeps, and disbursement of funds; receipt and delivery of securities and funds; bank, custody, and depository reconciliation; settlement, fail control, buy-ins, segregation, and possession and control; trade confirmations and account statements; margin; stock loan; prime brokerage; approval of pricing models; financial control; and contributing to financial regulatory reports.

Then the list turns to systems. Item m covers "defining and approving business requirements for sales and trading systems and any other systems related to the covered functions, and validation that these systems meet such business requirements." Items n and o cover defining and approving business security requirements for information technology, and information entitlement policies for the covered functions.

What Item m Means When You Automate

Read item m next to a project plan. When a firm moves fail management, Letter of Free Funds processing, or a reconciliation into software, someone defines what the system has to do, someone approves those requirements, and someone confirms that the system does it. Each of those steps is a covered function. A registered person has to own them: the senior manager directly in charge, or someone senior management designates to approve or authorize the work. The people senior management designates have to cover every covered function the firm performs.

The exclusions turn on what a person does. Supplementary Material .05 leaves out people whose work is ancillary, supportive, or advisory, such as internal audit, or legal and compliance staff who review a function without primary responsibility for it. It also leaves out people doing only clerical or ministerial tasks. A technology job title isn't on the list.

To register, a person passes the Series 99 exam and the SIE. The Series 99 has 50 questions, a 90-minute limit, and a passing score of 68. Someone who held an eligible registration, such as the Series 7 or Series 27, within the two years before registering can qualify without taking it.

What Changes on the Desk

Automation moves work to new places. We traced where it lands for one process in Automated Isn't Free. It's Unpriced. For the people on the desk, three changes show up first.

• Exceptions become the job. Once the system handles the clean items, staff spend their day on the ones it can't. The exception queue needs a named owner, an aging report, and a written rule for when an item escalates.
• Testing repeats. A change to the system's rules, its data feeds, or a vendor's model means new requirements, and under item m someone has to approve them and confirm the system meets them. Plan for that work on every release.
• Someone has to be able to explain the system. A person on the desk should be able to say in plain language why an item was rejected or routed. If only the vendor can, you have a supervision problem. FINRA's Regulatory Notice 21-29 says outsourcing a function "does not relieve members of their ultimate responsibility" for it.

The same holds when a firm outsources the processing itself, as some do with Loffa's Compliance Service Desk, whose staff work under the client firm's procedures. The approvals and the supervision stay with the firm's own registered people. Losing the one person who understands the system is a related risk, covered in our post on key-person risk in operations.

A Checklist for the Project Plan

1. Map the process against the covered functions in Rule 1220(b)(3) before the project starts.
2. Name the person who approves the requirements and signs off on the testing, and check that they're registered as an Operations Professional.
3. Keep a record of each test that shows which requirement it checked and what happened, signed by the person who approved it.
4. Give the exception queue an owner and an aging limit before go-live.
5. Retest after every change to the system's rules, data feeds, or model, and keep that record too.

This post is for informational purposes only and does not constitute legal advice. For guidance on specific regulatory obligations, consult your counsel or compliance advisor.