Account Acceptance Is a Trust Company’s First Risk Control

The first decision is the one that binds you

A trust company takes on fiduciary risk the moment it accepts an account, not the moment something goes wrong. Custody, records, distributions and examinations all trace back to what the company agreed to hold, and for whom.

I have spent more than 10 years auditing and testing controls inside banks, broker-dealers and insurers. This month I completed the American Bankers Association’s Certificate in Trust Administration, and the course on account acceptance read to me like a control standard. It asks what an auditor asks: can we do this, should we do this, and can we prove it later?

What acceptance commits you to

Once an account is accepted, the trustee owes the full set of fiduciary duties: loyalty, prudence, keeping trust property separate and identified, keeping accurate records, and accounting for what it holds. Those duties do not shrink because the account is small, the asset is new or the client is in a hurry.

A sound acceptance review settles three things before the first asset arrives:

  • Capability. Can we actually hold and administer this asset, with the systems and skills we have today?
  • Authority. Do the governing document, the parties and the source of funds check out?
  • Capacity. Do we have the people, capital and processes to service the account for its whole life?

In audit terms, acceptance is a preventive control. Reconciliations, reviews and examinations come later and are detective. They can tell you that you took on something you could not handle, but only after you have it.

What two Nevada receiverships show

Nevada has put two digital-asset trust companies into receivership since 2023, and in both the public record points to basic fiduciary questions rather than a market event. I was not inside either company, so I rely on the regulator’s filings and press coverage of them.

Prime Trust, 2023. The Financial Institutions Division’s petition said the company found in December 2021 that it could not reach a set of older wallets it had told customers to use. It then bought replacement crypto with customer money from its omnibus accounts to meet withdrawals (CoinDesk).

Fortress Trust, 2025. The Division issued a cease-and-desist order in October 2025, and coverage of the order reported that the company could not produce recent financial statements or account reconciliations (Bloomberg Law). A court appointed a receiver for its parent in November 2025 (Nevada Department of Business and Industry).

My reading is that both come back to two questions any acceptance process should answer. Can the company reach the assets it agreed to hold? Do its records agree with what it holds?

Five questions for the board

  1. Who can say no? Acceptance should be decided by someone independent of sales, with a committee for exceptions and a record of what was declined.
    1. Write an acceptance policy that lists the account and asset types the company will take, and the ones it will not.
    2. Name the approver for standard accounts, and make sure that person does not report to business development or carry a sales target.
    3. Set up an acceptance committee for anything outside the standard, with risk, compliance and operations each holding a vote.
    4. Keep a log of declined and withdrawn accounts, with the reason for each.
    5. Report approvals, declines and exceptions to the board every quarter.

What good looks like: the decline log has entries in it. A company that has never turned an account away either has a perfect pipeline or has no control.

  1. Can we prove we control the asset? Before the first deposit, test access and recovery for every account or wallet a customer will be told to use.
    1. List every place the asset will sit: bank account, sub-custodian, wallet or key.
    2. For each one, record who holds access, who approves movement, and who can restore access if a person or vendor is lost.
    3. Move a small test amount in and back out before any customer is given deposit instructions.
    4. Run a recovery test on a schedule, at least once a year, and after any change of vendor, key holder or wallet structure.
    5. Require sign-off from operations and risk on the test results before the asset type goes live.

What good looks like: no customer has ever been sent an address or account number that the company has not first moved funds out of.

  1. Do our records tie out from day one? Each new account should be set up on the system of record and reconciled to an independent source, with breaks escalated on a fixed clock.
    1. Open the account on the system of record before the first asset arrives, not after.
    2. Reconcile daily to a source the company does not control, such as a bank statement, sub-custodian report or the blockchain itself.
    3. Have someone who did not process the transactions perform or review the reconciliation.
    4. Set a clock for breaks: for example, cleared in one business day, escalated to the head of operations at three, to the board risk committee at ten.
    5. Keep customer assets in accounts titled and recorded separately from the company’s own money.

What good looks like: on any given day the company can produce yesterday’s reconciliation for every account, with every open break listed by age and owner.

  1. Where do exceptions go? Every waiver of the acceptance standard should be logged, approved by name and reported to the board with its age.
    1. Define what counts as an exception, so that a missing document or an untested wallet cannot be waved through informally.
    2. Record each exception with the reason, the named approver, the compensating control and an expiry date.
    3. Review open exceptions monthly and close or re-approve any that have passed their expiry date.
    4. Give the board a one-page ageing report each quarter: how many are open, how old, and who owns each.
    5. Treat a rising count or an exception renewed more than once as a signal that the standard or the business model needs to change.

What good looks like: every open exception has an owner and an end date, and none has been renewed without the committee seeing it.

  1. Can we hand it back? Termination is the other half of acceptance. If the company cannot return or transfer an asset cleanly, it should not take it.
    1. Before accepting an asset type, write down how it would be returned to the client or moved to a successor trustee.
    2. Confirm at acceptance who is entitled to receive the assets and what documents a release requires.
    3. Build a termination checklist: final reconciliation, fees settled, tax reporting, release and receipt signed.
    4. Test one full exit for each asset type, the same way access was tested on the way in.
    5. Track how long terminations take and report any that run past the target to the board.

What good looks like: the company can state, for every asset type it holds, how many days a full return would take, and it has done one.

Treat acceptance as a control you can audit

The test I would apply is simple: pick any account and ask for the file that shows why it was accepted. If the file exists, is complete and was approved by someone with the authority to refuse, the control works. If it has to be rebuilt from email, it does not.

Nevada’s Commissioner weighs the competence of management and the adequacy of internal controls when licensing a retail trust company (NRS 669.085). A board that can show how each account was accepted has answered that question before an examiner asks it.

Muema Lombe is a risk and audit executive. He holds the ABA Certificate in Trust Administration and the CISA, CRISC, CGEIT, CRMA, CSSLP and CDPSE certifications. The views here are his own and are not legal advice.