How do an introducing broker and an FCM differ when a customer sends money?

An introducing broker solicits or accepts orders but does not accept customer funds for futures trading. The FCM handles the customer account and funds. A branch manager should trace the payment instructions and actual receipt: if a customer hands an IB representative a check intended for the IB, the problem is not cured by forwarding it later. The manager must address the improper receipt and direct future payments through the appropriate FCM process.

Why can a disclosed trading profit differ from an investor’s return?

Trading results may be reduced by commissions, management fees, incentive fees, upfront charges and pool expenses. If a hypothetical $10,000 investment earns $1,200 before costs and incurs $200 in commissions and $300 in other stated fees, the investor has $10,700, a 7% net gain rather than a 12% gross gain. The manager should check which costs a performance figure includes before allowing a comparison or sales claim.

What should a manager do when a stop order is described as a guaranteed exit price?

Correct the description before it is used with customers. A stop price is a trigger under the applicable order terms; a rapid market can produce a different execution price or prevent execution. The manager should review the proposed communication, ensure the relevant product risks are disclosed, and examine whether similar claims were made in earlier customer communications.

NFA Series 30 Branch Manager Study Guide

Start with concept 1 Choose a topic

A branch manager’s work is a sequence of decisions: identify who may conduct regulated activity, supervise how orders and customer funds move, check what customers are told, and respond when records or conduct signal a problem. This guide follows the subject areas of the NFA Branch Manager Examination (Series 30) through practical situations. You will trace an order from receipt to confirmation, distinguish an introducing broker’s role from an FCM’s, interpret pool and advisory disclosures, and work through fee and margin examples using stated assumptions. The emphasis is on what a manager can verify, what requires escalation, and how to explain a decision from the facts available.

General supervision and registration

1. Fair dealing as a supervisory standard

Fair dealing concerns the impression a customer receives, not just whether each sentence can be defended in isolation. A branch manager should compare a proposed gain illustration with the transaction’s known costs, material risks and assumptions. Ask what amount the customer could actually retain, which inputs are estimates, and whether favorable and unfavorable outcomes receive comparable attention. A signed form does not cure a sales conversation that leaves out a cost the representative knows about. When reviewing a claim, reconstruct its calculation and the surrounding explanation, then correct the communication before it is reused. The NFA Series 30 study outline identifies just and equitable principles and supervision as assessed subjects. Its topic list does not replace the manager’s judgment about the particular claim and customer.

Worked example: A representative tells a customer a proposed trade could gain $900 but omits a known $240 transaction cost. On the stated assumptions, the comparable gain after that cost is $900 − $240 = $660. The quoted figure exceeds that outcome by $240. The manager requires the cost and calculation to appear together and checks whether the gain scenario’s other assumptions are clear.

Watch the distinction: A complete account file does not make a selective gain claim fair. The manager must assess what the customer was led to expect from the whole communication.

Reference: [1]

2. Registration and sponsor checks

An examination result establishes proficiency for its purpose; it does not itself establish current registration, sponsor association or permission to solicit. Before assigning regulated work, the manager identifies the activity, determines the status required for the person and firm, and verifies the live records through the appropriate registration process. The same discipline applies when dealing with another firm: NFA Bylaw 1101 makes membership status relevant to certain business relationships, so an old certificate or verbal assurance is inadequate evidence. Record what was checked, when, and how exceptions were resolved. Changes in sponsorship, termination or temporary status can alter the answer after an initial check. FINRA’s Series 30 page identifies the examination; the branch still has to verify the status that permits the proposed activity.

Worked example: A new hire has passed Series 30, and the sales manager wants the hire to solicit futures accounts immediately. The branch has no confirmation that the hire’s required registration and sponsor association are effective. The manager withholds solicitation duties, checks current status through the firm’s registration process, and documents the result. Passing the exam alone does not authorize the calls.

Watch the distinction: Treating an exam pass as a registration approval skips the activity and sponsor checks. A person can have exam credit while lacking the status needed for assigned duties.

Reference: [1]; [2]

3. Supervisory systems and branch audits

A supervisory system assigns a reviewer, a review method and a response when something fails. Written procedures should tell staff how to detect exceptions, preserve evidence and escalate concerns; an audit tests whether those steps occurred in practice. A missing review mark is a signal, not proof that an order was mishandled. The manager first determines whether the review happened but was poorly documented, or did not happen at all. Next, examine the affected transactions for customer harm and common causes, such as staffing gaps or an unreliable queue. Assign a correction with an owner and deadline, then test a later sample to see whether the process works. A low exception count can still matter if the missing review concerns a serious order problem.

Worked example: An on-site audit samples 20 orders and finds four without evidence of supervisory review. The observed exception rate is 4 ÷ 20 = 20% of the sample; it is not automatically the branchwide rate. The manager investigates all four orders, repairs the review workflow, records who owns the fix, and tests later orders for the same gap.

Watch the distinction: Adding signatures to old tickets without checking the underlying orders can conceal a failed control. The manager needs the order facts and evidence that future reviews occur.

Reference: [1]

4. Order, option and retention records

Order records should let a reviewer reconstruct what the customer instructed, when the firm received it, how it was transmitted and what ultimately executed. A confirmation establishes execution details, but it usually cannot prove the earlier instruction or its timing by itself. For an option order, the manager also checks whether the branch followed its written option procedures, including the applicable review and authorization steps. Keep the functions distinct: a procedure explains how staff should act; a contemporaneous order record shows what occurred in one transaction. When a record is missing, seek reliable source evidence such as recorded instructions or system logs, preserve it, and investigate whether the gap is isolated or repeated. Retention controls matter because later disputes may turn on sequence rather than final price.

Worked example: An option confirmation shows one contract purchased at a stated premium, but the order file has no reliable receipt time or original terms. The confirmation proves the reported execution, not when the customer authorized it. The manager retrieves available call or system records, checks the option procedure followed, and documents any sequence that remains unverified.

Watch the distinction: A correct confirmation is not a substitute for the original order trail. The missing receipt record may prevent the branch from testing authorization, priority or delay.

Reference: [1]

5. Customer deposits and payment routing

An introducing broker may solicit or accept orders, while the carrying futures commission merchant handles the customer account and its funds. That division makes payment routing a supervisory issue: branch staff should not treat a customer deposit as ordinary office mail or redirect it through a branch account. The manager identifies who received the instrument, its payee, whether anyone endorsed or deposited it, and what instructions the customer was given. Preserve the facts and arrange a proper return or correction through the firm’s process. Then test whether sales scripts, account forms or staff training caused the customer to use the wrong route. The customer should receive clear funding instructions for the appropriate FCM account, and the branch should verify that the intended funds actually arrive there before assuming the problem is closed.

Worked example: A customer hands an IB employee a $5,000 check payable to the branch for futures margin. The manager stops the branch from processing it, records who received it and when, and follows the firm’s process for returning or correcting the instrument. The customer receives the FCM’s authorized payment instructions; the branch does not treat the check as available margin.

Watch the distinction: Because an IB accepts orders, staff may assume it can accept margin checks too. Order activity and custody of customer funds are different functions.

Reference: [1]

6. Continuity during a branch outage

A continuity plan should preserve control of customer instructions when normal systems fail. The immediate question is the status of each open or pending order: received, transmitted, acknowledged, filled, canceled or unresolved. Those states call for different actions. An unacknowledged order cannot safely be resubmitted merely because the branch screen is blank; it may already be live. The manager uses approved alternate communications to confirm status with the executing or carrying party, tells staff which channel is authoritative, and records decisions and customer contacts. Supervisory responsibility must remain assigned during the disruption, including review of any orders taken by phone or backup system. After service resumes, reconcile backup records with the normal order book and investigate discrepancies. A usable plan names people, channels and records, not just a backup location.

Worked example: Connectivity fails while three customer orders are pending. One has an execution confirmation, one has an exchange acknowledgment but no fill, and one has no transmission acknowledgment. The manager records those distinct states, confirms the last two through the approved alternate channel, and submits nothing twice until status is established. Recovered system records are reconciled afterward.

Watch the distinction: A blank screen does not mean an order was never transmitted. Blind resubmission can create a duplicate position and a dispute over who authorized it.

Reference: [1]

7. Reportable positions and bona fide hedges

Position reporting and bona fide hedging answer separate questions. Reporting asks whether positions meet applicable aggregation and reporting rules; hedging treatment asks whether a position offsets a qualifying commercial exposure under the relevant rules and exchange terms. A hedge label on a ticket proves neither. The manager should identify the underlying inventory or anticipated transaction, match its direction and size to the futures position, and retain evidence of the economic relationship. An oversized position may contain a supported hedge component plus an unsupported remainder. Position limits and reporting obligations still require their own analysis, including positions held through related accounts. For contract mechanics that underpin this comparison, a Series 3 futures study guide can help; the branch decision turns on documented exposure and the applicable market rules.

