The trade blotter for a small RIA: what to record for every trade, and why
A trade blotter is the firm's own chronological record of each trade: the account, security, side, quantity, date, the strategy it implements and the reason for it. The custodian's confirms show what happened; the blotter shows why. For a small RIA the most useful habits are linking every trade to the account's strategy of record, writing the reason in one line, and reconciling the blotter against custodian confirms on a set schedule.
An account in your balanced model sold half its bond fund in March while every other account in the model held. Six months later someone asks why. The custodian's confirm shows the sale: date, quantity, price. It says nothing about the client who called to raise cash for a house deposit. That reason exists only if the firm wrote it down.
What is a trade blotter?
A trade blotter is the firm's own chronological record of its trades, with the details of each one and the reason it was placed. Custodian records answer "what happened" and nothing else. When someone asks why a trade was placed, whether it matched the client's strategy, or why one account traded differently from the rest of the model, the answer has to come from the firm's own records.
What should each entry record?
Each entry should record six things, enough to match it to a confirm and to explain it without the adviser in the room.
| Field | Why it matters |
|---|---|
| Account | Ties the trade to a client and household. |
| Security, side and quantity | The basic facts, matched later to the confirm. |
| Trade date | Places the trade in time against the strategy of record. |
| Strategy implemented | Shows the trade served the model the account follows. |
| Reason | Rebalance, cash raise, client request, tax decision: one line. |
| Exception note | Anything that departs from the model, and why. |
How do you tie trades to the strategy?
You tie a trade to the strategy by linking it, at entry, to the account's dated strategy of record. Every account should have one. A trade that doesn't fit, for example a client-directed sale in a modelled account, goes to an exception list with its reason. That list is short when things are working and is the first place to look when something isn't.
A worked example
Take a two-person RIA with about 120 households. The firm and its trades are hypothetical. In one week it places a quarterly rebalance across one model and two one-off trades.
| Entry | Strategy | Reason | Confirm match |
|---|---|---|---|
| 18 accounts, rebalance trades | Balanced model, current version | Quarterly rebalance, bands breached | All 18 matched |
| Account sells bond fund | Balanced model | Exception: client cash request for property purchase | Matched |
| Account buys single stock | Growth model | Exception: client-directed purchase, unsolicited | Matched |
| No blotter entry | None | None | Confirm for a dividend reinvestment |
The reconciliation turns up one confirm with no entry. It's a dividend reinvestment set up at the custodian, which nobody placed by hand. The firm notes it as an automatic transaction and decides, in its procedures, how such trades will be recorded from now on. Two exceptions in a week, each with a one-line reason, is a list someone can review in a minute.
How do you reconcile against the custodian?
You reconcile by matching every confirm to a blotter entry and every blotter entry to a confirm.
- Import the custodian's confirms regularly.
- Match each confirm to a blotter entry by account, date, side, quantity and security.
- Investigate any confirm with no blotter entry, and any blotter entry with no confirm.
- Keep the match result with the record.
What about trades from before the blotter existed?
Load the history you have, mark it clearly as legacy, match it to confirms where you can, and use the full process from that date forward. Most new firms and firms changing systems have this gap. Don't fill in reasons after the fact as though they were recorded at the time. A clearly labelled legacy section is honest. Reconstructed reasons that look contemporaneous are a problem waiting to happen.
When is this overkill?
A firm that places a few dozen trades a quarter, all model rebalances, can keep a blotter in a spreadsheet and reconcile monthly in under an hour. The reason column will mostly say "rebalance". That's fine. The fields still matter, because the one trade that isn't a rebalance is the one you'll be asked about. A dedicated tool starts paying for itself when trade volume, the number of models, or the number of people placing trades makes a spreadsheet match slow or error-prone.
How Advorra handles trades
Advorra's trade blotter ties each trade to the strategy it implements, keeps an exception queue for trades that don't match an account or model, and supports legacy trade upload from a template, matched to custodian confirms where possible. If you want every trade linked to its strategy at entry, see the product page, or read about the strategy of record.
General information, not legal or compliance advice. Your procedures and compliance consultant decide what your firm must record.
Questions advisors ask
How often should the blotter be reconciled to confirms?
Set a schedule in your procedures and keep it. Weekly or monthly is a workable range for a small firm. The longer the gap, the harder it is to remember why an unmatched trade happened.
How do I record a block trade allocated across accounts?
Record the block and each account's allocation, with the allocation method. The confirms will come back per account, so the match happens at the allocation level.
Should cancelled or corrected trades stay on the blotter?
Yes. Mark them as cancelled or corrected with the date and reason rather than deleting them. A missing entry is harder to explain than a corrected one.
Who should enter trades on the blotter?
Whoever places the trade, at the time it's placed. Entering trades days later from confirms turns the blotter into a copy of the custodian's record and loses the reason.
Is this compliance advice?
No. It is a practical description of trade records. Your procedures and compliance consultant decide what your firm must record.
See it on a demo firm
Advorra is practice software for independent RIAs: clients, models, IPS, billing and compliance records in one place, on top of the custodian you already use. Built by The CollabHub.
Get in touch