AUM Fee operator guide

AUM Fee accrues an annual management fee against a token's time-weighted supply. This operator guide covers the task flow: configure the rate and recipient, read the current estimate, collect the fee, and freeze the configuration when the programme policy requires it.

For the conceptual model, dilution mechanics, events, and feature-ordering notes, use the canonical AUM Fee architecture page. For endpoint-level facts, use the AUM Fee API reference.

When it attaches

Fund, ETF, money-market-fund, private-equity-fund, and real-estate templates attach AUM Fee. See the system templates catalog.

Configure the fee

In the Asset Designer details step, the wizard surfaces:

The rate is annualised. Collection is an explicit operator action; DALP does not automatically collect the fee on a calendar schedule.

Operate after deployment

After deployment:

• Inspect accrued AUM fees on the asset detail workspace's AUM Fee tab. The tab shows the running estimate since the last collection.
• Collect accrued fees through the platform's fee collection flow. Collection mints newly issued token units to the configured recipient, so existing holders pay through dilution rather than through a treasury transfer.
• Review the collection history when you need audit evidence for previous collections. The collection-events API returns indexed AUMFeeCollected rows with collector, recipient, amount, block, transaction, and timestamp fields.
• Set the rate or recipient through the Manage AUM fee menu when governance approves a change. Collect first when you need a clean cut-off before the new configuration applies.
• Freeze the configuration after launch when the rate and recipient should no longer change. Freeze is irreversible, but collection remains available.

Operating considerations

• The fee accrues against token supply over time, not against an off-chain NAV figure.
• Burns reduce the AUM base for future accrual because they reduce total supply.
• Rate and recipient changes are governance-controlled and blocked after freeze. Collect before changing either value when your accounting period needs a clean break.
• The recipient must satisfy the token's mint compliance rules when collection mints fee tokens. Configure and test the recipient before relying on scheduled operations.
• The feature does not prove that the recipient belongs to the same operating organisation. Treat recipient selection as an operational control.

Troubleshooting

Read next

• AUM Fee architecture: canonical model, events, risks, and feature ordering
• AUM Fee API reference: endpoint paths for estimates, collections, updates, and collection history
• Funds use case
• System templates catalog