Worked example: A firm holds 120 futures contracts against inventory that supports an equivalent exposure of 90 contracts under the stated contract size. The difference is 120 − 90 = 30 contracts. The manager investigates the purpose and treatment of those 30, verifies the 90-contract hedge claim against inventory records, and separately checks reporting and position-limit obligations.

Watch the distinction: Commercial status does not convert every futures position into a bona fide hedge. The quantity and economic relationship need support, while reporting remains a separate question.

Reference: [1]

8. Foreign exchange trading venues

A futures contract listed on a foreign exchange carries terms set by that venue and the route through which the customer trades. Before describing it to a customer, the branch should verify trading hours in the relevant time zones, contract size and currency, delivery or settlement method, order types, market holidays, and how the carrying arrangement handles confirmations and funds. Currency conversion can affect the customer’s account result even when the contract is quoted accurately. The manager also checks which protections and dispute procedures actually apply instead of borrowing descriptions from a domestic exchange product. Distinguish a futures contract traded on a foreign exchange from off-exchange retail forex; similar currency exposure does not make their market structure or disclosures interchangeable. Supervisory review should compare the sales description with verified venue and account terms.

Worked example: A customer expects a foreign-exchange-listed futures contract to trade during the same hours as a familiar U.S. contract. The manager checks the foreign venue calendar and converts its hours into the customer’s time zone before accepting an order plan. The manager also confirms the contract currency and settlement terms, then corrects the representative’s unsupported claim that domestic arrangements automatically apply.

Watch the distinction: A familiar underlying currency does not imply familiar venue rules. Assuming identical hours or protections can make an otherwise accurate contract description misleading.

Reference: [1]

9. Discipline and arbitration serve different purposes

A customer dispute and a disciplinary inquiry may arise from the same trade but seek different decisions. The customer may pursue compensation through an available dispute process; a regulator examines whether conduct rules were broken and what response is appropriate. Neither process should be treated as a substitute for the other. When an unauthorized-trade allegation arrives, the manager preserves original instructions, order and execution records, communications, approvals and the relevant account history. Establish a factual chronology without editing records to make the file look complete. Route the complaint and regulatory request to the responsible personnel, track each response, and avoid promising a result before the facts are assessed. The branch can investigate possible customer harm while also cooperating with the conduct inquiry. A settlement of the customer claim does not by itself resolve the regulatory concern.

Worked example: A customer seeks repayment for a trade she says she never authorized, while NFA asks about the representative’s conduct. The manager preserves the recorded instruction, order ticket, timestamps and confirmation, then builds one factual timeline. The customer claim and NFA request are handled through their respective processes; resolving one does not establish the outcome of the other.

Watch the distinction: Calling a complaint a private payment dispute can cause the branch to overlook a conduct problem. Conversely, a regulatory inquiry does not decide the customer’s monetary claim automatically.

Reference: [1]

CPO/CTA General

10. Classifying CPO and CTA activity

The classification turns on what the business does with customer assets and trading decisions. A commodity pool combines participants’ contributions in a common vehicle for commodity interest trading; operating or soliciting for that arrangement raises CPO questions. A CTA provides advice about commodity interest trading, often for separately held accounts, raising CTA questions. One organization may perform both functions, so a label such as “investment manager” is insufficient. The manager traces who owns each account, who directs trades, whether results are shared through pool units, and how customers receive reports. Then assess registration and any claimed exclusion or exemption against the actual activity and current applicable conditions. Do not infer that a separate account is a pool merely because several clients follow one strategy, or that a pool operator avoids advisory responsibilities by outsourcing execution.

Worked example: Firm A combines ten investors’ contributions in one vehicle and allocates each investor units reflecting the vehicle’s results. Firm B sends trading instructions for clients whose accounts remain separately held. The manager analyzes A’s pool operation as CPO activity and B’s advice as CTA activity, then checks each firm’s status and any claimed exception against its actual functions.

Watch the distinction: The strategy name does not determine CPO or CTA status. Pooling assets and advising on separate accounts create different records, disclosures and registration questions.

Reference: [1]

11. CPO and CTA supervisory controls

Supervision of CPO and CTA activity links what personnel say to what the business actually does. A manager should know the current strategy, trading authority, account or pool structure, and approved customer description. Review a material model change for effects on risks, order practices, performance comparisons and disclosure documents. Then identify every channel carrying the old description: presentations, adviser conversations, website copy and third-party material. The review should have an assigned owner and evidence of approval, while trade and account records should let supervisors test whether implementation matches the stated approach. NFA Compliance Rule 2-13 appears in the Series 30 CPO/CTA scope; it does not mean one generic sign-off covers personnel, trading and communications. A change that improves a model can still make an unchanged sales claim inaccurate.

Worked example: A CTA replaces a trend model with a strategy that also sells options, but sales staff still describe only the former approach. The manager pauses the stale description, identifies recipients and active materials, checks the new trading authority and risks, and routes corrected communications and disclosure material through the required review before further use.

Watch the distinction: Approving the new trading model does not automatically approve old marketing language. Customers need a description that fits the activity now being conducted.

Reference: [1]

12. Pool records and participant reports

Pool reporting should reconcile trading results with cash movements, expenses and participant interests. Start with opening net assets, add realized and unrealized trading gains or losses under the stated valuation method, add contributions, subtract withdrawals and expenses, then compare the result with custody and accounting records. Unit records determine how the pool result is assigned to participants; a correct pool total can still produce wrong participant statements if units or contribution dates are wrong. The manager should investigate breaks rather than force a plug entry to make totals agree. Separate gross trading performance from the net change in pool assets, and explain material expenses so participants understand what they actually own. A participant report is strongest when each displayed figure can be traced back through position, cash, expense and unit records.

Worked example: A hypothetical pool starts with $100,000, earns $8,000 from trading and pays $3,000 of expenses, with no contributions, withdrawals or other changes. Ending net assets equal $100,000 + $8,000 − $3,000 = $105,000. A participant report showing $108,000 reflects gross trading gain while omitting expenses. The manager reconciles and corrects it.

Watch the distinction: Gross trading gain is not the pool’s net gain. Reporting the larger figure as ending assets hides expenses borne by participants.

Reference: [1]

13. CTA client records and reports

A CTA’s recommendation, an order sent for an account and an executed trade are three different events. Records should show which clients were eligible for an instruction, who authorized it, whether it was sent, and what each account actually received. Account restrictions, available equity, timing or execution conditions can make results diverge even when the advice is identical. A manager comparing client reports should therefore reconcile each report to its own confirmations and cash flows, rather than copy a model result across accounts. If a trade was intended for multiple clients but reached only some, determine whether the allocation method or transmission process failed and whether customers need a correction. Performance comparisons must identify their account set, period and costs. Separately managed accounts retain separate histories; similarity of strategy does not merge their results.

Worked example: A CTA recommends buying one futures contract for Client A and Client B. A’s order executes; B’s account restriction prevents entry. A’s report includes the position and its later gain or loss, while B’s report shows no trade. The manager traces the restriction and instruction records instead of assigning the same performance to both clients.

Watch the distinction: A shared recommendation does not create a shared return. Reporting a model trade as an executed client trade can misstate both activity and performance.

Reference: [1]

14. Bunched order allocation

Bunching orders can reduce execution differences across managed accounts, but fairness depends on an allocation method established before the fills are known. The manager checks which accounts were eligible, their intended quantities, restrictions and available capacity. An average-price method assigns the same volume-weighted execution price to eligible accounts when its terms permit; another documented method may be appropriate, but staff should not choose winners after seeing prices. Reconcile the pretrade allocation, exchange fills and final account bookings, including partial fills and transaction costs. Changes to an allocation need a reason recorded at the time. Review repeated outcomes as well as a single trade because a pattern may reveal favored accounts. Series 30 practice questions can reinforce the distinction between a prearranged allocation and a retrospective price choice.

Worked example: Two eligible accounts are assigned one contract each before a two-contract buy order. One contract fills at $70 and one at $72, in the same quoted unit and contract. Under the stated equal average-price method, ($70 + $72) ÷ 2 = $71 per contract for each account, before fees. The manager checks the pretrade allocation and both final bookings.

Watch the distinction: Assigning $70 to a favored account and $72 to another after execution is not made fair by recording the decision afterward. Timing of the method matters.

Reference: [1]

15. CPO and CTA promotional claims

CPO and CTA promotions should identify what a result measures and where it came from. Actual account performance reflects trades placed in real accounts, subject to the stated account selection and cost treatment. A backtest applies rules to historical data under assumptions about signals, fills and costs; it is a hypothetical result even if the price data are real. A strategy description can explain intended decisions but cannot stand in for evidence that those decisions produced a return. The manager compares every number with supporting records, checks the period and account population, and reads surrounding claims for implied certainty. Material limitations belong near the result they qualify. Review also covers oral scripts and third-party content used by the branch. A technically correct chart can mislead if its title makes simulated performance appear to be customer experience.

