# Configure asset sweeping

Asset sweeping moves funds from multiple source wallets to a single destination wallet on a schedule. As an owner or administrator, you configure sweep workflows to consolidate funds, simplify treasury management, and reduce the number of wallets that hold active balances.

Sweeps create on-chain transactions and incur network fees.

## How asset sweeping works

A sweep configuration defines:

- Which **blockchain** to sweep
- Which **assets** to include and the **minimum amount** that triggers a sweep
- Which **destination wallet** receives the swept funds
- Which **fee wallet** pays transaction fees
- How often the sweep runs (**hourly** or **daily**)


You don't select source wallets in the sweep configuration. Instead, each wallet has a **Sweeping** toggle in its settings. When the sweep runs, Palisade checks sweep-enabled wallets that are eligible for the sweep blockchain. If a source wallet's available balance meets the minimum amount for a configured asset, Palisade creates a transaction to move those funds to the destination wallet. Pending or frozen balances don't count toward the sweep amount.

You can create only one sweep configuration per blockchain. Add all assets that you want to sweep on that blockchain to the same configuration.

## Supported blockchains

Use the blockchain dropdown in **Settings** > **Workflows** to see supported sweep chains in your organization. The sweep workflow supports the blockchains shown in that dropdown, including Ethereum, Solana, and Tron when they are available to your organization.

The same fee-funding model applies across supported blockchains that require native assets to pay transaction fees.

## Fee funding

Palisade uses just-in-time fee funding for sweeps. For a source wallet that needs native asset to pay network fees, Palisade:

1. Estimates the native asset amount required for the sweep transaction.
2. Transfers native asset from the fee wallet to the source wallet.
3. Creates the sweep transaction from the source wallet to the destination wallet.


Palisade currently transfers about 3 times the estimated network fee to help account for fee changes before the sweep transaction confirms. You can't currently configure this multiplier or set a sweep to pre-fund enough native asset for several future sweeps.

## Remaining native asset after a sweep

After Palisade completes a sweep, any unused native asset remains in the source wallet. Palisade doesn't currently reclaim this remaining balance or return it to the fee wallet automatically.

If the same source wallet qualifies for a later sweep, Palisade considers the existing native asset balance before it sends more native asset from the fee wallet. If you create a new receive wallet for each deposit and sweep each wallet only once, each wallet may retain a small native asset balance after its sweep.

## Enable source wallets

Enable sweeping on each wallet that acts as a source. The sweep configuration applies to every enabled source wallet on the selected blockchain.

1. Open the wallet and select the **Settings** gear icon.
2. Go to the **Sweeping** tab.
3. Turn on **Sweeping**.
4. Turn on **Outgoing transactions** for the wallet.


## Prerequisites

Before you create a sweep configuration:

- For each **source wallet**, turn on **Sweeping** and **Outgoing transactions**.
- You must provision the **destination wallet** on the sweep blockchain.
- You must enable the **fee wallet** on the sweep blockchain. For blockchains that use native asset for fees, the fee wallet must hold enough native asset to pay transaction fees.
- The **source wallets** must be eligible for the sweep blockchain.


Asset sweeping bypasses transaction policies. A source wallet doesn't need a transaction policy to be swept, and existing transaction policies don't block sweep transactions. To restrict sweeping, manage the wallet's **Sweeping** setting and the sweep configurations in **Settings** > **Workflows**.

## Create a sweep configuration

1. Go to **Settings** > **Workflows**.
2. Select **Create sweep**.
3. Enter a **name** (5 to 50 characters) that describes the sweep.
4. Enter an optional **description** (5 to 100 characters).
5. Select the **blockchain** for this sweep. Palisade marks blockchains that already have a sweep configuration and prevents you from selecting them.
6. Add one or more **assets** to sweep:
  - Select the asset from the dropdown, or toggle to enter a **non-standard asset** manually (symbol and contract address).
  - Set the **minimum sweep amount** - the smallest balance that triggers a sweep from a source wallet.
