Reading a digital asset SMA execution report: a guide for allocators
A line-by-line reading of a transaction cost report, including the questions it leaves unanswered.
The page below is an execution report for a single order in a managed account: a purchase of 25 bitcoin, worked over two hours. Every figure on it is invented for the purpose and describes no real trade or market level.
Illustrative figures only. Prices in USD per BTC.
Pages like this tend to sit near the back of a reporting pack, behind performance and the manager's commentary, and they are easy to file unread. In a separately managed account that is an expensive habit. The allocator owns the assets directly, so every basis point lost between the decision and the execution comes out of their own return.
What a digital asset SMA execution report records
An execution report, often called a transaction cost analysis or TCA report, is the broker's account of how an instruction became a set of trades. Read from top to bottom, it answers a narrow question: given the order as it arrived, how was it worked and what did that cost? Whether the order was a good idea belongs to the manager's performance review and appears nowhere on this page.
The order line: instruction, timestamps, and execution method
The first rows fix the terms of the test. The instruction gives the quantity and the direction. The received timestamp marks the moment responsibility passed from the manager to the broker, and every later measurement is anchored to it. An allocator who compares this time with the manager's own decision log can see how long an idea waited before anyone acted on it. No broker report captures that delay, because the broker's clock starts only on receipt.
The method row carries as much weight. This order was worked as a TWAP, which slices the quantity evenly across a two-hour window. That was a choice, made by the manager or agreed with the broker, and it shapes every number beneath it. A patient schedule accepts the risk of the market moving during the window in exchange for a smaller footprint in the order book. The fill timestamps confirm the schedule was followed, with the first trade inside a minute of receipt and the last shortly before the window closed.
Venue-level fills in a crypto execution report
Digital asset liquidity is spread across many exchanges, and a single order is commonly completed on several of them. A report that shows only an average price hides that. Venue-level fills let the reader see where the quantity went and what was paid on each exchange.
In the example, nearly half the order traded on Venue A, and Venue B produced the highest price of the three. Neither fact is a problem on its face. Prices differ between venues from one moment to the next, and a router will pay slightly more on one exchange once the depth it needs has run out elsewhere.
The breakdown earns its place over time. An allocator who sees the same venue taking most of the flow month after month has a fair question to ask about why, and about how much exposure to that venue the account carries as a result.
Execution benchmarks: arrival price and interval TWAP
A fill price means little without something to compare it with. The example offers two comparisons, and they disagree.
The arrival price is the mid-market price at the moment the order was received, here 100,000.00. The order filled at an average of 100,056.80, which is 5.7 basis points worse. Measured this way, the cost covers everything that happened after the broker took the order, including the order's own impact and any drift in the market across the two hours.
The interval TWAP is the time-weighted average market price over the same window, here 100,070.00. Against that yardstick the order did 1.3 basis points better. The market rose while the order was being worked, and the fills kept pace with it.
Both figures are accurate, and they answer different questions. Arrival price asks what the decision cost to implement. Interval TWAP asks whether the schedule was carried out competently once it had been chosen. A report that offers only the second will rarely look bad, because the benchmark moves with the market and absorbs part of the order's own impact. A report that offers only the first can hold the broker responsible for a market move nobody controlled. An allocator shown both can tell the two effects apart.
One caution applies to any market-wide benchmark in this asset class. Digital asset markets have no consolidated tape, so a TWAP or VWAP is calculated from a set of venues that somebody selected. The report should say which venues those were.
Fees in an SMA execution report: charged separately or inside the price
The final rows deal with what the broker was paid. Here the fee is 5 basis points of the traded value, shown on its own line as USD 1,250.71. The all-in price of 100,106.83 adds that fee back to the average fill.
This presentation allows a clean reading. Of the total implementation cost of 10.7 basis points against arrival, 5.7 went to the market and 5 went to the broker. Some providers earn their revenue inside the price instead. Their fill prices already contain the charge, and the slippage figure quietly mixes market cost with margin. The report looks simpler and the fee line may read zero, yet the allocator is left with no means of telling how much of the gap to the benchmark was paid to the market and how much to the intermediary.
Exchange fees need the same treatment. They vary by venue and by whether an order adds liquidity to the book or takes it, so the report should state whether they sit inside the fill prices or are passed through as a separate line.
What transaction cost analysis cannot tell an allocator
A single report describes one order on one morning. Its slippage figure blends the order's impact with market movement that would have happened anyway, and nothing on the page can separate those for an individual trade. The pattern becomes legible only across many orders, where market drift tends to cancel out and persistent cost remains.
The report is also silent on the alternatives. It cannot show what a faster schedule or a different mix of venues would have achieved. It may say nothing about quantity that was requested but never filled, unless the provider chooses to include it, and an unfilled order carries a cost of its own because the position the manager wanted was never fully held.
These limits are the reason to read execution reports as a series. Average slippage against arrival, tracked by order size and by method, shows whether costs rise sensibly with the difficulty of the order. Venue shares reveal whether routing responds to conditions or runs on habit. The interval between the manager's decision and the broker's receipt, which the allocator has to assemble from two sources, can matter as much as anything inside the report.
All of this depends on the reports being comparable from one period to the next, with the same benchmarks and the same fee treatment each time. That consistency is far easier to write into a mandate at the outset than to negotiate after a disappointing quarter.
If you're exploring digital asset SMAs, speak to us.