Worked example: A CTA brochure calls a backtested 18% return an “actual client return.” The manager checks the underlying records and finds no client account traded that test period. The brochure is held, the result is identified as hypothetical with its material assumptions and costs examined, and any actual-client claim is removed unless supported by account records.

Watch the distinction: Historical market prices do not turn a backtest into live performance. The result depends on simulated decisions and execution assumptions that customers must be able to recognize.

Reference: [1]

CPO/CTA Disclosure Documents

16. Disclosure document content and review

A CPO or CTA disclosure document should give a prospective customer a consistent picture of the activity offered. Read strategy, material risks, management, conflicts, performance and costs together: a new strategy may change several sections, not just its name in one paragraph. The manager checks the proposed document against current trading authority, actual practices and supporting records, then identifies missing or stale statements. NFA review is part of the document-use process identified in the Series 30 outline, so the branch should verify the required review status for the version it intends to distribute. Version control matters because staff may keep sending an older document after a revision. A reviewed document is still the firm’s responsibility; if facts change materially, reassess accuracy before further use and complete the applicable amendment and review steps.

Worked example: A pool document describes currency futures, but its manager has added options to the planned strategy. The old risk and strategy sections no longer explain what participants may face. The branch manager stops use of that version, checks related performance and fee language, prepares a coherent revision, and completes the required review before distribution.

Watch the distinction: Adding “options” to a product list may leave risk, authority and performance sections inconsistent. A disclosure update should make the whole document accurate.

Reference: [1]

17. Management and incentive fees

Fee labels do not reveal the amount an investor pays. An asset-based management fee depends on the stated asset measure and timing; an incentive fee depends on the defined profit base and any stated conditions. Work in the order specified by the document, because changing the base changes the answer. Ask whether the asset fee is assessed on opening, average or ending assets, whether incentive profit is measured before or after that fee, and how losses or prior periods affect the calculation under the stated terms. Then reconcile the computed fees with the performance figure shown to customers. A gross return can look attractive while net growth is much smaller. Use only the actual disclosed terms for a real account; example percentages are arithmetic inputs, not claims about standard or required fee levels.

Worked example: Assume an account starts at $100,000, earns $10,000 before fees, and its stated terms charge 2% of opening assets plus 20% of profit remaining after that asset fee. The asset fee is $2,000; remaining profit is $8,000. The incentive fee is $1,600, leaving $10,000 − $2,000 − $1,600 = $6,400 net gain.

Watch the distinction: Charging 20% on gross profit when the stated base is profit after the asset fee overstates the incentive fee. Identify each fee’s base before calculating.

Reference: [1]

18. Performance record comparability

Two performance figures are comparable only after their measurement bases are understood. Check whether each comes from live accounts or a model, whether the dates and market conditions match, which accounts were included, and whether commissions, management fees and other expenses were deducted. Returns also need the same denominator and cash-flow treatment before a direct numerical comparison is meaningful. A gross model return may illustrate how a rule set behaved under assumed fills, while a net client return records actual account experience after costs; their difference cannot automatically be attributed to trading skill or execution. The manager should request underlying records and label each figure near its presentation. If a fair comparison cannot be constructed, explain the limits rather than imply that one number measures the same thing as the other.

Worked example: A presentation places a 15% gross model return beside an 8% net client return and calls the seven-percentage-point difference “execution loss.” Subtraction gives 15% − 8% = 7 percentage points, but the cause is unknown: costs, account selection, timing and simulated fills may all differ. The manager labels both bases and removes the unsupported explanation.

Watch the distinction: A difference between two percentages is not an explanation for that difference. First align periods, accounts and costs, then investigate what remains.

Reference: [1]

19. Conflicts and principal-owned units

A conflict exists when a person’s separate interest could influence a decision made for the pool or its participants. Principal-owned units may align a principal with participants in some respects, yet the principal may also receive compensation that rises with trading volume or select an affiliate as a service provider. The manager maps each interest to the decisions it might affect: trade frequency, broker choice, expense allocation, valuation or timing of entry and exit. Then check that disclosures describe the relationship and economic incentive clearly enough for a reader to understand it. Disclosure does not replace review of whether decisions were made fairly. Records of fee calculations, related-party transactions and approvals help test conduct against the stated arrangements. Assess each interest separately; one disclosed stake does not explain every compensation stream.

Worked example: A principal owns pool units and receives $4 per contract whenever the pool trades through an affiliated broker. Unit ownership gives the principal an interest in pool results; the per-contract fee can reward more trading even if returns suffer. The manager identifies both interests, checks broker-selection and trading records, and ensures the fee arrangement is described.

Watch the distinction: Disclosing a principal’s pool units alone does not reveal compensation tied to trade volume. Readers need to see the incentive that could affect trading decisions.

Reference: [1]

20. Business and disciplinary backgrounds

A disclosure document’s management section should reflect the people actually responsible for the CPO or CTA and relevant aspects of their histories. The manager compares named principals, roles and business backgrounds with current firm records, then checks whether disciplinary information requiring disclosure is complete and accurately framed. A change in personnel can make a previously reviewed document stale even if its trading strategy is unchanged. Verify the event from reliable records rather than relying on a principal’s short summary, and distinguish an allegation, a pending matter and a final outcome where relevant. Update connected sections if the person’s role creates a new conflict or changes decision authority. Before the document is used again, complete the applicable amendment and NFA review process for that version, and remove outdated copies from distribution.

Worked example: A new principal takes charge of trading after a pool document was drafted. The principal has a relevant disciplinary history absent from the draft. The manager verifies the history and role, updates the background and any affected management description, stops staff from using the old version, and completes the required review before using the revised document.

Watch the distinction: A document does not stay accurate merely because it was accurate when drafted. A new decision-maker’s role and relevant history can change what prospective participants need to know.

Reference: [1]

21. Amendments and document currency

A disclosure document must describe the program being offered, not an earlier version of it. A changed fee, trading strategy, principal, conflict, or material risk can make a document misleading even if every sentence was accurate when drafted. Compare the proposed activity with the version staff currently distribute, identify the changed facts, and assess their effect on a prospective customer’s decision. A fee increase directly changes the customer’s expected net result; it cannot wait for a routine housekeeping edit. Stop using the outdated version, prepare an amendment, complete the applicable review, and ensure staff have the current document before distribution resumes. Keep the superseded version and evidence of the review so the branch can establish which information each customer received. The NFA Series 30 study outline identifies amendments, document currency, and review as supervisory topics.

Worked example: A CTA raises its stated annual asset fee from 1% to 2%, but representatives still distribute a document showing 1%. On a hypothetical $100,000 account held at that value for a year, the stated fee rises from $1,000 to $2,000, a $1,000 difference before other costs. The manager halts the old document, corrects the fee description, completes the required review, and checks which customers received the outdated version.

Watch the distinction: An accurate signature page does not cure an outdated fee description. The customer needs the terms of the program actually being offered, including changes that affect expected costs.

Reference: [1]

Customer Information and Risk Disclosure

22. Customer financial and trading information

Customer information helps a branch judge whether it understands the person behind an order and the risks the person proposes to take. Financial resources, trading objectives, occupation, and experience each answer a different question. Liquid assets indicate resources available without selling illiquid property; income and obligations affect capacity to withstand continuing losses; experience helps reveal whether a customer understands futures mechanics. A stated speculative objective does not by itself show that the proposed deposit is affordable. Compare the deposit and likely exposure with the customer’s resources, then ask about discrepancies or unusually concentrated commitments. Document the answers and the reasoning, including whether the customer understands that a futures loss can exceed an initial deposit. The manager’s task is an informed supervisory assessment, rather than a promise that any account can avoid loss.

Worked example: A customer lists $20,000 in liquid assets and proposes depositing $15,000 for speculative futures trading. The deposit would use $15,000 ÷ $20,000 = 75% of reported liquid assets, leaving $5,000 outside the account. The manager asks about other obligations, income, objectives, and trading experience. The 75% figure signals a concentration requiring inquiry; it is not a universal prohibition or proof that the customer understands leverage.

Watch the distinction: Checking that every application field contains an answer is not the same as assessing the answers. A large deposit relative to available resources calls for a closer look.

Reference: [1]

23. Resolving inconsistent customer facts

Conflicting customer facts should prompt a focused question before anyone relies on either version. First identify the precise conflict: the product, period, or meaning of “experience” may differ between a form and a conversation. Ask the customer for a concrete account of past trades, such as products traded, approximate frequency, and whether the trades were placed personally. Then record the clarified answer, update the relevant account information, and consider whether prior risk explanations assumed knowledge the customer does not have. A representative’s informal note is useful evidence of a conflict, but it does not automatically override a signed application. Similar habits of documenting discrepancies appear in financial crime work; the certified financial crime specialist cfcs guide explores that broader field. Here the immediate decision concerns the accuracy of the branch’s customer information and risk discussion.

