Do Vault Previews Include the Fund Entry Fee?
ERC-4626 fee preview reconciliation is the control that proves a vault quote, the investor cash leg and the fee recipient balance describe the same subscription or redemption. The standard requires preview methods to include deposit and withdrawal fees, while conversion methods must exclude them, so the two numbers legitimately differ.
TL;DR — Key Takeaways
- ✓Specification: ERC-4626 preview methods must include deposit or withdrawal fees; convertToShares and convertToAssets must exclude them.
- ✓Convention: A fee on the total paid and a fee on the net invested differ: about 497.51 versus 500.00 on an illustrative 100,000-unit deposit at 50 bp.
- ✓Evidence: Reconcile gross cash, net shares and the fee recipient balance for every subscription and redemption, not just the transaction hash.
- ✓Separate fees from rounding and from donation effects before opening an investor exception.

Which vault methods include the fee?
The four ERC-4626 preview methods include the fee for their operation; the two conversion methods do not. A screen that shows convertToShares as the investor's allocation overstates the result by exactly the entry fee.
ERC-4626 is a Final standard, and it is explicit on this point. Conversion functions describe an idealized exchange between assets and shares. Preview functions simulate the actual operation in the current block, including the charge that the vault applies to that operation.
| Method | Fee treatment in the standard | Rounding direction |
|---|---|---|
| convertToShares / convertToAssets | Must not include fees charged against vault assets | Round down |
| previewDeposit | Must include deposit fees | No more than the exact shares |
| previewMint | Must include deposit fees | No fewer than the exact assets |
| previewWithdraw | Must include withdrawal fees | No fewer than the exact shares |
| previewRedeem | Must include withdrawal fees | No more than the exact assets |
previewDeposit: “MUST be inclusive of deposit fees. Integrators should be aware of the existence of deposit fees.”
ERC-4626: Tokenized Vaults, previewDeposit specification
The standard defines the interface, not the fee level, the fee base or who receives it. Those come from the implementation and the product documents. How ERC-4626 sits alongside permissioned share tokens is covered in the RWA token standards guide.
How does an entry fee change a subscription?
An entry fee splits one gross cash amount into two destinations: assets that buy shares and assets sent to the fee recipient. Reconciliation must show both parts and prove they sum to the investor's payment.
Take an illustrative vault where one share converts to 1.00 asset unit and the entry fee is 50 basis points, calculated the way the OpenZeppelin fee example does for deposits: as a portion of the total amount paid. An investor deposits 100,000 asset units. The fee is 100,000 × 50 / 10,050, about 497.51. The net 99,502.49 units buy about 99,502.49 shares.
In that scenario convertToShares(100,000) returns 100,000 shares, while previewDeposit(100,000) returns about 99,502.49. Both are correct. Only the second describes what the investor will receive, and only the second belongs on a confirmation or contract note.
Illustrative deposit of 100,000 units at a 50 bp fee on the total: fee 497.51, net shares 99,502.49. The idealized conversion shows 100,000 shares for the same input.
OpenZeppelin ERC-4626 fee example; editorial calculation
The fee recipient is an implementation choice. The OpenZeppelin example transfers the fee to a configured address after the deposit and skips the transfer when the recipient is the vault itself; in that case the fee stays in the vault and benefits existing holders. OpenZeppelin labels that contract unaudited and not production ready, so it shows one design, not market practice.
Why can the fee terms and the contract disagree?
A rate such as 0.50% does not specify its base. Charged on the total paid, it yields a different fee from the same rate charged on the net amount invested, and both can be implemented correctly.
Using the same illustrative deposit, a prospectus that says “0.50% of the gross subscription amount” implies a fee of 500.00 and net investment of 99,500.00. The contract above charges 497.51 and invests 99,502.49. The investor receives 2.49 more shares than the administrator's spreadsheet expects, a difference of about 2.5 basis points of the subscription.
Mint and withdraw paths in the OpenZeppelin example add the fee on top of a requested net amount, while deposit and redeem take it out of the total. One vault can therefore apply both conventions, depending on which function the investor or distributor calls. Record the function name alongside the amount.
The fix is documentation, not arithmetic: the product terms, the deployed code and the administrator's fee calculation must name the same base, the same rounding direction and the same entry function before the first subscription.
How should an exit fee appear in a redemption?
previewRedeem must return assets after the withdrawal fee, so it is the number an investor statement should show. convertToAssets on the same shares returns the pre-fee value.
Illustratively, an investor redeems 10,000 shares when one share converts to 1.02 asset units, with a 30 bp exit fee taken from the total. The gross value is 10,200.00, the fee is 10,200 × 30 / 10,030, about 30.51, and the investor receives about 10,169.49. A fee charged at 0.30% of gross would be 30.60, leaving 10,169.40.
A preview that includes the fee still may not be executable. Limits, gates and paused redemptions are a separate question addressed in why a vault can quote an exit you cannot execute. Fee reconciliation assumes the operation executed; it explains the amount, not the eligibility.
previewWithdraw and previewRedeem: “MUST be inclusive of withdrawal fees. Integrators should be aware of the existence of withdrawal fees.”
ERC-4626: Tokenized Vaults, preview method specifications
Is the shortfall a fee, rounding or a donation?
Classify every gap between expected and actual shares before raising an investor exception. Fees scale with the amount, rounding stays within a few base units, and donation effects change the exchange rate itself.
| Cause | Signature in the data | Evidence to collect |
|---|---|---|
| Entry or exit fee | Gap proportional to amount; matches the stated bp rate | Fee recipient balance change in the same transaction |
| Rounding | Constant gap of a few base units regardless of size | Raw integer outputs and the rounding direction for the method |
| Unit error | Gap of a power of ten | Asset and share decimals used by each system |
| Donation or rate change | totalAssets moved without matching share issuance before execution | Vault balances in the block before and after the subscription |
The last row is a different failure, explained in how a vault donation can dilute a small RWA subscription. A power-of-ten gap usually means one system applied the wrong precision, the problem covered by token decimals reconciliation for subscription amounts.
What should the reconciliation record contain?
Each subscription and redemption record should let a reviewer rebuild the investor outcome from on-chain values and the fee terms, without access to the engineer who deployed the vault.
- Operation: the function called (deposit, mint, withdraw or redeem), because the fee base can differ by path.
- Quote: the preview value shown to the investor, the method that produced it and the block it was read at.
- Cash leg: gross assets moved from the investor or paid to the investor, in raw base units.
- Fee leg: the fee amount, the configured recipient address and its balance change in the same transaction.
- Share leg: shares minted or burned, and the check that gross equals net plus fee within the documented rounding tolerance.
- Terms reference: the clause defining the rate and base, and the contract version that implements it.
For request-based funds that settle later at a NAV strike, the preview methods may not be usable at request time, so the fee leg must be reconciled at claim instead. These checks are proposed acceptance criteria, not observations of a specific deployed fund.
Sources: ERC-4626: Tokenized Vaults (Final); OpenZeppelin ERC-4626 guide and fee example. Sources checked October 27, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.
Frequently Asked Questions
Does convertToShares show what an investor will receive?
No. ERC-4626 states that convertToShares and convertToAssets must not include fees charged against assets in the vault. They describe an idealized exchange rate. For a quote an investor can act on, use previewDeposit, previewMint, previewWithdraw or previewRedeem, which the standard requires to include the fee relevant to that operation, and record which method produced the displayed number.
Is a 0.50% entry fee always 0.50% of the gross subscription?
Not necessarily. A fee can be calculated on the total amount paid or on the net amount invested. In an illustrative 100,000-unit deposit, those conventions produce fees of about 497.51 and 500.00 respectively. The product terms, the contract code and the administrator calculation must state the same convention before launch.
Who receives the fee in an ERC-4626 vault?
The standard does not specify a recipient. Implementations decide. In the unaudited OpenZeppelin fee example, entry and exit fees are transferred to configurable recipient addresses, and no transfer occurs when the recipient is the vault itself, which leaves the fee inside the vault for remaining holders. Reconciliation must identify the configured recipient for each operation.
How can I tell a fee from a rounding difference?
Rounding differences are bounded by the token base unit and do not grow with the subscription size. Fees scale with the amount at a stated basis-point rate. A shortfall that is a constant few base units is precision; one that is proportional to the amount and matches the fee rate is a fee; one that changes the exchange rate itself needs a separate investigation.
Related Articles
Should Tokenized Funds Use ERC-7540 Async Vaults?
ERC-7540 is Final and adds a mandatory Pending to Claimable to Claimed lifecycle that ERC-4626 cannot express. The spec concedes that shares received may not match convertToShares at request time, and defines no mandatory cancellation path.
Tokenized Fund Structures on Layer-0 RWA Protocols: A Guide for Fund Managers
Private equity, real estate, private credit, and venture capital fund structures each have distinct tokenization requirements. This guide covers how each major institutional fund structure maps to Layer-0 RWA protocol capabilities, LP interest tokenization, capital call mechanics, waterfall distribution automation, and multi-class fund design.