7. Select the **destination wallet** - the wallet that receives swept funds. The list groups wallets by vault.
8. Select the **fee wallet** - the wallet that pays transaction fees. You must enable this wallet. For blockchains that use native asset for fees, fund it with the blockchain's native asset.
9. Set the **frequency**:
  - **Hourly** - the sweep runs every hour.
  - **Daily** - the sweep runs once per day.
10. Select **Create**.


One sweep per blockchain
You can create only one sweep configuration per blockchain. If you need to sweep multiple assets on the same blockchain, add them all to the same configuration.

Sweeps create real transactions
Each sweep triggers automated transactions on your behalf. Make sure the sweep settings, wallet settings, and destination wallet are correct before you enable a sweep.

## Manage sweep configurations

After creating a sweep, you can manage it from **Settings** > **Workflows**:

### Enable or disable a sweep

Toggle the sweep on or off. A disabled sweep doesn't run on its schedule but retains its configuration.

### Trigger a sweep manually

Select **Trigger** to run the sweep immediately outside its normal schedule. Use this to test the configuration or to sweep funds on demand.

### Update a sweep

Select the sweep configuration, then select **Update** to change the name, description, assets, wallets, or frequency.

### Delete a sweep

Select the sweep configuration, then select **Delete**. Deleting a sweep stops all future runs and removes the configuration.

## Monitor sweep runs

Each time a sweep runs, Palisade creates a **sweep instance** that records the results.

1. Go to **Settings** > **Workflows**.
2. Select the sweep configuration.
3. View the list of sweep instances with their status, timestamp, and transaction details.
4. Select an individual instance to see which wallets Palisade swept and which transactions Palisade created.


If the fee wallet doesn't have enough native asset, Palisade can't fund source wallets that need fee funding for that run. Palisade records a failed sweep instance and checks the configuration again on the next selected cadence, either hourly or daily. You can also top up the fee wallet and trigger the sweep manually.

Palisade doesn't currently send a dedicated webhook when the fee wallet balance is low or empty. Transaction webhooks notify you about status changes for transactions that Palisade creates, but they don't replace fee wallet balance monitoring.

## Troubleshooting

| Issue | What to check |
|  --- | --- |
| The fee wallet is missing from the dropdown | Make sure you enabled the wallet and that it uses the same blockchain as the sweep configuration. |
| Palisade doesn't sweep a wallet | Make sure the wallet is eligible for the sweep blockchain, has **Sweeping** enabled, has **Outgoing transactions** enabled, and has an available balance that meets the minimum sweep amount. |
| A sweep keeps retrying without creating sweep transactions | Make sure the fee wallet holds enough native asset to fund source wallets and pay transaction fees. |
| Small native asset balances remain in source wallets | Expect this behavior. Palisade leaves unused native asset in the source wallet and takes it into account on later sweeps. |


## Best practices

- **Monitor fee wallet balances** - keep enough native asset in each fee wallet for scheduled sweeps and fee-funding transfers.
- **Test in sandbox first** - create and run a sweep in sandbox before you configure production sweeps.
- **Set appropriate minimum amounts** - set minimum sweep amounts high enough to avoid creating many small transactions that cost more in fees than they consolidate.
- **Account for remaining native asset** - if you use one-time receive wallets, plan for small native asset balances to remain after sweeps.
- **Monitor sweep execution** - review sweep instances, use [audit logging](/products/wallet/admin-guide/configure-audit-logging) to track sweep activity, and use [webhooks](/products/wallet/admin-guide/configure-webhooks) for transaction status changes when Palisade creates sweep transactions.


## Related guides

- [Asset sweeping](/products/wallet/user-interface/wallets/asset-sweeping) - Reference documentation
- [Configure wallets and vaults](/products/wallet/admin-guide/configure-wallets-and-vaults) - Enable sweeping on individual wallets
- [Policy concepts](/products/wallet/user-interface/policies/policies-concepts) - Understand why sweep transactions bypass policies