An operations professional must be able to follow a transaction from the customer’s instructions through the firm’s records and the movement of money or securities. A valid trade can still produce a serious problem if account authority is wrong, settlement fails, a security is unavailable for delivery or the ledger does not match the custodian. This guide builds that chain step by step. You will learn to distinguish similar processes, calculate what a discrepancy means and decide when an exception needs correction or escalation. It also treats conduct as part of the work: protecting customer information, recognizing complaints and red flags, and understanding the controls that keep one person from initiating, approving and concealing the same transaction.
F1: Knowledge Associated with the Securities Industry and Broker-dealer Operations
1. Retail, institutional and prime brokerage accounts
Start by identifying who has the customer relationship, who executes the trade, and who carries the resulting position. In a typical retail arrangement, one carrying broker may handle execution, custody, statements, and settlement for the customer. An introducing broker may instead take the order while another firm carries the account. Institutions often separate these tasks further. A hedge fund can use several executing brokers but appoint one prime broker to consolidate custody, financing, and clearing arrangements. The executing broker handles the trade; the prime broker receives it under an agreed process and maintains the fund’s broader account relationship. Operations staff must match trade details and account identifiers across the parties so positions and cash reach the intended books. The Series 99 exam covers these operational functions, including prime brokerage.
Worked example: A hedge fund buys 400 shares through Broker A and designates Broker P as its prime broker. Broker A executes the purchase. Under the agreed prime brokerage arrangement, Broker P receives the trade for clearing and maintains the fund’s consolidated position. A retail customer who trades through one carrying firm normally sees that firm handle the execution and carry the resulting 400 shares.
Watch the distinction: A prime broker does not necessarily execute every trade for its client. Check the executing broker and the agreed clearing path separately before assigning operational responsibility.
2. Account registration and trading authority
Account registration identifies the legal owner; trading or disbursement authority identifies who may act for that owner. An individual account belongs to the named person, while a corporate account belongs to the corporation, even when an officer communicates with the firm. For an entity, review its formation documents, resolutions, authorized signer records, and any limits placed on instructions. Authority to place trades may differ from authority to withdraw cash or change settlement details. Match the requested action to the documented permission, verify the person giving the instruction, and check whether the authorization remains effective. A job title, familiar voice, or prior contact cannot substitute for the account record. If the documents conflict, resolve that conflict before moving assets and retain evidence of the decision.
Worked example: A company president calls to withdraw $18,000 from its brokerage account. The account registration names the company, but its current resolution authorizes the treasurer alone to request withdrawals. Operations does not release the $18,000 on the president’s title. It verifies the resolution and asks for an instruction from an authorized signer, or properly documented updated authority.
Watch the distinction: Ownership and signing power are different questions. An officer may represent a company generally yet lack documented authority for a particular account transaction.
Reference: [2]
3. Retirement account operations
Retirement accounts require records that distinguish money entering the account from money leaving it. A contribution adds funds and must be classified by account type and applicable tax year; a distribution removes funds and may create withholding and tax reporting duties. Traditional IRAs and employer-sponsored plans have different governing arrangements, administrators, and distribution records. Required minimum distribution analysis depends on the owner’s circumstances, the account type, the relevant year, and any applicable exception. Operations should therefore review each account separately rather than treating all retirement balances as one pool. Determine what transaction the customer requested, identify the account holding the assets, obtain the relevant plan or custodian information, and record the movement under the correct transaction type. When a distribution is requested, clarify its destination and reporting treatment before processing.
Worked example: Mira has a traditional IRA and an employer-sponsored plan. She takes $4,000 from the IRA and asks whether that automatically settles any distribution duty for the plan. It does not establish that result. Operations reviews the applicable year and each account’s requirements and records. The $4,000 is an IRA distribution; a later $4,000 deposit would be a separate contribution or transfer question.
Watch the distinction: Do not combine an IRA and workplace plan merely because one person owns both. Their records and distribution rules must be evaluated by account.
Reference: [2]
4. Retirement transfers and rollovers
Follow the path of the money to classify a retirement movement. In a direct custodian-to-custodian transfer, the owner does not receive the funds; the institutions move them between accounts. A distribution paid to the owner followed by a deposit into another eligible account is a rollover route. That route introduces questions about reporting, withholding, timing, eligibility, and whether the full distributed amount is redeposited. Operations should establish the source and destination account types, the named payee on any check, and whether cash or securities will move. The same intended destination does not make the two paths operationally equivalent. Document the customer’s instruction accurately, use the process supported by the institutions, and avoid promising a tax result from the transfer form alone.
Worked example: Jon wants $40,000 moved between traditional IRA custodians. If Custodian A sends the assets directly to Custodian B for Jon’s IRA, Jon never receives the money. If A writes Jon a $40,000 check, it is paid to him first. His later deposit raises separate rollover timing, reporting, and withholding questions, even if he intends the same $40,000 destination.
Watch the distinction: A check made payable to the account owner is not made direct by mailing it to another custodian. Classify the movement by payee and control of the funds.
Reference: [2]
5. Customer identification and know your customer
Customer identification and know your customer answer related but different questions. A customer identification program establishes and verifies the identity of the person or entity opening an account using required identifying information and suitable verification methods. Know your customer work builds an understanding of the customer, the account’s purpose, and the activity the firm should expect. For an entity, its formation, ownership, control, business, and expected cash or securities movements may matter to that understanding. A valid identity document can support the first task without explaining why a company will receive frequent third-party wires. Compare later activity with the account profile and investigate material inconsistencies. Operations staff should record missing facts and route them for review before treating an identity check as approval of every proposed activity.
Worked example: A company representative presents a verified passport and valid entity documents. The application says the account will hold long-term investments, but the representative also describes frequent payments to unrelated recipients. Identity verification supports who is applying. Operations still seeks a clear account purpose and expected transaction pattern, because the stated uses conflict and affect the review of future activity.
Watch the distinction: A verified passport establishes an individual’s identity; it does not explain an entity’s business or make unusual account activity consistent with its stated purpose.
Reference: [2]
6. Opening documents, approvals and settlement instructions
Account opening is a sequence of checks, not a single signed form. Confirm the account registration, required customer information, authorized persons, and applicable approvals. Then compare standing settlement instructions with the approved account record and the parties expected to deliver securities or cash. An SSI directs routine settlement, so an incorrect destination can repeatedly misroute transactions. A new or changed bank detail needs its own validation, including appropriate authentication and approval, even when the rest of the application is complete. Record which version is effective and when, and prevent activity from relying on an unresolved instruction. The Series 99 content outline identifies account paperwork, approvals, and standing settlement instructions as operations knowledge areas.
Worked example: An institution submits signed opening documents and an SSI naming Bank B. Its approved account record names Bank A. Operations compares the records, holds use of Bank B, and independently validates whether an authorized person requested the change. Once the bank detail and effective date are documented and approved, settlement can use the confirmed instruction.
Watch the distinction: A complete application does not authenticate every payment destination written on it. Resolve a mismatch in settlement instructions before relying on them for funds or securities.
Reference: [2]
7. Maintaining account information and disclosures
Account maintenance has two tracks: keep customer facts current and establish permission for any new product or activity. An address change affects records and delivery of communications, so authenticate the request, update the relevant systems, and check that the change propagates to statements and notices. Options trading raises a separate approval and disclosure question. The firm must assess the account for that activity and provide the applicable options disclosure before the customer trades, according to its obligations. Product disclosures may also be needed for other securities with distinctive features or risks. Treat each request according to what it changes: an address update changes contact information, while an options request changes the activities the account may undertake. A successful update in one system is not evidence that another approval was completed.
Worked example: Lena reports a new mailing address and asks to trade options that afternoon. Operations verifies and records her address change, then checks whether the options review, account approval, and required disclosure are complete. If they are not, the address may be updated while options activity remains unavailable. The two requests have different controls and outcomes.
Watch the distinction: Do not infer product approval from an active account or a recent profile update. A product request requires its own review and applicable disclosure.
Reference: [2]
8. Account restrictions and unclaimed property
An activity restriction limits specified transactions while the firm investigates or satisfies a control; it does not itself close the account or transfer ownership. Returned mail, lost contact, and an unfamiliar withdrawal request each require attention, but they answer different questions. Authenticate the request and protect the account against unauthorized movement. Separately, attempt appropriate owner contact and maintain a record of unresolved property. Unclaimed-property procedures depend on the type of property and applicable jurisdiction; after the required process, the firm may have to report and remit it to the state. An operations professional should track dates, contact efforts, balances, and any legal hold or exception. Do not use an uncertain withdrawal as a convenient way to clear an inactive balance, and do not treat inactivity alone as permission to escheat immediately.
Worked example: Mail to Sam is returned, no verified contact succeeds, and a caller unknown to the firm asks for a $2,000 withdrawal. Operations restricts the relevant movement, independently investigates the caller’s authority, and documents attempts to reach Sam. The $2,000 remains in the account during review. If it later meets applicable unclaimed-property conditions, the firm follows that separate process.
Watch the distinction: A restriction is a control on activity, not a final decision about ownership. Returned mail also does not make an unfamiliar caller an authorized claimant.
Reference: [2]
9. Verifying transfer instructions
A letter of authorization communicates a requested movement, but its signature is only one item in the verification chain. Identify the source account, security or cash amount, destination, and requested delivery method. Compare the signer with the account’s documented authority and confirm that this person may initiate that specific kind of transfer. Then assess the destination: an account in the same name may follow a different process from a transfer to a third party. New destinations and unusual instructions warrant independent verification through a trusted contact channel, along with any required guarantee or supporting documents. Check for restrictions on the position before releasing it. Preserve the instruction and the verification evidence so the movement can be traced from request through approval, delivery, and reconciliation.
Worked example: A signed letter asks to send 250 shares from Pat’s account to a newly named third party. Operations verifies that Pat signed it and has transfer authority, then checks the recipient details, any applicable restrictions, and the required independent confirmation. Until those checks support the destination, the 250 shares stay put. The signature alone does not authorize delivery.
Watch the distinction: Recognizing a signature does not establish that a third-party destination is permitted or authentic. Verify the action, authority, and destination as separate facts.
Reference: [2]
10. Wires, ACH transfers and journals
Choose a movement method by asking where the money starts and ends. A wire sends funds through banks, generally for a specific payment. An ACH transfer uses a bank-network process with its own authorization and return characteristics. A journal moves value between ledgers within the firm; it does not itself send money to an outside bank. For every movement, verify authority, destination, available funds, and the matching debit and credit. A journal between customer accounts reduces one customer balance and increases another by the same amount, subject to valid transfer authority. A wire or ACH also affects the firm’s external cash reconciliation when the bank movement occurs. Operations should distinguish an instruction’s acceptance from its completion and investigate any difference between the customer ledger and bank record.
Worked example: Account A journals $6,000 to Account B at the same firm. A’s customer cash ledger decreases by $6,000 and B’s increases by $6,000, so the combined customer balance changes by $0. No bank wire or ACH entry is needed for this internal movement. Operations verifies both postings and the authority linking the accounts.
Watch the distinction: An internal journal is not an external payment. If the bank balance changed, investigate whether another transaction occurred or the movement was misclassified.
Reference: [2]
11. Automated and manual account transfers
Account transfers depend on the institutions, account registrations, and assets involved. ACATS provides an automated path for eligible transfers between participating firms. It requires the receiving firm to submit matching customer and account information so the delivering firm can validate the request and identify transferable positions. A separately held asset at a nonparticipating custodian needs another supported transfer method, possibly with issuer or custodian documentation. Before promising a full move, identify assets that cannot travel by the proposed channel and how they will be handled. Compare account titles and ownership, record any exceptions, and reconcile positions and cash on receipt. A transfer request can be valid even when different parts require different workflows; one failed channel should not silently erase the customer’s broader instruction.
Worked example: Nora asks to move her brokerage account and a separately held fund position. Her old broker participates in ACATS, so the receiving firm submits the matching brokerage account transfer there. The fund position sits at a nonparticipating custodian, so operations obtains its separate transfer requirements. It reconciles each asset only after the respective delivering party confirms movement.
Watch the distinction: ACATS eligibility of one broker account does not make every asset at every custodian eligible. Identify the current record holder for each position.
Reference: [2]
12. Residual credits after a full transfer
A full account transfer moves the known positions and cash at a particular point in time. Dividends, interest, corporate-action proceeds, corrections, and other adjustments can post at the delivering firm afterward. These later items are residuals, not necessarily signs that the original transfer was incomplete. Operations must connect the new credit to the transferred account, confirm that it belongs to the customer, and send it through the applicable residual process to the receiving firm. The receiving firm should post and reconcile it against the delivering firm’s advice so it is neither omitted nor duplicated. Track unresolved residuals even if the old account shows a zero balance immediately after the main transfer. The timing of a later income posting explains why a clean initial reconciliation can subsequently require another movement.
Worked example: A brokerage account transfers with $0 cash. Two days later, a $37 dividend for shares formerly held there reaches the old firm. The old firm identifies the payment as a residual credit and forwards $37 to the receiving firm. The receiving firm posts $37 to the customer and reconciles the advice; the original zero-cash transfer remains valid.
Watch the distinction: A later credit does not, by itself, mean the main transfer failed. Trace its source and payment date before reopening settled positions.
Reference: [2]
13. Check controls and the check blotter
A check must be both traceable and negotiable before it is handled as customer funds. Inspect the date, amount, payee, drawer, alterations, and required endorsement. The named payee determines who can negotiate the instrument; a check payable to someone else cannot simply be deposited into a customer account because that customer brought it in. Record the check’s receipt in the blotter or equivalent control record, including identifying details, amount, date, and ultimate disposition. If a defect is found, secure the instrument while it is reviewed and document whether it was returned, corrected, or otherwise handled. Keep that trail even when no deposit occurs. This helps reconcile checks received with checks deposited and exposes instruments held too long, altered, or diverted.
Worked example: A customer hands operations a $2,500 check payable to an unrelated person. It has no valid endorsement from that payee. Operations does not credit the customer account or deposit the check. It records the $2,500 receipt and identifying details, follows the controlled return or correction process, and records the final disposition so the check remains traceable.
Watch the distinction: Possession of a check does not make the customer its payee. Crediting an account before negotiability is established can create an unsupported cash balance.
Reference: [2]
14. Cash sweeps and reinvestment
A sweep arrangement moves eligible idle cash from the brokerage ledger into a designated vehicle, such as a bank deposit program or money market fund, under the account’s terms. Operations needs to know where the value is held at each point, how it becomes available for purchases or withdrawals, and what balance the customer statement represents. A securities purchase may use cash already on the brokerage ledger, with any shortfall funded by redemption or transfer from the sweep vehicle. The sweep balance can have different features, risks, and availability from free brokerage cash, so avoid treating the two as identical merely because both appear in an account view. Reconcile sweep entries with the vehicle’s records and confirm that redemptions cover settlement obligations without counting the same cash twice.
Worked example: Assume an account’s $8,000 available balance includes $6,000 in its sweep vehicle and $2,000 on the brokerage cash ledger. A $3,000 securities purchase requires $3,000 in settlement cash. The ledger supplies $2,000, leaving $3,000 minus $2,000 = $1,000 to redeem from the sweep, assuming no other available cash or charges.
Watch the distinction: Do not add a sweep balance to a displayed total that already includes it. Determine the ledger cash and sweep components before calculating a redemption.
15. Cash transaction reports and cashiering red flags
Physical currency has reporting and recordkeeping considerations distinct from an ordinary wire, ACH entry, or internal journal. A currency transaction report addresses qualifying cash activity under applicable rules; suspicious-activity review considers the behavior and surrounding facts. Those are separate analyses. A customer who asks about reporting and then divides a planned deposit among visits presents a potential structuring pattern, even if each visit appears small in isolation. Operations should connect related transactions, preserve amounts, dates, parties, and the customer’s statements, and promptly refer the pattern through the firm’s escalation path. The responsible team evaluates reporting obligations using the full facts and current requirements. Staff should neither promise that smaller deposits avoid reporting nor accuse a customer solely because multiple deposits occurred.
Worked example: A customer plans to bring in cash, asks when reporting applies, then makes three smaller deposits on separate visits. Operations records each deposit and links the customer’s earlier statement to the series. The split pattern warrants suspicious-activity review. Whether a currency report or another report is required depends on the aggregate facts and applicable rules, not the customer’s chosen visit size.
Watch the distinction: Several smaller deposits do not automatically eliminate reporting duties. Review connected activity and intent rather than treating each cashiering event as isolated.
Reference: [2]
16. Possession, control and segregation
Safekeeping describes protection against loss or theft. Possession or control and segregation ask an additional question: are customer securities available for customers, free from an improper firm claim? A firm may physically locate certificates or a control-location position yet have pledged some shares for its own borrowing. The pledge creates a claim inconsistent with treating those shares as fully available customer property. Operations compares customer obligations with positions at acceptable locations, identifies encumbrances, and investigates shortages or improper uses. The location, legal status, and ledger designation all matter. Documented custody alone is insufficient when another party has rights over the position. Broader financial-control study, including related firm obligations, appears in the Series 27 guide.
Worked example: A firm locates 1,000 shares attributable to customers in a secure depository account. Its borrowing records show 200 of those shares pledged for the firm’s loan. At most 1,000 minus 200 = 800 shares are shown free of that pledge. Operations investigates and resolves the 200-share encumbrance before treating all 1,000 as available for customers.
Watch the distinction: A secure location does not prove unrestricted customer control. Reconcile the shares’ location with pledges, liens, and the firm’s customer obligation.
17. Street name and directly held positions
Street name and direct holding describe where the registered ownership record sits and which party services the position. In street name, securities are registered in a broker or nominee name while the broker’s records show the customer’s beneficial interest. The broker generally reflects that position on its statement and handles account servicing. A directly held mutual fund position is recorded on the fund or transfer agent’s books in the investor’s name; its statement and servicing may come from that organization. When a customer questions a missing dividend, transfer, or balance, first identify the record holder and compare the appropriate statement and transaction history. A brokerage view may include information about outside assets, but display alone does not establish custody. The operational question is which records control the position and who can process the requested action.
Worked example: Evan’s brokerage statement lists 100 street-name shares, while his fund-company statement lists 50 mutual fund shares. Operations reconciles the 100 against the broker’s customer and depository records. It checks the 50 against the fund or transfer agent record. The two positions total 150 shares of different holdings, but they are serviced through different record holders.
Watch the distinction: A position shown to a customer is not necessarily held by the broker. Trace registration and the controlling record before directing a transfer.
Reference: [2]
18. Stock records and security counts
A stock record tracks securities positions and where the firm expects them to be held or owed. A security count tests those records against physical certificates, depository balances, and other verified control locations. Begin with the recorded customer or firm obligation, then total confirmed positions that can satisfy it. The difference is a shortage or overage requiring investigation. Check whether a recent receipt, delivery, corporate action, loan, or transfer was posted in the wrong account or period. A timing explanation needs supporting evidence; it cannot be used merely to force a match. Identify the specific security and share quantity because values can change while the share break remains. Resolve the underlying location or posting and document the correction so the stock record and independent evidence agree.
Worked example: The stock record requires 700 shares for customer positions. Confirmed control locations show 400 shares at a depository and 250 with another verified custodian, totaling 650. The shortage is 700 minus 650 = 50 shares. Operations checks recent deliveries and postings for those 50 shares and does not mark the count balanced until evidence identifies or replaces them.
Watch the distinction: A plausible pending entry is not a verified position. Keep a shortage open until the missing shares or a documented posting error is resolved.
Reference: [2]
19. Certificates and good delivery
Physical certificates require checks before they can be accepted for transfer or delivery. Identify the security and certificate number, inspect for apparent alteration or invalidity, and verify that the registered owner and transfer documents align. A registered certificate generally needs an endorsement by the owner or a properly executed stock or bond power. Someone signing for the owner needs documented authority in the capacity claimed. Bearer securities follow a different ownership form, so do not apply registered-owner assumptions without first classifying the instrument. Good delivery also depends on the receiving party’s requirements and any restrictions or legends. Record receipt and disposition in the securities trail, and avoid forwarding a defective package to a transfer agent as though its paperwork were complete.
Worked example: A certificate for 120 shares names Ada as registered owner. Its stock power is signed by Ben, with no power of attorney or other authority for Ben in the file. Operations identifies a signature-authority defect and holds the transfer package. It obtains a valid owner endorsement or documentation establishing Ben’s authority before sending the 120 shares for re-registration.
Watch the distinction: An attached stock power does not cure a mismatched signer by itself. Match the signer to the registered owner or documented representative authority.
Reference: [2]
20. Electronic registration and depository movement
Electronic ownership and electronic movement are related but distinct. Under the Direct Registration System, an investor’s position is recorded in the investor’s name on the issuer or transfer agent’s books without a paper certificate. Deposit/Withdrawal at Custodian is a depository process for moving eligible positions between a transfer agent and a depository participant. To bring issuer-recorded shares into a brokerage account, operations first confirms the share balance, registration, eligibility, and receiving account details, then uses the supported transfer channel and reconciles the receipt. A proposed sale should not be treated as ready for delivery merely because the customer can see the shares on an issuer statement. Determine when the broker actually receives a deliverable position and whether any restriction affects it. Practice applying these distinctions with Series 99 practice questions.
Worked example: A customer holds 300 issuer-recorded shares and asks the broker to sell 100. Operations confirms the 300-share direct-registration position and requests movement through the channel supported for that security and transfer agent. Once 100 shares are received and reconciled in the brokerage account, the firm can process the sale under its controls. The issuer statement alone is not proof of broker delivery.
Watch the distinction: DRS identifies where ownership is recorded; DWAC describes a depository movement process. Do not confuse an issuer-recorded balance with shares already available in the brokerage account.
Reference: [2]
21. Restricted securities and legends
A restrictive legend warns that a certificate cannot be treated as freely transferable simply because the owner possesses it. Operations should identify whether the shares are restricted securities acquired in an unregistered transaction, control securities held by an affiliate, or both. Those classifications affect the available resale path. A review then considers the acquisition date, how the shares were obtained, the seller’s affiliate status, the issuer’s reporting status, and any applicable resale conditions. Reporting status can affect the holding-period analysis, but a completed holding period alone does not establish that every other condition is met. The transfer agent generally needs appropriate documentation before removing a legend. Keep the position restricted in the firm’s records until the review and transfer process support release. The Series 99 content outline identifies legends and reporting status as custody topics.
Worked example: Two owners present similarly legend-bearing certificates. The first issuer files reports; the second does not. Even if both owners acquired their shares on the same date, operations cannot apply one holding-period conclusion to both. It records each acquisition history, issuer status, and owner relationship, then obtains the required resale and transfer review before accepting either certificate as freely deliverable.
Watch the distinction: A legend is not removed automatically when a calendar period ends. Holding time is one fact; issuer status, affiliate status, acquisition history, and other resale conditions can still matter.
Reference: [2]
22. Trade reporting and late corrections
A correction has two connected jobs: repair the firm’s economic records and repair the report sent to the relevant trade reporting facility. Start with the original execution evidence, including time, security, price, capacity, parties, and quantity. Determine whether the error arose in execution, allocation, booking, or reporting; that distinction controls which records need adjustment. A late discovery does not turn the trade into a new Wednesday execution. The reporting correction should retain the Monday execution context and use the procedure of the applicable facility, while the customer, counterparty, clearing, and ledger records are reconciled to the same actual trade. Check whether settlement or a prior confirmation has already occurred, since those events may require additional corrections or notices. Preserve the audit trail showing both the original entry and its amendment.
Worked example: A Monday execution was 600 shares, but the firm booked and reported 900; staff discover this Wednesday. The overstatement is 900 minus 600, or 300 shares. They verify the execution record, reduce the booked quantity by 300, reconcile settlement and any confirmation, and submit the appropriate amendment referencing Monday’s trade. Wednesday is the discovery date, not the execution date.
Watch the distinction: Changing the customer ledger alone leaves an incorrect external trade report. Reporting a fresh Wednesday trade also misstates when the original 600-share execution occurred.
Reference: [2]
23. Trading capacity, quotes and execution quality
Capacity describes the firm’s role in a transaction. Acting as agent means arranging a trade for a customer with another party; acting as principal means buying from or selling to the customer for the firm’s own account. Capacity affects confirmation details, compensation analysis, and the evidence used to examine execution quality. Begin with the order and execution records, then trace the offsetting position through inventory and clearing. Compare the reported capacity with what the firm actually did; an inventory entry is a strong clue, but an apparent mismatch still needs investigation because booking sequences can be complex. To review execution quality, use contemporaneous quotes and available market information, the order’s instructions, execution time, price, size, and any fees. A favorable quote viewed later is not proof of what was available when the order executed.
Worked example: A customer confirmation calls a 200-share sale an agency trade, while the inventory record shows 200 shares leaving the firm’s position to fill that customer order. Operations flags the mismatch and checks order, execution, inventory, quote, and confirmation records. If the firm sold its own shares to the customer, it corrects the capacity and related records through the controlled process.
Watch the distinction: A confirmation label does not establish capacity by itself. Nor does the best displayed price at some later moment prove that an earlier execution was poor.
Reference: [2]
24. Error accounts and trading abuses
An error account provides a traceable place to book a genuine firm trading error while its financial effect is resolved. It is not a pool from which staff may choose who receives favorable or unfavorable outcomes after prices move. Identify the original order, intended account, execution time, allocation instruction, and point of failure. Correct the customer record according to those facts, measure any resulting firm gain or loss, and keep the approval and audit trail. A pattern of late allocations that systematically favors the firm or selected customers can indicate trading abuse rather than clerical mistakes. Operations should also distinguish a wrong-account correction from misconduct such as trading ahead, excessive trading, or manipulation; the same records may reveal both. Escalate apparent self-dealing without changing the evidence to make an allocation look timely.
Worked example: A trader executes an order for the wrong account. After the market moves, the trader proposes giving the loss to the customer but keeping a profitable fill in the firm’s error account. The allocation depends on the original order and error, not the later price. Operations preserves timestamps and instructions, blocks the selective reassignment, and escalates the proposal for review.
Watch the distinction: Calling a posting an “error correction” does not make it fair. Moving losses to customers after outcomes are known can conceal an improper allocation.
Reference: [2]
25. Margin equity and loan balance
In a long margin account, equity is the market value of the securities minus the debit balance owed to the broker-dealer. The securities are account assets, but the customer has borrowed part of their purchase cost; a higher account value does not mean the full value is withdrawable. Recalculate equity when market prices or the loan balance change. For a margin review, compare equity with the applicable requirement for that account and security, often expressed as a proportion of market value, and account for any stricter firm requirement. A decline in price can lower both the asset value and equity while the debit stays fixed, increasing the loan’s share of the account. A margin deficiency does not automatically specify how it must be met; available responses depend on the applicable rules, firm terms, and account facts. The Series 7 study guide provides related customer trading context.
Worked example: Securities worth $20,000 support a $9,000 debit, so equity is $20,000 minus $9,000, or $11,000. If their value falls to $16,000 with no loan payment or added borrowing, equity becomes $7,000. The customer has lost $4,000 of equity. Whether a call exists requires comparing that $7,000 with the account’s applicable requirement.
Watch the distinction: Subtracting the debit only when the account is opened overstates later equity. The loan remains owed when securities decline, so the full market value is not the customer’s equity.
Reference: [2]
26. Margin eligibility and documentation
A cash account and a margin account have different permissions and obligations. Before booking a purchase that requires a broker loan, operations must establish that the customer account is eligible for margin, the necessary agreement and approvals are in place, and the security itself is eligible under the applicable requirements and firm terms. A readily traded security is not automatically marginable, and account approval does not make every product eligible. Margin documentation addresses the customer’s borrowing relationship and the firm’s rights concerning pledged securities; required disclosures explain material costs and risks. Check account registration as well as product characteristics, because some account types have different borrowing limits or restrictions. If the purchase cannot be funded in the existing account, resolve the funding or authorization problem before treating it as a margin transaction. Do not create an unapproved debit by assuming later paperwork will cure it.
Worked example: A customer with a cash account orders securities costing $12,000 but has only $8,000 available. The proposed $4,000 loan would require margin authority. The account has no margin agreement or approval, so operations cannot simply book a $4,000 margin debit. It checks whether the customer will provide funds or whether a properly approved margin arrangement is possible before processing the purchase accordingly.
Watch the distinction: Marketability of the security does not authorize borrowing. The customer’s account permissions, documentation, and the security’s margin eligibility must each support the transaction.
Reference: [2]
27. Initial and maintenance margin calls
An initial margin review asks whether a new purchase has sufficient qualifying funding at the time it is made. A maintenance review asks whether an existing position still has the required equity after prices, balances, or positions change. Both involve equity, but the cause and calculation context differ. First establish market value and debit balance, then calculate equity. Next apply the appropriate requirement for the security, account, and firm. If required equity exceeds actual equity, the difference is the deficiency in dollars. A call documents that shortfall; it is not the same as the account’s entire loan balance. Review deposits, withdrawals, open orders, and other positions before concluding how much additional funding is needed. If a price drop created the shortfall, label it as a maintenance issue rather than recasting it as a new purchase.
Worked example: Assume, solely for this example, that an existing account must hold $5,000 of equity and currently has $4,200 after a price decline. Its maintenance deficiency is $5,000 minus $4,200, or $800. A separate proposed purchase requires its own initial-funding calculation; paying the $800 deficiency does not, by itself, establish that the new purchase is sufficiently funded.
Watch the distinction: “Margin call” does not identify the cause. A shortfall from a new purchase and one from a later market decline require separate analyses, even if their dollar amounts match.
Reference: [2]
28. Short sales, locates and borrowing
A short sale creates a delivery obligation even though the seller does not own the shares being sold. Before executing, the broker-dealer must satisfy the applicable locate requirement by having reasonable grounds to believe shares can be borrowed and delivered when due. A locate is a pre-trade basis for that belief, not an actual transfer of shares or a promise by a lender. After execution, the firm still must arrange delivery through borrowing or another valid source. Record the locate evidence, expected source, loan arrangements, and settlement status separately. If the source fails, identify the resulting fail to deliver and pursue replacement shares or the applicable close-out process. The timing and method of a required close-out depend on the governing rule and transaction facts. Do not relabel a failed delivery as a defective locate without examining what was reasonably known before the sale.
Worked example: A firm documents a valid locate for a 500-share short sale. Its expected lender then cannot supply the shares on settlement. The locate supported the pre-trade decision, but zero shares arrived from that lender, leaving a potential 500-share delivery problem unless another source supplies them. Operations seeks replacement stock, records the fail if delivery is missed, and applies the relevant close-out requirements.
Watch the distinction: A locate does not place 500 shares in the firm’s account. Treating it as completed borrowing can hide a settlement fail and delay its resolution.
Reference: [2]
29. Stock loan and day-trading buying power
A stock loan transfers securities to a borrower against collateral under an agreement that requires the borrower to return equivalent securities. The firm tracks the number and type of shares, lender, collateral, fees, recalls, and return status. A lender recall does not cancel the short position supported by the loan; the borrower must return the shares or obtain replacements while meeting its delivery duties. Day-trading buying power is a separate account measure. It represents conditional capacity for eligible trading under margin rules and firm controls, based on account equity and other factors. It is not cash held for the customer and cannot be treated as a withdrawal balance. A trade may consume buying power without changing available cash by the same amount. For a question combining the two subjects, identify the securities delivery obligation first and the customer’s trading limit independently.
Worked example: A firm borrows 300 shares to settle a short sale. When the lender recalls the loan, the firm must return or replace 300 equivalent shares; the recall does not mean the original short seller bought them back. Separately, if a customer screen displays $20,000 of day-trading buying power, that figure describes conditional trading capacity, not $20,000 available for a cash withdrawal.
Watch the distinction: Stock loan shares are not permanently acquired by the borrower. A displayed day-trading limit is also not a cash balance merely because it appears as a dollar figure.
Reference: [2]
30. Trade comparison and don't-know responses
Trade comparison checks whether both sides agree on the economic terms needed for clearing and settlement: security, side, quantity, price, trade date, parties, and settlement details. A mismatch is a comparison break, so the team should inspect execution evidence before sending or relying on settlement instructions. A “don’t know” response signals that a purported trade or its stated terms are disputed; it is a prompt to investigate, not permission to erase the counterparty’s claim. Work from time-stamped orders, executions, allocations, and communications, then determine which entry must be corrected. Quantity errors can create a large money difference even when the price matches. Once both sides agree, update the comparison and downstream records consistently. For extra scenarios, Series 99 practice questions can help you rehearse that sequence.
Worked example: One side records 400 shares at $25, a $10,000 trade. The other records 40 shares at $25, a $1,000 trade. The quantity break is 400 minus 40, or 360 shares, and the gross value difference is $9,000. Operations checks the execution and allocation records, resolves the correct quantity with the counterparty, and updates settlement instructions to match.
Watch the distinction: Matching prices do not make the trades matched. A 360-share quantity difference changes the delivery and payment obligations and must be resolved before settlement.
Reference: [2]
31. Clearing brokers and continuous net settlement
An introducing firm may originate customer business while a carrying or clearing firm maintains specified customer accounts, custody, clearing, and settlement functions under their agreement. Identify which firm holds each operational obligation rather than assuming the executing or introducing firm performs every later step. A clearing facility can further reduce the number of securities deliveries through continuous net settlement, where eligible purchases and sales of the same security for a participant are offset into a net position. Netting changes how much the participant must deliver or receive, but it does not erase underlying customer trades, confirmations, or account allocations. Cash obligations and exceptions must be reconciled alongside the securities net. A transaction outside the applicable netting service may settle separately. When solving a netting problem, group only eligible obligations for the same security and settlement context, then subtract deliveries from receipts.
Worked example: For one eligible security and settlement cycle, a participant buys 1,000 shares and sells 700. Its net securities position is a receipt of 1,000 minus 700, or 300 shares, through the net settlement process. The two gross trades still appear in the relevant customer and firm records; only the participant’s clearing delivery is netted, subject to the facility’s rules.
Watch the distinction: Netting 700 shares against a purchase does not delete the 700-share sale. Customer accounts still need the correct gross trades, even when clearing uses one net movement.
Reference: [2]
32. Delivery versus payment
Delivery versus payment links release of securities to the corresponding payment, commonly through a customer’s designated custodian and the broker-dealer’s settlement arrangement. The parties compare instructions in advance, including security, quantity, money amount, settlement date, and account identifiers. On settlement, the custodian should pay against a matching securities delivery rather than sending cash on an unmatched instruction. If fewer shares arrive, operations should identify whether there is a partial-delivery arrangement or a break requiring corrected instructions. Do not presume the custodian may release a proportional payment; the transaction terms and settlement system control that decision. A mismatch can stem from an allocation error, unavailable shares, or incorrect standing settlement instructions, so trace the source before changing records. The aim is to avoid paying for securities that have not been properly delivered.
Worked example: A custodian’s instruction calls for 2,000 shares against $50,000, an implied $25 per share. Only 1,900 shares arrive, so 100 shares are missing; their implied value is $2,500. The $50,000 instruction does not match the delivery. Operations investigates the shortage and obtains matching instructions or delivery before releasing the full payment.
Watch the distinction: DVP does not mean payment is safe merely because some shares arrive. The delivered quantity and payment must match the authorized settlement terms.
Reference: [2]
33. Repurchase agreement settlement
A repurchase agreement joins two movements: one party sells securities for cash now and agrees to buy them back later at an agreed price. Economically, the cash receiver obtains short-term financing secured by the securities, while the price difference represents the financing cost for the stated term. Operations must track the opening cash and securities delivery, the agreed repurchase date and price, collateral details, and the closing return of cash and securities. The reverse side of the transaction is a resale agreement for the cash provider. A complete reconciliation therefore follows both legs, not only the initial receipt of money. Changes in collateral value or a failure by a counterparty can create exposures addressed by the agreement’s terms. Without a stated term and day-count basis, the dollar cost can be calculated but an annualized financing rate cannot be justified.
Worked example: In a hypothetical repo, a firm delivers securities and receives $1,000,000 today. It agrees to return $1,001,000 later to repurchase those securities. The financing cost is $1,001,000 minus $1,000,000, or $1,000. At the closing leg, operations verifies the $1,001,000 cash payment and return of the agreed securities; the term is unspecified, so no annualized rate is calculated.
Watch the distinction: Recording only today’s $1,000,000 receipt leaves the firm’s repurchase obligation untracked. The later cash payment and securities return are essential settlement obligations.
Reference: [2]
34. Fails, buy-ins and close-outs
A comparison break means counterparties have not agreed on trade terms. A settlement fail occurs when an agreed obligation is not delivered or paid as due. The distinction directs the investigation: verify terms before settling a break, but trace inventory, borrow, depository, or counterparty delivery when a matched trade fails. For a securities delivery fail, calculate the undelivered quantity and record its age and source. Seek the stock through permissible channels and apply the relevant buy-in or close-out process when required; those remedies have different triggers and procedures depending on the transaction and rule. Keep customer, clearing, and stock records aligned as the fail is resolved. Do not rewrite a valid matched execution to eliminate the apparent shortage, because that would conceal the true obligation and could corrupt downstream reporting.
Worked example: Both parties agree on a sale of 800 shares, but only 500 shares are available for delivery on settlement. The undelivered amount is 800 minus 500, or 300 shares. Operations records and investigates a 300-share delivery fail, seeks the missing shares, and follows the applicable buy-in or close-out path. The matched 800-share trade remains the underlying obligation.
Watch the distinction: A 300-share fail is not a 300-share comparison error when both parties agree on 800. Changing the trade quantity would hide the delivery problem.
Reference: [2]
35. Statements and performance reports
An account statement reports holdings, cash, transactions, and balances for a period. A performance report tries to measure investment results, which requires separating market gains and income from deposits and withdrawals. Begin with ending value minus beginning value, then remove net external contributions to find a simple dollar investment change, subject to fees, distributions, and valuation accuracy. A percentage return needs a method that treats the timing of cash flows correctly. A time-weighted approach breaks the period at external flows; a money-weighted approach reflects when and how much the customer invested. Neither follows automatically from two statement balances. Review pricing sources and any corrected transactions before publishing performance. A statement can be accurate as an accounting record while a return inferred from its opening and closing balances is misleading.
Worked example: An account begins at $10,000, receives a $1,500 deposit, and ends at $12,000. Its balance increased $2,000, but $1,500 came from the customer, leaving $500 of simple investment change if there were no other flows or adjustments. The $2,000 increase is not a 20% return; calculating a defensible percentage also requires the deposit’s timing and a stated method.
Watch the distinction: Dividing the $2,000 balance increase by the $10,000 opening value treats the customer’s deposit as profit. Statements and performance reports answer different questions.
Reference: [2]
36. Trade confirmations and other notices
A trade confirmation records a particular transaction, so verify the security, side, quantity, price, capacity, trade and settlement information, and charges against the execution and account posting. For a sale, gross proceeds generally start with quantity multiplied by price; disclosed charges may reduce the net cash credited. A periodic statement then places that transaction among the account’s broader holdings and activity. Other notices serve different purposes: a prospectus describes a security offering or product, while an activity notice may alert a customer to a non-trade change or action. Delivery requirements and methods vary with the transaction and applicable rules, including electronic delivery arrangements. Operations should not use a prospectus or a later statement as a substitute for checking whether a confirmation accurately reflects the execution. Investigate unexplained differences without assuming every difference is an error.
Worked example: A sale confirmation shows 200 shares at $30, giving gross proceeds of 200 times $30, or $6,000. The account receives $5,970, a $30 difference. Operations checks whether $30 of disclosed charges explains the net proceeds. If the confirmation and supporting records show no such charge, the cash posting or transaction detail needs investigation and correction.
Watch the distinction: A $30 difference does not automatically prove a bad trade price. First distinguish gross trade value from net proceeds and verify the actual disclosed charges.
Reference: [2]
37. Cost basis and tax withholding records
Cost basis, sale proceeds, and tax withholding serve separate recordkeeping purposes. Basis generally starts with the acquisition cost and may change through events such as reinvestments, splits, or other applicable adjustments. Proceeds measure what the disposition produced under the relevant reporting rules. A preliminary gain or loss is proceeds minus adjusted basis, with transaction costs and other adjustments handled according to their proper treatment. Withholding is money remitted toward a tax obligation; it affects the cash delivered to the customer but does not itself reduce economic gain. Operations should trace lots, acquisition dates, corporate actions, and transferred basis information when reconciling reported figures. If basis is missing or disputed, preserve the known transaction facts and follow the appropriate correction path rather than inventing an acquisition cost. Tax forms then communicate the supported figures.
Worked example: Assume a customer sells shares for $4,800 gross, their adjusted basis is $3,500, and $100 is withheld, with no fees or other adjustments. Preliminary gain is $4,800 minus $3,500, or $1,300. Cash paid is $4,800 minus $100, or $4,700. The $100 withholding changes cash distribution, not the $1,300 gain calculation.
Watch the distinction: Subtracting withholding from gain confuses tax payment with investment cost. A $100 withholding does not turn a $1,300 gain into $1,200.
Reference: [2]
38. General ledger and regulatory reporting
The general ledger organizes the broker-dealer’s financial position from supported transaction postings. Subledgers, bank records, custody records, and the ledger should reconcile; an unmatched item must be traced to its source and period. A missing outgoing wire makes recorded cash too high if the bank has already paid it. The balancing entry depends on why the firm sent the wire: a customer withdrawal may reduce a customer payable, while a vendor payment may reduce a payable or record an expense. Do not choose that offset merely to force the reconciliation to zero. The financial and operations principal oversees the integrity of financial records and reporting processes, including analysis of capital and reporting effects. The Series 27 study guide covers that principal role in more detail; an operations analyst supplies accurate records and escalates material exceptions.
Worked example: The bank shows a $20,000 wire that the general ledger omits. Assuming it cleared, ledger cash is overstated by $20,000. Operations obtains the approved wire and identifies its purpose, then posts a $20,000 cash credit with the supported offset. It rechecks the bank reconciliation and assesses whether any pending financial report used the overstated cash balance.
Watch the distinction: A reconciliation is not complete when someone inserts a balancing entry without support. The wire’s purpose determines the other side of the posting and its reporting effect.
39. Net capital mechanics
Net capital is a regulatory measure of a broker-dealer’s available financial resources, calculated from its accounting net worth with prescribed adjustments. Start with net worth, remove assets that cannot readily support obligations under the rule, and deduct applicable securities haircuts and other charges. Some allowable adjustments can also matter, so a short classroom formula is only an illustration. Compare the result with the requirement that applies to the firm’s activities and circumstances; the requirement is not the same for every broker-dealer. A firm may have positive accounting equity yet insufficient regulatory net capital because some assets are illiquid or its positions create charges. Review source balances, valuation, classification, and dates before relying on the figure. An operations professional helps maintain and reconcile the inputs, while responsible financial supervision evaluates the calculation and any required response.
Worked example: Assume a simplified firm has $500,000 net worth, $80,000 of nonallowable assets, and $30,000 of applicable charges, with no other adjustments. Illustrative net capital is $500,000 minus $80,000 minus $30,000, or $390,000. If its separately determined, hypothetical applicable requirement were $350,000, excess would be $40,000. An actual filing requires the full rule-based calculation.
Watch the distinction: Net worth is not automatically net capital. Nonallowable assets and position-related charges can reduce the regulatory measure even though accounting equity stays positive.
40. Customer reserve calculation
The customer reserve calculation is part of protecting customer funds from use as the broker-dealer’s operating cash. Its formula organizes specified customer credit balances and permitted debit items; a net credit indicates funds that must be addressed through the special reserve framework. Credits can reflect amounts the firm owes customers, while only qualifying debits reduce the reserve requirement. The calculation therefore needs accurate customer ledgers and correct classifications, not simply the firm’s bank balance. Reconcile inputs to underlying accounts, investigate stale or unsupported items, and account for the calculation date and governing deposit process. A reserve bank account has a distinct purpose from an ordinary operating account. A simplified credits-minus-debits exercise teaches the direction of the calculation, but the actual requirement includes detailed definitions, adjustments, timing, and firm-specific facts. Do not count an unsupported debit merely to lower the result.
Worked example: Assume, for a simplified exercise, eligible customer credits total $900,000 and permitted debits total $650,000, with no other adjustments. The net credit is $900,000 minus $650,000, or $250,000. That amount belongs in the customer reserve analysis rather than being treated as free operating cash. Actual deposit obligations require the full calculation and applicable timing rules.
Watch the distinction: A positive bank balance does not replace the reserve formula. Customer credits and permitted debits determine the simplified net amount; firm operating cash serves a different purpose.
41. Reconciliation and timely posting
A reconciliation compares records made from different evidence, such as the firm's cash ledger and a bank statement. Start with the same account and cutoff date, then list transactions recorded on one side but absent from the other. A documented deposit in transit is a timing difference; an unexplained withdrawal is a possible error or shortage. For each difference, identify its source document, amount, date and expected clearing path. Post a correction only when evidence shows that a ledger entry is wrong or missing. Do not force the balances to agree with an unsupported plug. Timely posting matters because stale records can distort customer balances, financial reports and control decisions. The operations professional should investigate exceptions and preserve the work showing how each was resolved. The related financial oversight role is covered in the Series 27 guide.
Worked example: At the same cutoff, the firm's bank ledger shows $75,000 and the bank statement shows $70,000. A deposit receipt and transaction record support a $5,000 deposit made before cutoff but not yet credited by the bank. Bank balance $70,000 plus $5,000 in transit equals the $75,000 ledger balance. Keep the item open and verify that the bank credits $5,000; if it does not, investigate.
Watch the distinction: Matching totals does not prove every transaction is correct. Two errors can offset each other, so compare underlying items and clear each exception with evidence.
42. Books, records and electronic preservation
Creating a record and preserving it solve different problems. A trade record should capture the transaction accurately when it occurs, including its account, terms and timing. Preservation keeps the record retrievable and protects the history of later changes. If an account number is wrong, identify the authoritative order and execution evidence, correct the affected record through a traceable entry, and retain who changed it, when, why and what the previous value was. Check downstream confirmations, statements, settlement instructions and reports for the same error. Electronic storage controls must support retrieval and guard against improper alteration or loss; simply placing a file on a shared drive does not establish that. FINRA's Series 99 content outline identifies record creation, retention and electronic storage as operations topics. The operations professional applies these controls to the records touched by the firm's covered functions.
Worked example: A trade for 200 shares was executed for account A, but the entry names account B. The order and execution records support A. Operations retains the original entry and its time stamp, posts a documented correction from B to A, and checks both accounts' confirmations and positions. Deleting the B entry without an audit trail would conceal the original error.
Watch the distinction: A correct final screen is not enough. If the old value disappears without a trace, reviewers cannot reconstruct the transaction or determine who corrected it.
F2: Professional Conduct and Ethical Considerations
43. Customer and public communications
An operations employee may communicate about balances, transfers, sweeps or delays without presenting a sales pitch. Those messages can still make substantive claims about a product or service. Read each claim as a customer would: Does it describe risk, availability, yield or protection accurately, and does it omit a condition that changes the meaning? A sweep destination might differ from brokerage cash in its features, access procedures and risks. An absolute promise about safety or immediate access needs support in the actual product terms; a broad assurance cannot substitute for them. Before release, confirm the product identified, the customer's relevant arrangement and the current approved description. Route public or customer communications through the firm's review controls when required. Keep an approved version and evidence of delivery where applicable. Operational urgency does not make an inaccurate statement acceptable.
Worked example: A service draft says a customer's sweep product is “risk-free and always available.” The employee checks the designated sweep vehicle and its disclosure, removes both absolute claims, and states the applicable redemption and access terms in plain language. The revised message goes through the required review before delivery. The customer receives usable information without an unsupported guarantee.
Watch the distinction: Calling a message “service only” does not excuse a product claim. Its content and likely customer interpretation determine whether accuracy and review controls matter.
Reference: [2]
44. Payments and registered activity
Classify a payment by what the recipient does and how the amount is earned. A fixed fee for software hosting or document processing ordinarily compensates an operational service. A payment tied to customer referrals, securities transactions or commissions raises a different question: whether the recipient is performing activity that requires registration and whether the compensation arrangement is permitted. The invoice label cannot change the underlying economics. Trace who solicits or refers customers, whether the vendor discusses securities, how the payment formula works and which firm approves it. Hold a questionable payment while the responsible registration and compliance personnel review the facts. This protects against using a vendor contract to route transaction-based compensation to an unregistered person. It also helps the firm record the expense accurately, since a commission-linked referral payment is not the same business event as a routine technology bill.
Worked example: A vendor maintains the firm's appointment software for a monthly fee. It then proposes receiving 8% of commissions from customers it refers. The proposed fee rises with securities activity, and the vendor is sourcing customers. Operations stops the new payment, records the proposed formula and activities, and sends them for registration and compensation review. Renaming the invoice “service fee” would not resolve the issue.
Watch the distinction: A vendor's existing contract does not authorize every new payment term. A commission-based referral arrangement needs review based on the activity and payment formula.
Reference: [2]
45. Soft dollars and commission arrangements
A soft dollar arrangement uses brokerage commissions to obtain research or brokerage services for an investment decision process. It creates a conflict because the person choosing where to trade may receive a benefit while customers bear commission costs. Analyze the actual item purchased, its connection to research or brokerage work, whether the commission arrangement is permitted, and whether trading decisions remain consistent with obligations owed to customers. General office equipment or furniture serves the manager's business rather than investment research merely because a broker supplies it. An operations professional may see the conflict in commission schedules, invoices or broker allocation instructions. Preserve those details and escalate a questionable arrangement before changing allocations or paying an invoice. Oversight should compare the stated service with what was delivered and watch for trading volume generated chiefly to earn a benefit.
Worked example: A manager wants to route more customer trades to Broker X because X will provide office furniture. The proposed benefit is furniture for the manager's workplace, not research used in investment decisions. Operations records the proposed trade allocation and benefit, does not treat the furniture as an ordinary research expense, and escalates the arrangement. Extra trading to obtain it could add customer costs without a trading reason.
Watch the distinction: “Soft dollars” is not a blanket permission to buy business supplies with commissions. The benefit's purpose and the effect on customer trading both matter.
Reference: [2]
46. Vendor due diligence and ongoing oversight
Outsourcing a task changes who performs it, but the broker-dealer still needs to know whether the work is controlled and can be verified. Evaluate a vendor against the task's risks: what customer information or assets it can reach, who can change instructions, how changes are approved, what audit evidence is retained, and how service continues after an outage. Performance measures should test accuracy as well as speed. For a provider handling transfers, the ability to identify the person, time, prior value and approval behind a payment-instruction change is especially important. Document deficiencies, resolve material gaps before relying on the service, and monitor exceptions after launch. Reassess when the vendor's access, systems or duties change. A clean initial review is only a starting point; recurring errors or missing logs can reveal a control failure during operation.
Worked example: A proposed transfer service completes requests quickly but cannot show who replaced a customer's payment destination. Speed does not establish that the new destination was authorized. Before using the service, the firm requires a change log, independent approval evidence and a way to retrieve both. If the vendor cannot provide them, the firm must choose a controlled process for those requests.
Watch the distinction: A vendor's efficiency does not transfer accountability for customer assets. The firm must be able to oversee the service and reconstruct sensitive actions.
47. Confidential customer information
Customer data should move according to a work need, not merely because the requester works for the firm. First define the task and the smallest record needed to complete it. Then verify the recipient's role and use an approved channel with appropriate access and retention controls. An employee troubleshooting one transfer may need that account's transaction identifier and status, not a full list of customer balances. The same reasoning applies outside the firm: identify the recipient, purpose and data elements before sharing. Broader access increases the chance of unauthorized use, mistaken distribution and exposure after a system compromise. If an unusual request appears legitimate but exceeds the requester's normal duties, seek authorization through the established access process and record the business reason. Need-to-know is a practical way to limit both the number of viewers and the amount each viewer sees.
Worked example: A marketing colleague asks for a spreadsheet containing 4,000 customer balances to investigate one delayed transfer. Operations locates the transfer's account ID and status, confirms the colleague's assigned role, and sends only information needed through the approved channel or routes the task to the proper service team. The broad balance file is not necessary for this investigation.
Watch the distinction: Being a coworker does not grant access to every customer file. Internal sharing still requires a defined task, appropriate entitlement and limited data.
Reference: [2]
48. Privacy notices and information sharing
A privacy notice describes a firm's information practices and customers' applicable choices. It does not independently approve every later transfer of customer data. For each proposed sharing event, determine the purpose, recipient, permitted use and minimum fields required. Check the applicable privacy terms and vendor controls, then use a secure, authorized channel. A service provider may need an account identifier to post a transaction while having no reason to receive a Social Security number. Keeping those fields separate reduces harm if data is sent to the wrong place or exposed. Operations should also know whether the recipient may retain, reuse or pass the information onward, because those facts affect oversight. Record what was shared and why when the process calls for it. A valid servicing relationship is relevant, but the data set still needs a task-specific justification.
Worked example: A servicing vendor matches daily transactions using account IDs. A team proposes adding every customer's full Social Security number to the file. Operations confirms that account IDs complete the match, removes the unnecessary numbers, checks the approved sharing arrangement and sends the limited file through the authorized channel. The vendor relationship does not justify the extra identifiers.
Watch the distinction: Delivering a privacy notice does not make unlimited data sharing acceptable. The particular recipient, purpose and fields still require review.
Reference: [2]
49. Beneficial-owner information elections
A beneficial owner holds the economic interest in securities carried in an intermediary's name. For issuer-related ownership information, records distinguish a non-objecting beneficial owner, or NOBO, from an objecting beneficial owner, or OBO. That election affects whether identifying information may be provided through the authorized intermediary process. It does not change whether the customer owns the position or receives the economic benefit. When an issuer requests a holder list, operations should verify the request's channel and purpose, use current position and election records, and separate eligible NOBO information from protected OBO identities. Counts or other permitted information may be handled differently from names and addresses, so do not treat every field as equivalent. Reconcile the list to the relevant record date and investigate inconsistent elections before release. The key decision is which identities may be disclosed, not whether the securities exist.
Worked example: An issuer requests holders as of a stated record date. The intermediary finds 120 beneficial-owner accounts: 85 marked NOBO and 35 marked OBO. It validates the date and elections, then processes identifying information for the 85 NOBO accounts through the authorized channel. It does not add the 35 OBO names to that identifying list merely to make the total equal 120.
Watch the distinction: OBO does not mean the customer lacks ownership or issuer-related rights. The election concerns disclosure of identifying information through the intermediary.
Reference: [2]
50. Identity theft red flags
Identity theft concerns often emerge from a sequence rather than a single event. Compare a requested action with the account's recent access, contact changes, usual behavior and payment destinations. A new device alone may be harmless; a new device followed by an address change, a phone change and an urgent third-party wire gives several independent reasons to question whether the true customer is acting. Pause the sensitive action under the firm's control process, preserve the request and change history, and verify through a reliable channel that was established before the suspicious changes. Do not rely on the newly supplied phone number to validate the same change. Escalate the pattern so the responsible team can assess account protection and reporting. Practice identifying which facts change the decision in Series 99 practice questions.
Worked example: At 10:00, an account is accessed from a new device. At 10:05, its address and phone number change; at 10:12, a third-party wire is requested. Operations pauses the wire, retains the access and request records, and contacts the customer using a previously verified route. The new phone number is part of the suspicious sequence, so it cannot independently confirm the request.
Watch the distinction: A successful login does not prove the customer authorized later changes. Stolen credentials can make an unauthorized sequence appear technically valid.
Reference: [2]
51. Information barriers and access entitlements
An information barrier limits the flow of confidential information between people whose duties create different needs and risks. Access entitlements put that barrier into system permissions. Start with the analyst's actual task: a settlement employee may need trade identifiers, quantities and delivery status, but not a pending block order unrelated to settlement. Compare assigned permissions with that task, remove excess access, and review logs when exposure may already have occurred. The review should distinguish mere entitlement from an actual file opening, download or disclosure, because each calls for a different response. Changes in role, team or project should trigger another entitlement check. A screen that is easy to open is not evidence that viewing it is authorized. Operations professionals who define or approve information entitlements should make permissions specific enough to perform the work while limiting unrelated confidential trading data.
Worked example: A settlement analyst can open a pending block-order file despite needing only executed trade identifiers. The access team removes that permission and checks logs. If logs show no access, it documents the excess entitlement and fix. If the file was opened or shared, the firm investigates what was viewed, by whom and whether further action is needed.
Watch the distinction: Permission granted by a system administrator is not proof of business need. Entitlements can outlive duties or be configured too broadly.
52. Recognizing a customer complaint
A complaint is recognized from what the customer alleges, not from the channel used or the employee's first view of the facts. A written statement that the firm moved securities without permission alleges improper firm conduct even if it arrives in a service inbox. Capture the customer's words, date, account and transaction identifiers, then route the matter through the complaint process. Investigate the transfer separately using instructions, authority records and the audit trail. Do not wait to classify the message until the allegation is proved; the complaint record describes what was asserted. An ordinary status question can become a complaint when the customer attributes a problem to firm error or misconduct. Prompt recognition lets supervisors examine the event, respond consistently and assess any further obligations. Operations staff should avoid promising an outcome before the records establish what happened.
Worked example: A customer emails, “Your firm moved my shares without my permission.” The service employee records the email as a written allegation, identifies the transfer and escalates it. The employee also collects the signed instruction and processing history for review. Even if those records later support authorization, the original message remains a complaint and the investigation result is documented separately.
Watch the distinction: A complaint does not require a formal form or proof that the customer is right. The allegation itself triggers recording and escalation.
Reference: [2]
53. Preserving and escalating complaint evidence
Complaint handling depends on preserving both the customer's original account and the firm's transaction history. Keep the incoming message with its date and context, identify related instructions and system events, and prevent later corrections from erasing earlier entries. If a transfer was posted incorrectly, correct the account through a documented adjustment that shows the original posting and the reason for change. Route the complaint and evidence to the responsible reviewers promptly, including any employee request to remove or alter evidence. A clean current balance does not answer whether the prior transaction harmed the customer or whether controls failed. Separate three records in your reasoning: what the customer reported, what the system originally did, and what remediation followed. That sequence supports a reliable response and lets reviewers assess whether the problem extends beyond one account.
Worked example: A customer alleges an unauthorized transfer, and a representative asks operations to delete the mistaken entry before compliance reads the email. Operations preserves the email and original transfer log, refuses the deletion, and posts any supported correction with a traceable reason. It escalates both the complaint and the deletion request. Reviewers can then see the event, correction and attempted interference in order.
Watch the distinction: Fixing an account balance does not justify removing the old entry. Erasure can conceal the event the complaint asks the firm to investigate.
Reference: [2]
54. Suspicious cashiering patterns
Cashiering review should connect accounts, people, destinations and timing. Several transfers may look ordinary one by one but become unusual when accounts under common control change profiles and send funds to the same newly added payee. Build a timeline of the profile changes, authorizations, amounts, payment methods and receiving details. Compare the pattern with known account purposes and prior activity, and identify whether one actor could be directing all movements. Apply any transaction hold or verification control that the facts trigger, then refer the pattern to the responsible review team. Do not tell a customer that a particular report will or will not be filed. The operations professional's job is to preserve accurate facts and protect the transfer process; the firm's designated personnel evaluate whether suspicious-activity or other external reporting is required.
Worked example: Accounts A, B and C share a controlling person. Each updates contact details on Monday and requests a Tuesday payment to the same new beneficiary. Operations links the three requests, saves the change logs and payment instructions, and applies the relevant verification and hold controls. It refers the combined pattern for review instead of approving each request solely because its individual form is complete.
Watch the distinction: Separate account numbers do not make related transfers independent. Shared control, timing and destination can reveal a pattern that single-request review misses.
Reference: [2]
55. Regulatory escalation and reporting inputs
Regulatory escalation begins with a sound factual record. An operations employee who sees repeated unexplained valuation changes should identify affected securities and accounts, dates, old and new prices, source files, approvers and resulting statement differences. Preserve the underlying records and distinguish a known correction from an unsupported change. Report the pattern promptly through the firm's escalation route; do not decide alone whether an external filing is required. That decision may depend on facts the employee does not have, including cause, scope, customer impact and applicable reporting criteria. The receiving team can assess regulatory obligations and remediation only if the inputs are specific and reproducible. Follow up on unresolved requests for evidence, and avoid editing source history to make statements appear consistent. Clear internal reporting is an operational duty even when the final regulatory conclusion remains open.
Worked example: An analyst finds that the same security's month-end value changed from $42 to $48 per share on statements for 30 accounts without a source note. For an account holding 100 shares, the difference is $600. The analyst preserves both price files, lists affected accounts and dates, and escalates the unexplained changes for investigation and reporting assessment.
Watch the distinction: An employee need not prove a reporting violation before escalating. Waiting for certainty can allow inaccurate records and customer effects to persist.
Reference: [2]
56. Separation of duties
Separation of duties prevents one person from creating a transaction, approving it, sending value and concealing an exception. Map the path from instruction receipt through destination setup, approval, release, bank confirmation and reconciliation. Assign independent review at points where an unauthorized change could cause a loss, especially creation of a new payee and release of a wire. The reviewer needs evidence of the source instruction and authority, not merely a second click. Reconciliation should compare the bank's independent record with the firm's approved transactions and investigate unmatched items. System permissions should enforce the design, while logs show who performed each step. Small teams may need alternative independent controls, but a single unchecked user who controls the whole path creates the same risk regardless of job title. Consider how errors as well as deliberate misconduct could pass through the workflow.
Worked example: One cashiering employee can add a wire destination, approve a $25,000 wire and clear its bank exception. The firm removes that combined permission. One authorized person enters the destination, another verifies the instruction and approves release, and an independent reviewer reconciles the bank debit. The $25,000 payment proceeds only after the destination and approval evidence match.
Watch the distinction: A second person's name on a workflow is insufficient if that person cannot examine the instruction or if the initiator can clear the exception.
Reference: [2]
57. Written supervisory procedures
A written supervisory procedure should tell staff how a controlled activity is performed and how a supervisor can verify it. For an electronic transfer channel, specify who may accept instructions, how authority and destination are checked, who approves exceptions, what evidence is retained and which supervisor reviews results. Name the owner of the procedure and link the review to actual logs or samples. When a channel, system or risk changes, compare the written steps with current work, revise the procedure, train affected people and retain evidence of the change. An obsolete procedure can make routine actions appear compliant while leaving new steps unchecked. The Series 24 principal guide offers related supervision context; the Series 99 operations professional needs to understand and follow the controls governing the functions they perform.
Worked example: A firm now accepts electronic transfer requests, but its procedure still tells staff to inspect mailed signatures. Operations documents the live workflow and its gaps: electronic authentication, new destination approval and audit-log review are unspecified. The procedure owner updates the instructions, assigns reviewers and tests a sample of requests. Staff use the approved path and retain evidence for each transfer.
Watch the distinction: A procedure is not effective merely because it exists. If it describes a channel the firm no longer uses, it cannot guide or evidence current supervision.
Reference: [2]
58. Supervisory testing and certification
Daily supervision, supervisory control testing and senior certification answer different questions. A supervisor's review of an exception log is an operating control: it should decide whether each item was investigated and resolved. Testing examines whether that review worked, often by sampling items and tracing them to source evidence, follow-up and closure dates. A senior-level certification addresses the firm's compliance and supervisory processes; it is not a statement that every transaction was perfect. If a sample reveals unsupported closure, expand the investigation enough to understand scope, repair the process and document the result. Testing should challenge both the design of the control and its actual performance. For example, a log may require sign-off but provide no field for the underlying bank evidence. An operations professional should retain records that let reviewers reconstruct each exception from discovery to resolution.
Worked example: A supervisor signed 40 daily exception logs. A tester selects five closed items and finds two without supporting resolution records. Those two closures cannot be validated from the signatures alone. The firm investigates the two transactions, checks whether similar unsupported closures occur elsewhere, and improves the evidence and review process before relying on the log as proof of effective supervision.
Watch the distinction: A signed checklist is evidence that someone signed it, not proof that every exception was resolved. Testing must inspect the underlying work.
Reference: [2]
59. Physical and system access controls
Least-privilege access gives a person the physical and system permissions needed for current duties. Begin with the role's tasks, then map them to offices, files, applications and specific actions such as viewing, editing or releasing a payment. Granting broad access because it is convenient weakens control over customer information and assets. When an employee changes roles, remove old entitlements and issue only those needed in the new position. Review activity during any gap between the role change and removal, particularly for sensitive functions. A valid login establishes that the system recognized credentials; it does not establish that the user had a business reason to perform every available action. Physical keys and badge rights deserve the same review as software permissions. Periodic entitlement checks should compare actual access with current duties and resolve unexplained privileges.
Worked example: An employee moves from cashiering to research on June 1 but keeps wire-release access until June 15. The access team removes the permission, checks release logs for that 14-day period and investigates any use. If no wires were released, it still documents the stale entitlement and adjusts the role-change process so removal occurs when duties change.
Watch the distinction: Access that was once appropriate does not remain appropriate after a transfer. The role change itself is a reason to review and remove old permissions.
60. Business continuity for critical operations
A business continuity plan identifies how critical operations continue when normal facilities, people or systems are unavailable. On a settlement day, priorities include knowing which deliveries and payments are due, accessing reliable records, assigning authorized staff and keeping an audit trail. Use a tested alternate system or location only with its defined approvals and security controls. Record transactions made during the disruption so they can be entered or reconciled when normal service returns. Communicate through approved channels to relevant counterparties and customers when the event affects them. After recovery, compare alternate-process records with clearing, bank and customer records; duplicate or missing entries are a common risk when work moves between systems. The plan should identify dependencies such as connectivity, depository access and contact information, then be updated when those dependencies change. Continuity means preserving control as well as completing urgent work.
Worked example: A power outage disables the normal settlement workstation at 11:00. The team retrieves the approved alternate queue, identifies two pending deliveries, and uses authorized backup access to process them. It records each instruction, approval and confirmation. Once the primary system returns, operations compares the backup log with depository results and firm records, resolving any missing or duplicate posting before closing the incident.
Watch the distinction: Finishing a delivery during an outage is not the end of the task. Without preserved evidence and post-recovery reconciliation, the firm may lose or duplicate the transaction.
Reference: [2]