MiFID Internal Allocations (INTC) & Block Trades: Troubleshooting Guide
Key Takeaways
- INTC Balancing Rule: National competent authorities expect the INTC account to end each day flat, making overnight warehousing explicitly unacceptable.
- Allocation Integrity: Internal allocations should use the earliest market-facing timestamp and a common average price to preserve coherence with the executed block.
- Short-Selling Distinction: Market-facing trades should not carry a short-selling indicator, while client allocations may legitimately require one instead conditionally downstream.
- Linkage Weakness: Current INTC implementation lacks explicit market-to-allocation linkage, making reconciliation operationally complex, manual, and error-prone for firms today broadly.
- Proposed Reform: ESMA's idea of replacing INTC with a unique code could improve matching accuracy but would require material systems changes across firms.
Internal allocations and block trades are a major source of MiFID reporting confusion, especially when using the INTC buyer/seller code. This guide explains what regulators expect, common reporting breaks, and practical controls to reconcile market-facing trades to internal allocations.
As part of the MiFID transaction reporting requirements, a common cause of confusion is the use of the special INTC code when reporting trade allocations. National Competent Authorities (NCA) use this code, in their market surveillance, to identify trades that are part of an allocation. If INTC appears in the Buyer or Seller fields of a MiFID Transaction Report, it serves to link an internal allocation to the market-facing trade.
NCAs expect the following:
At the end of day, the sum of all transactions noted with Buyer or Seller as INTC should sum 0. That is, the account is flat.
All the internal allocations should have the timestamp of the earliest market-facing trade(s) corresponding to the internal allocation.
All allocations have the same price (average price of market-facing trade(s)).
Market-facing trades do not have a short selling indicator, whereas the client allocations may have a short selling indicator.
Each market-facing trade must have more than one internal allocation trade. Otherwise, it would be deemed as a straight transfer between two counterparties without the use of the INTC indicator.
Whilst market-facing trades can have multiple fills, Internal trades are consolidated under one block trade with the market-facing trade considered as the head of the block. Therefore, it would be unlikely that there would be a duplication of LEIs in the internal allocation as the quantities would be combined for each LEI therefore ensuring only unique LEIs appear in the internal allocations.
The final point can cause issues if a firm has several sub funds under one LEI, the Qomply Report Assurance software highlights this as a warning.
Throughout the trading day, firms should keep a careful watch on the balance in the INTC account. Using INTC as an overnight warehouse is not permitted therefore, at the end of the business day the INTC account should be flat.
Another issue with the INTC system is that it can be difficult to identify which market trades match to which allocations as there is no explicit linkage. Systems must be in place to consolidate all INTC trades to ensure that the INTC account balances. This can be a complex task.
ESMA have recognised that there are problems with the current INTC implementation. Therefore, ESMA have proposed the use of a unique code in the buyer/seller code field instead of the code INTC. If ESMA go forward and introduces this change to the MiFID transaction reporting requirements, this would mean that firms would need to change their systems to generate a unique code and insert this into the relevant buyer/seller fields of the market and allocation trades.
The unique code proposal would simplify the matching of market and allocation trades and hopefully reduce the number of errors around allocations. The multiple LEI issue would remain, but the INTC code change would greatly help operations teams and improve reporting accuracy.
Internal trade allocations can occur when a firm places an order in the market and allocates quantities of the overall order across client accounts.
How Qomply can help
Qomply’s Regulatory Reporting Hub combines regulatory expertise with AI, automation and data analytics to deliver scalable, audit-ready reporting intelligence that reduces errors, lowers remediation costs, and minimises operational and regulatory risk.
Covering regimes including MiFIR, EMIR Refit, SFTR, CFTC, CSA, MAS, ASIC and HKMA, Qomply also offers a fully managed service and operates globally from London.
Frequently asked questions
-
INTC is the special buyer or seller code used to identify allocations linked to a market-facing trade. The article says NCAs use it to recognise trades that are part of an internal allocation structure.
-
It says the INTC account should sum to zero by the end of the day. The article stresses that using INTC as an overnight warehouse is not permitted.
-
It says internal allocations should use the timestamp of the earliest market-facing trade and should all carry the same average price from the market-facing executions. The article presents both as core NCA expectations.
-
It says matching is difficult because there is no explicit linkage between market-facing trades and internal allocations. The article notes that firms need systems that consolidate INTC trades so the account balances correctly.
-
It says ESMA has proposed replacing INTC with a unique code in the buyer and seller fields. The article says this would make market and allocation matching easier, although firms would need to change their systems to generate and use the new code.
Purpose-built solutions and services for regulatory reporting
Designed to improve accuracy, reduce risk, and support confident transaction reporting.
