Excess Margin Securities

A customer's margin account holds securities that exceed what's needed to meet the account's margin requirement. A principal assumes that because the account is a margin account, the firm may use all of the customer's securities in it for the firm's own purposes, including the portion beyond what secures the margin loan. Is this assumption correct?

1. A.Yes — a margin account, by virtue of the customer's margin agreement, permits the firm to use the entirety of the securities held in that account for its own purposes.Wrong. A margin agreement authorizes use of securities needed to secure the margin obligation, not the entirety of the account's holdings.
2. B.No — even within a margin account, only the securities actually needed to secure the customer's margin obligation may be used by the firm; the portion beyond that, known as excess margin securities, must still be segregated the same as fully paid securities.Correct. Excess margin securities beyond what secures the margin debit remain subject to the same segregation protection as fully paid securities.
3. C.No, but only because the customer must resign a new margin agreement annually reauthorizing the firm's use of the securities securing the loan.Wrong. This invents an annual reauthorization requirement that is not the actual basis for the segregation distinction.
4. D.Yes, provided the firm discloses to the customer, in the account statement, the total dollar value of securities being used.Wrong. Disclosure on a statement after the fact does not create authority to use securities beyond what actually secures the margin obligation.

Why: No. Even within a margin account, only the securities actually needed to secure the customer's margin obligation may be used by the firm; the portion beyond that, known as excess margin securities, must still be segregated the same as fully paid securities.

A principal discovers that a software error has, for several months, been causing certain customer securities that should have been segregated as "excess margin securities" to instead be included in the pool of securities available for the firm's own use. What must the principal do upon discovery?

1. A.Refer the matter solely to the software vendor responsible for the bugWrong. Responsibility for addressing the customer protection exposure rests with the firm's own supervisory function, not solely the vendor.
2. B.Fix the software bug going forward and consider the matter closedWrong. This ignores the need to address the months of retrospective exposure the bug already created.
3. C.Correct the error, quantify the scope and duration of affected customer positions, and evaluate remediation and reporting obligationsCorrect. A multi-month segregation failure requires assessing what was exposed retrospectively, not just correcting the bug going forward.
4. D.Wait for a customer complaint before assessing the scope of the affected positionsWrong. The principal should proactively assess the scope upon discovering the error, not wait for a complaint to surface.

Why: The principal must immediately correct the error, quantify the scope of affected customer positions and the duration of the exposure, and evaluate the firm's remediation and reporting obligations -- not simply fix the bug prospectively without addressing the retrospective exposure it created.