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.
Q: Why are some of my Coinbase trades not showing in Bitwave?
🅰️:
If trades are missing despite an API connection, it could be due to syncing issues or delayed imports. Ensure the Coinbase activity CSV is reviewed, and contact Bitwave support with the report for manual reconciliation or investigation.
Q: Why are Uniswap transactions missing from my register in Bitwave?
🅰️:
Missing Uniswap transactions may occur if the relevant blockchain wallet (e.g., Avalanche) hasn’t been added in Bitwave. Ensure that the correct chain version of the wallet is created in Bitwave to allow all related transactions to flow in. If transactions were manually entered previously, duplicates might appear after syncing.
Q: How can I add NFT tokens for manual CSV upload in Bitwave?
🅰️:
To add NFT tokens manually, provide Bitwave Support with the Ethereum token contract address and the desired symbol for each NFT. These must be added to the system before import. Once added, you can use these symbols in the "AmountTicker" column during CSV upload.
Q: What causes a “500 error” when uploading a CSV file in Bitwave?
🅰️:
A “500 error” during CSV import typically indicates a backend processing issue, often triggered by incorrect or mismatched data. In this case, trade transactions in the file lacked matching blockchain IDs. Ensure that trade entries have consistent blockchain identifiers to prevent import failures.
Q: What values should I use for Contact and Category ID when manually uploading data in Bitwave?
🅰️:
Contact and Category IDs are optional unless you’ve filled out the cost basis column. To find them, go to Accounting > Contacts for contact IDs and Accounting > Categories for category IDs. Use the Bitwave ID shown for each entry.
Q: Why did my Bitwave import fail with a “Invalid BIGNUMERIC value” error?
🅰️:
This error typically occurs when the amount field contains invalid formatting, such as commas or negative values. Ensure all amounts are in absolute form and do not include commas or minus signs before uploading.
Q: Why is my CSV import into Bitwave stuck on upload or not showing a preview?
🅰️:
If your import is stuck or not showing a preview, common issues may include: incorrect time format (use mm/dd/yyyy hh:mm:ss), invalid transaction types (e.g., use “withdrawal” instead of custom labels), commas in numeric fields (should be removed), or incorrect account IDs. Also, ensure your file uses commas as separators—not semicolons, which can result from locale settings in Excel.
Q: Why does my Bitwave import show errors in all rows even after formatting corrections?
🅰️:
If errors persist, check the accountID values and your field separators. Incorrect IDs or using semicolons ; instead of commas , as delimiters can prevent a successful import. Switching to Google Sheets or correcting the delimiter in Excel settings can resolve the issue.
Q: What happens if I upload a CSV file without cost basis or USD conversion values in Bitwave?
🅰️:
If you upload a CSV without cost or conversion columns, Bitwave will attempt to price the transaction using market rates as of the transaction’s date and time assuming the asset is supported and pricing data is available. For missing or unsupported tokens, pricing may not populate without backend assistance.
Q: What should I do if a transaction fails to import or validate in Bitwave?
🅰️:
Transactions may fail due to incorrect or unrecognized ticker symbols or formatting issues. Removing problematic entries and re-uploading usually works. You can also manually add transactions using the "+" icon in the transactions UI.
Q: Can I categorize transactions before pricing is complete?
🅰️:
You can categorize transactions once pricing data has populated. However, do not categorize transactions for assets still pending backend pricing (e.g., TRX), as this can interfere with the pricing process.
Q: What should I do if I get an “error loading preview” when uploading a CSV file?
🅰️:
If you encounter an “error loading preview” while uploading a CSV file, check that the formatting and column values comply with Bitwave's manual import guidelines. Specifically, ensure the timestamp format is correct and required columns (like “Tax Exempt”) are populated appropriately (e.g., use “FALSE” if not applicable). Refer to Bitwave’s Manual Import documentation for formatting requirements.
Q: How should timestamps be formatted in CSV uploads?
🅰️:
Timestamps in manual CSV uploads should match the format specified in Bitwave’s manual import guide (MM/DD/YYYY HH:MM:SS). Incorrect time formats are a common cause of upload errors. Always refer to the manual import documentation to ensure proper formatting.
Q: What values should be used in the "Tax Exempt" column for manual CSV imports?
🅰️:
The "Tax Exempt" column should be filled with either “TRUE” or “FALSE.” If the transaction is not tax-exempt, use “FALSE.” Leaving this field blank can lead to upload errors.
Q: What should I check if Bitwave reports errors while importing a file but doesn't specify them?
🅰️:
Make sure numeric fields do not include commas or formatting characters. For example, use "300000" instead of "300,000".
Q: How can I import BTC ordinals, BRC-20 tokens, TON activity, and Jettons into Bitwave?
🅰️:
Currently, Bitwave does not automatically track BTC ordinals, BRC-20 tokens, TON activity, or Jettons. You can manually import this activity into Bitwave using CSV files. Follow the documentation here: Manual Import Guide.
Q: Will I encounter a “missing ticker” error when importing tokens like BRC-20 or Jettons into Bitwave?
🅰️:
You won't see a "missing ticker" error as long as the token ticker already exists in Bitwave's system. If the ticker isn't available, it must be added first, otherwise an error may occur.
Q: How can I import staking reward transactions with $0 cost basis?
🅰️:
Create a CSV with the rewards and set the "Cost" column to 0. Upload it using Bitwave’s manual import tool. This approach lets you treat rewards as created property with deferred income recognition.
Q: Why are only some entries from my CSV file being imported into Bitwave?
🅰️:
If only partial data from your CSV file uploads successfully, the most likely cause is same/repeated blockchain ids.
Q: How do I upload beginning balance data into Bitwave and troubleshoot CSV format errors?
🅰️:
To import beginning balances, use the Bitwave manual import template and follow the formatting guidelines in this documentation. If you encounter errors, double-check date formats, required fields, and ensure column headers match the template exactly. If the file fails to upload, review any provided error messages and correct them before retrying. For persistent issues, contact support with the file and a screenshot of the error.
Q: Where can I find the Bitwave import template for uploading manual wallet transactions?
🅰️:
You can download the Bitwave import template from the following Google Sheets link: Bitwave Import Template. This template allows you to manually import both transfer and trade transactions for a wallet.
Q: Can I use one Bitwave import template for both trades and transfers?
🅰️:
Yes, you can include both trades and transfers in a single import template. Bitwave supports multiple transaction types in one upload as long as they are formatted correctly according to the template guidelines.
Q: In the Bitwave import template, should the “Cost” column for trades be filled or left blank?
🅰️:
The instructions tab on the Bitwave import template advises leaving the “Cost” column blank for trades. Bitwave calculates the cost automatically based on the trade details. Manually entering a cost may cause validation issues.
Q: Why am I getting an error when using a wallet ID in the Bitwave import template?
🅰️:
Errors can occur if the wallet ID is entered incorrectly. Be cautious with similar-looking characters, such as capital “I” and lowercase “l.” Always copy the wallet ID directly from the Bitwave wallet details to avoid formatting mistakes.
Q: Why did my CSV file upload pass validation but still fail in Bitwave?
🅰️:
One common cause is including a “0” value in the fee field. Bitwave may reject uploads that contain explicitly zeroed fees. Removing the zero resolves the issue and allows the upload to proceed successfully.
Q: How should I format timestamps in a Bitwave CSV import file?
🅰️:
Timestamps in the Bitwave import CSV must follow the format mm/dd/yy hh:mm:ss. Using incorrect formats can lead to validation errors during upload. Always double-check your time entries before importing.
Q: How do I manually import wallet data into Bitwave using the import template?
🅰️:
Bitwave provides a manual import template for uploading wallet data. Each column corresponds to a specific field, such as transaction date, token, quantity, and wallet address. You can review the manual import documentation for detailed guidance. If you have specific questions about any columns, support can help clarify them.
Q: What causes the "error generating preview" message during file import in Bitwave?
🅰️:
This can occur if there are formatting or validation issues in the file, such as empty required fields or incorrect column headers. Check that all required fields are filled and formatted correctly, especially time format and category fields. Contact support with a screenshot if the issue persists.
Q: What should I do if my import file gets stuck or doesn’t complete in Bitwave?
🅰️:
If your import appears stalled, first reduce the file size Bitwave recommends importing fewer than 10,000 rows per file. You can also try refreshing your browser. If the file still doesn't process, try reimporting it later or reach out to support.
Q: What are common reasons import files fail or show blank errors?
🅰️:
Import errors can result from missing headers, inconsistent time formats, values with commas, or fields incorrectly labeled. Ensure the file includes correct headers and uniform formatting, and remove commas from number values. Refer to Bitwave's import templates for accuracy.
Q: Can Bitwave detect and prevent duplicate transactions if I reimport a file?
🅰️:
No, Bitwave does not automatically prevent duplication. If you upload the same file twice, the transactions will be duplicated unless transaction IDs are unique. Always ensure unique IDs in imports or clean up duplicates manually.
Q: How do I structure trade imports for assets whose pricing not recognized by Bitwave?
🅰️:
For unrecognized assets like BTC5L or ETH5L, manually add a pricing rule or fill in the cost column using external price data (e.g., TradingView). Only the disposed and acquired lines need pricing. Ensure that trade values are logically matched to avoid pricing errors.
Q: Can I bulk edit or delete transactions without blockchain IDs?
🅰️:
If transactions lack blockchain IDs (e.g., off-chain trades), use Bitwave’s system jobs feature with a CSV bulk action to ignore them. You must identify the transaction IDs within Bitwave to apply this process.
Q: Why am I receiving an error when trying to import a transaction involving DYDX_CHAIN?
🅰️:
Import errors can occur if a token ticker is not yet recognized or supported in Bitwave. In this case, DYDX_CHAIN was not in the system at the time of import, leading to the error. To resolve this, the token must be formally added by Bitwave’s support team.
Q: What should I do if a token isn’t recognized during transaction import?
🅰️:
If a token is unrecognized, you should gather details such as the Org ID, Org Name, proposed Bitwave Token Ticker, Blockchain, Token Contract Address, and Coingecko link. Submit this to Bitwave support to request the token be added to the platform.
Q: Why do I get an “error generating preview” when importing transactions into Bitwave?
🅰️:
This error often occurs due to incorrect date formatting in the import file. Bitwave requires the date format to be in "MM/DD/YYYY HH:MM:SS". Review and correct the formatting before uploading. Refer to the Manual Wallet Import Guide for proper formatting examples.
Q: Why does the date format change when I copy from the transaction screen?
🅰️:
When copying from the UI, some browsers or spreadsheet tools may automatically reformat the date, especially if regional settings differ. Always double-check and reformat the date cells to "MM/DD/YYYY HH:MM:SS" before uploading to Bitwave.
Q: How can I search for past manual transactions in Bitwave?
🅰️:
To locate a manual transaction, go to the Transactions screen and use filters such as date range or transaction ID. Manual transactions are not always easily filtered by type, so using a narrow date range around when the transaction was created can help.
Q: Why do some trades show up as multiple transactions in Bitwave?
🅰️:
Bitwave may show separate transactions if tokens move through multiple protocols or steps in a trade path, especially if each has a different transaction ID. If they share the same hash and represent a single economic event, you can manually combine them in Bitwave.
Q: How do I import historical transactions from Coinbase into Bitwave for periods before connecting the wallet?
🅰️:
When connecting a Coinbase account via API, Bitwave typically syncs historical data automatically. However, if earlier transactions (e.g., before 12/31/2023) are missing, it's possible they fall outside the API's default lookback range. In such cases, contact Bitwave support and provide access so they can initiate a full historical sync or assist with manual import if needed.
Q: How can I delete an imported file in Bitwave?
🅰️:
Bitwave does not currently allow users to delete imported files directly through the UI. If you've imported a file in error, contact support and provide the Import ID so they can assist with removal.
Q: What should I do if my file import is stuck and not progressing?
🅰️:
If a file import is stuck (e.g., frozen at a percentage), it could be due to backend processing delays. Try refreshing the page first. If the issue persists, contact Bitwave support and provide the Import IDs so the team can investigate and complete or reset the import.
Q: Can I connect the Pionex API to Bitwave?
🅰️:
Bitwave currently does not support direct integration with Pionex. To import data from Pionex, manually upload the transaction history by creating a manual wallet. Check the supported exchanges list for other integrations.
Q: How can I delete partially uploaded or stuck import files from Bitwave?
🅰️:
You can request Bitwave support to delete partially imported files by providing the file IDs. There's currently no self-service option to delete uploads from the interface.
Q: What does the “health-controller - Bad status from transaction batch create: 500” error mean in Bitwave?
🅰️:
This error indicates a server-side failure during the transaction batch processing stage. It typically requires intervention from Bitwave's engineering or support team to resolve.
Q: What does the "Amount" column represent in the Bitwave import template?
🅰️:
The "Amount" column in the import template refers to the number of tokens, not the dollar value. To set the dollar value (cost basis), use the "Cost" and "CostTicker" columns.
Q: When should I use the "Cost" and "CostTicker" fields in the Bitwave import template?
🅰️:
Use the "Cost" and "CostTicker" fields if you want to manually define the cost basis of the tokens. If these fields are left blank, Bitwave will use its default pricing source (typically CryptoCompare) to derive the cost basis based on the timestamp of the transaction.
Q: What should be used as the "Transaction Type" for uploading 12/31/23 opening positions?
🅰️:
Use “Deposit” as the transaction type when establishing opening positions. This is appropriate when you are not recording trades but simply stating the holdings as of a specific date.
Q: Is the "TradeID" field required when uploading opening balances for year-end positions?
🅰️:
No, the "TradeID" field is not required if the transaction type is “Deposit.” This field is only necessary for trade transactions where you are matching buys and sells.
Q: How should I fill in the ID column (Column A) of the Bitwave import template?
🅰️:
Each row in the import file must have a unique ID in Column A. You can use a simple numbering system such as 1, 2, 3 or labels like a1, a2, a3, etc.
Q: What happens if my manually entered cost basis differs from Bitwave’s calculated value?
🅰️:
If your cost basis differs from Bitwave’s default pricing-based value, an adjusting journal entry may be required to reconcile your books. This is typically recorded in the current year to align Bitwave’s system with your historical accounting.
Q: What data is needed to establish opening balances in Bitwave?
🅰️:
To establish opening balances, Bitwave requires: (1) token quantities held in each wallet as of the opening date, (2) cost basis for each holding, and (3) acquisition dates. These can be provided as totals per wallet or detailed lot-level data.
Q: How do I format the import template to establish opening balances as of a specific date?
🅰️:
To upload opening balances, fill in the required columns: ID (unique per row), Amount (token quantity), Ticker, Time (use 12/31/23 11:59:59 for beginning balances), Transaction Type ("Deposit" for holdings), Wallet ID (as Account ID), Tax Status, and Blockchain ID (optional but helpful). Use Cost and CostTicker if you want to set specific cost basis values. Wallet IDs must be used instead of wallet addresses in the Account ID column.
