Reporting Timeliness and MPID Mapping

The general rule for trade reporting is that the report has to land at the facility very quickly after execution. The exam tests three windows: 10 seconds (equities), 15 minutes (TRACE debt), and what counts as "late" when a report misses the window. It also tests how a firm uses multiple MPIDs to carve up its reporting activity by desk so the supervisor can attribute every late report to a specific business unit.

The 10-Second Window for Equities

All four equity facilities use the same 10-second window during normal market hours:

A trade reported after 10 seconds must be marked "late" (the late modifier carries through to public dissemination). Normal market hours for these purposes are 9:30 a.m. to 4:00 p.m. ET.

Trades executed outside normal market hours must be reported within the deadlines defined by each facility's rulebook. The general pattern is that pre-market and after-hours executions are reported by the next system open or end of trading day, depending on the facility.

Exam Tip: Gotchas

• All four equity facilities use the same 10-second window during normal market hours. The exam will sometimes try to vary the window by facility; the answer is they are all the same.
• A trade reported after 10 seconds is not "rejected"; it is accepted with a late modifier. The late modifier travels through dissemination so the consolidated tape shows it. The submitting member is also exposed to late-report sanctions under the timely-transaction-reporting standard.
• Normal market hours are 9:30 a.m. to 4:00 p.m. ET. Pre-market and after-hours trades use facility-specific deadlines (typically by the next system open or end of trading day).

TRACE: 15 Minutes for Debt

Debt trades have a more relaxed timeline. The TRACE reporting standard requires each transaction in a TRACE-Eligible Security to be reported as soon as practicable, but no later than 15 minutes after the Time of Execution.

Specific products and time-of-day modifiers may shorten the window. For example, transactions executed less than 15 minutes before TRACE system close must be reported before close. Some asset classes have their own narrower windows.

Time of Execution must be reported to the second, and the firm's clocks used for that timestamp must be synchronized to NIST (the same clock-sync regime that governs CAT, covered in a later section).

Exam Tip: Gotchas

• Equity facilities use a 10-second window; TRACE uses 15 minutes. Test traps swap the windows ("all trade reports must be within 10 seconds") or apply the equity window to debt. The answer is product-specific: equities = 10 seconds, debt = 15 minutes.
• TRACE Time of Execution must be reported to the second, not the minute. Coarse timestamps fail the rule even if the report is on time.
• Specific TRACE products may have narrower windows. The exam-relevant general rule is 15 minutes, but transactions near system close compress that window further.

Timely Transaction Reporting

Beyond any single late report, FINRA's timely-transaction-reporting standard requires each member to report transactions promptly to the appropriate FINRA facility. The principal must monitor for late-trade patterns.

Repeated lateness, even if no individual report is grossly late, is a separate violation independent of any single late report. The supervision focus is on the firm's reporting performance over time, not just one missed report.

Exam Tip: Gotchas

• The timely-transaction-reporting standard is the umbrella "be prompt" rule. A firm that is consistently right at the 10-second edge, with frequent slips into late territory, fails the standard even if no single report is far late.
• A pattern violation is separate from any specific facility's late-report rule. A pattern of lateness can produce both supervisory-pattern sanctions and individual late-report sanctions on the underlying TRF/ADF/ORF/TRACE reports.

Multiple MPIDs

A "Market Participant Identifier (MPID)" is the four-character code that identifies a member's reporting activity on a FINRA facility. A member may use separate MPIDs to identify trade-reporting activity by business unit, desk, or function:

The point of multiple MPIDs is supervisory attribution. With one MPID, every late report and every modifier looks the same to the supervisor; with separate MPIDs by desk, the supervisor can immediately see which desk produced which report.

The principal must maintain a roster mapping each MPID to its responsible desk and supervisor. MPIDs are tested in audits to verify trade-blotter and CAT reporting integrity.

Think of it this way: MPIDs are how the firm and FINRA tell which desk did what. If the equities desk and the convertible desk both report to the same MPID, you cannot tell at a glance which desk produced a late report. With separate MPIDs, every report is attributable.

Exam Tip: Gotchas

• Multiple MPIDs are permitted, but the firm must maintain a roster mapping each MPID to its responsible desk and supervisor. A firm with a dozen MPIDs and no map fails the supervision test even if the reporting itself is on time.
• The TRF MPID-mapping rule covers TRF MPIDs; the ADF MPID rule covers ADF MPIDs. The exam will sometimes try to swap the scopes. ORF MPIDs are governed by the ORF series, not by the TRF/ADF MPID rules.
• MPIDs feed into CAT reporting (covered later in this unit). A misattributed MPID in a CAT report is a CAT violation as well as an MPID violation; the data must be consistent across systems.