FINRA Rule 7160

The rule carried forward into FINRA Rule 7160 through SR-FINRA-2008-021, effective December 15, 2008, and received a further, largely conforming amendment through SR-FINRA-2013-053, effective February 3, 2014, the same filing discussed throughout the other Rule 7100 Series entries elsewhere in this dictionary that eliminated TRACS-specific terminology across the series.

FINRA has adopted essentially identical audit trail language across every one of its equity and debt trade reporting facilities: Rule 7260A for the FINRA/Nasdaq Trade Reporting Facility references the parallel content requirements in Rule 7230A(d), Rule 7260B for the FINRA/NYSE Trade Reporting Facility references Rule 7230B(d), and Rule 7360 for the OTC Reporting Facility references Rule 7330(d). This consistent structure means a firm that understands Rule 7160's function for the ADF has, in substance, already understood the equivalent audit trail obligation applicable across every other FINRA equity trade reporting facility as well.

What Rule 7130(d) Actually Requires

Understanding Rule 7160 in practice requires understanding what the underlying Rule 7130(d) content elements it protects actually consist of, since Rule 7160 itself contains no independent substantive content beyond the cross-reference, functioning purely as an enforcement anchor for data that Rule 7130 defines elsewhere. Rule 7130(d) requires, among other elements, a symbol indicating whether a transaction is a buy, sell, or cross, and, where applicable, a symbol indicating whether the transaction is a sell short or sell short exempt trade from either the Reporting Member's or the contra side's perspective, regardless of whether that contra side is itself a FINRA member, though this short sale indicator is not required on a clearing-only, non-regulatory report. It also requires a symbol indicating whether the trade was executed as principal, riskless principal, or agent, the identity of the reporting side's clearing broker where different from that firm's normal clearing broker, and identification of the reporting side's executing broker as a "give-up" where applicable.

A particularly notable content requirement ties Rule 7130(d) directly to the Consolidated Audit Trail framework covered extensively elsewhere in this dictionary: for any transaction involving an order for which a member has recording and reporting obligations under CAT Rules 6830 and 6870, the ADF trade report must include an order identifier, meeting parameters FINRA prescribes, uniquely identifying that order for the date it was received. This cross-reference means Rule 7160's audit trail integrity obligation is not a standalone, ADF-specific concern; accuracy failures in this specific order identifier field can simultaneously implicate a firm's CAT reporting accuracy under Rule 6893, since the same order identifier links the ADF's own trade reporting audit trail to the far more comprehensive audit trail CAT maintains for the same underlying order.

Rule 7160 as a Minor Rule Violation Plan Category

Rule 7160 is specifically named among the categories of violation eligible for streamlined disposition under FINRA's Minor Rule Violation Plan, pursuant to Rule 9217. FINRA's list of MRVP-eligible transaction reporting violations groups Rule 7160 together with Rules 6380B, 6622, 6730, 7130, 7230A, 7230B, 7260A, 7260B, 7330, and 7360, collectively described as covering transaction reporting in equity and debt securities. This means an isolated, technical failure to accurately or completely input the Rule 7130(d) data elements can, in appropriate circumstances, be resolved through FINRA's streamlined minor violation process rather than a full disciplinary proceeding, mirroring the same graduated enforcement philosophy discussed in connection with Rule 6893 and the broader CAT Compliance Rule Series elsewhere in this dictionary.

This MRVP eligibility does not mean audit trail accuracy is treated as unimportant; it means FINRA has built a proportionate response mechanism specifically for the kind of isolated, technical data quality lapse that does not reflect a sustained or systemic supervisory failure. A firm with a demonstrated pattern of audit trail inaccuracies, or an adverse existing disciplinary history, can still face more significant sanctions through FINRA's standard disciplinary process rather than the streamlined MRVP route, consistent with how FINRA has structured graduated enforcement responses throughout its trade reporting and audit trail rules generally.

Comparing Rule 7160 to CAT's Rule 6893

