Which Cash Can a Family Office Move, Who May Approve It, and What Proves Settlement?

A family office can see US$2.6 million across its bank portals and still be unable to fund a US$800,000 obligation tomorrow. Some cash may belong to another entity. A debit may already be in flight. A reserve may be committed, or the person who can view an account may lack authority to move it.

Family office treasury management keeps these facts in one operating record. It establishes which entity owns each balance, what the office can use at a stated time, who may authorize a movement, and what evidence closes the transfer. A cash forecast supplies future demand; treasury decides what can actually move today.

01What Family Office Treasury Management Controls

Treasury is the recurring control over cash positions and movements across the family office's accounts. It connects a bank view to the entity that owns the money, the rules for using it and the people authorized to act. The record must stay usable when the office operates through several banks, trusts, investment vehicles and currencies.

This is broader than checking a balance in one portal. Bank of America Private Bank describes its family-office treasury offering in terms of payments, liquidity, integration and fraud prevention across personal and business accounts. FIS also identifies bank-account reconciliation and dual authorization as operational challenges for family offices. Those are supplier descriptions, not evidence that a particular office has implemented the controls.

Four adjacent jobs have their own owners. A cash-flow projection estimates future demand; bill pay and capital-call management execute particular obligations. Bank selection chooses institutions. Treasury maintains the cash, authority and movement record those processes use.

02Which Cash Is Available to the Paying Entity?

1A Current Account and Authority Register

A consolidated dashboard is useful for visibility. The decision record needs a few more fields. One row per bank account and currency should show:

This is a standing account record. Keep the bank statement or feed timestamp, entity books, account mandate and current policy accessible from it. A particular cross-entity movement also needs its own route, amount, approver, deadline and decision status; those terms can change from one movement to the next. Do not copy full account numbers or credentials into a broadly shared worksheet.

Here is one filled account record from the illustrative case below. Role names are assigned for this fixture; they do not describe an actual office:

A missing legal route, stale balance or unresolved reconciliation is unknown, with an owner and next check. It is neither zero nor available cash.

2Restrictions, Pending Debits and Operating Floors

For a stated payer and time, calculate office-deployable cash from the account's dated position. This is an internal decision amount. Bank release still depends on its available balance, holds, access and cutoff:

Dated bank position − known debits not yet posted − confirmed holds − approved floor = office-deployable cash, subject to account authority and bank cutoffs.

Record each subtraction once. If the bank's displayed available balance already reflects a hold or debit, do not deduct it again. A receivable expected tomorrow stays out of today's position until it has settled and the receiving account is confirmed. Refresh the position immediately before approval and again before release when a payment cutoff or intervening debit could change the result.

Where a currency conversion is needed, identify its rate, execution owner and settlement timing separately; a translated dashboard total cannot establish that the payer has usable cash in the required currency.

The Cobase family-office treasury discussion names multi-bank visibility, multi-entity handling, controlled payments and audit logs as evaluation points for a treasury system. The register above states the decision fields an office would need whether it uses a system or a controlled manual process.

3Review Access, Concentration and Unmatched Items

Refresh the register routinely, including when no payment is imminent. Assign an owner to update each material account's position and exception status at a cadence that matches the office's payment volume and deadlines. The owner should record when the bank data was last received, who still has portal and signing access, and which movements have not matched the entity books.

Set escalation thresholds for cash concentrated at one institution or held in one currency in the office's own policy. Log an exception when concentration exceeds that threshold, a departed person retains access, or a transfer misses its matching deadline. Record the decision owner, next check and closure evidence. A green dashboard total cannot close an exception whose underlying records still disagree.

03Who Can Authorize a Move Between Entities?

1Decide the Route Before Counting the Cash

An account owned by Entity B cannot simply be added to Entity A's spendable balance. A proposed movement needs the documented route applicable to this transaction. Depending on governing documents and circumstances, that might be an intercompany loan, capital contribution, distribution or reimbursement; these are examples, not interchangeable choices. The required legal, tax and accounting reviews and approvals follow the entities' governing documents, mandates and transaction facts. Record what the actual route requires before treating it as authorized.

The treasury record should name the sending and receiving entities, amount and currency, purpose, proposed route, approving authority, supporting document, bank cutoffs and accounting treatment. If any material element is unconfirmed, label the route pending. A pending route can appear in the funding-options column; it cannot make today's cash test pass.

2Separate Request, Approval, Execution and Verification

For a material movement, assign four acts even when a small office combines some roles under its approved policy:

1. Request: state the payer, purpose, amount and deadline; attach the obligation and proposed funding account.
2. Approve: confirm the entity route, liquidity effect and authority under the applicable mandate and policy.
3. Execute: use the bank's permitted signers and release controls; record the transaction reference.
4. Verify: independently match the outgoing confirmation to the receiving-account credit and send the final record to accounting.

The bank's signers and the family's internal approvers may differ. A person with portal access may only be able to view balances. Conversely, an internal approval may not satisfy the bank's signing rules. Keep both authorities visible. If one person performs multiple acts, record the compensating review that the office actually uses; do not claim separation of duties that has not occurred.

04Work One US$800,000 Funding Decision

The following numbers are illustrative, fixed at 09:00 on a fictional decision day. They are not a family-office result, a bank's available-balance calculation or a recommendation to move money between particular legal entities.

