Five Sleeves, One Custodial Account: What Sleeve-Level Accounting Means for RIA Operations

The Account the Custodian Sees as One and the Firm Must Run as Five

A hypothetical RIA moves a household's $2.4 million taxable account into a unified managed account with five sleeves: an S&P 500 direct index SMA, a fixed income SMA traded by a third-party manager, a large cap value model, an international ETF sleeve, and a transition sleeve that holds appreciated legacy shares until they can be sold within the client's tax budget. At the custodian, the household has one account and one list of positions.

On Tuesday the client sends in $60,000. On Thursday the fixed income manager trades their sleeve. At quarter end the firm owes that manager a fee on their sleeve alone, the firm's own overlay fee runs on the entire account, and the client asks how the direct index sleeve did against its benchmark. Each of those events depends on whether the firm's platform knows which positions, lots, and dollars belong to which sleeve.

Three questions decide how much of that work falls on a person:

How the books are kept: Each sleeve may have its own positions, transactions, and tax lots, or the sleeves may be labels attached to one account-level list.
How cash moves: A contribution, a withdrawal, or a reallocation between sleeves may be a journal inside the platform, or it may be a manual exercise.
How the outputs are produced: Sleeve-level performance, manager fees, and the client's tax statement may come from the same records, or someone may have to assemble them from separate sources.

A direct index sleeve holds dozens or hundreds of positions, each with its own tax lots, so a sleeve record that drifts from the custodian creates a long list of breaks to resolve. The answers to the three questions set the operations workload for every multi-sleeve account the firm opens.

For a broader look at how to select a direct indexing provider, and why tax management should reach past the index sleeve, the direct indexing provider guide covers the full set of selection criteria. This blog focuses on the accounting and operations underneath a multi-sleeve account, which that guide covers in a single line.

What Does Sleeve-Level Accounting Change in Daily Operations?

Sleeve-level accounting is an investment accounting technique in which the holdings of a single custodial account are tracked in separate account sleeves. How a platform implements it shows up in a different part of the operations day.

The areas it touches are:

Positions and tax lots by sleeve: In VestmarkONE, each sleeve holds the positions, transactions, tax lots, and trading tied to its model or manager. The platform keeps a sleeve-level investment book of record without tagging.
Overnight reconciliation: Transaction, position, and tax lot information from the custodian is ingested overnight and reconciled so that both systems match at the start of the day at the account level. The sleeve records roll up to that account total.
Cash by sleeve: SMA model sleeves typically hold their own cash percentage, which belongs to the manager's mandate and is not treated as account cash. A client who wants a specific cash allocation typically holds it as its own allocation outside the managed sleeves.
Journals between sleeves: Because all positions sit in one custodial account, a transfer between sleeves is an accounting entry in the platform, and nothing moves between sub-accounts at the custodian. VestmarkONE handles these journals automatically during rebalances.
Discretion by sleeve: Whoever has discretion over a sleeve can trade it. A third-party manager can trade a sleeve by viewing it as an account in their own trading window, or by taking a sleeve-level extract and importing trades back into VestmarkONE. An overlay manager without sleeve discretion typically journals funds in and out to prompt the manager's trading, with exceptions such as tax-loss harvesting and sleeve liquidations.
Fees by sleeve: The overlay manager's fee is calculated on whole-account assets, and each manager earns a fee only on their own sleeve. Fee transactions can be prorated across sleeves.
Reporting by sleeve: Performance reporting runs at both the sleeve level and the account level. Firms that move clients from several custodial accounts into one UMA often see those clients receive a single 1099 for the account's tax ID.

Lot-level records by sleeve are also what let tax management target specific lots when the account trades.

Five Scenarios That Show Whether a Platform Keeps Sleeves as Books or as Labels

Each question below is tied to an ordinary operations event instead of a general question about multi-sleeve support, since the general version is easy for any vendor to answer with a yes. Each scenario pairs the event with an answer that shows separate sleeve records and an answer that signals sleeves are labels on one list.

Bring these into a live demonstration, where the follow-up detail matters as much as the first answer.

