For an institutional treasury, cryptocurrency brokerage is best understood as a transaction-intermediation function: it can connect an institution’s transaction request with a trading venue or counterparty. It does not, by itself, define treasury policy, establish who controls assets, or show that a transaction has settled. Those responsibilities must be identified separately in the institution’s workflow and in the documented service arrangement.

What a cryptocurrency brokerage does

A brokerage function helps arrange a transaction between parties or through a trading venue. The institution decides whether a transaction is authorized and specifies its instruction; the intermediary’s role may involve connecting that instruction to a trading process. The label “brokerage,” however, does not establish one universal workflow or service package. The particular arrangement must say what the intermediary does, which other entities participate, and where each role ends.

It helps to distinguish a trading venue’s execution process from an institution’s later operational checks. For example, a centralized exchange can provide near-real-time trading, liquid order books, and advanced order functionality after assets are deposited, but performance and liquidity vary by venue, asset pair, and market conditions. That describes a general centralized-exchange operating model, not a guarantee about any brokerage relationship or its execution results. It also does not establish who holds the assets or what settlement evidence the institution should rely on. source

A brokerage workflow may be described in broad stages: an authorized party submits an instruction; the intermediary connects it to the relevant trading process; the parties receive information about the outcome; and operations checks whether the obligations arising from the transaction have been completed. These stages are a way to map responsibilities, not a universal sequence or statement that a broker performs each task. The evidence available here does not specify a general brokerage settlement method, so the institution should establish that method from the arrangement itself.

Keep the terms “execution” and “settlement” distinct in operational documentation. Execution refers to carrying out the trade; settlement is the completion of the resulting obligation. A trading record may help show what occurred in a venue, but it should not be treated automatically as proof that every settlement and reconciliation task is finished. The applicable records and completion conditions depend on the particular parties and workflow; define them rather than assume them from the service label.

Where brokerage fits in an institutional treasury workflow

Brokerage activity belongs after the institution’s internal decision and authorization to transact. Treasury governance determines the institution’s objectives, risk appetite, and approval process. A brokerage function may help carry out an authorized transaction, but it does not set those objectives or decide whether the institution should hold or transact in a digital asset.

A practical responsibility map can follow the transaction from approval through reconciliation:

  1. Decision and approval: Identify the internal policy and authorized roles that govern whether a transaction may proceed.
  2. Instruction: Record what was requested, who approved it, and who submitted it to the intermediary.
  3. Transaction handling: Document what the brokerage function performs and identify any trading venue or other counterparty involved.
  4. Outcome confirmation: Specify what evidence indicates that the trade was executed and who receives or reviews it.
  5. Settlement and exceptions: Define how the institution determines whether resulting obligations are complete, and who investigates unclear or mismatched records.
  6. Reconciliation: Assign responsibility for comparing transaction information with treasury and accounting records and for resolving differences.

This sequence is a control-mapping aid, not a claim that every institution or service provider uses these exact stages. It makes handoffs visible: an approved instruction is not itself evidence of execution, and evidence of execution does not necessarily establish that the institution’s settlement and accounting checks are complete.

The institution should also separate transaction records from asset-control arrangements. A record of a trade does not answer who can access, transfer, or safeguard the assets involved. The brokerage documentation and the relevant custody arrangements should identify those responsibilities explicitly. Do not infer asset control from the entity that arranged or facilitated a transaction.

Brokerage, custody, and prime brokerage are different functions

Brokerage is the transaction-intermediation function discussed here: helping connect a transaction request with a trading process or counterparty. Custody concerns holding an asset on a customer’s behalf in the specific scope of the 2025 interagency statement concerning covered United States banking organizations. That definition has a defined jurisdiction and institutional scope; it is not a universal definition of treasury management or every custody arrangement. The key operational distinction is that arranging a transaction does not, by itself, tell the institution who holds or controls assets.

Prime brokerage is a related but separate topic. It can refer to a broader institutional service relationship, but the functions and operating models involved are outside this article’s scope. A team should not treat the terms “brokerage,” “custody,” and “prime brokerage” as interchangeable. Instead, identify the functions relevant to its own workflow and verify which entity performs each one. This also helps avoid assuming that an intermediary’s trading role includes custody or other institutional services.

A useful way to prevent confusion is to map the arrangement by function rather than by brand or label. For each step, record the responsible party, the action it performs, the evidence it supplies, and the next party that receives the handoff. The resulting map can distinguish an internal approval from an external transaction service, and a trade record from an asset-control or accounting record, without assuming these are bundled together.

Operational questions to resolve before integrating brokerage

Before adding brokerage activity to a treasury process, answer practical questions from the institution’s actual agreements and operating procedures. The goal is not to assume that a particular service includes a given protection or capability; it is to determine where responsibilities sit and how the institution can verify each handoff.

  • Authority: Who may approve a transaction, who may submit the instruction, and how are those actions recorded?
  • Execution: Which entity arranges or carries out the transaction? What information confirms the outcome, and who reviews it?
  • Settlement: What conditions and records establish completion for this arrangement? Who handles a delayed, unclear, or disputed status?
  • Asset control: Which party holds or controls assets at each stage, and how does that role relate to the transaction intermediary?
  • Accounting and reconciliation: How are transaction details connected to internal records? Who investigates mismatches and documents their resolution?
  • Counterparty and incident procedures: Which entities are involved, what documented procedures govern the relationship, and who is responsible when an operational issue occurs?
  • Compliance and jurisdiction: Which requirements apply to this institution and arrangement? The evidence used in this article does not establish jurisdiction-specific duties, so do not infer them from a general description of brokerage; verify them with authoritative sources and qualified advice.

Market structure can also affect what happens between an instruction and execution. In public-blockchain automated market-maker trading, a swap can be affected by public transaction visibility, execution ordering, pool depth, and price impact before block inclusion. This is a specific execution consideration, not a description of every brokerage workflow or trading venue. If an institution’s transaction path uses this kind of market, its documentation should make clear how that path relates to the intermediary’s role and the institution’s controls. source

The available evidence does not establish general brokerage fees, security protections, service availability, counterparty arrangements, or a universal settlement process. Those details should be established from the documents and procedures for the institution’s own relationship. In the same way, this overview does not determine legal or tax treatment or replace compliance review.

What a brokerage relationship does not decide for the institution

A brokerage relationship does not decide whether, when, or why an institution holds or transacts in digital assets. Those are treasury decisions governed by the institution’s own policy, approvals, and risk controls. Nor does the relationship automatically resolve who has custody, how the institution accounts for transactions, or which compliance responsibilities apply. Each of these functions requires explicit allocation and suitable supporting documentation.

The practical takeaway is to assess brokerage as one component in a wider treasury workflow. Define what the intermediary does, map each handoff from authorization to reconciliation, and verify separately who executes, confirms, settles, and controls assets. The arrangement—not the brokerage label alone—must establish how those responsibilities work together.

Sources and references