# CryptoTuts Wallet Check: synthetic test package v1

US edition reviewed October 4, 2026. All transactions, account names and IDs are invented. No real wallet addresses, keys or personal information. The dollar amounts are synthetic example costs, not conversions of real euro purchases or market valuations. No tax amount is an expected result.

## Which file should I use?

- 01-cointracking-test.csv: eight transactions in the CoinTracking custom CSV layout (15 columns).
- 02-waltio-trade-table-test.csv: the same eight transactions in the CoinTracking Trade Table layout (13 columns). The old filename is retained for existing download links; it is a synthetic format example, not an actual provider export or a supported US Waltio integration.
- 03-nur-lokal-fehlende-buchung.csv: deliberately incomplete seven-transaction negative control. The outgoing XRP transfer is missing. Use only locally in this test.
- sollwerte.json: independent expected quantities for automated comparisons.

Files 01 and 02 are alternatives: never import both into the same account. Never load these examples into a production tax account. Do not open and resave the CSV in Excel, which can change its format. All timestamps use UTC. Decimal point, English transaction types, comma-separated fields.

## 1. Try it without a provider account

1. Open Wallet Check and choose “View an example without a real wallet”. The demo balance is 2,500 XRP.
2. Open “Import a file / continue”, then “Load the synthetic test file”, or select file02 yourself.
3. Confirm the possible own transfer from row6 to row7. This confirmation applies only to this invented exercise.
4. Choose source account TEST_WALLET and source time zone UTC.
5. Expect 2,500 XRP remaining from purchaseA dated January2,2025. After transfer confirmation there is no origin block. The local FIFO model assigns about $1,666.666667 of the synthetic USD purchase cost, with the stated trading fee already included. This is a technical cost allocation, not a tax calculation.
6. After reviewing it, optionally add the remaining quantity to the demo. This changes no real wallet and sends no transaction.
7. For an export, instead open “Prepare a file for tax software”, select the CoinTracking draft, select all technically exportable rows, enter UTC and confirm. Save the review JSON and download the CSV. It must retain all eight original transactions, rather than just today's remaining balance.

## 2. Review in CoinTracking only in an empty separate test account

The public compatibility boundary is unchanged: no successful provider import is claimed. This local exercise needs no provider signup or purchase. If you later test a provider, use an independently authorized, empty account.

1. Check the account/import time zone is UTC and follow the provider's current import instructions. Keep existing portfolios separate.
2. Use file01 in the CoinTracking custom CSV importer with its documented header mapping, not the Excel importer.
3. Before confirmation, check eight rows: three Trades, two Deposits, two Withdrawals and one Other Fee. Check for skipped rows or unexpected categories.
4. Compare quantities, fees, accounts, timestamps and IDs with the table below. Do not subtract the fee again from Buy/Sell amounts that already include it.
5. Review the provider's transaction-validation, duplicate, missing-transaction, flow and balance reports. Without independent real account balances there is no external balance confirmation. Fiat bank counterparts are deliberately outside the package.
6. Record warnings. A provider's historical valuation or tax figure is not an expected result of this package.

## 3. Review an actual provider export before a compatibility claim

1. An actual CoinTracking Transactions CSV export is separate from this synthetic Trade Table example. Use the current export instructions, retain its timestamps and leave the source file unchanged.
2. Keep source and destination test runs separate. Never import both alternatives or duplicate a real exported history.
3. Verify all eight economic transactions, especially the transfer of2,501 XRP out,2,500 XRP in and1 XRP fee, against the expected balances below.
4. Document changed headers, omitted IDs, date formats or transaction types. Rejection or silent skipping means the integration remains unverified. Do not silently relabel entries to make a test pass.
5. File02 can test its declared layout in an independent local run. It does not replace an actual export/import roundtrip. Provider import has not been confirmed. The provider's general CSV export documentation warns that Trade IDs may be omitted.

## Expected transactions (UTC)

| Row | Event | Received / Buy | Outgoing / Sell | Fee field |
| --- | --- | --- | --- | --- |
|2|Fiat deposit, TEST_EXCHANGE|3,000 USD|none|empty|
|3|PurchaseA|3,000 XRP|2,000 USD|10 USD, already included|
|4|PurchaseB|1,000 XRP net|800 USD|1 XRP, already reflected|
|5|Partial sale|400 USD net|500 XRP|2 USD, already reflected|
|6|Transfer out, TEST_EXCHANGE|none|2,501 XRP|1 XRP, already included|
|7|Transfer in, TEST_WALLET|2,500 XRP|none|empty|
|8|Separate Other Fee, TEST_EXCHANGE|none|2 XRP|empty; the2 XRP is the outgoing amount|
|9|Fiat withdrawal, TEST_EXCHANGE|none|600 USD|empty|

Independent quantity checks:

- TEST_EXCHANGE XRP:3,000+1,000-500-2,501-2=997 XRP.
- TEST_WALLET XRP:2,500 XRP.
- Total:3,497 XRP. An own transfer is not a new purchase.
- TEST_EXCHANGE USD:3,000-2,000-800+400-600=0 USD.
- Synthetic remaining wallet cost:2,000 USD *2,500/3,000=1,666.666666… USD. Do not add the already included10 USD fee again.

## Negative control

Load file03 only locally. The transfer's outgoing side is missing: no confirmable pair,2,500 XRP with unknown origin in TEST_WALLET, and remaining-lot application blocked. In the export assistant, select all readable rows: the transaction-chain check must block generated CSV. A format check alone must not accept it. Review JSON remains available as a record of the problem.

## Additional checks before a public compatibility claim

Separately review precision beyond six decimals, daylight-saving time boundaries, quoting/newlines, third-currency fees, missing/duplicate IDs, unsupported staking/LP/derivative types, multiple accounts and existing transactions. This basic package does not cover them all. Local negative regression tests do not replace a provider roundtrip.

## Sources for format and fee conventions

- CoinTracking custom CSV:11 basic fields plus4 optional fields in its import instructions. No extra CSV comment rows.
- CoinTracking fees: https://cointracking.freshdesk.com/en/support/solutions/articles/29000007202-entering-fees
- CoinTracking local export/restore: https://cointracking.freshdesk.com/en/support/solutions/articles/29000031008-create-backup-restore-or-export-your-account-data
- CoinTracking validation: https://cointracking.freshdesk.com/en/support/solutions/articles/29000049924-validate-transactions

All CSV amounts and IDs are TEST DATA. Keep them as technical test records, never as evidence of real acquisitions. US holding periods can affect a capital-gains rate; holding longer than a year does not make a sale tax-free. This package supplies no tax-return calculation.
