Don't see your question listed here? Hit the "Suggest Edits" button in the upper right and add a question for our Support Team!
Send us your questions! We're happy to help!
Q : How can I verify that my transactions have been successfully imported and are visible in Bitwave?
🅰️ : To check if the transactions are successfully imported into your bitwave instance, you can come to import page and check the status. If it says complete, check the wallet you imported the transactions into. The transactions should show in there.
Q : Why did I receive a “Data Upload Failed” error when importing a upload file to the wallet?
🅰️:
This error typically indicates a temporary server issue. Try clearing your browser cache and reattempting the upload. If the issue persists, please share the file with our support team so we can investigate further.
Q : How do I import transactions with categorizations into Bitwave?
🅰️:
You can follow this documentation on manual imports. Make sure to use the provided template and include categorization data in the appropriate fields.
Q : I’m importing transactions into Bitwave, but I keep getting an error that a trade must include two transactions. What does that mean?
🅰️:
Each trade must include both sides of the transaction (buy and sell). If your import file includes only one side or uses unique Trade IDs, it will error out. You can: 1) Remove the Trade IDs and import as regular transactions. 2) Then, manually combine and categorize them as trades in the Bitwave UI.
Q : Why am I getting errors even though my data was validated during upload?
🅰️:
"Common causes include: 1: Incorrect date format (must be YY:MM:DD HH:MM:SS) 2: Missing seconds in timestamps. 3: Non-unique IDs. 4: Inconsistent account IDs across trade transactions.
Review your import file carefully before uploading."
Q : What is the difference between the Standard Import and Advanced Import features?
🅰️:
The Standard Import allows basic transaction imports, while the Advanced Import provides more detailed categorization options and additional fields for better control. Use the Standard Import for simple uploads and Advanced Import for more complex data handling.
Q : Why am I receiving an unclear error message when trying to manually import transactions?
🅰️:
This error often occurs due to issues in the import file, such as missing data, duplicate transaction IDs, or incorrect amounts. Please check that all required fields are filled, transaction IDs are unique or grouped properly, and amounts include fees where applicable.
Q : What should I do if my import file contains duplicate transaction IDs?
🅰️:
If your file has duplicate transaction IDs, Bitwave will overwrite the older transactions with the new ones. To record multiple transactions under the same ID, use the "groupID" column and assign the same groupID to those transactions.
Q : How do I handle transactions with zero amounts but associated fees in my import file?
🅰️:
For transactions with zero amounts but fees, enter the fee amounts in the "amount" column to ensure they are recorded correctly.
Q : I received an error when importing transactions for a new token. What does that mean?
🅰️:
This usually happens when the token ticker is not yet recognized in Bitwave. Once the token or a placeholder version (e.g., "ALLO-100") is created in the system, you’ll be able to import transactions using the new ticker.
Q: What should I do if Bitwave doesn’t support a blockchain I use?
🅰️:
If Bitwave doesn’t support a particular blockchain, you can manually import your transaction data to ensure complete reporting. We recommend reviewing our blockchain integrations list first to confirm support status.
Q: My imported internal transfer doesn’t show up what could be wrong?
🅰️:
"Common issues include:
Reusing a blockchain ID already present in Bitwave.
2.Mismatched blockchain IDs between the two sides of the transfer.
Ensure each import uses a new blockchain ID shared by both rows and new unique row IDs."
Q: How can I ensure my transactions appear correctly in the transaction feed after import?
🅰️:
Use a unique blockchain ID for both sides of the transaction and ensure it's not already used. Also, assign a new unique ID for each row in your import file.
Q: I successfully imported my file, but the transactions are not showing in Bitwave. What should I do?
🅰️:
If your file imported without errors but no transactions are appearing, check to ensure required fields are properly filled. For example, the taxexempt column must be populated—enter "FALSE" if the transaction is not tax-exempt. Also, confirm that your blockchain ID is correctly formatted.
Q: What is required in the taxexempt column of the import file?
🅰️:
The taxexempt column must be included in your import file, and each row should contain either "TRUE" or "FALSE". If you’re unsure, you can safely use "FALSE" to indicate the transaction is not tax-exempt. This is a required field for a successful import.
Q: Where can I find more information on how to correctly format import files?
🅰️:
You can review our import documentation here: Bitwave Import Guide. It provides detailed instructions on formatting, required fields, and troubleshooting tips.
Q: Can I use different values for the blockchain ID as long as they are unique?
🅰️:
Yes! Each blockchain ID should be unique per transaction. You can use labels like import1, import2, and so on—just ensure no two rows share the same ID.
Q: How do I know the correct wallet IDs to use during import?
🅰️:
Make sure to verify your Wallet ID before uploading. Here is the documentation on how to find the walletID associated with the wallet
Q: Can Bitwave distinguish between manually entered transactions and those imported automatically?
🅰️:
Yes, Bitwave generates unique transaction IDs for manually entered trades, which differ from system-imported transaction IDs. This distinction helps both clients and support teams track which transactions were entered manually and which were synced through the Binance connection.
Q: My file has the same format as another one I successfully uploaded. Why is this one failing?
🅰️:
While the formats may look identical, subtle differences—especially in the timestamp format—can cause validation issues. A successful upload doesn’t necessarily mean every file with similar formatting will pass; please ensure all fields, particularly date and time, meet the required ISO 8601 standard for each upload.
Q: I'm receiving a "503 upstream connect error" while importing a file. What does this mean?
🅰️:
This error typically indicates a temporary backend connectivity issue. We recommend waiting a few minutes and then retrying the import. If the error persists, please refresh your Bitwave session and try again. You can also share the file with us for further investigation.
Q: My import isn’t proceeding even after uploading the file—there’s no button to complete the import. What should I do?
🅰️:
If the import steps appear to complete but the “Upload” button does not appear, please try clearing your browser cache and refreshing the page. If the issue continues, contact our support team—we may need to escalate the issue to our engineering team.
Q: How long should I wait between file imports?
🅰️:
If you're importing large files, please wait 2–3 minutes between each import to allow the system to process them effectively. Refreshing your Bitwave session can also improve performance.
Q: What should I do if I encounter repeated errors while importing CSV files?
🅰️:
" If you're seeing a 503 error or import failures:
Wait 2–3 minutes between large imports.
Refresh your Bitwave instance.
Clear your browser cache.
Try reimporting the file.
If issues persist, send the file to support so we can test it and provide guidance."
Q: Why don’t I see the “Start Import” button after uploading my file?
🅰️:
"This may be due to a UI rendering issue.
Try:
Clearing browser cache and cookies.
Refreshing the page.
Ensuring your file only includes necessary data (no extraneous tabs, notes, or formats).
If the problem continues, contact support. We may need to escalate to engineering."
Q: Can I request support to upload a CSV for a specific entity?
🅰️:
Yes! Just let us know the entity name and Org ID where you want the data imported. We'll take it from there.
Q: Do I need to include headers in my CSV import file?
🅰️:
Yes, headers are required for a successful import. Removing them will cause errors during the upload process.
Q: Does each line in a trading import file need a unique transaction ID?
🅰️:
Yes, each line in your trading import file must have a unique transaction ID to ensure proper processing and avoid duplication errors.
Q:What should I do if my import files are stalled or not processing?
🅰️:
Large file sizes can cause imports to stall. Try breaking the file into smaller batches of 10,000 lines or fewer. If an import is stuck, contact support to have it removed so you can re-upload it.
Q: Is there a file size limit or recommended maximum for imports?
🅰️:
While there is no strict file size limit, we recommend keeping import files under approximately 10,000 lines for optimal performance.
Q: Can I upload multiple import files at the same time?
🅰️:
It's best to avoid running multiple large imports simultaneously, as this can cause delays or stall the process. Upload files sequentially, especially if they are close to the size limit.
Q: Is there a way to accept a large volume of trades more efficiently?
🅰️:
Yes, you can use the System Jobs > Mark as Reconciled feature to accept trade transactions in bulk for a selected date range. Be sure that all non-trade activity is already reconciled before using this feature.
Q: How do I refresh Bitwave if an import appears stuck?
🅰️:
You can refresh Bitwave by reloading the browser page. If that doesn’t resolve the issue, try restarting the import after your current uploads finish.
Q: How should I handle token tickers during import if Bitwave doesn’t recognize them?
🅰️:
Ensure the token ticker matches Bitwave’s expected format (e.g., use “OP_ETH” for Optimism ETH). Incorrect tickers may cause import errors.
Q:Why does my import file get stuck on “validating” or fail without clear errors?
🅰️:
This can be caused by formatting issues such as using incorrect date formats or not suffixing the Blockchain ID with .import1. Ensure dates are in the correct format (e.g., MM/DD/YYYY HH:MM:SS), and that blockchain IDs are unique with the correct suffix.
Q: How should the Blockchain ID be formatted in the import template?
🅰️:
Append a unique suffix like .import1 to the end of each Blockchain ID. Do not prefix it. Also ensure each ID is unique to prevent conflicts or duplicate errors during import.
Q: Why does my import error during the preview stage in Bitwave?
🅰️:
Preview errors during import often result from incorrect formatting in the CSV template. Common issues include using an invalid timestamp format (should be YYYY-MM-DD HH:MM:SS) and incorrect casing for transaction types (use lowercase like deposit and withdrawal).
Q: What format should I use for custom blockchainId values to make them searchable?
🅰️:
For best results, use underscores instead of spaces in custom blockchain IDs, such as Daily_rollup_2024-04-25 instead of Daily rollup 2024-04-25. This improves searchability in Bitwave.
Q: Can I fix combined transactions by updating the CSV and reuploading it?
🅰️:
No, you must first delete the combined transactions from Bitwave before reimporting updated versions. Using unique transactionIds per wallet & group Ids will prevent this issue in the future.
Q: Why are transactions being automatically combined during import?
🅰️:
Bitwave automatically combines transactions with the same group ID across wallets. To avoid this, ensure each transaction has a unique group ID, especially when importing from unsupported chains.
Q: Can having duplicate transaction IDs cause import errors in Bitwave?
🅰️:
Yes, duplicate transaction IDs can lead to preview errors or cause transactions to be combined incorrectly. Ensure each transaction has a unique ID to prevent issues during import.
Q: Why am I getting errors when uploading trade transactions using the Bitwave import template?
🅰️:
Errors can occur if the same tradeID has been used previously or if inconsistent blockchainIDs are used for parts of the same trade. Ensure that all rows for a single trade use the same transaction ID and a new, unique trade ID to avoid conflicts.
Q: Why does Bitwave reject imports that use "Deposit" and "Withdrawal" in the transactionType column?
🅰️:
Bitwave requires lowercase entries for transaction types. Use "deposit" and "withdrawal" instead of capitalized versions to avoid import errors.
