vexdu.
All buying guides

Records and support

Prepare crypto purchase records for support

Preserve exports, align times and record types, and describe an unexplained difference with matching evidence.

On this page 5

Keep the original before opening a working copy

Export the relevant order, execution or funding records from your official account. Preserve the original file and use a separate copy for sorting and calculations. Spreadsheet software can automatically change dates, long identifiers and decimal formats. The untouched original lets you check whether an apparent problem came from the records or from opening the file.

Treat order and transaction reference numbers as text when necessary, so long identifiers do not lose digits. For amounts, establish what the decimal and thousands separators mean before converting values. Removing every comma is not a safe rule across regional number formats.

Choose the question before combining the files

To check one purchase credit, select the order, related fees and asset credit.

To investigate a larger card charge, select the payment, settled bank amount and any refund. Combining every account's complete history first can increase mismatches and expose information unrelated to the problem.

Keep a source-file field, record type, original time and timezone, linked identifier, currency, quantity and direction. If you normalize time, add another column instead of overwriting the original. The export range should cover the transaction and surrounding activity, especially when different timezones put related records on different dates.

Deduplicate records, not matching amounts

Two purchases on the same day for the same amount can both be valid. Prefer an official unique identifier together with its record type when detecting duplicate exports. Without a unique identifier, compare several fields and manually review ambiguous rows instead of deleting every repeated amount.

Order summaries and execution rows create a different problem.

The executions can verify the summary, but both levels must not be added to the purchase total. Internal transfers also have two sides; preserve their relationship without treating each credit as another purchase.

Write one difference that somebody can reproduce

For example: “The accepted net quantity was 100; the matching credit is 99.5; the difference is 0.5. I checked the fees for this order and have not found that deduction.” These are sample numbers, not evidence. Replace them with your actual fields and add the order reference and timestamp.

If the final confirmation is missing, say so. A current quote or another customer's screenshot cannot replace it. Where several explanations remain possible, describe the gap as unresolved rather than inserting a convenient adjustment into the records.

Separate an official ticket from a public discussion

Reach support through the institution's official website or verified application and provide relevant information according to its process. Material posted publicly needs further redaction of names, account identifiers, full card numbers and unrelated activity. Passwords, verification codes, private keys and recovery phrases do not belong in an ordinary reconciliation explanation.

Keep the ticket reference, submission time and replies. Add explanations beside the working rows while leaving original files unchanged. Mark a difference explained only when the payment, credit and relevant fee records correspond. Pending settlement or a missing fee breakdown remains pending. For calculations, see weighted execution costs or the account-balance method in receipt reconciliation.

Related reading