Scenario	What To Ask	Strong Answer	Weak Answer Signal
The custodian file arrives and a position does not match the books	How does the platform reconcile the custodian's account-level file against each sleeve, and who resolves a break?	Custodian positions, transactions, and tax lots are ingested overnight and reconciled to the account total. Each sleeve carries its own lots, so a break traces to a sleeve and a lot	Sleeves are tags on account-level lots, so a break appears as one account-level difference that someone allocates across sleeves by hand
A client contributes $60,000 on Tuesday	Where does the cash land, and which sleeves receive it?	A documented rule tied to the account's target allocation. The overlay manager handles the cash, and rebalance journals move it between sleeves inside the platform with no custodial transfers	Cash waits at the account level until someone allocates it, or the result depends on which person handles the account
A client asks to move 10% from the fixed income sleeve to the direct index sleeve	What happens to the tax lots and the custodian records when assets move between sleeves?	The move is a journal in the accounting engine, the positions stay in the same custodial account, and the lots carry their original dates and cost basis	The platform sells and repurchases, or the firm has to move assets between sub-accounts at the custodian
A sleeve manager is replaced	How is a sleeve added, replaced, or liquidated, and what record of the change remains?	The change is made at the product level, the platform adds or removes the sleeve, an audit history is kept, and the account's other sleeves are untouched	Replacing a manager means closing and reopening accounts or rebuilding the allocation account by account
Quarter end arrives with manager fees, an overlay fee, and a client performance review	Can the platform produce sleeve-level performance, sleeve-level fees, and an account-level view from the same records?	Performance and fees come from the sleeve records at both levels. The overlay fee runs on whole-account assets, each manager's fee runs on their own sleeve, and fee transactions can be prorated across sleeves	Only account-level performance is available, and operations rebuilds sleeve returns and fee splits in spreadsheets

The Question Most RIAs Never Ask: Are Sleeves Separate Books or Labels on One Book?

Most RIAs ask whether a platform supports multi-sleeve accounts. Nearly every platform says yes, because most can display more than one model inside an account. Far fewer ask how the platform stores a sleeve.

Two designs answer that question differently:

Sleeve tagging keeps one account-level list of positions and lots and attaches a sleeve label to each.
Sleeve-level accounting keeps a separate set of positions, transactions, and tax lots for each sleeve and reconciles them to the account.

Vestmark describes VestmarkONE as the second design. It maintains a true sleeve-level investment book of record that tracks tax lots and transactions at the sleeve level, without tagging.

A hypothetical shows where the designs diverge. The same large-cap stock sits in two sleeves of one account, the value model sleeve and the direct index sleeve. When the same security appears in more than one sleeve, each sleeve keeps its own position, with its own lots, drift, and performance. That means:

The value manager's performance reflects only that sleeve's shares of the stock
The direct index sleeve's tracking against its benchmark reflects only its own shares
If the value manager is replaced, that manager's shares leave with the sleeve and the direct index sleeve's lots stay as they were

A tag-based design has to decide, at the moment of each event, which shares belong to which sleeve. A useful vendor question is how that decision is made and where it is recorded.

Separate books still allow one set of tax decisions. VAST's optimizer operates at the total account level, so a loss harvested in the direct index sleeve and a gain realized in the value sleeve are netted within the account. The sleeve records then show which sleeve each came from.

Putting the design question to a vendor directly shows which kind of platform it is: "Take one security that sits in two of my client's sleeves. Show me the lots, the cost basis, and the performance for each sleeve, then replace one of the managers."

Two answers tend to come back:

A platform with sleeve-level books will show two positions with separate lots, separate performance, and a sleeve removal that leaves the other sleeve unchanged.
A platform that uses labels will show a single position with a sleeve column, and the replacement will involve re-allocating lots.

Separate sleeve books also carry more operational work than blending several models into a single allocation. A blended account merges overlapping holdings into one position, which simplifies maintenance and gives up manager-level performance and fee attribution.

It is also not intended for manager-traded models. For a firm that needs per-manager reporting, fees by sleeve, or a third-party manager with real trading discretion, the sleeve design makes the account possible, and the platform's job is to absorb the added work.

