How Venue Sub-Accounts Express a Fund's Segregated Portfolio Boundaries

A fund sub-account at a trading venue does not create a segregated portfolio, and cannot repair a defective one. Its function is to express a boundary that already exists in the constitution of a segregated portfolio company, in a form the administrator can observe, reconcile and value. Where the account structure fails to express that boundary, the vehicle still has segregated portfolios in law, but no independently evidenced net asset value for each. That gap surfaces at the first audit, not the first trade. Choose the account model against portfolio-level reconcilability before any portfolio trades.

Account topology at a venue is an accounting decision long before it is a trading decision. We ask managers to show that every balance can be attributed to one portfolio without a spreadsheet, because a balance needing manual attribution is a balance the auditor will question.David Lloyd, Chief Executive Officer at CV5 Capital

Executive Summary

A segregated portfolio company is one legal entity whose portfolios are ringfenced from one another. A venue contracts with that entity and offers whatever account structures its systems support, so the mapping between the two decides whether portfolio-level reporting survives.

• Venue account structures do not create legal segregation; only venue-issued, portfolio-level records let it be evidenced without manual attribution.
• The taxonomy runs from separately onboarded accounts, through sub-accounts beneath one master, to an omnibus account ledgered internally.
• Margin, close-out and fee logic often operate at master level even where positions report per sub-account.
• Movements between portfolios are transactions between distinct pools of assets and must be documented as such.

What a Fund Sub-Account Must Do for a Segregated Portfolio

The test is narrow. A venue account model works for a segregated portfolio company if a third party, without the manager's records, can establish the balances and transaction history of one portfolio at a defined valuation point. If reaching that answer needs the manager's allocation logic, the model has failed, whatever the venue calls it.

Three properties carry that test. Identity: every account has a stable identifier tied to one portfolio. Completeness: balances, positions, funding, fees and accruals land in an identified account, not a pooled residue. Independence: the record is issued by the venue, not derived by the manager afterwards.

None of this is statutory. Neither the Mutual Funds Act (as amended) nor the Private Funds Act (as amended) prescribes a venue account structure. Both require audited financial statements prepared by a CIMA-approved auditor, and that audit only works where each portfolio's assets can be evidenced separately. The account model is institutional practice driven by an audit consequence, not a rule.

The Account Taxonomy a Fund Meets at a Digital Asset Venue

Venue nomenclature is inconsistent. The same words describe different capabilities across venue categories, so the label matters far less than what the venue will issue in a statement.

At diligence, ask for a specimen statement, not a product description. A venue producing a per sub-account statement showing opening balance, movements, fees and closing balance offers something an administrator can consume. One describing sub-accounts but issuing a consolidated statement offers a trading convenience.

One Legal Entity, Several Portfolios, One Venue Relationship

A segregated portfolio company is a single legal entity, and its portfolios are not separate legal persons. The Companies Act provisions establish that the assets of one segregated portfolio are not available to meet the liabilities of another, and require directors to keep portfolio assets separately identifiable. How a counterparty under another legal system would treat that ringfencing is a separate question, not one an account structure answers; the statutory position appears in how segregated portfolio ringfencing works.

The operational consequence is what matters here. The venue contracts with the company, not the portfolio, so terms of business, margin agreements, netting, close-out rights and fee schedules operate against the entity that signed them.

A sub-account is therefore a reporting arrangement inside one relationship, and should never be described to an allocator as conferring legal separation. What it confers is visibility, from which the net asset value and the audit are built. The segregated portfolio company structure supplies the legal boundary; the account model decides whether anyone downstream can see it.

Choosing an Account Model by Venue Capability and Strategy

Unmargined portfolios

A spot-only portfolio posting no collateral has the widest range of workable models. Sub-accounts beneath a master usually suffice: the balance record is the whole reconciliation and there is no financing to allocate. Deposit addresses must still be dedicated per portfolio, or the on-chain side reintroduces the attribution problem the sub-account was meant to solve.

Margined and derivative portfolios

Once a portfolio posts collateral the question changes from reporting to risk. If the venue margins on aggregate entity exposure, collateral from one portfolio can support positions held by another, and a close-out can consume assets of a portfolio that did not cause the deficit. That exposure is created by the risk engine, and statutory ringfencing does not prevent it operationally.

The workable positions are narrow. Either the venue applies margin and close-out per sub-account, so a margined portfolio can trade there, or it does not, so only one margined portfolio should hold that relationship. Running two margined portfolios through an entity-level risk calculation is the commonest defect in a multi-portfolio vehicle.

Where Cross-Portfolio Exposure Creeps In

Most mapping failures are undramatic. They are pooled amounts and shared benefits nobody assigns to a portfolio until the auditor asks.

Two mechanisms stay invisible in normal conditions. Entity-level close-out shows up only under stress, and pooled accruals only when a portfolio is redeemed and someone must decide who owns the accrued amount. Both should be tested at onboarding, while the questions are cheap. The control problem across multiple venues compounds each once a portfolio trades in several places.