Worked example: An application says “no derivatives experience,” while a representative’s note calls the applicant an “active futures trader.” Asked to clarify, the customer explains that a relative traded futures and discussed the results, but the customer never placed a trade. The manager records that account, corrects the representative’s characterization, and assesses the proposed transaction using the customer’s actual experience. The original conflict should remain traceable.

Watch the distinction: The more confident sounding statement is not necessarily the accurate one. Do not treat a sales note as verified trading history when the customer’s own account contradicts it.

Reference: [1]

24. Leverage and loss disclosure

A futures deposit supports a position whose market value can be much larger. To explain leverage, start with the contract’s stated size and price, calculate the position’s value, and apply a price change to that full exposure. Then compare the dollar loss with the deposit and with account equity. Margin is a performance bond and may change; it does not cap the loss. A position can also lose value quickly enough that liquidation occurs at a worse price than expected. State the direction clearly: a long position loses when its price falls, while a short position loses when it rises. The distinction between exposure and deposited cash is central to risk disclosure. The SERIES-30 practice questions can reinforce the arithmetic after you can explain what each denominator means.

Worked example: Assume a long futures position has a stated market value of $50,000 and the customer deposits $5,000, with no other account equity or costs. A 4% adverse price move produces a $50,000 × 0.04 = $2,000 loss. That is 40% of the $5,000 deposit, leaving $3,000 equity before further changes. The 4% measures the market move; 40% measures its effect on the deposit.

Watch the distinction: A 4% market decline does not imply a 4% loss of deposited cash. Apply the price move to the full position first, then compare the resulting dollars with the deposit.

Reference: [1]

25. Long and short option risks

An option buyer pays a premium for a right, subject to the contract’s terms. If the option expires without value, the buyer loses the premium and transaction costs. The writer receives the premium but takes on the corresponding obligation if the buyer exercises, and an adverse market move can make that obligation costly. The payoff depends on whether the option is a call or put, the strike, the underlying contract, and whether the position is covered or offset. A branch risk discussion should distinguish maximum premium at risk for a straightforward long option from the potentially much larger exposure of an uncovered short option. It should also explain that selling an option for income is not equivalent to collecting a fee free of future duties. Confirm that the customer understands which side of the option they propose to take.

Worked example: Assume a customer buys a call for a $300 total premium and pays no other charges. It expires without value, so the buyer’s loss is $300. A different customer writes that same call and receives $300. If exercise later creates a hypothetical $1,100 obligation before costs, the writer’s net loss is $1,100 − $300 = $800. The premium offsets part of the obligation; it does not eliminate it.

Watch the distinction: The premium received by a writer is not the writer’s maximum possible gain and loss together. It is income that can be outweighed by the option obligation.

Reference: [1]

26. Stop orders under fast conditions

A stop price is an activation condition, not a promised execution price. When the market reaches the specified trigger under the venue’s order rules, the order becomes eligible for execution in the manner specified. If bids disappear or the market gaps, a sell order may fill below its stop; a buy order may fill above it. Distinguish a stop order from a stop limit order: the latter constrains acceptable execution prices but may remain unfilled. Check the side, quantity, trigger, and resulting order type against the customer’s purpose. For a customer long a contract who wants to exit after a decline, the relevant direction is usually a sell stop. A precise explanation should discuss both the chance of slippage and the possibility that a price constrained order does not execute.

Worked example: A customer long 100 units places a sell stop with a $70 trigger. After a rapid decline, the first executable bid is $68, and all 100 units fill there. Proceeds are 100 × $68 = $6,800, rather than 100 × $70 = $7,000, a $200 difference before costs. The trigger worked as an activation point; it did not guarantee $70 per unit.

Watch the distinction: Calling a stop a guaranteed exit price confuses activation with execution. Market liquidity after the trigger determines the available fill; a limit condition may instead leave the position open.

Reference: [1]

27. Product-specific risk conversations

Start a product risk conversation by identifying the actual transaction. An exchange-traded futures contract has an exchange, standardized terms, and clearing arrangements. An off-exchange retail forex arrangement has a different transaction structure, counterparty relationship, and set of applicable disclosures. Both can involve leverage and rapid losses, but a futures acknowledgment does not establish that the customer has been told how a retail forex transaction works. Ask what product is proposed, where and with whom it will trade, how prices are quoted, what costs apply, and how losses affect available funds. Then verify that the branch is authorized to offer the product and that the appropriate disclosure and supervisory steps are completed. Describing a product simply as “currency trading” obscures distinctions the customer needs to evaluate.

Worked example: A customer who received a futures risk discussion asks to trade an off-exchange retail forex product instead. The manager identifies the proposed counterparty and quotation method, checks the firm’s authority and applicable customer materials, and arranges a product-specific risk explanation before solicitation proceeds. No futures contract size or exchange margin assumption can be carried over automatically. The customer’s earlier acknowledgment establishes only what was previously discussed.

Watch the distinction: Currency exposure alone does not make two products interchangeable. Exchange-traded currency futures and off-exchange retail forex differ in trading structure and the disclosures the branch must consider.

Reference: [1]

CPO/CTA cost disclosure

28. Upfront costs and break-even returns

An upfront charge reduces the money available to trade from the moment an investor contributes it. To calculate the break-even trading return, subtract the charge from the contribution, then divide the amount needed to restore the original contribution by the capital actually invested. Using the original contribution as the denominator understates the required return on deployed capital. Explain whether the charge is taken once, whether other expenses continue afterward, and whether the quoted performance figure is before or after the charge. A CPO or CTA cost discussion should connect the fee to the investor’s attainable net result, not merely list a dollar amount. In practice, market losses, recurring charges, and taxes can change the outcome; a simple break-even example isolates the effect of one stated upfront cost.

Worked example: Assume a $10,000 contribution incurs a $600 upfront charge and no other costs. Invested capital is $10,000 − $600 = $9,400. To restore the original $10,000, trading must earn $600. The required return on invested capital is $600 ÷ $9,400 = 0.06383, or about 6.38%. A 6% gain on $9,400 produces only $564, leaving the investor $36 short.

Watch the distinction: Dividing $600 by the original $10,000 gives the fee as a share of the contribution, 6%. It does not give the return required on the $9,400 invested.

Reference: [1]

29. Organizational expenses in net results

A pool may report profitable trading while its participants earn less after expenses borne by the pool. Organizational expenses, such as eligible startup costs described in the offering terms, reduce pool assets when charged to the pool. For a period return, begin with starting assets, add trading gains or losses, subtract expenses recognized for that period, and divide the net change by the appropriate starting value, assuming no contributions or withdrawals. Identify whether an expense is paid by the pool, the operator, or a participant directly; otherwise the same cost may be omitted or counted twice. Gross trading performance and net participant performance answer different questions. A branch manager should inspect the expense basis and the period covered before approving a comparison or explaining a stated return.

Worked example: Assume a pool begins a period with $100,000, has no contributions or withdrawals, earns $12,000 from trading, and pays $4,000 of stated organizational expenses during the period. Ending assets are $100,000 + $12,000 − $4,000 = $108,000. The net gain is $8,000, or 8% of starting assets. The gross trading gain was 12%; presenting 12% as the investor result would omit the expense.

Watch the distinction: An expense paid from pool assets still affects participants, even if no participant receives a separate bill. Gross trading profit is not the same as net pool growth.

Reference: [1]

30. Combined CPO and CTA cost effects

Several charges may affect one CPO or CTA result, but their names do not reveal whether they are separate amounts. Establish the calculation period and starting value, identify gross trading profit, and list each charge actually borne by the account or pool. Commissions can be embedded in a reported trading figure, so determine whether the figure is before or after them before subtracting anything. Management fees, incentive fees, and other stated expenses can have different calculation bases and sequences. Apply the disclosed terms in their proper order, then reconcile the cost total to the change in account value. If a fee is assessed at a different level, such as by a pool and again by an underlying account, trace which investor bears it. Clear cost attribution makes the net result understandable and prevents double counting.

Worked example: Assume a hypothetical account earns $2,000 before all charges and pays $300 in commissions, $500 in management fees, and $200 in other separately disclosed expenses. Total costs are $300 + $500 + $200 = $1,000. Net gain is $2,000 − $1,000 = $1,000. If a report already described the $2,000 as after commissions, subtracting the $300 again would incorrectly show $700.

Watch the distinction: Do not subtract a charge twice because it appears both in a fee schedule and in the calculation of a reported return. Establish the return’s basis first.

Reference: [1]

FCM/IB cost disclosure

31. FCM and IB transaction charges

A customer’s transaction cost depends on both the stated rate and the number of chargeable sides. Opening and closing a futures position ordinarily involve two trades, and a per-contract, per-side charge applies to each relevant contract on each side. Separate the FCM or IB commission from exchange-related and other stated charges so the customer can see what is being collected and by whom. Confirm whether a quoted amount is per side, per round trip, or a minimum ticket charge; these bases produce different totals. Price movement, spread, and slippage affect trading results but are not the same as an itemized fee. A branch manager should make the customer’s likely cost concrete using the actual proposed trade size and the current stated schedule.