Placing Rule 7160 alongside Rule 6893, the Consolidated Audit Trail's own timely, accurate, and complete data standard discussed extensively elsewhere in this dictionary, reveals both a genuine conceptual continuity and a meaningful difference in scale. Both rules establish essentially the same underlying principle: a firm using a FINRA reporting facility bears an ongoing obligation to ensure the data it submits is accurate and complete, since that data forms the basis for FINRA's broader regulatory surveillance capability. Rule 7160, however, predates CAT by well over a decade, and its scope is narrower, tied specifically to the ADF's own trade reporting content rather than the dramatically more comprehensive order-lifecycle data CAT captures across NMS Securities, OTC Equity Securities, and Listed Options.

Rule 6893 also carries a considerably more developed quantitative enforcement framework, including the Error Rate and Compliance Threshold concepts discussed in that entry, along with a documented history of serious enforcement action reaching into the tens of billions of erroneous events in a single matter. Rule 7160 has not generated comparably documented, large-scale enforcement history, likely reflecting both the ADF's own diminished current trading volume, discussed in the Rule 7110 entry elsewhere in this dictionary, and the narrower scope of data Rule 7130(d) requires relative to CAT's dramatically more extensive reporting obligations spanning the full order lifecycle rather than trade-level content alone. Candidates and practitioners should understand Rule 7160 as an earlier, narrower ancestor of the audit trail integrity philosophy CAT's Rule 6893 now embodies at a considerably larger scale, reflecting how FINRA's underlying regulatory philosophy toward data quality has remained consistent even as the technical infrastructure implementing that philosophy has grown substantially more sophisticated over time.

A Worked Example of the CAT Linkage in Practice

Consider a firm that executes an order in an NMS stock and reports the resulting trade to the ADF, where that same order also carries recording and reporting obligations under CAT Rules 6830 and 6870 given the security's status as an NMS Security. If the firm's ADF trade report includes an incorrect order identifier in the field Rule 7130(d) requires, that single error can generate two distinct, parallel compliance concerns. Under Rule 7160, the firm has failed to input the Rule 7130(d) data elements accurately, exposing it to the audit trail obligation this rule establishes for the ADF specifically. Simultaneously, because that same order identifier is meant to link back to the identical order as reported under CAT, an inconsistency between the ADF's order identifier and the actual CAT-reported identifier for that order can undermine the Central Repository's own ability to correctly connect the ADF trade report to the broader CAT order lifecycle record, a distinct data quality concern reaching into the Rule 6893 framework discussed extensively elsewhere in this dictionary.

This dual exposure illustrates why firms should not treat their ADF audit trail compliance and their CAT compliance as entirely separate, independently managed programs, at least with respect to any data element the two regimes genuinely share. A firm that catches and corrects an order identifier error in its CAT reporting but fails to make the corresponding correction in its ADF trade report, or vice versa, has only partially resolved the underlying data quality problem, leaving one of the two audit trails still carrying the inaccurate information even after the other has been properly corrected.

The Practical Weight of Minor Rule Violation Plan Fines

Firms should understand what MRVP treatment actually means in practical financial terms, since the mechanism's name can understate its genuine deterrent function. FINRA's Minor Rule Violation Plan generally permits fines calibrated to the specific violation and the firm's own compliance history, and while individual MRVP fines are typically modest relative to the more substantial sanctions available through FINRA's full disciplinary process, a firm accumulating repeated MRVP dispositions across multiple examination cycles builds a documented compliance history that FINRA can, and does, take into account when evaluating whether a subsequent, similar issue still warrants MRVP treatment or instead justifies escalation to a more significant enforcement response. A firm should not view MRVP eligibility as effectively cost-free simply because any individual fine tends to be modest; the cumulative pattern such fines create over time carries its own independent significance for how FINRA characterizes the firm's overall compliance posture in any future examination or enforcement matter.

Relevance Across FINRA's Examination Programs

