Start by navigating to the Transactions section in the left menu of your Bitwave dashboard.
From the Transactions menu, select the Rules sub-menu. This will direct you to the Rules screen, displaying a list of all your existing rules.
Once on the Rules screen, locate the "Select All" checkbox positioned at the top left corner of the screen. Check this box to select all rules listed.
Optionally, you may also select individual rules instead.
Next, click on the "Actions" button located in the top right corner of the screen. A drop-down menu will appear. Select the "Disable" option from this menu.
This action will deactivate the selected rules in your organization, temporarily halting automated categorization for those rules.
Q: How do I enable rule(s)?
🅰️:
Start by navigating to the Transactions section in the left menu of your Bitwave dashboard.
From the Transactions menu, select the Rules sub-menu. This will direct you to the Rules screen, displaying a list of all your existing rules.
Once on the Rules screen, locate the "Select All" checkbox positioned at the top left corner of the screen. Check this box to select all rules listed.
Optionally, you may also select individual rules instead.
Again, click on the "Actions" button located at the top right corner of the screen, but this time select the "Enable" option from the drop-down menu.
This action will activate the selected rules in your organization, temporarily halting automated categorization for those rules.
Q: How do I troubleshoot a rule not working for categorized transactions in Bitwave
🅰️:
Follow these steps to troubleshoot:
Clear cache and cookies for the Bitwave page, then log out and log back in.
Ensure the rule direction is filled out when creating the rule.
Run the rule by selecting it, clicking on "Actions" on the right side, and then clicking on "Run."
If the rule processes successfully but doesn't apply, try refreshing the page and running the rule again.
Ensure transactions include a description.
If issues persist, contact Bitwave support for further assistance.
Q: Can a rule run successfully without the token get priced in the transactions?
🅰️: Yes, the rule can be run successfully without the token get priced in Bitwave. You need to enable the “Ignore Fail Pricing” while setting up the rule. However note. this means that any transactions for which we "Ignore Fail Pricing" would result in that transactionbeing priced at $0 fair market value. If that is not your intention then it means that Bitwave has failed to price a token you expect to be priced. You should reach out via our bitwave chat to request the token be priced.
Q: How do I automatically categorize trades and gas fees as "crypto fees"?
🅰️:
"You can set up categorization rules for trades and gas fees by following these video guides:
Be sure to check the ""Include Fee Categorization"" box when setting up trade rules to ensure fees are included."
Q: Why is the advanced categorization option greyed out in my rules setup?
🅰️:
This may be due to a caching issue. Try performing a hard refresh of your browser and clearing your cache and cookies. If the problem persists, reach out to our support team for assistance.
Q: How long does it take for categorization rules to apply to transactions?
🅰️:
Processing time depends on the volume of transactions. If you have a large number of entries, it may take a little while for the rules to fully apply.
Q: How can I create rules to automatically categorize transaction fees and gas fees?
🅰️:
Bitwave supports creating trade rules to automatically categorize fees such as "crypto fees" for both trade fees and contract execution (gas) fees. To do this, use the rule creation feature under categorization rules. If the advanced categorization option is greyed out, try clearing your browser cache and cookies, then refresh.
Q: Should I enable the option to include fee categorization when setting up trade rules?
🅰️:
Yes, selecting the option to include fee categorization ensures that associated fees are also properly categorized when trades are processed.
Q: Why isn’t my rule applying to transactions having fees I believe it should match?
🅰️:
One common reason rules don’t apply is if transaction fees are included but the rule doesn’t account for them. Make sure to check the "Categorize Fees" option in your rule settings. This will ensure the rule matches transactions that include fees.
Q: What should I do if my rule isn’t working due to missing price data for a token?
🅰️:
If a transaction involves a token that doesn’t have pricing data, the rule may not apply. To resolve this, you can either update the pricing for that specific ticker or enable the “Ignore Fail Pricing” option in your rule. This allows the rule to categorize the transaction even if pricing data is missing.
Q: I created a categorization rule, but my transactions are still uncategorized. Is there a delay?
🅰️:
Yes, due to high volume, it may take some time for rules to process and apply to transactions. Please allow some time, then refresh to see the updates.
Q: How can I troubleshoot why a transaction wasn’t categorized by a rule?
🅰️:
To investigate, confirm the transaction ID and rule name, and compare the transaction type and details to those that were successfully categorized. You can also re-run the rule and check Bitwave's interface for matching issues. If needed, Bitwave support can help validate which rule applied or why one didn’t.
Q: Do categorization rules in Bitwave run automatically, or do they need to be triggered manually?
🅰️:
Rules do not run automatically in Bitwave. After creating or editing a rule, you must manually run it. Once executed, allow a short time for the “Rules processed successfully” message to appear before expecting results. If categorization doesn't happen immediately, try re-running the rule to ensure it applies.
Q: Why aren't internal transfers from manual wallets automatically picked up by rules in Bitwave?
🅰️:
Internal transfer rules rely on wallet addresses to match transactions. Manual wallets may not have associated addresses, which prevents the system from detecting them as part of an internal transfer. In such cases, manual combination and categorization is required.
Q: Why did a transaction get ignored in Bitwave?
🅰️:
Transactions may be ignored due to active rules in your organization. For example, a rule set to ignore QuickBooks transactions can suppress them from appearing. Review your rules list to see if any are unintentionally excluding valid entries.
Q: Why does my rule not categorize a transaction even though the "validate" feature confirms it should?
🅰️:
This may happen if the transaction includes a token that Bitwave is unable to price. In such cases, rules may not apply unless the “Ignore Fail Pricing” option is enabled within the rule. Once this option is selected, the rule can be executed successfully to categorize the transaction.
Q: What does the "Ignore Fail Pricing" feature in rules do?
🅰️:
The "Ignore Fail Pricing" feature allows a rule to be applied even if Bitwave cannot fetch pricing data for one or more assets in the transaction. Enabling this option is especially useful when dealing with unsupported or unpriced tokens that would otherwise prevent rule execution.
Q: How long does it take for a rule to categorize or ignore a transaction after it is run?
🅰️:
The time it takes for a rule to apply depends on the total number of transactions being processed. However, if only one transaction is involved, the rule should execute almost immediately.
Q: What are the steps to validate and run a rule on a specific transaction?
🅰️:
"To validate and apply a rule:
Create the rule with desired conditions and actions.
Use the transaction ID with the ""validate"" feature in the rule editor to check if the rule applies.
If confirmed, navigate to the rules screen and run the rule to apply it to transactions.
Note: If issues persist, ensure all required fields are correctly populated and consider using “Ignore Fail Pricing” if tokens are not priced."
Q: What is the benefit of using an Ignore Rule for spam tokens?
🅰️:
Ignore Rules let you automatically exclude transactions involving specific spam or mispriced tokens as they sync into Bitwave, helping to prevent report contamination without needing manual intervention each time.
Q: What pricing source does Bitwave use for a specific token?
🅰️:
Bitwave typically sources token prices from providers like CoinGecko or CoinMarketCap, but the specific source can vary depending on availability and token support. If you suspect the pricing source is incorrect, you can request support to confirm or update the source.
Q: What support options does Bitwave offer for setting up rules and categorizing transactions if I’m not technical?
🅰️:
Bitwave offers help documentation and customer support to assist with rule setup and transaction categorization. If you find the guides challenging, you can reach out to Bitwave Support for personalized assistance. A support agent can walk you through the rule creation process or help set them up on your behalf.
Q: Why didn't my rule categorize a USD transfer even though similar transfers were picked up?
🅰️:
This issue often occurs due to missing required fields like wallet information in the rule, or because Bitwave currently has limitations categorizing fiat (USD) transactions via rules. Even if similar transfers were picked up before, inconsistent metadata or rule configuration can cause failures. Use the "Validate" option within the rule settings with a specific transaction ID to test it. As of now, USD transactions may still need manual categorization.
Q: What does the “Coin: Cannot handle fiat” error mean during rule validation?
🅰️:
This error indicates that Bitwave currently does not support automatic rule-based categorization for fiat currencies like USD. This is a known limitation under review by engineering. For now, manual categorization is recommended for fiat transactions.
Q: What direction should be selected when creating a Trade Rule?
🅰️:
When setting up a Trade Rule in Bitwave, the direction field should be set to "All" to ensure proper application across transaction types.
Q: How long does it take for new QuickBooks contacts to sync into Bitwave?
🅰️:
New contacts added in QuickBooks typically take about 12 to 18 hours to sync into Bitwave.
Q: How long does it take for a rule to apply after I run it?
🅰️:
Rules in Bitwave typically apply shortly after being run, but processing time can depend on the volume of transactions. If transactions remain uncategorized after running a rule, try rerunning it, validating sample transactions, or temporarily disabling other rules.
Q: Why is a rule only categorizing a limited number of transactions (e.g., 10 at a time)?
🅰️:
This may be due to a bug or performance issue in the rule engine. If suspected, raise the issue with Bitwave support or engineering to investigate further.
Q: Why aren't some transactions being categorized even though a rule is applied in Bitwave?
🅰️:
If a rule isn't categorizing all expected transactions, double-check that the rule has been properly run after creation. Go to the Rules tab, select the checkbox for the rule, and use the Actions menu to run it manually. If issues persist, check that the rule conditions match all applicable transactions and consider re-reviewing the transaction metadata. Some transactions may require adjustments or manual categorization if they fall outside the rule parameters.
Q: Why isn't my rule categorizing transactions automatically after it's created?
🅰️:
After creating a rule, you must run it manually by selecting the checkbox next to the rule and clicking "Run" under the Actions menu. If the rule appears to run but doesn't apply changes, verify that affected transactions match the rule's parameters and that all assets involved are priced. Rules may fail if unpriced assets are included unless "Ignore Fail Pricing" is enabled.
Q: Can I use manually created contacts in rules for categorizing transactions to QuickBooks Online?
🅰️:
No, Bitwave rules that export to QuickBooks Online require contacts to be synced from your ERP. Manually created contacts in Bitwave won’t work for ERP integration. Instead, create the contact in your ERP and sync it into Bitwave.
Q: Do I need to uncategorize transactions before reapplying rules in Bitwave?
🅰️:
Yes, transactions must be uncategorized before rules can reprocess them. If a rule has been updated or the contact was changed, uncategorize affected transactions before rerunning the rule.
Q: Should I use the token ticker or identifier when creating a rule for a specific coin?
🅰️:
When creating a rule for a specific token, use the Coin Ticker instead of the identifier. This ensures the rule correctly targets transactions involving that token.
Q: How to setup the Internal transfer rule?
🅰️:
Here's a step-by-step guide:
Go to the transactions menu on the left side and then the rules sub-menu under transactions.
Click "Create Rule"
Select "Internal Transfer" as the rule type
Configure the following settings:
Set matching conditions (e.g., specific wallets, amounts, or tokens)
Define which transfers should be marked as internal
Set the desired accounting treatment.
📬
Don't see your question listed here? Hit the "Suggest Edits" button in the upper right and add a question for our Support Team!