Worked example: Assume one contract is opened and later closed. The stated commission is $8 per contract per side, and an exchange-related charge is $2 per contract per side. Each side costs $8 + $2 = $10, so the completed trade costs 2 × $10 = $20. A $15 favorable market move measured in dollars would still leave a $5 net loss after these charges, assuming no other costs.

Watch the distinction: Quoting only the opening-side commission understates a completed trade’s stated charges. Identify the fee basis and include the closing side when estimating a round trip.

Reference: [1]

32. Fee schedules and trade size

A fee schedule stated per contract must be scaled to the customer’s quantity. First combine charges that share the same basis, such as dollars per contract per side. Multiply by the number of contracts, then by the number of charged sides. Check for stated minimums, volume tiers, or distinct opening and closing rates before using that simple formula. A single-contract round-trip illustration is useful for explaining a unit price, but it is not the total for a larger order. The branch should also distinguish a three-contract order from three separate orders if ticket minimums apply. The calculation should show what is known from the schedule and state any assumed holding or closing pattern. That keeps an estimate useful without implying that market execution costs are fixed.

Worked example: Assume a flat $6 commission plus a $1 other charge per contract per side, with no minimum or volume discount. A customer opens three contracts and later closes all three. The charge per contract per side is $7. Total stated charges are 3 contracts × 2 sides × $7 = $42. The $14 one-contract round-trip figure is a unit cost, not the three-contract total.

Watch the distinction: A per-contract quote does not automatically cover an entire order. Multiply by quantity and the relevant sides, then check whether any minimum or tier changes the result.

Reference: [1]

33. Changes to disclosed charges

A changed charge can alter a customer’s expected result even when the trading plan stays the same. Compare the amount previously explained with the proposed amount using the same unit, such as dollars per round trip. Then scale the difference to the customer’s anticipated activity, while making clear that anticipated trades are an illustration rather than a commitment. Identify whether the change affects a commission, an exchange-related charge, or another fee, and ensure the customer receives an accurate explanation before relying on the old estimate. The branch should update scripts, schedules, and staff communications that still quote the superseded amount. Record which schedule applied to actual transactions so a later confirmation can be reconciled. The supervisory question is whether the customer has a fair account of likely charges at the time of the decision.

Worked example: A stated charge rises from $18 to $24 per completed one-contract round trip before a customer undertakes a plan involving ten such trades. At the old rate, estimated charges are 10 × $18 = $180; at the new rate, they are 10 × $24 = $240. The $60 increase should be explained, and staff should stop quoting $180 for that plan. The estimate excludes market losses and other unstated costs.

Watch the distinction: A fee change is not immaterial simply because it is $6 per trade. Its effect depends on the customer’s expected quantity and frequency of trading.

Reference: [1]

IB General

34. IB order role and funds boundary

An introducing broker can solicit or accept orders within its authorized business, but customer margin and other trading funds belong in the appropriate futures commission merchant account process. The IB’s order relationship does not make its branch a collection point for customer money. When a representative asks for a payment to the IB, identify the intended recipient, payee, and account before funds move. If money has already reached the branch, preserve the facts and escalate the incident through the firm’s controls; do not quietly redirect it in a way that hides the error. The manager should also examine whether the instruction arose from an isolated mistake or a recurring script. Keeping the order role separate from the funds role helps customers know where their money is held and gives the firm a clear transaction trail.

Worked example: A customer gives an IB representative an order to buy one futures contract. The representative then says to wire $5,000 of margin to the IB’s operating account. The manager stops the instruction, documents what was said, and provides the FCM’s authorized funding route. The accepted order and the funding request are separate events: authority to receive the order does not authorize the IB to receive the customer’s margin.

Watch the distinction: A customer’s consent to pay the IB does not change the IB’s funds boundary. The correct recipient depends on the regulated account structure, not the representative’s convenience.

Reference: [1]

35. Guarantee agreements

A guarantee agreement links an IB to a guarantor FCM under the applicable regulatory arrangement. It changes how the IB’s financial responsibility is supported, and it gives the FCM a direct reason to supervise the IB’s conduct. It does not transfer every operational duty away from the IB. The IB still needs accurate order records, appropriate customer communications, and supervision of its personnel. When reviewing a guaranteed IB, identify what the agreement covers, how issues reach the guarantor, and which firm performs each control in practice. A manager should test the actual process rather than assuming the contract’s existence fixes recordkeeping or conduct problems. If an order record is wrong, the guarantor may need to know, but the IB must still investigate and correct its own records.

Worked example: A guaranteed IB’s supervisor says its FCM guarantee means the IB need not keep reliable order records. One ticket lacks a receipt time, so the customer’s instruction cannot be compared with transmission. The manager rejects the claim, obtains the available source evidence, corrects the record as appropriate, and alerts the guarantor through the agreed process. The guarantee concerns the firms’ regulatory relationship; it does not erase the IB’s order-record duty.

Watch the distinction: A guarantee is not a blanket delegation of the IB’s conduct and recordkeeping. Treating it that way would leave customer orders impossible to reconstruct.

Reference: [1]

36. Guarantor FCM oversight

A guarantor FCM needs information that reveals how its guaranteed IB deals with customers. Order records, complaint patterns, advertising, exception reports, and branch reviews can each expose a problem that account statements alone miss. When a concern appears, establish its frequency and source, identify customers or communications affected, and determine whether an IB practice is causing it. The FCM should communicate findings to responsible IB personnel, require a specific correction, and check that the correction worked. A complaint may be about one account, but repeated complaints using similar words can indicate a shared sales script or training failure. The branch manager’s role is to turn that pattern into evidence and action, while preserving the individual customer matters. A guarantee arrangement requires functioning oversight, not merely a signed document.

Worked example: Over two weeks, three customers of a guaranteed IB say representatives described margin as their maximum possible loss. The guarantor FCM compares the complaints with call records and the IB’s sales materials, finds the same misleading phrase in a script, and requires correction and staff retraining. It also reviews affected accounts and later calls to test the change. Handling each complaint alone would miss the common source.

Watch the distinction: Repeated complaints are not necessarily independent misunderstandings. Similar wording across accounts is a diagnostic clue that the IB’s communications or training may be defective.

Reference: [1]

37. IB capital monitoring

Capital monitoring begins with the IB’s actual regulatory status and the applicable requirement for that status. A manager then compares qualifying capital, calculated under the governing rules, with the requirement. The arithmetic difference shows a surplus or shortfall, but the numbers are only as good as the underlying records and classification. Items that appear valuable on a balance sheet may not all qualify in regulatory capital, so the firm must use the proper computation rather than ordinary book equity alone. If qualifying capital falls below the applicable requirement, the issue calls for prompt escalation and the required response under the firm’s regulatory framework. Do not memorize a single threshold for every IB; guaranteed and independent arrangements can have different financial responsibility treatment. In a question that supplies the requirement and qualifying amount, calculate the gap directly.

Worked example: Assume an independent IB has a stated applicable capital requirement of $80,000 for this hypothetical problem and qualifying capital of $73,000. The shortfall is $80,000 − $73,000 = $7,000. The manager verifies the calculation and status, then escalates the deficiency for the required response. The $80,000 figure is an input to this example, not a universal IB minimum.

Watch the distinction: Positive book equity does not establish regulatory compliance. Compare properly calculated qualifying capital with the requirement applicable to that IB’s status.

Reference: [1]

38. Order receipt and timestamps

Order timestamps help reconstruct what the customer instructed, when the IB received it, when it was transmitted, and how the eventual execution followed. These events should not be collapsed into one time. A reliable review compares the order ticket with phone, electronic, routing, and FCM records, accounting for any documented clock differences. If a ticket’s receipt time comes after a transmission record, the inconsistency requires investigation; simply selecting the ticket as authoritative could conceal a delay or entry error. The manager should determine the actual sequence, correct records through a traceable process where appropriate, and assess whether other orders show the same problem. Time evidence matters for customer disputes, execution quality, and supervision. It is useful only when the event each timestamp represents is clearly identified.

Worked example: A recorded call shows a customer instruction at 10:02, and an electronic route log shows transmission at 10:07. The ticket labels 10:09 as the receipt time. That is seven minutes after the call and two minutes after transmission. The manager compares system clocks and source records, documents the cause, and corrects any erroneous entry with an audit trail. The ticket alone cannot explain the sequence.

Watch the distinction: A timestamp is not reliable merely because it appears on a formal ticket. Check what event it records and whether independent evidence supports the chronology.

Reference: [1]

39. IB books and reconciliation

An IB’s order log, the FCM’s execution and confirmation records, and customer account activity should describe the same transaction history. Reconcile them by a stable identifier where possible, then compare contract, month, side, quantity, status, and time. A missing confirmation may mean an order was canceled or unfilled, but it may also mean a routing failure or a missing record. Do not infer execution from an accepted order, or cancellation from the absence of a confirmation. Investigate the unmatched item, document its final status, and check whether the customer received an accurate account. Repeated mismatches may point to a process defect between the IB and FCM. Reconciliation is complete when each accepted instruction has a supported disposition, not simply when two totals appear close.

