CAT Linkage Error 3701

A linkage error is not only a bad field. It is a broken relationship between events. CAT needs to connect order receipt, route, modification, cancellation, execution, and allocation events into a coherent lifecycle. If one event uses one key and another event uses a different key, the central audit trail may ingest both records but fail to link them.

That is why "is this reported by the OMS or clearing firm?" is the right question but the wrong stopping point. The OMS may own the original order and cancel-replace chain. The EMS or FIX gateway may own the outbound route and execution identifiers. The clearing firm may own a service-bureau feed or allocation record. The CAT Reporting Agent may own field mapping and file generation. The counterparty or exchange may own the matching event on the other side. The Industry Member still needs to supervise the process and prove timely repair for the data it is required to report, including the T+3 8:00 AM ET correction window for repairable CAT order-event errors where applicable.

The regulatory responsibility point should stay clean. Using a clearing firm, OMS vendor, service bureau, or CAT Reporting Agent does not remove the Industry Member's responsibility for the timeliness, accuracy, and completeness of the data it must report. A written reporting agreement can allocate operational functions. It does not make the exception disappear from the firm's supervisory record.

The first step is to confirm the code context. Pull the feedback file, reporter portal detail, process date, event type, reporter IMID, destination or counterparty IMID, and CAT event identifier. If the firm's vendor labels the issue as 3701, confirm whether that is the native CAT code or a vendor-normalized code mapped to another CAT feedback category.

The second step is source retrieval. Operations should pull the raw OMS order record, EMS route record, FIX messages, execution reports, allocation records, clearing feed, CAT file row, and reporting-agent transformation log. The goal is to compare the source event to the reported event, not to repair the CAT row blind.

The third step is key comparison. Start with ClOrdID, OrderID, ExecID, Routed Order ID, UTI where applicable, session, symbol or option ID, reporter, destination, event timestamp, and event type. If the internal source value differs from the CAT file value, the likely defect sits in mapping, transformation, truncation, or manual repair. If the source and CAT file match but the linkage still fails, the issue may sit with the other side, sequence timing, exchange linkage, clearing-firm feed, or a CAT known issue.

The fourth step is clock and sequence review. A route after an execution, a child event before a parent event, or a destination event outside the expected window can be a true lifecycle issue or a timestamp defect. That is where CAT clock synchronization evidence matters. The firm should check source time, receipt time, reporting time, timezone handling, and business-clock offset for the affected event window.

The fifth step is ownership assignment. An OMS issue should route to the order-system owner. A FIX or EMS issue should route to the gateway owner. A clearing-feed issue should route to the clearing firm or service bureau under the reporting agreement. A CAT Reporting Agent mapping issue should route to the agent. A counterparty or exchange mismatch may require outreach and external evidence. The firm's compliance owner should still track the case to closure.

The final step is repair and retention. If a correction is submitted, the record should preserve original value, corrected value, root cause, owner, approval, submission timestamp, accepted status, and any vendor or counterparty communication. The assembled evidence pack should be retained in a non-rewriteable, non-erasable WORM archive where the firm's records policy and SEC Rule 17a-4 requirements apply. If the firm determines the issue is on another party's side, it should still retain the analysis that supports that conclusion.