❓FAQs - 2

Q: What should I use as the transaction type for importing beginning balances?

🅰️:

Use “Deposit” as the transaction type for establishing opening balances if you're not recording a trade but simply reflecting held positions as of a specific date (e.g., 12/31/23). “TradeAcquire” or “TradeDispose” is only needed for trades.

Q: Is the Blockchain ID field required in the Bitwave import template?

🅰️:

Blockchain ID is not a required field, but including it can be useful for locating transactions in the UI. If it's not available, Bitwave support may help populate it using a unique identifier based on the date and ID.

Q: What happens if I upload opening balances without cost basis values in Bitwave?

🅰️:

If the Cost and CostTicker columns are left blank, Bitwave will use your organization’s default pricing source (e.g., CryptoCompare) to assign a market value at the time of the transaction. This may differ from your actual cost basis, and a journal entry may be needed to adjust for any discrepancies.

Q: What should I use for the ID and TradeID columns when importing opening balances?

🅰️:

Column A (ID) should contain a unique identifier per row (e.g., 1, 2, 3). TradeID is not needed for simple deposit entries—only for trade transactions. If you're importing only holdings as of a specific date, you can omit TradeID.

Q: What should I do if there are issues with an import I submitted to Bitwave and I haven’t received a resolution yet?

🅰️:

If you've reported an import issue and it's taking time to resolve, the Bitwave support team is likely investigating it internally. You can follow up via support chat to request an update. In time-sensitive situations, clearly mention any reporting deadlines or urgency so your ticket can be prioritized.

Q: hat should I do if I get stuck using "Import Advanced" for uploading opening positions?

🅰️:

If "Import Advanced" is unresponsive or not proceeding past the "Next" button, try using the standard import tool instead. This method is more stable, especially during temporary issues with the advanced importer.

Q: What fields are required when including cost data in an import file?

🅰️:

"If you include cost data in your import (column E), you must also include:

Column F: Cost Ticker (e.g., USD)

Column N: Contact ID

Column O: Category ID
These fields are necessary for Bitwave to process cost information correctly."

Q: Where can I find the Contact ID and Category ID needed for import files?

🅰️:

"In the Bitwave app:

Navigate to Accounting > Categories to find the Category ID.

Navigate to Accounting > Contacts to find the Contact ID.
These IDs are required in your import file if you're including cost values."

Q: How can I verify that my imported opening positions in Bitwave match our records?

🅰️:

After importing, you can verify correctness by comparing Bitwave’s wallet balances as of the start date with your own accounting records. Use the Wallet or Inventory Views to cross-check token quantities and values.

Q: How can I delete all transactions in Bitwave across all wallets?

🅰️:

To delete all transactions across all wallets, navigate to Administration > System Jobs, then click Create Job. Choose Delete Transactions from the Action dropdown, select All Wallets, and leave the date fields blank to delete all data.

Q: What should I do if my CSV import into a manual wallet shows blank in the UI?

🅰️:

If a CSV import results in blank data, check that the transaction IDs (typically in column A) are valid and unique. Changing the IDs can help trigger proper processing. Also, verify your import format matches Bitwave's specifications, and reach out to support if the issue persists.

Q: Where should I expect to see imported transactions in Bitwave?

🅰️:

Imported transactions may not appear directly in the dashboard. Instead, check the wallet transaction view to confirm the import worked. If transactions appear blank or missing, consult the wallet-specific view before assuming a failed upload.

Q: What should I do if my manual wallet remains empty after a successful CSV upload?

🅰️:

If your wallet appears empty after uploading a CSV file, confirm that the file contains valid and complete transaction data. If the upload reports success but no data appears, double-check formatting and content, then reach out to support for review and troubleshooting.

Q: What should I do if I receive an "Internal Server Error" when adding a transaction?

🅰️:

If you encounter an "Internal Server Error" when adding a transaction, first try refreshing the page or logging out and back in. If the issue persists, take a screenshot and report it to Bitwave Support with details including your Organization ID, Wallet Name, and Wallet ID. A support ticket may need to be created to resolve backend issues.

Q: What format should I use to share Coinbase transaction history with Bitwave Support?

🅰️:

Bitwave Support typically requests full historical transaction exports in CSV format for thorough reconciliation. Include all portfolios (e.g., Default, Treasury, Trading) and ensure the file covers all relevant dates. You may also share reference numbers or transaction hashes to aid identification.

Q: What should I do if some transactions are missing from Bitwave?

🅰️:

If transactions are not appearing in Bitwave, first check if they are associated with a synced wallet. You can try a wallet re-sync or manual import. To re-sync, provide your wallet ID to Bitwave support. If that doesn’t resolve the issue, support may assist with a manual import.

Q: Why am I getting an error when importing transactions via CSV into Bitwave?

🅰️:

Bitwave requires specific column headers (e.g., id, amount, amountTicker) in the CSV file to recognize the data structure. Deleting headers will cause the import to fail. Always follow Bitwave's standard import template and use unique IDs for each transaction across the organization.

Q: What should I do if my import overwrote previous transactions in Bitwave?

🅰️:

If a newer import reused existing transaction IDs, it may overwrite prior data. To fix this, re-upload the original file with new, unique IDs for each transaction. Bitwave requires each ID in the organization to be unique.

Q: What’s the correct way to format a trade with fees for manual import in Bitwave?

🅰️:

"When importing a trade with fees:

Use tradeFee (not tradeDFee) as the transaction type

Assign the same unique tradeId to all related trade entries (e.g., the asset sold, asset received, and fee)

Use Simple Import, not Advanced Import, for smoother processing"

Q: I imported transactions into a manual wallet, but the activity doesn’t show—what should I check?

🅰️:

If imported transactions are not appearing in your manual wallet, verify that the import file was formatted correctly and contained all required fields. Also, ensure the transactions were associated with the correct wallet ID. You can try re-importing the file or contact support with the file and wallet ID for further assistance.

Q: What are Bitwave’s customer service hours?

🅰️:

Bitwave's customer support is available from 8:00 AM to 5:00 PM Eastern Time (EST).

Q: Why aren't my manually imported transactions appearing in Bitwave wallets?

🅰️:

If your imported transactions aren’t showing up in Bitwave, ensure the import was successful and the correct wallet was selected. It's also important to verify that the file format and data structure matched Bitwave’s requirements. If issues persist, review the import file and check for confirmation of success, or contact support with the file for review.