Entity A has a US$800,000 operating obligation due tomorrow. Its approved policy requires a US$300,000 floor after funding. A separate cash-flow projection identified the obligation; the question here is whether treasury can fund it under today's records and authority.

Entity A's separate US$250,000 debit has not yet posted, and its policy floor is US$300,000. In this fictional case, the trust instrument restricts the trust balance to beneficiary expenses; no trustee decision authorizes Entity A's obligation. Recheck bank availability and timing before any release.

1The Payer's US$150,000 Gap

Entity A's US$1,200,000 posted balance is reduced by the US$250,000 unposted debit and US$300,000 required floor. That leaves a provisional US$650,000. Against the US$800,000 obligation, the provisional gap is US$150,000. The debit is assumed absent from the posted figure; if the bank has already reflected it, correct the calculation rather than deducting it twice.

The decision is not funded yet. Treasury can ask whether Entity B has an approved, timely route for at least US$150,000, whether Entity A has another permitted source, or whether the payment date can be changed. It should not show the group-wide US$2.6 million balance as Entity A's liquidity. Nor should it silently lower the floor: a policy exception needs its own authorized decision and record.

2Why Another Entity's Balance Is Still Unknown

Suppose Entity B's controller proposes a US$200,000 transfer. The bank balance alone does not establish whether Entity B can spare it, which route is permitted, who approves it, or when Entity A will receive it. Put each question in the movement record. Entity B's unposted debits, protected floor, route, both entities' approvals, bank signers and cutoff remain unknown.

In this fixture, B's controller validates B's surplus and coordinates its route and approval check. A's controller owns A's funding decision and refreshed cash test. Each entity's mandated approver and bank signer must authorize the act assigned to them; a separate treasury reviewer checks the receiving credit and reconciliation. These are assigned example roles, subject to the actual mandates.

If those checks pass and US$200,000 is credited to Entity A in time, its provisional deployable amount rises from US$650,000 to US$850,000. Paying US$800,000 would leave US$50,000 above the protected US$300,000 floor. Entity B's bank balance would be US$300,000 before its own holds, debits and floor, which still require a separate test.

The conditional verdict is release only if Entity B's separate surplus and route are approved, Entity A receives the net credit before cutoff, its refreshed position still supports US$800,000, and that external payment has its own approval. Otherwise, stop or escalate. The arithmetic alone authorizes nothing.

Keep two statuses separate. The B-to-A funding transfer stays open until Entity A's bank confirms its credit and both entities' books reconcile. The external US$800,000 payment then needs its own release approval, sending-bank status, payee receipt or another obligation-specific independent confirmation, and accounting match. The payee's acknowledgment that payment was received, tied to the invoice, amount and date, is one possible confirmation. If receipt cannot be independently established, label it unverified and keep the payment record open. A funded payer does not prove a paid obligation.

This example tests one movement. It does not replace a rolling liquidity forecast or the invoice and capital-call execution records.

Current status: hold. View the wider desktop diagram. An authorized transfer must arrive before cutoff; the external payment needs its own approval and proof.

05What Proves the Cash Arrived and the Records Agree?

Approval is permission to attempt a transfer. A sending-bank record shows the instruction's or debit's status. Neither alone proves the receiving entity has the cash or that both entities' records now agree.

Close the movement with a short chain of evidence:

The treasury owner records the status and evidence links. Accounting owns the entries and reconciliation under the office's assigned responsibilities; treasury should not assume a bank transfer automatically creates the correct intercompany balance. If the payment deadline arrives while the receipt or route is unresolved, escalate the funding decision to the authorized owner and keep the item open.

06When Should the Office Add a Treasury System?

An office with a small, stable set of accounts may operate a controlled register and bank portals. Repeated difficulty establishing a current position, applying signer rules, tracing movements or closing exceptions may justify a treasury system. Weigh those failures against the office's volume, deadlines and control costs.

Ask a prospective system to demonstrate the office's actual account and authority record: import account ownership and currency, identify stale bank data, preserve approval roles, show the movement through both banks and export a reconciliation trail. Mark a capability unknown if the demonstration does not prove it. Then check contracted modules, bank connections, implementation work and permissions in writing. A demo pass does not establish that the office can cut over safely.

The Cobase guide discusses connectivity, security and payments in a TMS selection; Bank of America's service page shows that a banking relationship may also supply treasury tools. Neither source proves a particular fit for this office. The right test is whether its own account and authority record survives the process.

07A Treasury Control Checklist for the Next Movement

Create two movement records for the worked case. The first moves funds from Entity B to Entity A; the second pays Entity A's external obligation. Each record needs its own owner, amount, route, decision time, approver, bank signer, independent verifier, source links and next action. Keep the standing account register alongside them.

Before either release, refresh the sending account's bank-available balance and source time. Check outstanding holds and debits without deducting the same item twice, the required floor, signer access, the bank's actual cutoff and value date, and the receiving deadline. Record an unknown cutoff or inaccessible signer as a stop, with an owner to resolve it. The 09:00 arithmetic alone cannot authorize tomorrow's payment.

If the B→A transfer cannot clear its gates before the bank cutoff, A's controller must seek another authorized source or change the payment date. The hypothetical US$850,000 deployable amount exists only after the credited transfer and a fresh cash test; it is not the 09:00 status. Timestamp every changed verdict and keep either leg open when its proof is missing.