Delegated reporting is an arrangement in which a firm authorizes a third party — a broker, central counterparty, or specialized vendor — to submit its mandatory transaction reports to a trade repository or regulator. The mechanics move to the delegate. The legal obligation, in almost every regime, does not. If reports go in late, incomplete, or wrong, the regulator looks to the firm that owed the report, not to the party that pressed send.
That single point drives everything else about how these arrangements should be structured, supervised, and priced.
What Delegation Is, and What It Isn’t
In a standard arrangement, the delegating firm captures trade data internally and passes it to the delegate. The delegate formats it to the regulator’s schema, validates it, and transmits it to the relevant repository or authority. Smaller asset managers and buy-side firms use delegation because building and maintaining reporting infrastructure across multiple regimes is expensive; a delegate spreads that cost across many clients.
Delegation is not ordinary IT outsourcing. The delegate is performing a regulated function on your behalf, which brings written-agreement requirements, oversight duties, and in some regimes a notification to your competent authority. Ordinary vendor terms will not carry those obligations.
Who Is Liable When a Report Is Wrong
The general rule across major regimes is that delegation transfers the task, not the obligation. The specifics differ enough that they need to be read regime by regime.
EMIR: The Delegating Firm Keeps Full Liability
Article 9(1f) of the European Market Infrastructure Regulation expressly permits counterparties and CCPs to delegate reporting.1Legislation.gov.uk. Regulation (EU) No 648/2012 – Article 9 It does not shift liability. Germany’s BaFin states the position directly: “The obligation of delivering a correct report will not pass to the third party. The party subject to the reporting obligation will not be released from this obligation until the trade repository has received a correct and full report.”2BaFin. Reporting Obligation Under Article 9 of EMIR Late, malformed, or missing submissions by the delegate produce penalties for the delegating counterparty.
MiFIR: A Narrow Carve-Out for ARM-Attributable Failures
Under Article 26 of MiFIR, investment firms remain responsible for the completeness, accuracy, and timeliness of transaction reports as a general rule. But when a firm reports through an Approved Reporting Mechanism or trading venue, the firm is not responsible for failures that are “attributable to the ARM or trading venue.” In those cases, the ARM or venue is on the hook.3European Securities and Markets Authority. Article 26 Obligation to Report Transactions
That carve-out is narrow, and comes with a condition. The same article requires firms to “take reasonable steps to verify the completeness, accuracy and timeliness of the transaction reports which were submitted on their behalf.”3European Securities and Markets Authority. Article 26 Obligation to Report Transactions Errors traceable to data the firm supplied stay the firm’s responsibility. Firms that hand off data and stop checking give up the protection.
US CAT: No Shifting Allowed
FINRA is direct on the point for the Consolidated Audit Trail: “The member receiving or originating the order…is responsible for complying with the CAT Rules, and cannot contract away or otherwise shift this responsibility to a third party.”4FINRA. Regulatory Notice 20-31 The CAT Reporting Agent Agreement holds both the agent and the firm “solely responsible for ensuring that any information or data that CAT Reporting Agent submits to the CAT System is accurate and complete.”5CAT NMS Plan. Consolidated Audit Trail Reporting Agent Agreement There is no MiFIR-style carve-out.
SFTR
The Securities Financing Transactions Regulation permits delegation of SFT reporting to a third party under Article 4.6European Securities and Markets Authority. Article 4 Reporting Obligation and Safeguarding in Respect of SFTs As with EMIR, the delegate’s involvement does not lift the obligation from the reporting counterparty.
EMIR Refit: When Reporting Is Assigned to You by Default
The 2019 EMIR Refit added a rule that goes further than delegation. When a financial counterparty trades an OTC derivative with a non-financial counterparty that sits below the clearing threshold (an “NFC-“), the financial counterparty is “solely responsible, and legally liable, for reporting on behalf of both counterparties” and for the correctness of the reported details.1Legislation.gov.uk. Regulation (EU) No 648/2012 – Article 9
The NFC- has not chosen to delegate; the regulation places the burden on the FC by default. An NFC- can opt back in and report its own side, but it must notify the FC first, and it then assumes legal liability for its own report.1Legislation.gov.uk. Regulation (EU) No 648/2012 – Article 9
UCITS management companies and AIFMs sit in an analogous position: they are responsible and legally liable for reporting the OTC derivatives entered into by the funds they manage. The obligation attaches to the management entity, not the fund.
What the Delegating Firm Still Has to Do
Because liability stays put, the compliance work does too. Regulators expect due diligence before engagement, a written contract that spells out roles, and active oversight for the life of the relationship.
Due Diligence, Before and Throughout
Before signing, assess the delegate’s operational stability, technology infrastructure, control framework, staffing depth, and track record of accurate submissions across the regimes and instrument types you need. For data security, firms commonly look for adherence to standards such as ISO 27001.7International Organization for Standardization. ISO/IEC 27001 – Information Security Management Systems Due diligence does not stop at onboarding. Your oversight duty runs for the life of the contract, so a delegate whose error rates climb or whose staffing thins out is a problem you need to catch before the regulator does.
What the Contract Must Cover
At minimum, the written agreement should address:
- Scope: the instruments, transaction types, and regulatory regimes covered.
- Data security controls for sensitive transaction data.
- Measurable performance metrics such as daily submission success rates, error rates, and time-to-resolution for rejected reports.
- Audit rights over the delegate’s systems, processes, and submission records.
- Error correction: who repairs and resubmits rejected data, and on what timeline.
- Termination and transition, including how quickly reporting access and historical data return to you if the relationship ends.
For CAT reporting agents, FINRA requires that the written agreement outline each party’s functions and responsibilities, including exception management and error correction.4FINRA. Regulatory Notice 20-31
Notifying the Regulator
Under EMIR, national competent authorities must be informed of reporting arrangements, particularly where a financial entity has sole responsibility for reporting on behalf of a non-financial counterparty.8CNMV. Reporting Obligations Under EMIR You also need to confirm that the delegate has correctly registered your Legal Entity Identifier with the relevant trade repository, since LEI codes are mandatory for counterparty identification under both EMIR and MiFIR.9European Securities and Markets Authority. EMIR Reporting
Data Quality Starts With You
The delegate can only report what you send. Instrument type, quantity, price, execution timestamp, counterparty identifiers: any error in these fields will produce a rejected or inaccurate report, and the trail leads back to you as the source. Many jurisdictions require submissions to conform to the ISO 20022 messaging standard.10ISO. ISO 20022 and Regulatory Reporting
Reconciliation That Actually Reconciles
Reconciliation means comparing what the delegate submitted against your internal trade records. For CAT reporting, FINRA expects firms to conduct daily reviews of the CAT Reporter Portal to confirm files were accepted and to identify submission or integrity errors, and to perform periodic comparative reviews of accepted CAT data against internal order and trade records.11FINRA. Consolidated Audit Trail
The frequency and sample size of comparative reviews must be “sufficiently representative of the firm’s overall CAT reporting volume.”12FINRA. 2024 FINRA Annual Regulatory Oversight Report – Consolidated Audit Trail (CAT) A small monthly spot check when submissions run into the thousands per day will not meet the standard. When you use a reporting agent, FINRA also requires you to periodically obtain a complete set of the CAT data submitted on your behalf so you can independently validate accuracy.4FINRA. Regulatory Notice 20-31 Discrepancies trigger your error resolution protocol, and under the CAT rules firms must repair errors by the T+3 correction deadline.11FINRA. Consolidated Audit Trail
Penalties When Reporting Fails
Regulators on both sides of the Atlantic have shown they will impose meaningful penalties, and the existence of a delegation arrangement is no defense.
Under EMIR Article 12, competent authorities can impose administrative penalties or periodic penalty payments when reported data “repeatedly contains systematic manifest errors.” The periodic penalty can reach up to 1% of the entity’s average daily turnover for the preceding business year, imposed for every day the infringement continues, for a maximum of six months.13European Securities and Markets Authority. Article 12 Penalties
The UK’s Financial Conduct Authority has been active in this area. The FCA fined Sigma Broking Limited £1,087,300 for failing to submit complete and accurate transaction reports over a five-year period. That was Sigma’s second fine for reporting failures; the FCA had previously fined the firm £531,600 for failing to report 56,000 transactions and identify 97 suspicious trades.14Financial Conduct Authority. FCA Fines Sigma Broking Limited for Transaction Reporting Failures
In the US, FINRA fined one major broker-dealer $1,000,000 for failing to timely and accurately report tens of billions of equity and option order events to the CAT Central Repository between 2020 and 2024. FINRA Rule 6893(a) requires members to record and report data “in a manner that ensures the timeliness, accuracy, integrity and completeness of such data.”11FINRA. Consolidated Audit Trail TRACE late submissions also carry direct fees.15FINRA. 7730. Trade Reporting and Compliance Engine (TRACE)
When the Delegate Can’t Deliver
System outages, cyberattacks, or the delegate’s own financial distress can interrupt reporting. Because the obligation stays with you, a delegate’s failure does not pause your deadline. FINRA Rule 4370 requires broker-dealers to maintain business continuity plans that address regulatory reporting, and where a firm relies on another entity for a mission-critical system, the BCP must address that relationship.16FINRA. Books and Records In practice, that means a backup route: a second delegate you can activate, or the internal capability to submit directly in emergency mode.
The delegation contract should reinforce continuity from the other side. Termination and transition clauses need to specify how quickly the delegate must transfer data and reporting access back to you, and in what formats. A delegate that holds your reporting infrastructure during a contract dispute is a risk to manage in advance, not after.
Records
Retention periods for reporting-related records vary by regime and are longer than firms sometimes expect. US equities and options records under SEC Rule 17a-4 must be preserved for at least six years, with the first two years in an easily accessible location.17FINRA. SEA Rule 17a-4 and Related Interpretations US swap dealers and other counterparties must keep records throughout the life of the swap and for five years after termination, with swap data repositories subject to a 15-year retention requirement after termination.18Commodity Futures Trading Commission. Final Rule on Swap Data Recordkeeping and Reporting Requirements Under EMIR, CCPs must maintain records on services and activities for at least 10 years, and records on all contracts processed for at least 10 years following termination.19European Securities and Markets Authority. Article 29 Record Keeping
For CAT reporting, FINRA expects firms to maintain the underlying books and records that support reported transactional data, along with a map showing how internal records correspond to reported CAT fields, and to archive CAT feedback within a 90-day window to facilitate corrections.11FINRA. Consolidated Audit Trail Where your delegate holds submission confirmations and error logs, the contract must guarantee your access to those records for the full retention period, including after the relationship ends.