The SIE, Series 63, and Series 65 do not test Rule 7160's specific content, since these exams do not reach into facility-level audit trail data quality standards at this level of technical detail. Series 7 candidates should understand conceptually that accurate trade report data underlies FINRA's broader regulatory surveillance capability, reinforcing awareness of why trade reporting accuracy matters beyond simple timeliness.

Series 24 candidates supervising ADF trade reporting activity need to understand Rule 7160's MRVP eligibility and its relationship to the underlying Rule 7130(d) content requirements, since a principal's written supervisory procedures should specifically address data quality accuracy as a distinct concern from mere reporting timeliness, mirroring the equivalent supervisory emphasis already discussed in the CAT context. A principal should also understand the order identifier cross-reference to Rules 6830 and 6870 precisely, recognizing that an ADF trade reporting error in this specific field can generate simultaneous exposure under both Rule 7160 and the CAT Compliance Rule Series. Series 57 candidates handling actual trade submission need practical fluency with the Rule 7130(d) content elements Rule 7160 protects, since accuracy at the point of order entry and trade submission is what ultimately determines whether a firm satisfies this ongoing audit trail obligation.

Practical Guidance for Firms

Firms should build their ADF trade reporting quality assurance program around the specific Rule 7130(d) content elements Rule 7160 protects, rather than treating audit trail accuracy as an undifferentiated general concern. A firm's internal review process should specifically verify accuracy in the buy/sell/cross indicator, the short sale and short sale exempt marking, the principal/riskless principal/agent capacity indicator, and, where applicable, the CAT-linked order identifier field, since each of these represents a distinct data point capable of independently generating an audit trail deficiency.

Firms should also recognize the connection between Rule 7160 and their broader CAT compliance program, given the order identifier cross-reference to Rules 6830 and 6870. A firm's CAT quality assurance efforts, discussed extensively in the Rule 6893 entry elsewhere in this dictionary, should not be treated as entirely separate from its ADF trade reporting quality assurance program, since an error in the shared order identifier field can simultaneously implicate both regulatory regimes. Building integrated review processes that check this field's accuracy once, rather than through two entirely separate, uncoordinated review streams, reduces the risk of one program catching an error the other misses.

Firms should treat Rule 7160's MRVP eligibility as useful context for calibrating their own internal escalation response to an identified audit trail accuracy issue, without treating that eligibility as a reason to deprioritize genuine remediation. An isolated, promptly corrected data quality lapse is precisely the kind of issue MRVP treatment was designed to address efficiently, but a firm that discovers a recurring pattern of Rule 7130(d) content errors should treat that pattern with the same seriousness FINRA itself would apply in distinguishing an isolated technical violation from a systemic supervisory failure, rather than assuming MRVP eligibility caps the firm's own potential exposure regardless of how the underlying pattern actually develops over time.

Firms should build specific, dedicated testing for the order identifier cross-reference field into their trade reporting quality assurance program, given how this single field connects a firm's ADF audit trail obligations directly to its broader CAT compliance exposure. A firm's testing protocol should verify not merely that this field is populated, but that the specific value populated genuinely matches the corresponding order identifier used in the firm's own CAT reporting for the same underlying order, since a field that is technically present but substantively inconsistent between the two reporting streams creates exactly the kind of audit trail linkage failure this cross-reference was designed to prevent.

Legal and compliance teams reviewing a firm's historical pattern of MRVP dispositions across its various trade reporting obligations should specifically track whether Rule 7160 violations recur alongside CAT-related findings under Rule 6893, given the direct data linkage between the two rules through the shared order identifier field. 

A firm noticing this kind of recurring co-occurrence pattern has strong reason to suspect a shared underlying root cause, such as a specific system misconfiguration generating inconsistent order identifiers across both reporting streams simultaneously, warranting a coordinated remediation effort addressing both regulatory exposures at their common source rather than treating each individual MRVP disposition as an isolated, unrelated event.