# Transaction fee accounting how-to

Source: https://docs.settlemint.com/docs/operators/token-features/transaction-fee-accounting
How operators configure the transaction-fee-accounting token feature for off-chain settlement of mint, burn, and transfer fees.



The `transaction-fee-accounting` feature records fee accruals for each token operation on-chain, supporting settlement outside the platform. Configure it when you have chosen off-chain settlement and need the platform to maintain the accrual trail.

For the canonical product model, event semantics, controls, and risks, read [Transaction fee accounting](/docs/architects/components/token-features/transaction-fee-accounting). For route shapes, read the [API reference](/docs/api-reference/token-features/transaction-fee-accounting).

## When it attaches [#when-it-attaches]

The ETF template (`system-etf`) and the asset-backed-token template (`system-asset-backed-token`) attach transaction-fee-accounting automatically. No manual feature selection is needed.

## Configure the feature [#configure-the-feature]

In the Asset Designer details step, set the parameters below. Any rate set to zero suppresses accrual logging for that operation type.

| Parameter        | Description                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------- |
| `mintFeeBps`     | Mint-fee accrual rate logged for each mint, in basis points.                                            |
| `burnFeeBps`     | Burn-fee accrual rate logged for each burn.                                                             |
| `transferFeeBps` | Transfer-fee accrual rate logged for each transfer.                                                     |
| `recipient`      | Recipient identity captured with each accrual entry. The recipient is not transferred to automatically. |

## Operate accruals after deployment [#operate-accruals-after-deployment]

Once the asset is live, follow this sequence to manage the accrual trail:

1. **Inspect accrued fees** on the asset detail workspace's fee-accounting tab. The tab shows total accrual per operation type and the recipient.
2. **Settle off chain** on the published schedule. The recipient or the administrator transfers value from the operating treasury to the manager outside DALP, using the accrual record as the reconciliation source.
3. **Reconcile periodically** between the accrual record and off-chain settlement so the two stay in sync.
4. **Use [transaction-fee](/docs/operators/token-features/transaction-fee) instead** when the fee should be collected on chain at the moment of the token operation.

## Troubleshooting [#troubleshooting]

| What you see                              | What to check                                                                                                                     |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Recipient wallet shows no incoming tokens | The accounting feature does not transfer. Read the fee-accounting tab to see accruals; settle off chain.                          |
| Need on-chain collection instead          | Use [transaction-fee](/docs/operators/token-features/transaction-fee). The two features are mutually exclusive on the same asset. |
| Accrual rate mismatch                     | Confirm the configured `*FeeBps` values and the platform accrual frequency match the operating-team approval.                     |

## Read next [#read-next]

* [Transaction fee accounting architecture](/docs/architects/components/token-features/transaction-fee-accounting)
* [Transaction fee accounting API reference](/docs/api-reference/token-features/transaction-fee-accounting)
* [Transaction fee](/docs/operators/token-features/transaction-fee) - the on-chain collection variant
* [Feature constraints](/docs/architects/components/token-features/feature-constraints#mutually-exclusive-rules)