What to Ask Reference Clients About Running Multi-Sleeve Accounts

A reference call about direct indexing in general will rarely surface how the accounts are run day to day. A call focused on sleeve operations will. Organize the conversation around four areas.

Reconciliation and Breaks

How many sleeve-level breaks does the operations team see in a typical week, and where do they come from?
When a break appears, can the team trace it to a sleeve and a tax lot without leaving the platform?

Cash and Journals

How is cash handled when a client contributes or withdraws, and who decides which sleeves are touched?
How often does someone on the team journal between sleeves by hand?

Manager and Sleeve Changes

When the firm replaced or added a sleeve manager, what happened to the existing lots, and how long did the change take?
How did the change appear in the audit history?

Billing and Reporting

Does the firm produce sleeve-level fees and performance from the platform, or from spreadsheets?
Did clients with multi-sleeve accounts receive a single 1099, and did that change the questions the firm gets at tax time?

How Does an Operations Week Play Out With Sleeve Books or Sleeve Labels?

In a firm whose platform keeps separate sleeve books, an operations week tends to look like this:

The overnight reconciliation finishes before the team starts, and exceptions are listed by sleeve
A contribution is invested through a rebalance, and the platform generates the journals between sleeves
A manager change is a product change, and the platform adds or removes the sleeve
Month-end fee and performance files come from the sleeve records

In a firm whose platform relies on sleeve labels, the same week tends to look different:

Reconciliation breaks appear at the account level, and a person decides which sleeve they belong to
New cash waits for someone to allocate it
A manager change involves rebuilding the allocation or opening new accounts
Month-end billing and sleeve returns are rebuilt in a spreadsheet, and the results vary by preparer

Both lists are illustrative composites for comparison. They do not describe any specific Vestmark client or competitor.

Three Things to Request Before You Commit to a Platform

A multi-sleeve walkthrough on your own account structure. Ask the vendor to build an account with at least four sleeves, including a direct index sleeve and a manager-traded sleeve, and to show the positions, lots, and cash for each. Include one security that appears in two sleeves.
A walkthrough of three cash events. Ask the vendor to process a contribution, a withdrawal, and a reallocation between two sleeves, and to show the journals created, the sleeves touched, and the tax lots relieved.
Sample outputs and references from live multi-sleeve accounts. Request sleeve-level and account-level performance, a fee calculation with an overlay fee and a manager fee, and the year-end tax statement. Ask for reference clients who run accounts where more than one party has trading discretion.

RIA Evaluation Checklist: Sleeve-Level Accounting and Operations

Use the checklist below during vendor evaluation or an internal platform review to confirm that sleeves are kept as separate books. Each row describes a mechanism a firm should be able to see and verify.

A general assurance that the platform supports multi-sleeve accounts does not meet any of these rows.

Evaluation Area	What Strong Sleeve-Level Operations Look Like
Sleeve records	Each sleeve has its own positions, transactions, and tax lots, and sleeves are more than tags on one account-level list
Custodian reconciliation	Custodian data is reconciled overnight at the account level, the sleeve records roll up to it, and a break traces to a sleeve and a lot
Cash by sleeve	Sleeve cash and account-level cash are kept apart, with documented rules for contributions and withdrawals
Journals between sleeves	Transfers are platform journals created during rebalances, with no movement at the custodian
Duplicate securities	The same security in two sleeves keeps separate lots, drift, and performance in each
Discretion	Each sleeve can have its own source of trading discretion, including a third-party manager, and the overlay manager's exceptions are documented
Sleeve changes	Adding, replacing, or liquidating a sleeve is a product change with an audit history
Fees	The overlay fee runs on whole-account assets, manager fees run on sleeve assets, and fee transactions can be prorated across sleeves
Reporting and tax statements	Performance is available at the sleeve and account level, and the approach to the client's 1099 is documented
Link to tax management	Tax decisions are made across the whole account and recorded by sleeve
Exception management	Drift parameters and exception-based views let operations review the accounts that need attention instead of every account