Worked example: An IB log shows twelve accepted orders for the day, while the FCM sends eleven execution confirmations. The manager matches the eleven by order ID and finds one unmatched sell order. A route log shows it was rejected before reaching the market, and the customer was informed. The manager records that supported disposition and reviews why the rejection was absent from the IB’s end-of-day record. Eleven confirmations did not, by themselves, resolve the twelfth order.

Watch the distinction: An unmatched order should not be labeled unfilled without evidence. It could have been rejected, canceled, executed without a matched confirmation, or recorded incorrectly.

Reference: [1]

General Account Handling and Exchange Regulations

40. Account risk statement and confirmation

A risk statement addresses the product and transaction risks described in it; a trade confirmation records what the account actually did. Compare the confirmed contract, option type if relevant, side, quantity, price, and account with the customer’s instruction and authorized activity. If the confirmation shows an unfamiliar product, establish whether the customer ordered it, whether the account had the relevant disclosures, and whether a booking error occurred. A signed futures risk acknowledgment does not settle an option-specific question merely because the option relates to futures. Confirmations also help detect wrong months, quantities, or sides before a discrepancy becomes harder to resolve. For a broader grounding in futures contract terms, the nfa national commodity futures examination series 3 guide is a useful companion. The branch manager’s immediate task is to reconcile the customer’s authority, disclosures, and actual trade.

Worked example: A customer acknowledges futures risks and later receives a confirmation for one June call option. The customer says the instruction was to buy one June futures contract. The manager compares the recorded instruction, order ticket, and execution record, checks the account’s option authorization and disclosure, and escalates any mismatch for correction. A confirmation proves what was booked; it does not prove the customer requested or understood the option.

Watch the distinction: A signed risk statement is not blanket approval for every related product. Check the precise instrument on the confirmation against both the customer’s instruction and the applicable account materials.

Reference: [1]

41. Margin and daily account equity

Futures margin is collateral supporting a position, not the most the customer can lose. A long position gains when the futures price rises and loses when it falls. Daily settlement credits or debits the account for the price change multiplied by contract size and the number of contracts. Start with account equity, apply that signed gain or loss, then compare the result with the applicable margin requirement. A short position reverses the direction of the price effect. The requirement can change, and adverse moves can exceed the cash initially deposited. A branch manager should check the contract multiplier, position side, settlement price, available equity and account terms before explaining a margin call or liquidation. The NFA Series 30 study outline identifies margin and account handling as supervisory topics.

Worked example: A customer is long one futures contract representing 1,000 units. Its settlement price falls from $50 to $48 per unit, so the daily loss is ($48 − $50) × 1,000 = −$2,000. Equity falls from $6,000 to $4,000. Given a hypothetical $4,500 maintenance requirement, the account is $500 below it. The manager follows the applicable account terms; $4,500 is not a loss limit.

Watch the distinction: A $6,000 deposit does not cap loss at $6,000. Futures exposure depends on the contract’s full value, while margin is collateral that may require replenishment.

Reference: [1]

42. Stop order instructions

A stop instruction needs a side, quantity, contract and trigger price. For a customer long futures, a sell stop below the market may be intended to exit after a decline. A buy stop ordinarily sits above the market and can initiate or add to a long position, or close a short position. The branch manager should compare the ticket with the existing position and the customer’s stated purpose before entry. A triggered stop becomes the order type specified under the applicable venue’s rules; triggering does not guarantee execution at the stop price. Fast markets can produce a materially different fill or no immediate fill. Check whether the instruction is a stop market or stop limit order, because a limit controls acceptable execution price but may leave the position open. The Series 3 futures guide provides related contract fundamentals.

Worked example: A customer is long two June contracts trading at $75 and asks for an exit if price falls to $70. The ticket reads “buy stop, two, $70.” Buying two would leave the customer long four if filled, assuming no other trades. The manager obtains a clarified instruction for a sell stop of two June contracts at $70 and explains that $70 is a trigger, not a guaranteed fill.

Watch the distinction: A stop price is not a promised execution price. Also, matching the quantity alone is insufficient: the wrong side can increase the position the customer meant to close.

Reference: [1]

43. Complete order terms

An order must identify what the customer actually authorized: buy or sell, number of contracts, product, delivery month, and order type with any price condition. A missing or wrong month can expose the customer to a different market and delivery cycle even when the price looks familiar. Translate phrases such as “sell at 75 or better” into the correct order instruction only after confirming the contract’s quotation units and venue conventions. A sell limit at 75 generally seeks 75 or higher; a market order has no such price constraint. Record when the instruction was received and transmit the verified terms without inventing missing details. If the ticket differs from the customer’s source instruction, resolve the discrepancy before routing. A later confirmation helps identify what executed but cannot retroactively establish that the customer gave the mismatched order.

Worked example: At 10:02, a customer instructs the branch to sell three June contracts at a limit of 75 price units per contract unit or higher. The prepared ticket instead names September. Although side, quantity and limit match, the month does not. The manager verifies the recorded instruction, corrects the ticket to June, and preserves the correction and receipt time before transmission.

Watch the distinction: A correct fill price does not make a wrong delivery month harmless. Contract month is an essential order term, and the resulting risk can differ substantially.

Reference: [1]

44. Proprietary and customer accounts

Firm and employee trading near a customer order creates a conflict because someone with access to customer instructions could obtain a favorable position or allocation. Review the chronology: when the customer order arrived, when each proprietary order was entered, the market conditions, executions, cancellations and account allocations. Do not infer misconduct merely from one earlier timestamp; determine what information was available and which priority or trading rules applied. Equally, a confirmation showing that both orders filled does not resolve whether the customer was disadvantaged. The manager should preserve source records and examine any repeated pattern, including whether employee trades appear before customer orders or receive consistently better prices. Controls over access, order handling and exception review help prevent conflicts and make a fair reconstruction possible.

Worked example: A customer buy instruction arrives at 10:01. The firm enters its own buy at 10:03, then transmits the customer buy at 10:05. Both concern the same July contract. The manager obtains receipt logs, entry records and fills, then checks the applicable priority rules and why the customer order waited four minutes. The timestamps warrant investigation but alone do not establish the final outcome.

Watch the distinction: Treating a proprietary trade as acceptable merely because it used a separate account misses the conflict. Order timing, information access and allocation still matter.

Reference: [1]

45. Limits and reportable positions

Position limits restrict how much exposure may be held under the applicable market rules; reporting rules require specified positions to be identified to the relevant body. They answer different questions. Begin by identifying the contract and month, the position side, and accounts whose positions must be combined because of common control or other applicable aggregation rules. Netting or offsetting requires its own rule analysis; do not cancel positions casually across accounts or months. Compare the resulting position with the current applicable limit and reporting requirements, which can vary by contract and circumstance. A claimed hedge may affect treatment only if the underlying exposure and required conditions support it. The manager should retain the position calculation, account relationships and evidence for any claimed treatment, then escalate an apparent breach or reporting gap promptly.

Worked example: One person controls two accounts holding 60 and 50 long contracts in the same market and month. Their combined long position is 60 + 50 = 110 contracts. If a hypothetical applicable limit were 100, the position would exceed it by 10; a separate reporting test would still be needed. The manager checks aggregation, any valid exemption and reporting status using the actual applicable rules.

Watch the distinction: Reporting a position does not make an over-limit position permissible. Likewise, staying below a limit does not by itself remove a separate reporting obligation.

Reference: [1]

Discretionary Account Regulation

46. What makes an account discretionary

Discretion turns on who chooses material trade terms. A customer who specifies the contract, side, quantity and order type is directing the trade, even if the representative performs ordinary execution work. If an adviser chooses whether to trade, which contract to use, or a material part of the strategy for the customer, the activity calls for discretionary-account controls. Limited execution judgment must be assessed in context rather than automatically treated as authority to select trades. A manager should compare the customer’s actual words, the order record and the account’s written authority. This classification matters because discretionary trading requires the proper authorization, approval and ongoing review. An adviser cannot convert an unauthorized discretionary choice into a customer-directed order by writing a completed ticket after making the choice.

Worked example: A customer says, “Buy one June wheat futures contract at market now.” The representative enters exactly that order. The customer selected the trade; routine routing does not change that. Later, the representative decides on a currency option and its entry time without a fresh customer instruction. That second decision involves discretionary trade selection and must be evaluated against the account’s authority before placement.

Watch the distinction: Calling every trade discretionary because the representative clicks “submit” confuses execution with selection. Conversely, a signed ticket does not cure a trade the representative chose without authority.

Reference: [1]

47. Authority before discretionary trading