Transfers Between Portfolios and the Wallet Address Map

A movement of assets from one portfolio to another is a transaction between two distinct pools, not an internal transfer. It requires an instruction recorded at board or manager level, a stated valuation basis, a venue or on-chain reference, and matching entries in both ledgers. Where it settles an expense borne by one portfolio, the expense allocation policy should already say so.

Automated venue features are the usual source of undocumented movements. Auto-repayment, unified balance modes, collateral top-up and internal rebalancing tools all move assets between sub-accounts without producing an instruction. Each should be disabled at onboarding and the setting evidenced, because a manager cannot document a transfer it did not initiate.

The same discipline applies on-chain. Each deposit address should serve one portfolio permanently, because a reused address destroys attribution for any inbound transfer sent to it. A register tying addresses and sub-account identifiers to portfolios, with effective dates and version history, is what lets a reconciliation run unattended. Working from venue balances to a portfolio net asset value depends on that register.

Naming, Identifiers and the Per-Portfolio Audit Trail

Naming conventions look trivial and are not. A convention encoding the entity, the portfolio code, the venue category and the account's purpose lets a reconciliation run by matching strings rather than asking the trading desk. Strategy nicknames, trader initials and sequential numbers fail once a portfolio is renamed or a second relationship opens.

Portfolio codes should be immutable for the life of the portfolio and never reused. Identifiers should be issued per sub-account, and interface credentials scoped so no single key can read or act across two portfolios. The administrator should hold read-only credentials of its own, per portfolio, so the reconciliation source is independent of the manager's systems.

Account titling and authorised signatories are a distinct subject. The account must be titled in the name of the company acting for and on behalf of the named segregated portfolio, with signatory authority documented against that portfolio. Those questions are covered under account titling and authorised signatories, and the wider process under venue onboarding for a fund.

What the Administrator Needs to Strike a Portfolio Net Asset Value

The list is short and the same across venue categories. An administrator producing an independent net asset value for one portfolio needs the following, sourced from the venue rather than the manager.

• Balances by asset at the valuation cut-off, per sub-account, with the cut-off stated.
• Open positions with venue marks, and the margin attributed to the sub-account.
• Accrued funding, fees, rebates, interest and rewards at sub-account level.
• A complete transaction history reconciling opening to closing balance.
• Deposit and withdrawal records showing the counterparty address for each on-chain movement.
• The current register mapping accounts, identifiers and addresses to portfolios.

Where a venue cannot supply the first four per portfolio, the administrator is reconciling to a manager-prepared allocation. That is a weaker basis. It should be disclosed as such, raised with the auditor in advance, and reflected in the valuation policy. Appointing an administrator that reconciles per portfolio before venue relationships open avoids finding the limitation at the first period end.

Where no capability expresses the boundary at all, the honest conclusion is that the portfolio should not trade there. That carries a real cost, since the venue may hold the liquidity the strategy needs. The alternative moves that cost to the audit and to operational due diligence.

Key Takeaways

• Select the account model against portfolio-level reconcilability before onboarding, and ask for a specimen sub-account statement.
• Keep margined portfolios off any venue that margins and closes out at entity level, or limit that relationship to one margined portfolio.
• Disable automated sweeps, unified balance modes and collateral top-up at onboarding, and evidence the setting.
• Document every movement between portfolios as a transaction, with an instruction, a valuation basis and entries in both ledgers.
• Dedicate deposit addresses and interface credentials per portfolio, and reuse neither after a portfolio closes.
• Maintain a versioned register mapping accounts, identifiers and addresses to portfolios, with read-only access for the administrator.

Frequently Asked Questions

Does a venue sub-account create legal segregation between portfolios?

No. Segregation arises from the constitution of the segregated portfolio company and the statutory provisions governing it. A sub-account is a reporting arrangement inside a relationship the venue holds with the company, not with any portfolio. It makes the boundary visible, not legally effective.

Can a segregated portfolio company use one omnibus venue account for several portfolios?

It can, but each portfolio net asset value then rests on manager allocation. Venue records are entity level, so the administrator has no independent source for portfolio balances. Expect the auditor to test that allocation closely.

What happens to margin when two portfolios trade at the same venue?

It depends on whether the venue margins at sub-account or entity level. Under entity-level margining, collateral posted by one portfolio can support positions held by another, and a close-out may consume assets of a portfolio that did not cause the deficit. Without sub-account margining, only one margined portfolio should use it.

What should a manager do when a venue offers no sub-account capability?

Treat it as a venue able to support one portfolio only. Either restrict the relationship to a single portfolio, or accept that it does not trade there. Running two portfolios through one undifferentiated relationship turns a venue limitation into a problem for the whole vehicle.

What does an administrator need to value each portfolio separately?

Venue-issued balances and open positions per sub-account at a stated cut-off, accruals at the same level, a transaction history reconciling opening to closing balances, and deposit and withdrawal records with counterparty addresses, plus the current mapping register.