Explore Sleeve-Level Accounting with Vestmark

For RIAs running more than one strategy for a client, the accounting design decides how much manual work sits behind each account. VestmarkONE keeps a sleeve-level investment book of record that tracks positions, transactions, and tax lots by sleeve without tagging. It reconciles to the custodian overnight and handles journals between sleeves during rebalances. It supports accounts in which an overlay manager and third-party managers each hold discretion over their own sleeves.

VAST applies tax optimization across the whole unified managed account on top of those records. Vestmark has supported leading direct indexing providers for more than a decade, and VestmarkONE supports six of the top 10 managed account program sponsors. Learn more about Vestmark's Investment Advisory solutions, or visit Vestmark's page for RIAs.

Ready to see how your current platform handles a five-sleeve account on an ordinary Tuesday? Contact Vestmark to learn how VestmarkONE and VAST support sleeve-level operations for RIA clients.

Key Takeaways

A custodian sees one account. The firm has to run several sleeves inside it, and the platform's accounting design decides how much of that work is manual.
Sleeve-level accounting keeps positions, transactions, and tax lots for each sleeve, while sleeve tagging attaches labels to one account-level list. Ask a vendor which one it uses.
Cash, journals between sleeves, manager changes, fees, and reporting all follow from that design choice.
A security held in two sleeves should keep separate lots, drift, and performance in each, and removing one sleeve should leave the other unchanged.
Separate books still allow one set of tax decisions. VAST's optimizer works at the total account level, and the sleeve records show where each trade landed.
A reference call about daily sleeve operations reveals more than a reference call about direct indexing in general.

_{Important Disclosures: Vestmark Advisory Solutions, Inc. ("VAS") is an SEC-registered investment adviser subsidiary of Vestmark, Inc., acting as a paid sub-advisor and/or overlay portfolio manager offering VAST and tax optimization services. Investing involves risk, including loss of principal; past performance does not guarantee future results. Tax-loss harvesting involves the risks that the new investment could perform worse than the original investment and that transaction costs could offset the tax benefit. Investment strategies that seek to enhance after-tax performance may be unable to fully realize strategic gains or harvest losses. UMAs are not suitable for all investors. The account, bonds, budgets, and figures in this guide are hypothetical and illustrative and are not a projection of results. The tax treatment described on this page is general and may not apply to every client. It is not tax advice, and clients should consult a tax professional.}

FAQ

What is sleeve-level accounting in a unified managed account?

Sleeve-level accounting tracks the holdings of one custodial account in separate sleeves. In VestmarkONE, each sleeve holds the positions, transactions, tax lots, and trading tied to its model or manager, and the sleeves are reconciled to the custodian's account-level records each night.

How is sleeve-level accounting different from sleeve tagging?

A tagging design keeps one list of positions and lots at the account level and marks each with a sleeve label. Sleeve-level accounting keeps a separate set of records for each sleeve. The difference appears when something changes, such as a break, a reallocation, or a manager replacement, because a tag-based design has to infer which shares belong to which sleeve.

How does cash work across sleeves?

SMA model sleeves typically hold their own cash percentage as part of the manager's mandate, and that cash is not treated as account cash. A client who wants a specific cash allocation typically holds it as a separate allocation outside the managed sleeves. The overlay manager is typically responsible for cash management across sleeves when the client contributes or withdraws.

Is a multi-sleeve account harder to operate than a blended model account?

It involves more work. A multi-sleeve account requires sleeve creation, more than one source of discretion, and drift and tax lots tracked by sleeve. A blended account merges overlapping holdings into one position, which is simpler and gives up manager-level performance and fee attribution. Firms that need those attributions, or that use a manager-traded sleeve, choose the multi-sleeve design and rely on the platform to handle the added work.

Does a multi-sleeve account mean the client is taxed separately on each sleeve?

The sleeves are accounting records inside one custodial account, and tax statements follow the account's tax ID. A firm that consolidates several custodial accounts into one UMA often sees clients receive a single 1099. VAST optimizes taxes across the entire account, so losses in one sleeve can offset gains in another.