Vested Tokens

Option 1 Use Account Transfer:

Transactions for fully vested tokens that are synched from on chain or imported can be categorized as Account Transfer. When categorizing as Account Transfer an Asset type category must be selected in the Transfer From dropdown. The example below credits Account Receivable to close the open balance, assuming the accounting system has an existing entry that debited AR for the tokens receivable.

The cost basis of the token receivable is updated in the External Costs Basis screen under Accounting in the left pane. Use the edit button to open the Edit External Tax Details screen and edit the Acquisition Cost and Acquisition Date.

The Balance Report will continue to show the assets in the portfolio balance as of the on chain transaction date.

Inventory View reporting will show the asset acquired using the date and cost edited in the External Cost Basis screen.

**Note that this difference in timing will result in a variance in the reconciliation workbook.

Option 2 Use a Manual Wallet:

A manual wallet can be created for locked token transactions manually entered or imported into Bitwave at acquisition cost and on the date of the start of the vesting schedule.

The example below categorizes to an clearing account, assuming the accounting system has an entry that credits the consideration given to enter into the vesting agreement.

The vested token inflows that are synched from on chain or imported will need a matching outflow from the locked token manual wallet. The inflow and outflow will be combined in order to categorize as an internal transfer.

All reporting will show the locked tokens in the portfolio balance. Since they will be in their own wallets, the locked token balance and fully vested token balances will be separate.

**Note that Wallet Level Inventories may be required if additional tokens are acquired before all tokens have been fully vested. Without separate inventories, the locked tokens will be pickable for disposals.

Option 3 Use DeFi Module:

A DeFi wallet can be created for locked token transactions manually entered or imported into Bitwave at acquisition cost and on the date of the start of the vesting schedule. As a best practice the wallet address were the fully vested tokens will be received and the token address can be used in the wallet's configuration.

The example below categorizes to an clearing account, assuming the accounting system has an entry that credits the consideration given to enter into the vesting agreement.

Categorizing the vested token inflows that are synched from on chain or imported as Advanced DeFi will automatically create the matching outflow from the locked token DeFi wallet.

All reporting will show the locked tokens in the portfolio balance. Since they will be in their own wallets, the locked token balance and fully vested token balances will be separate.

**Note that Wallet Level Inventories may be required if additional tokens are acquired before all tokens have been fully vested. Without separate inventories, the locked tokens will be pickable for disposals.