Vertical · 4 min read

Fund administrator instruction authority: subscriptions, redemptions and the NAV nobody signed

Nadia Ferreira-StrandOperator's Playbook

Fund operations is a cross-organisational protocol implemented entirely in email, governed by a list of names exchanged at contract signature and updated by correspondence. It processes billions and it has less structure than a purchase order.

Who is authorised to instruct a fund administrator?

A list of named individuals held by the administrator, usually established at onboarding and updated by email. Subscriptions, redemptions and NAV-affecting corrections all move on instructions checked against that list, and the check is that the sender looks like someone on it.

Key takeaways

Administrators maintain authorised signatory lists and verify by matching names, sometimes with callbacks. Instruction content is unbound and list updates propagate by correspondence.
Operational due diligence questionnaires ask whether a signatory list exists. They do not ask whether it can be verified.
Expressing signatory authority as a signed, expiring delegation makes stale authority detectable rather than invisible.

Part of Private capital and fund identity

Prerequisites

The list is real. The check is that the email looks right.

Your administration agreement's instruction and authorised signatory provisions.
The current authorised signatory list, and the date it was last updated.
Twelve months of instruction volume by type and value.

Step 1 — Inventory the instruction types

Not all instructions carry equal consequence, and most fund managers have never listed them.

Instruction type	Typical value	Reversibility
Subscription processing	High	High — funds arrive before shares issue
Redemption payment	High	Low — funds leave
NAV adjustment or restatement	Very high	Moderate — corrections propagate to investors
Expense approval and payment	Moderate	Low
Investor static data change (bank details)	Very high	None
Transfer of shares between investors	High	Low

The last row and the fifth are where the loss sits, and both are commonly treated as administrative rather than as payment instructions.

Step 2 — Test your signatory list

Three questions, answered against the actual list rather than the agreement.

When was it last updated, and by what mechanism?
Does it include anyone who has left the manager in the past year?
Does the administrator hold the same version you do? Ask them to send theirs and compare.

The third question produces the most interesting answers. Divergence between the manager's list and the administrator's list is common and is discovered, usually, during an incident.

Step 3 — Convert the list into delegations

A signatory list is a static document. A delegation is the same information with three properties added: it is signed, it expires, and it is revocable.

delegation:
  issuer:   [manager COO or authorised officer, credential]
  delegate: [named individual, credential]
  scope:    instruction_types = [redemption, expense_payment]
  limits:   max_value_per_instruction = [amount]
            max_aggregate_per_day = [amount]
  notAfter: [6 months]
  depth:    0

Expiry is what fixes the stale-authority problem without anyone having to remember. A departed employee's authority ends at the next renewal even if nobody informs the administrator, which is the failure mode that currently requires diligence to prevent.

Step 4 — Sign the instruction, not just the sender

Authority answers who may instruct. Content binding answers what they instructed.

A signed instruction renders the material terms — investor, amount, account details in full, value date — and the signature covers them. An instruction altered in transit fails verification, which closes the interception case that callbacks are meant to address.

Step 5 — Put it in the administration agreement

Model language, adapted by counsel:

The Administrator shall act only upon Instructions accompanied by a valid cryptographic authorisation issued under a Delegation current at the time of the Instruction and verifiable against the Manager's published verification key. The Administrator shall not be required to act upon, and shall not incur liability for declining to act upon, an Instruction lacking such authorisation.

The second sentence is what makes the administrator willing. It converts refusal from a commercial risk into a contractual protection, which is the change that makes them an ally rather than an obstacle.

Failure traps

Setting expiry too long. Twelve months recreates the stale-list problem at a slower cadence.
Excluding investor static data changes from scope because they feel administrative. They are the highest-value instruction in the list.
Omitting the aggregate daily limit. A per-instruction ceiling alone permits a sequence of instructions under it.
Leaving an email fallback for urgent cases. It will become the normal path within a quarter.

On the evidence base

Loss data specific to fund administration instructions is not published — managers and administrators have no incentive to disclose it, and it would surface in operational due diligence if they did. The mechanics described here come from practice and from adjacent published BEC patterns rather than from a measured sector figure, and this record is graded accordingly.

Three instruction classes, three consequences

What each moves
Instruction	Consequence
Subscription	Investor capital enters; units issued
Redemption	Cash leaves, to a nominated account
NAV correction	Valuation changes for every holder
Signatory list change	Every future instruction is affected

The last row is the one to gate hardest. A change to the authorised signatory list is rarer than any instruction and enables all of them.

Objections and honest limits

“We call back on redemptions above a threshold.” On the amount. The bank account the redemption pays to is frequently a separate field changed on a different day, and it rarely triggers the same callback.

“The administrator holds the relationship.” They hold a list of names. Whether the person sending today's instruction is the person on the list is exactly the unanswered question.

Binding fund instructions

Gate the signatory list change hardest. It is rarer and it enables everything else.
Sign the instruction, not the covering email. Amount, account, entity and date inside the signature.
Render the delta on banking changes. Old and new, plus when it last changed.
Verify without contacting the manager. So the check happens on every instruction, not on suspicion.

Terms used here

Fund administrator: The third party maintaining the register, striking NAV and processing subscriptions and redemptions.
Authorised signatory list: The named individuals permitted to instruct the administrator on the fund's behalf.
NAV: Net asset value — the per-unit valuation a correction changes for every holder at once.

Frequently asked questions

Will administrators accept this? The contractual protection for declining unauthorised instructions is a genuine benefit to them. Several will move faster than their managers expect once that clause is on the table.

What about instructions from investors directly? Investor-originated instructions — redemption requests, bank detail changes — need the same treatment with the investor as signer. That is a larger enrolment problem and the higher-value one.

Does this require systems integration between manager and administrator? No. Verification uses published keys. Neither party grants the other access to anything.

How does this interact with operational due diligence? An ODD questionnaire asking whether a signatory list exists can be answered with something considerably stronger, which is a differentiator in an allocator's review.

Which instruction should be gated hardest? A change to the authorised signatory list. It is the rarest event and it enables every other instruction.

Why isn't a callback on large redemptions enough? It checks the amount. The destination account is usually a separate field changed on a different day, without the same trigger.

What should the signature cover? The amount, the destination account, the entity and the date — not a reference to an email.

Where this fits in Manav

Manav binds the authorising individual to the exact instruction being given — the amount, the destination and the entity — and produces a receipt an administrator, a custodian or an LP can verify without calling the issuer.

See instruction receipts →

Sources and further reading

Fund administration agreement standard terms on instructions and authorised persons.
Operational due diligence questionnaire standards used by institutional allocators.
FBI IC3 2025 Internet Crime Report
Published guidance on fund operations control environments.
ILPA — industry guidance and model documents