❓FAQs -2
Q: How can I delete transactions in bulk from my wallet in Bitwave?
🅰️:
To delete a transaction, go to the Administration section on the Dashboard and use the System Jobs feature. There, you can create a job by selecting the desired action (e.g., delete transaction) from the Actions tab.
Q: How do I combine transactions in Bitwave?
🅰️:
To combine transactions, go to the Transactions page in your Bitwave Org. Use the checkboxes next to the transaction hashes to select the ones you want to combine. Once selected, a "Combine" option will appear above the filters. Click it to merge the transactions.
Q: Why can't I find a transaction in the categorization section, even though it's visible in the register?
🅰️:
If a transaction is visible in the register but not in the categorization section, ensure that your filters are set to "RECONCILED ALL UNIGNORED" and search the transaction hash in the search bar. This often helps surface the transaction in the categorization section.
Q: Can I ignore an LP token transaction and still reconcile a gas fee manually?
🅰️:
Yes, if you deleted the LP token and only want to account for the gas fee, you can ignore the transaction and book a manual entry for the gas fee. This prevents the LP token from appearing in the balance report.
Q: What should I do if a transaction’s gain/loss seems incorrect due to fee handling?
🅰️:
If the gain/loss appears incorrect, it may be due to how transaction fees are handled—especially if your organization does not capitalize fees. Try uncategorizing and recategorizing the transaction. If the issue persists, a manual workaround involves splitting the transaction into two separate manual entries: one for the trade and one for the fee, and then ignoring the original transaction.
Q: How do I split a transaction into separate trade and fee entries in Bitwave?
🅰️:
Start by uncategorizing the original transaction. Then, create two manual transactions—one for the trade and one for the fee. Finally, ignore the original transaction to prevent duplication. This ensures accurate accounting for fee handling.
Q: What causes an “Internal Server Error” when saving a combined transaction in Bitwave?
🅰️:
This error may occur due to a temporary backend issue or bug. In this case. If you encounter it, report the transaction ID to support for resolution.
Q: How do I categorize gasless transactions for a zero-value ERC-20 token spent by a community?
🅰️:
Create a rule in Bitwave using the “coin” field to specify the token and assign the appropriate account for transaction fees. This enables auto-categorization while tracking relevant fees.
Q: How do I split a trade into two separate transactions in Bitwave?
🅰️:
To split a trade, manually create two identical transactions in Bitwave, each representing a portion of the original trade. Use the “+” symbol to add each transaction and replicate the details. If the original includes a fee, enter it separately as a Withdrawal.
Q: What should I do with the original transaction after splitting it into two?
🅰️:
After creating the two new transactions, uncategorize the original transaction and then ignore it. This prevents duplication and ensures accurate records.
Q: Why are ignored transactions still showing up in the unignored section in Bitwave?
🅰️:
This may be due to a display or filtering issue in the transaction view. To troubleshoot, ensure filters are set to "All Wallets," "Unreconciled," and "Ignored" in that order. If the problem persists after refreshing and allowing all transactions to load, it may require internal engineering support to resolve.
Q: What should I do if I get an “Internal Server Error” when trying to manually add a transaction in Bitwave?
🅰️:
If logging out and back in doesn’t resolve the issue, try using the manual import process instead. You can follow the instructions in Bitwave’s manual import guide to upload your transaction. If the issue persists, contact support with your organization name for further investigation.
Q: What should I do if I see an incomplete transaction in the Actions Report?
🅰️:
An incomplete transaction in the Actions Report typically indicates that Bitwave couldn’t fully classify or process that transaction due to missing data (e.g., token details, counterparties, or categorization). You should review the transaction in the Transactions tab, check for missing fields, and complete any categorization or linking that may be required.
Q: How long does it take to complete a system job for reconciling a large volume of transactions in Bitwave?
🅰️:
The time to complete a system job depends on the volume and complexity of the transactions. For reconciling thousands of transactions, it may take several hours. If the job hasn’t cleared within a business day, it's advisable to contact Bitwave support to ensure the job has processed correctly.
Q: Can I export a CSV of all open trading fee transactions in Bitwave?
🅰️:
You can export transaction data from Bitwave using the "Export Transactions" feature under the Transactions tab. However, this export typically includes finalized transactions such as deposits, buys, and sells. To capture open trading fees (pending acceptance), you'll need to manually review the "Transactions > Trading" tab, as these are not included in the standard export.
Q: How can I create a multi-token internal transfer in Bitwave?
🅰️:
Use the manual import feature to enter a multi-token internal transfer. Assign the same Group ID to all rows that are part of the same transaction. This enables grouping of multiple assets into one logical transfer. Refer to Bitwave Manual Import Guide for detailed instructions.
Q: What should I do if I accidentally delete transactions from a wallet in Bitwave?
🅰️:
You can request a wallet resync by providing the wallet name, wallet ID, wallet address and blockchain. Bitwave will pull all historical transactions back from the chain. It may take up to 24 hours for the transactions to reappear.
Q: Why does my manually updated exchange rate revert to the original rate after saving a transaction?
🅰️:
This may occur due to a temporary UI glitch where the amended rate is not properly saved. If this happens, try reloading the page and editing the transaction again. If the issue persists, report the transaction ID and intended rate to Bitwave support so it can be investigated and escalated if needed.
Q: Can I export a list of all ignored transactions in Bitwave to Excel or CSV?
🅰️:
No, Bitwave does not currently support exporting ignored transactions to Excel or CSV. This functionality is not available through the user interface. You may need to manually track or reclassify transactions to view them in exportable reports.
Q: Is there a way to accept or reconcile more than 100 trades at a time in Bitwave?
🅰️:
Yes, you can use the "Mark as Reconciled" system job feature in Bitwave to reconcile trades in bulk. This is ideal for large volumes of transactions and should only be used after all non-trade transactions for the period have been reconciled.
Q: Can I reconcile specific trades using a CSV file in Bitwave?
🅰️:
Yes, you can use the CSV Bulk Action feature in the System Jobs module to mark specific transactions as reconciled. You’ll need a list of the transaction IDs you want to reconcile. A template is available here.
Q: How can I compare my Coinbase transaction history with Bitwave to identify missing data?
🅰️:
Export the full transaction history from both Coinbase and Bitwave. To align timestamps, truncate Coinbase’s millisecond timestamps to match Bitwave’s formatting. Highlight rows with missing matches and share with Bitwave support. This helps identify transactions not imported due to sync issues.
Q: What should I do if I get a “GraphQL error: Internal Server Error” when clicking on a transaction?
🅰️:
This error can occur due to a temporary backend issue affecting transaction access. If it's affecting all transactions, contact Bitwave support with an example transaction ID. The issue is usually resolved by the support team on the backend.
Q: Why are internal transfer transactions duplicating when combined, causing negative balances?
🅰️:
This may be due to a bug where combining internal transfer transactions inadvertently creates duplicate entries. These duplicates can cause incorrect balances in inventory views and reports. If this occurs, contact Bitwave support with example transaction IDs and wallet filters so the issue can be escalated and resolved.
Q: How can I fix duplicate transactions in Bitwave caused by combining entries?
🅰️:
If combining transactions results in duplication, avoid using the combine function until support confirms the issue is fixed. Provide the affected wallet names and sample transaction IDs so Bitwave’s engineering team can investigate and correct backend data if needed.
Q: How can I export all transactions for a specific token like USDC?
🅰️:
You can export the transaction report and filter the "ticker" column in the CSV export file to only show USDC transactions.
Q: Will deleting transactions from Bitwave affect the wallet balance?
🅰️:
Yes, deleting transactions will impact the wallet's balance as balances are computed based on transaction history.
Q: Why didn’t my manual deposit transaction appear in Bitwave after I created it?
🅰️:
If a manual deposit doesn’t appear, check that the input format is correct (e.g., use "0.01" instead of ".01") and confirm that the transaction was saved successfully. If it still doesn’t show up, it may be due to system lag or a backend issue. Try refreshing or re-logging, and contact support if it continues to not appear.
Q: How do I correctly create a manual deposit in Bitwave?
🅰️:
Use the Transactions tab, check the box beside the transaction you want to edit or create, and enter the details using the full numeric format (e.g., "0.01" not ".01"). Ensure it is categorized and reconciled after saving. Reference the Register report to verify the update.
Q: Can a system job like unignoring transactions be expedited by Bitwave support?
🅰️:
Yes, Bitwave support can manually expedite a system job, such as unignoring transactions. You'll need to provide your organization name, organization ID, and the specific job ID to make the request.
Q: How can I confirm the assets involved in a transaction on Solana?
🅰️:
You can use a blockchain explorer like Solscan to review the full details of a Solana transaction, including asset transfers. This can help identify if multiple assets were involved or only a single token was transferred.
Q: What should I do if I get an error when editing a previously reconciled transaction?
🅰️:
If you receive an error while updating a transaction that was previously reconciled, try the following steps: first, unreconcile the transaction, then uncategorize and recategorize it. Afterward, refresh your browser. If the issue persists, contact support with the transaction ID and a screenshot of the error.
Q: How can I locate a transaction in the Bitwave dashboard using the ID from a journal entry report?
🅰️:
To find a transaction listed in the memo field of a journal entry report (e.g., "Fee for txn ARB.0x..."), search for the raw transaction hash. Use Bitwave’s Transactions dashboard and ensure you apply the right filters such as date range, wallet, and reconciled status. If the transaction is reconciled, it will appear under that section.
Q: Should I combine separate inflow and outflow transactions from Coinbase when they represent an on-demand trade?
🅰️:
Yes. Coinbase may execute on-demand trades between USDC and USD, which appear as separate inflow and outflow transactions in Bitwave. You should manually combine them into a single categorized trade transaction to reflect the correct accounting.
Q: Why are some Coinbase USD transfers not picked up by my rules, even though others are?
🅰️:
This inconsistency may stem from variations in transaction metadata (like wallet or account info), or limitations in Bitwave's rule engine, especially with fiat transactions. While some transfers may be recognized and categorized automatically, others—especially involving fiat—might fail due to unsupported coin types or missing data in rule configuration. It’s best to validate each rule with a sample transaction using the "Validate" tool and manually categorize any that fail due to these constraints.
Q: How does Bitwave track Solana staking rewards and why might they not appear as explicit transactions?
🅰️:
Bitwave syncs Solana staking rewards automatically by associating stake account earnings with the wallet that holds withdrawal authority. These rewards often appear via state changes rather than explicit on-chain transactions, which can make them hard to trace.
Q: What is the Rollup feature in Bitwave and should I use it for high-volume Binance trades?
🅰️:
The Rollup feature consolidates high-volume transaction data into summarized entries, reducing line-item clutter. However, it’s intended for exceptionally high-throughput wallets and must be configured by Bitwave Engineering. For Binance trades with similar IDs, using Rollups is not recommended unless necessary due to volume.
Q: What is the difference between Buy and Sell in Bitwave’s Trade transaction type?
🅰️:
In Bitwave, a Buy trade refers to the asset being acquired, while a Sell trade refers to the asset being disposed of. For example, if you're trading USDT to acquire SOL, then SOL is classified under Buy and USDT under Sell.
Q: When entering a trade manually, should I input the gross or net amount of tokens received?
🅰️:
Enter the gross amount of the acquired token and separately list the trading fee in the fee column. Bitwave will automatically compute the net amount by subtracting the fee from the gross. This ensures alignment with exchange balances.
Q: Can I edit a manually created trade transaction in Bitwave?
🅰️:
No, once a trade is created using the “Create Transaction” option, it cannot be edited. To make changes, you must create a new transaction and mark the original one as ignored.
Q: How can I remove a single line item from a combined transaction in Bitwave?
🅰️:
Bitwave does not allow partial deletion of line items from a combined transaction. To manage this, ensure all contacts and categories are filled in, then enable the “Allow Mismatch” checkbox and click “Save.” If you need to exclude a specific line due to its token type (e.g., ERC-1155), consider manually editing or re-separating the transactions before combining again.
Q: How do I manually override the price for a token in a combined transaction?
🅰️:
You can input a custom price during transaction editing. If Bitwave doesn't allow saving the update, it may be due to the transaction structure or backend sync constraints. In such cases, support can assist in applying the pricing manually if you provide the exact token, transaction ID, and intended price.
Q: How do I run a transaction history report for a single token in Bitwave?
🅰️:
"To view transactions for a specific token, you can use either the Register or Export options in the Transactions module:
- Register Method (single wallet): Go to Transactions > Register, input wallet name, date range, and token ticker, then click ""Load Register.""
- Export Method (all wallets): Go to Transactions > Export, select the date range, and export the CSV. Then, filter by the ""Asset"" column (typically column U) in Excel to isolate the token.
Confidence: High"
Q: What does the "Amount" column represent in Bitwave transaction exports?
🅰️:
The "Amount" column shows the number of tokens involved in the transaction, not the fiat value. Token pricing and fiat conversion may be available in other columns like “assetvalueInBaseCurrency.”
Q: What should I do if my token (e.g., rGMBL) isn't showing pricing in Bitwave reports?
🅰️:
If Bitwave cannot find pricing data for a token, you may need to provide a price feed link (e.g., from CoinGecko or CoinMarketCap) to support. Bitwave uses external sources for token pricing and may require manual setup for less common tokens.
Q: Is there a log or record of previously reconciled transactions in Bitwave?
🅰️:
Bitwave does not currently offer a formal log summarizing prior reconciliation events. However, the Transactions UI and export tools can be used to filter and review past reconciled transactions. Contact support for confirmation on specific reconciliation actions.
Q: How to Delete a transaction?
🅰️:
To delete a transaction, the user should go to the transaction page and find the transaction they want to delete. Then, they should check the box in the far left column next to the transaction. Once the transaction check box has been selected, the user should go to the more actions button that is above the transaction screen headers and in the more actions button, a drop-down will appear, and there will be an option to delete. The user can press that delete button to delete the transaction.
The user should know that if the transaction was imported or manually created in Bitwave, it will be deleted forever. However, if it is a synced-in transaction either from a direct blockchain connection or an exchange API, when that wallet resyncs Bitwave will detect that that transaction is missing and likely resync it in.
The user should also be aware that if that transaction has been pushed out to the ERP to produce a journal entry, deleting the transaction in Bitwave will only delete it in Bitwave and it will not delete it on the ERP side. The user should manually delete the transaction in the ERP directly.
Q: Can I remove zero FMV tokens from the Bitwave balance report or inventory view?
🅰️:
To exclude zero balance tokens from the balance report or inventory view, you need to ignore transactions associated with those tokens. This will effectively clean up the display, although the historical data remains in the system unless the wallet is deleted.
Q: What happens to historical transactions if I delete a wallet in Bitwave?
🅰️:
Deleting a wallet in Bitwave will remove all associated transactions from your organization. This action is irreversible, so make sure to export any necessary reports before deletion.
Q: How can I manually deposit a restricted token in Bitwave for tracking purposes?
🅰️:
To deposit a restricted token (e.g., a placeholder like RSOL), you’ll need to request Bitwave support to add the token if it doesn’t already exist. Once added (e.g., as RSOL-1), you can record manual deposits with a custom USD value and track them separately from tradable assets.
Q: Will restricted or placeholder tokens be excluded from gain/loss calculations in Bitwave?
🅰️:
Placeholder tokens (for example RSOL-1) can be excluded from gain/loss calculations by managing them as a separate inventory. This allows you to isolate them from active tokens, though they will still appear in inventory reports unless filtered out manually.
Q: Can I enter custom pricing for tokens that aren’t listed on public pricing feeds in Bitwave?
🅰️:
Yes, for tokens for example RSOL-1 used as placeholders, you’ll need to enter the value manually during each deposit. These tokens don’t have live pricing and require manual input to reflect the correct valuation.
Q: Why are some rollup transactions missing explorer links and wallet addresses in Bitwave?
🅰️:
Rollup transactions in Bitwave consolidate activity for a specific wallet over time (hourly/daily), which can result in missing “From” or “To” fields and lack of direct links to blockchain explorers. These summaries omit granular details by design to optimize performance and clarity.
Q: What should I do if a transaction incorrectly shows both inflow and outflow but is tagged only as an inflow?
🅰️:
This is likely a UI bug and does not affect underlying reporting or accounting values. Confirm the actual token movement and contact support for the resolution.
Q: How can I categorize internal transfer transactions using rules in Bitwave?
🅰️:
To categorize transfers, create a rule with “Internal Transfer Categorization” selected under the Categorize dropdown and set Direction to “All.” This captures transactions where assets move within the organization but don’t represent a gain or loss.
Q: How do I bulk reconcile transactions in Bitwave?
🅰️:
Go to Administration > System Jobs, click Create Job, choose Reconcile Transactions (not "Mark as reconciled"), select wallet(s), set the date range, and click Run. Start with a shorter range for efficiency.
Q: Why aren't my rules categorizing rollup wallet transactions?
🅰️:
Rules apply the same way to rollup transactions, but ensure you use appropriate direction filters. If a wallet has inbound, outbound, and mixed transactions, create and run rules in this order: inbound, outbound, then both. Test each rule on a short date range before scaling.
Q: What should I do if I accidentally ignored all transactions instead of just one?
🅰️:
If you mistakenly ignore all transactions, you can revert them by using the filter to show "Ignored" transactions. From there, you can selectively check and unignore only those transactions that should be restored. If unsure which ones to unignore, or if the issue appears to have affected a large set, contact Bitwave Support immediately. In some cases, a team member can help assess whether the change was successfully reverted or if a deeper reset is needed.
Q: What is the difference between 'Buy' and 'Sell' in a Trade transaction?
🅰️:
In Bitwave, a "Buy" trade represents the asset being acquired, while a "Sell" trade represents the asset being disposed of. For example, if you trade USDT for SOL, SOL is the "Buy" (acquired) and USDT is the "Sell" (disposed).
Q: Should I enter the net or gross amount when manually creating a trade transaction?
🅰️:
Enter the gross amount of the acquired asset and include any fees in the "Fee" field. Bitwave will show the net acquired amount in reports by subtracting the fee from the gross.
Q: Can I edit a manually entered trade transaction?
🅰️:
No, once a trade transaction is manually created in Bitwave, it cannot be edited. You will need to create a new transaction and ignore/delete the incorrect one.
Q: What happens if I accidentally ignore all transactions in a wallet?
🅰️:
You can undo this by filtering for ignored transactions, selecting those you want to restore, and clicking "Unignore." However, if you're unsure which transactions were originally ignored, it may be difficult to fully revert the mistake without support assistance.
Q: How should I handle a crypto-to-fiat conversion that appears as a USD inflow rather than a trade in Bitwave?
🅰️:
If a crypto-to-fiat conversion is incorrectly displayed as a USD inflow, you may need to combine the outgoing crypto transaction and the incoming fiat transaction. Then categorize the combined transaction as a trade to reflect the conversion correctly. Ensure neither side is marked as ignored or manually edited incorrectly.
Q: How can I update the value of a manually uploaded transaction?
🅰️:
To update a transaction’s value, un-reconcile it first. Then edit the exchange rate or cost basis using the pencil icon next to the rate field. This allows you to adjust the valuation to reflect the correct amount.
Q: How do I correctly categorize a staking transaction in Bitwave if no tokens were received in return?
🅰️:
For non-liquid staking transactions where no tokens are received, you can simulate the stake by creating a manual wallet representing the staking vault. Import the outgoing transaction to this wallet and combine it with the synced outflow. Categorize the result as an internal transfer to preserve inventory.
Q: What should I do if a transaction has been incorrectly categorized or combined?
🅰️:
First, uncombine the transaction if necessary. Then identify the correct matching transactions, combine them, and categorize them correctly (e.g., Trade, Internal Transfer). If the system blocks combining, verify that one side is not already part of another group.
Q: Why do some transactions in Bitwave appear blank or uncategorized?
🅰️:
Transactions may appear blank if the value received is zero. These typically don't affect reports and can be safely ignored. Always check if there's an associated fee or categorization needed, especially for sender-side fees.
Q: What should I do if a transaction appears uncategorized in Inventory Views even though it was categorized?
🅰️:
Try updating the inventory views by clicking “Update Now.” If the issue persists, ensure that the transaction includes a fee contact where applicable. If the categorization still fails, follow up with support.
Q: How can I categorize a token conversion (e.g., WETH to USDC) in Bitwave?
🅰️:
You should categorize such a transaction as a “Trade” and include a fee contact. Ensure you save the changes and allow time for the inventory views to update.
Q: What if a transaction in Bitwave has no link to Etherscan and appears uncategorized?
🅰️:
This likely indicates a manual transaction. In this case, you need to manually categorize the transaction in Bitwave.
Q: How do I add a fee to a transaction in Bitwave?
🅰️:
To include a fee in your transaction, create a separate manual withdrawal transaction representing the fee amount. Ensure it is categorized correctly to maintain accurate accounting.
Q: What should I do if some trades are missing from Bitwave after importing from Coinbase or Coinbase Pro?
🅰️:
First, verify whether the trades are included in your Coinbase transaction exports. If certain trades particularly older or nested portfolio transactions are missing from Bitwave, send a full historical CSV export and transaction references to Bitwave support to assist with data syncing.
Q: Why did a previously unseen transaction from a past year suddenly appear as uncategorized?
🅰️:
This can happen for two reasons: either the transaction was recently synced into Bitwave or it was manually uncategorized/unreconciled. Additionally, if categorization rules were set only for a parent token (e.g., USDC) and not for specific pairs like SOL-USDC, the transaction may have been left uncategorized.
Q: What should I do if Coinbase wallet transactions are missing or incomplete?
🅰️:
If your Coinbase transactions aren't appearing, the issue may be with the API connection (e.g., expired API keys). Contact support and provide a CSV of the full transaction history, including withdrawals, deposits, and trades, to help them investigate.
Q: How can I provide transaction history to help support investigate missing transactions?
🅰️:
Export a CSV of your complete transaction history from the relevant exchange, including all transaction types (withdrawals, deposits, trades). Send this file to Bitwave support for analysis.
Q: How can I export a list of uncategorized transactions in Bitwave?
🅰️:
You cannot directly export only uncategorized transactions. Instead, go to Transactions → Export, set the date range from the earliest transaction to the present, and export all transactions. Then, filter for uncategorized items in Excel or your spreadsheet tool.
Q: Why aren’t my trades appearing in the Trading tab even though they are marked as categorized?
🅰️:
If trades aren't showing up in the Transactions → Trading tab, ensure both transactions involved are categorized as Trade, not Standard, and that a Fee Contact is selected. Without a valid fee contact, Bitwave may not treat them as reconciled trades.
Q: Will disabling a wallet connection delete existing transactions?
🅰️:
No, disabling a wallet like Coinbase Retail stops new transactions from syncing, but existing ones remain.
Q: Why can’t I save a combined transaction in Bitwave?
🅰️:
If you're unable to save a combined transaction (e.g., a trade), check for missing required fields such as Fee Contact. Even if the field appears greyed out, it must be filled for the save to complete successfully.
Q: Can I download a list of transactions from Bitwave?
🅰️:
Yes, you can export transactions by navigating to Transactions → Export, selecting the desired date range, and clicking Export. The downloaded file will include transaction details in a CSV format.
Q: Why do some transactions in Bitwave not show "FROM" and "TO" addresses?
🅰️:
Some transactions, such as contract executions, may not display "FROM" and "TO" in the UI due to the way blockchain data is structured. For example, if a transaction involves internal movement (e.g., an internal transfer of ETH), Bitwave still correctly identifies the involved wallets, but the interface might present it differently based on the transaction type.
Q: How can I identify and categorize internal transfers in Bitwave?
🅰️:
Internal transfers are marked with two blue rounded arrows in the transaction list. Click on the transaction, change the categorization type from “Standard” to “Internal Transfer,” update the fee contact if needed, and then save the transaction.
Q: I am getting error while filtering uncategorized transactions?
🅰️:
When you get error message " There is error while loading the data" while filtering for uncatgeorized, just clear cache and refresh the browser.
Updated 13 days ago