Before a discretionary order, verify both that authority exists and that this particular trade falls within it. Read the authorization’s scope for permitted products, accounts, persons and any restrictions. Confirm the required account approvals and that the individual acting has the appropriate status and supervision. A broad relationship with the customer is not a substitute for documented trading authority. If an adviser may trade wheat futures, that wording does not automatically cover options on currencies or a different account. Where authority is unclear, obtain clarification through the proper process before entry; do not rely on an after-the-fact signature. The branch manager should also ensure orders identify the discretionary decision maker so subsequent review can compare actual activity with the mandate and investigate concentrations, costs or conflicts.

Worked example: An account authorization names adviser Lee and permits wheat futures in Account A. Lee proposes buying a currency option in Account A. The manager checks the authorization and finds no option or currency authority. The order is withheld while proper authority and approvals are addressed. Lee’s valid wheat authority establishes neither permission for the new product nor permission to trade another account.

Watch the distinction: Customer familiarity is not the same as trading authority. A discretionary mandate has boundaries, and a trade outside them remains a problem even if it later profits.

Reference: [1]

48. Reviewing discretionary account activity

Reviewing discretionary activity means testing whether trading served the customer’s authorized objectives, not merely whether each order was recorded. Compare turnover, commissions, realized and unrealized results, position size, risk and timing against the mandate and account resources. Repeated round trips can create substantial costs even where gross trading gains appear positive. Investigate clustered trades near reporting dates, trades that reverse quickly, and allocations that favor related accounts. Ask what market rationale and customer objective supported the decisions at the time; later profits or losses alone do not settle the question. Document exceptions, the adviser’s explanation and any corrective action, then check whether the pattern changes. The Series 30 practice questions can help rehearse the distinction between authorization and continuing supervision.

Worked example: A discretionary account makes 20 round trips in one month, each costing a stated $25. Total transaction charges are 20 × $25 = $500. Suppose gross trading gains were only $100; after these charges, trading is down $400, ignoring other costs. The manager examines trade purpose, mandate fit and account history rather than treating the $500 as routine simply because it was disclosed.

Watch the distinction: An authorized discretionary account is not exempt from activity review. Permission to select trades does not justify excessive turnover or trades inconsistent with the customer’s mandate.

Reference: [1]

Communications with the Public and Promotional Material

49. Recognizing promotional material

A communication can be promotional because of its purpose and context, even when it looks like education or appears on a personal social account. Examine who can see it, whether it invites trading business, and how charts, claims and contact instructions work together. A factual market chart may become part of a solicitation when paired with a call to trade a strategy. The branch manager should capture the complete communication, including captions, links and surrounding text, then apply the firm’s review and record procedures before use where required. Accuracy matters at the impression level: a technically correct chart can still imply that a suggested strategy is safe or predictably profitable. Staff should know that using an outside platform or informal tone does not remove supervisory responsibility for business communications.

Worked example: A representative posts a public chart showing a prior rise in oil futures and writes, “Contact me to trade my next signal.” The chart and invitation are viewed together. The manager treats the post as promotional material, checks whether the chart’s period and source are clear, reviews the trading claim, and retains the approved version and evidence supporting it.

Watch the distinction: Labeling a post “educational” does not determine its status. A public invitation to trade can make the surrounding material promotional, regardless of the representative’s chosen label.

Reference: [1]

50. Standard presentations and outside firms

A standard sales presentation is a repeatable message, so one misleading phrase can reach many customers. Third-party designers and advertising firms may prepare it, but the branch remains responsible for the communication it uses. Review the final delivered slides, script, voiceover and linked material, including revisions after an earlier approval. Distinguish a historical result, which describes an observed period under stated conditions, from an expected result, which predicts the future. Changing one word can transform the claim and its evidentiary burden. A manager should trace performance figures to their source, check risk context and confirm that staff use only the approved version. Version control makes this practical: an approval record should identify the actual file, date and supporting data, so a later edit triggers fresh review.

Worked example: An advertising firm changes a slide title from “Historical gain: 8% in the stated period” to “Expected gain: 8%.” The underlying chart still describes past data. The manager holds the revised deck because its new title predicts an outcome the chart cannot establish. The firm restores accurate wording, checks the full presentation for similar changes, and records approval of that version.

Watch the distinction: Outsourcing slide design does not outsource supervisory responsibility. Approval of an earlier deck also does not cover later wording that changes a historical claim into a forecast.

Reference: [1]

51. Article reprints and implied endorsement

An article reprint can mislead through selection and placement while every retained sentence remains accurate. Read the original article, the excerpt, its headline and any branch commentary as one communication. Omitting losses, limitations or dates may give readers a false impression of consistent success. A nearby invitation to open an account can also imply that the article endorses the branch or its strategy when it does not. Check whether the reprint fairly represents the source and whether any permission or attribution needed for its use has been addressed. The manager should preserve the original article and the exact distributed version to show what was reviewed. If the excerpt cannot convey the essential context, use a fuller passage or abandon the reprint.

Worked example: An article reports a trader gained $9,000 in April after losing $28,000 over the preceding three months. A proposed reprint includes only the April paragraph beside “Trade with us.” Across the stated four months, the combined result is −$19,000. The manager rejects the excerpt because it conveys a positive record while hiding the larger losses and suggests an unsupported connection to the branch.

Watch the distinction: A reprint is not automatically fair because its quoted sentence is accurate. The omitted context and surrounding sales message can change what a reasonable reader understands.

Reference: [1]

52. Past performance claims

A past-performance claim needs a defined account set, period, starting capital and cost basis. Ask whether it uses actual accounts, a selected subset or a composite, and whether it shows gross or net results. A return percentage requires a denominator: gain divided by the stated starting capital under the chosen method. Commissions, fees and other charged costs can materially reduce what customers experienced. The manager should reconcile the advertised figure to records and ensure the presentation does not imply that past gains predict future results. If accounts entered or left during the period, simple beginning-capital arithmetic may be inadequate; the method must reflect cash flows or clearly limit the claim. Comparing two figures without matching periods and cost treatment invites a false conclusion.

Worked example: A flyer reports a 14% return from a $14,000 gross gain on $100,000 of stated starting capital. The relevant accounts paid $4,000 in disclosed costs during the same period. Net gain is $14,000 − $4,000 = $10,000, or 10% of starting capital, assuming no intervening cash flows. The manager requires the flyer to identify which basis it uses and support both figures.

Watch the distinction: Gross and net returns are not interchangeable. Calling a gross figure “customer return” hides costs that customers paid and can overstate their actual outcome.

Reference: [1]

53. Hypothetical trading results

Hypothetical results come from a model or reconstruction rather than a customer’s live account. They can illustrate a method, but their assumptions may omit execution delays, liquidity, changing spreads, rejected orders and costs. Identify the data period, selection rules, position sizing and whether the strategy was changed after viewing results. Then compare the modeled trades with feasible execution and subtract reasonable stated costs to understand sensitivity. A branch manager should ensure the communication labels the results accurately and presents their limitations with enough prominence for the reader to understand them. A simulated gain is never evidence that a customer earned it. Nor does adding an estimated commission transform a backtest into live performance; it only improves one assumption in the simulation.

Worked example: A model reports $6,000 profit for a hypothetical year before trading costs. Its stated estimate for commissions and related charges is $1,500, so the cost-adjusted modeled result is $6,000 − $1,500 = $4,500. The manager checks whether the estimate covers the modeled trade count and whether fill assumptions are plausible. Both $6,000 and $4,500 remain hypothetical, not customer returns.

Watch the distinction: A detailed backtest is not an actual performance record. Precise arithmetic cannot remove hindsight, execution or data-selection limitations that affect the modeled outcome.

Reference: [1]

54. Promotional review and records

Promotional review must attach to the version customers actually see. A written procedure should identify who submits material, who checks claims and risk context, who approves distribution, and how changes return for review. Keep the approved file, its approval record, dates of use and evidence supporting numerical or factual claims. For web or social material, capture the complete published view, because captions, links and later edits can alter meaning. A manager should compare the released version with the approved one and investigate discrepancies, especially new performance figures or guarantees. Recordkeeping serves two purposes: it helps prevent unsupported claims before release and allows the branch to reconstruct what customers received afterward. An approval stamp without the underlying version or support provides little evidence of a meaningful review.

Worked example: A brochure approved on Monday contains a strategy description. On Wednesday, a designer adds a chart claiming a 12% historical return before printing. The prior approval covers the Monday file only. The manager pauses distribution, obtains the chart’s account data and calculation method, reviews the revised brochure as a whole, and retains the new approved file with its supporting records.

Watch the distinction: Reviewing the original brochure does not approve a later chart. A new performance claim changes the communication and needs its own substantive review and record.

Reference: [1]

Anti-Money Laundering Requirements

55. AML controls based on activity

