A QSR relationship allows an eligible NSCC member to submit specified locked-in trade data to NSCC on behalf of another consenting member.
A Qualified Special Representative (QSR) relationship is an arrangement under National Securities Clearing Corporation (NSCC) rules that allows an eligible NSCC member to submit specified locked-in transaction data to NSCC on behalf of another consenting member. The submitted obligations bind the designated parties for NSCC processing under the applicable rules.
A QSR does not mean the parties clear directly with each other outside NSCC. It is a submission and authorization relationship within NSCC’s clearing framework. It also does not, by itself, authorize one firm to satisfy another firm’s FINRA trade-reporting obligation.
The exact eligibility and procedure are governed by current NSCC rules. A simplified workflow is:
flowchart LR
A["Two firms execute or allocate a trade"] --> B["QSR prepares the locked-in record"]
B --> C["QSR submits both sides to NSCC"]
C --> D["NSCC validates the transaction data"]
D --> E["Eligible obligations enter NSCC clearing"]
E --> F["Errors and disputes are reconciled by the parties"]
The NSCC members document which firm will act as special representative and which member authorizes it to submit obligations. NSCC’s rules define additional conditions for qualified status. The relationship is not created merely because two brokers regularly trade with each other.
The transaction occurs through the relevant exchange, alternative trading system, dealer, or other permitted mechanism. A QSR relationship does not execute the trade and is not itself a trading venue.
The QSR sends transaction data to NSCC through the applicable service. NSCC’s Universal Trade Capture service accepts eligible transactions submitted by exchanges and QSRs that are NSCC members.
Because the QSR is authorized to submit for the designated parties, the record can be treated as locked in rather than awaiting an ordinary independent submission from each side. That reduces one comparison step; it does not remove the need for accurate terms or controls.
Eligible obligations proceed under NSCC’s clearing, netting, risk-management, and settlement arrangements. DTC may support the resulting book-entry securities movements. The QSR relationship changes how the trade reaches clearing, not the identity of NSCC as the clearing organization.
NSCC rules place responsibility for differences or claims concerning data submitted by a special representative on the relevant parties. A bad symbol, quantity, price, account, capacity, or counterparty identifier can create a binding operational problem that must be corrected promptly.
FINRA explicitly distinguishes a QSR agreement from authorization to report a trade for another member. A QSR establishes that one party can send a trade to NSCC clearing on behalf of another. It does not automatically authorize that party to submit the other member’s required report to a FINRA facility.
| Function | Typical question | Does the QSR alone answer it? |
|---|---|---|
| Execution | Where and when did the parties trade? | No |
| Public or regulatory reporting | Which member must report, to which FINRA facility, and by what deadline? | No |
| Clearing submission | May one NSCC member submit the locked-in obligation for the other? | Yes, within the approved relationship and rules |
| Central-counterparty processing | Did NSCC accept the obligation into an eligible service? | No; acceptance and eligibility still must be established |
| Settlement | Were securities and cash delivered on the contractual date? | No |
The Trade Reporting Facility page explains why a reporting facility and the ACT technology used by the FINRA/Nasdaq TRF should not be confused with the underlying clearing authorization.
Assume Broker A operates an eligible execution system and is an NSCC member acting as QSR for Broker B under a documented relationship.
The example isolates the submission relationship. It does not establish who had the trade-reporting obligation or when NSCC’s settlement guarantee began.
| Arrangement | Main purpose | Important boundary |
|---|---|---|
| QSR | One eligible NSCC member submits specified locked-in trade data for another consenting member | Does not itself delegate FINRA trade reporting |
| Automatic Give-Up (AGU) | Supports locked-in treatment under a relevant facility or workflow when parties have the required agreement | Terms and facility rules differ from NSCC QSR qualification |
| FINRA reporting agreement | Allows one member to report to a FINRA facility on another member’s behalf in covered circumstances | Does not by itself establish NSCC clearing authority |
| Clearing-broker agreement | Defines how an introducing or executing firm uses a clearing broker | Broader account and responsibility relationship, not automatically a QSR |
| Ordinary comparison | Each side submits or affirms information that is matched | A discrepancy prevents the record from becoming matched or compared |
Names can vary across rulebooks and systems. Analysts should identify which agreement controls which record rather than assuming that all “give-up” or representative arrangements are equivalent.
A valid QSR relationship can support automated submission of high-volume activity and reduce the need for two independent records to be compared at NSCC. It can be useful when an eligible execution or clearing workflow already produces agreed transaction data for both sides.
The benefit is operational standardization, not secrecy. Required public and regulatory reports remain subject to applicable rules. Cost and speed depend on system design, service fees, error rates, cutoffs, and downstream settlement; they should not be assumed from the QSR label alone.
The QSR’s record can create binding obligations for another member. Access controls, agreement checks, duplicate detection, field validation, and supervisory review are therefore critical.
The relationship may apply only to specified accounts, products, sessions, or transaction types. Using it outside its approved scope can create unauthorized obligations.
A firm can clear a trade correctly and still violate a separate trade-reporting requirement. Operations and compliance teams must map clearing submissions to tape, non-tape, and other regulatory reports without duplicating or omitting transactions.
The executing system, QSR submission, NSCC output, DTC settlement record, and each firm’s books must agree. Locked-in processing removes a matching step; it does not remove the need for reconciliation.
NSCC risk controls apply to accepted obligations, but members can default and trades can fail to settle. A QSR is not a guarantee of counterparty performance or timely delivery.
This article provides general market-structure education, not legal, regulatory, investment, or operational advice. Firms should use current NSCC and FINRA rules and qualified counsel for specific reporting or clearing obligations.