An anti-money laundering program should reflect how the firm actually opens accounts, receives funds and processes transactions. Start with the firm’s customer types, products, funding channels and geographic exposure; identify where unusual activity could enter or pass through those processes. Controls may include identity checks, review of third-party payments, transaction monitoring, escalation paths and documented decisions. A branch manager need not decide that suspicious conduct is criminal to escalate it. The useful question is whether the facts depart from the customer’s known purpose or the firm’s expected flow of funds. When activity changes, test whether the existing controls can still detect and route concerns. The financial crime specialist guide offers broader context, while Series 30 focuses on branch supervisory responsibilities within the NFA framework.

Worked example: A branch that historically receives customer funding from accounts in the customers’ own names gets five requests in a week to accept payments from unrelated third parties. The manager records the requests, account relationships and proposed payment paths, then escalates the pattern to the designated AML personnel. The branch reviews whether its funding controls identify and handle such requests consistently.

Watch the distinction: A generic checklist cannot assess a funding pattern it never captures. Controls should follow the firm’s real activity and route unusual facts for investigation.

Reference: [1]

56. Customer identification and records

Collecting identity fields and verifying identity are separate steps. An application may contain a name, address and other identifying details, yet those entries can be inaccurate or unresolved. The customer identification process must use the firm’s applicable verification methods, address discrepancies and keep records showing what was checked and what result followed. A branch manager should see the status of unresolved cases, prevent staff from marking them complete merely to move an account forward, and ensure exceptions reach the designated reviewer. The record should support a later reconstruction without exposing more information than needed to staff who have no role in the process. A mismatch may have an innocent explanation; the appropriate response is to investigate and document it, not automatically conclude that the customer is dishonest.

Worked example: A new application lists a customer’s name and residential address, but the verification check cannot match the address. The representative marks the form “complete” because every field is filled. The manager reverses that status, records the unresolved result and routes the discrepancy for the prescribed follow-up. The issue is verification, not whether the customer supplied text in the boxes.

Watch the distinction: Filled fields do not prove identity. Treating data collection as completed verification hides unresolved discrepancies and weakens the record of what the firm actually checked.

Reference: [1]

57. Suspicious activity patterns

Suspicious activity often emerges from a sequence rather than a single transaction. Compare deposits, trading volume, withdrawals, recipients and the customer’s stated purpose over time. Repeated funding followed by little market activity and requests to send money elsewhere can indicate that the account is being used mainly to move funds, although innocent explanations remain possible. The manager should preserve dates, amounts, account identifiers and customer communications, then route the pattern to the designated AML reviewers. Staff should avoid telling the customer what conclusion or reporting decision may follow. The objective is a documented investigation based on the whole pattern, including any explanation and corroborating evidence. Looking only at each deposit in isolation can miss the relationship between incoming and outgoing funds.

Worked example: Over three weeks, a customer deposits $8,000, $7,000 and $9,000, makes one small trade, then asks to withdraw $22,000 to another person. Total deposits are $24,000, so the requested withdrawal is most of the funded amount. The manager records the sequence and recipient details and escalates it for review. These facts warrant investigation; they do not alone prove wrongdoing.

Watch the distinction: A deposit that appears ordinary by itself can be significant in context. Review the funding, trading and withdrawal pattern together before drawing a conclusion.

Reference: [1]

58. Escalation and reporting decisions

Front-line staff should identify and preserve unusual facts, then pass them to the person or team responsible for AML investigation and reporting decisions. Useful escalation includes transaction dates and amounts, parties, account history, relevant communications and why the activity appears unusual. Keep observation separate from inference: “three deposits came from different named senders” is stronger evidence than an unsupported accusation. The designated reviewer can seek more information, document an explanation and decide what further action is required under the applicable program. A representative should not promise a reporting outcome or reveal a possible report to the customer. The branch manager should correct such a disclosure, preserve what was said and route the underlying concern promptly. A reporting decision should follow investigation, not a representative’s public announcement.

Worked example: A representative sees deposits of $4,000, $4,500 and $3,800 from separate sources and tells the customer, “We will file a report about your deposits.” The manager stops further discussion of reporting, records the dates, senders and statement made, and sends the facts to the designated AML reviewer. The pattern is examined under the program; the representative’s conclusion is not treated as the decision.

Watch the distinction: Escalating concern does not mean announcing a report or deciding guilt. Preserve observable facts and leave investigative and reporting judgments to the designated process.

Reference: [1]

59. Training for front-line detection

Training should give front-line employees practical cues tied to the activity they see: inconsistent identity information, unexplained third-party funding, transactions unlike the customer’s stated purpose, and withdrawals to unexpected recipients. Staff need to know what to record, whom to contact and how to avoid making promises or accusations. Exercises should distinguish a red flag from a finding; a mismatch prompts inquiry but does not prove illicit conduct. Managers can use actual anonymized patterns to check whether employees recognize combinations of facts and escalate them consistently. Training also needs a feedback path so recurring uncertainties reveal gaps in procedures. The designated AML function retains responsibility for deeper investigation and reporting decisions, while branch staff supply timely, accurate observations.

Worked example: A trainee sees that a customer’s application names Dana, while an incoming payment identifies Morgan as sender. The trainee records the sender, amount and account details and asks the designated team how to handle the mismatch before treating the funding as routine. The team investigates the relationship. The trainee has identified a cue, not established that Morgan’s payment is improper.

Watch the distinction: A front-line employee should not ignore a mismatch or decide alone that it proves wrongdoing. Training should produce accurate escalation and a documented review.

Reference: [1]

60. AML officer, independent review and evidence

The designated AML officer or responsible personnel oversee the program’s daily operation: making sure alerts are reviewed, decisions are documented, staff are trained and weaknesses are corrected. Independent review tests whether those controls work in practice, using records and samples rather than relying only on the procedure’s wording. The reviewer identifies findings; program owners assign fixes, verify completion and preserve evidence of the result. Independence matters because the person testing a control should be able to evaluate it objectively. A branch manager may supply records and carry out local corrections, but should not treat a clean policy document as proof that every alert was handled. Compare sampled alerts with disposition records, investigate omissions and retest after remediation. The result should show both the gap found and whether the repair held.

Worked example: An independent reviewer samples 15 AML alerts and finds three with no documented disposition. The missing-documentation rate is 3 ÷ 15 = 20% of that sample. The AML officer identifies the three cases, determines whether each was actually reviewed, assigns corrective work and checks a later sample. The 20% describes the sample; it is not a firm-wide rate without further evidence.

Watch the distinction: An independent finding does not repair the underlying control. The responsible personnel must resolve affected cases, document the correction and check whether the problem recurs.

Reference: [1]

Official references and further reading

All study guides

General supervision and registration

1. Fair dealing as a supervisory standard

2. Registration and sponsor checks

3. Supervisory systems and branch audits

4. Order, option and retention records

5. Customer deposits and payment routing

6. Continuity during a branch outage

7. Reportable positions and bona fide hedges

8. Foreign exchange trading venues

9. Discipline and arbitration serve different purposes

CPO/CTA General

10. Classifying CPO and CTA activity

11. CPO and CTA supervisory controls

12. Pool records and participant reports

13. CTA client records and reports

14. Bunched order allocation

15. CPO and CTA promotional claims

CPO/CTA Disclosure Documents

16. Disclosure document content and review

17. Management and incentive fees

18. Performance record comparability

19. Conflicts and principal-owned units

20. Business and disciplinary backgrounds

21. Amendments and document currency

Customer Information and Risk Disclosure

22. Customer financial and trading information

23. Resolving inconsistent customer facts

24. Leverage and loss disclosure

25. Long and short option risks

26. Stop orders under fast conditions

27. Product-specific risk conversations

CPO/CTA cost disclosure

28. Upfront costs and break-even returns

29. Organizational expenses in net results

30. Combined CPO and CTA cost effects

FCM/IB cost disclosure

31. FCM and IB transaction charges

32. Fee schedules and trade size

33. Changes to disclosed charges

IB General

34. IB order role and funds boundary

35. Guarantee agreements

36. Guarantor FCM oversight

37. IB capital monitoring

38. Order receipt and timestamps

39. IB books and reconciliation

General Account Handling and Exchange Regulations

40. Account risk statement and confirmation

41. Margin and daily account equity

42. Stop order instructions

43. Complete order terms

44. Proprietary and customer accounts

45. Limits and reportable positions

Discretionary Account Regulation

46. What makes an account discretionary

47. Authority before discretionary trading

48. Reviewing discretionary account activity

Communications with the Public and Promotional Material

49. Recognizing promotional material

50. Standard presentations and outside firms

51. Article reprints and implied endorsement

52. Past performance claims

53. Hypothetical trading results

54. Promotional review and records

Anti-Money Laundering Requirements

55. AML controls based on activity

56. Customer identification and records

57. Suspicious activity patterns

58. Escalation and reporting decisions

59. Training for front-line detection

60. AML officer, independent review and evidence

Official references and further reading

Frequently Asked Questions

Related Study Guides

NFA National Commodity Futures Examination (Series 3)

NFA Retail Off-Exchange Forex Examination (Series 34)

Certified Government Financial Manager (CGFM)