How to audit your own crypto transaction history before an exchange does: a self-review checklist
Published: Editorial policy
To audit your own history, export every transaction from each platform and wallet you used, merge them into one dated list, label each counterparty as yourself, a platform, a known person or unknown, and mark the items a reviewer is likely to question. Write one true sentence and name one supporting document for each marked item. Where you cannot explain something, say so plainly instead of guessing.
Questions about your case? Message us:
Key takeaways
- A self-review means seeing your history as a reviewer does: a dated list of amounts, counterparties and gaps, not a story you remember.
- Label every counterparty as yourself, a platform, a known person or unknown. The unknowns produce most of the questions, so they deserve the most attention.
- Mark the usual attention points: unknown senders, mixer contact, large round amounts, fast in-and-out movement and breaks from your normal pattern. Write one honest line for each.
- Never invent or reshape an explanation. A plain 'I do not know' with the records you do have is better than a neat story that a document contradicts.
Why audit your own history before a review?
Because a reviewer reads your history as a table, and most people remember it as a story. The reviewer sees dates, amounts, addresses and gaps. You remember why you did things, which is useful, but memory skips the deposit from an unfamiliar sender or the transfer made late one evening years ago. A self-audit finds those items first, while there is time to look for the records that explain them.
The audit does not assume that anything is wrong. Most histories contain a few entries that need a sentence of context, and the point is to have the sentence ready. It is useful before you expect a review, for example when you plan a large deposit, and it is useful when you have already received a question and want to answer the whole file in one message.
A word on terms. A counterparty is the person or service on the other side of a transfer. A reviewer wants to know who each one was, because the origin and the destination of funds are what an exchange is required to understand. The steps below are written for a person with a mixed history across several platforms and wallets.
Step 1: export everything and merge it into one list
Start by collecting the raw records, not by writing explanations. Every platform you used can usually produce a transaction export, and each wallet address you control can be looked up on a public block explorer, a website that shows transfers on a blockchain. Keep the original files untouched and work on a copy, so you can always show what the platform itself produced.
Merge the records into one spreadsheet in date order. Use the same columns for every row: date, platform or wallet, direction, asset, amount, counterparty, transaction hash and a notes column. A transfer between two wallets you own appears twice, once leaving and once arriving, so match the pair and mark it as an internal move.
Ask early for records that are slow to arrive, such as exports from closed accounts or older platforms. A gap in the list is itself something to note, because a reviewer reads a missing period as a question.
- Transaction exports from every exchange or service, including accounts you no longer use.
- Public transfer records for each wallet address you control, with transaction hashes.
- Bank statements for the fiat legs, meaning the purchases and sales that moved money in or out.
- Messages, order pages or receipts for peer-to-peer trades and private sales.
- Any earlier question from a platform, with your reply.
Step 2: label every counterparty
Go down the list and give each counterparty one of five labels: yourself, a regulated platform, a person you know, a business you know, or unknown. For each platform label, note which one. For each person or business label, note how you know them and what the transfer was for.
The label unknown is not a failure. It is the most useful label in the audit, because it marks the rows where you will need to work: look for the order page, the chat, the invoice or the bank record that shows how the transfer came about. Where the sender is a private person from a peer-to-peer trade, the order record often settles it.
Be strict about the label yourself. A wallet counts as yours only if you control it, and you should be able to show that without exposing any secret, for example with a signed message from the address. A wallet that a friend or a relative set up for you is not yours for this purpose, and the platform will treat it differently.
Step 3: mark what a reviewer is likely to question
Now read the list for the patterns that draw attention. These are not accusations, they are the places where a reviewer's eye usually stops. The table shows seven of them, why each one matters and what your line about it should cover.
Mixer contact needs a clear definition. A mixer is a service that pools funds from many users and sends them out in new amounts, which hides the visible link between sender and receiver. Platforms and their screening tools often rate funds by exposure, so coins that passed through such a service a few steps back can raise a flag even if you never used it yourself. If your history shows that kind of contact, mark it and describe it truthfully, whether you knew or not.
| What to mark | Why a reviewer looks at it | What your line should cover | What supports it |
|---|---|---|---|
| A sender you cannot identify | The origin cannot be tied to a person or a service | How the transfer came about, or plainly that you do not know | Order page, chat, invoice or the other party's confirmation |
| Contact with a mixer, directly or a few steps back | Such services break the visible link between sender and receiver | Whether you knew, when it happened and why, or how the coins reached you | Wallet history and the record of the trade or sale behind it |
| Large round amounts | A round sum can suggest an agreed price, a payment or a transfer made in pieces | What the amount paid for | Invoice, contract or sale record |
| Funds that arrive and leave quickly | It can resemble a pass-through of other people's money | The purpose of the transit and where the funds went | Records for both legs |
| Many small deposits from different senders | It can look like a collection or a business operating as a personal account | Whether it was sales, a shared payment or peer-to-peer trading | Trade records and chat logs |
| Activity far above your stated income | The account may not fit the profile declared at opening | What changed, such as a sale, an inheritance or a new job | The document that shows the change |
| A long gap followed by sudden activity | A dormant account revived can prompt questions about who is using it | What happened in between | A short note and any related record |
Step 4: write one true line for each marked item
A good line has three parts: what the item was, when it happened, and which document shows it. One sentence is enough. Reviewers read many files, and a short line with a named document is easier to check than a page of explanation.
A line states only what you can show. If the document does not exist, say so and name the closest alternative, such as an older export or a message from the other party. If you do not know who sent a deposit, write that you do not know and describe what you did to find out. Honest gaps are normal. Invented explanations are what damage a file, because reviewers compare dates and amounts across everything you send.
- Good: 'Deposit on [date], payment from a private buyer for a used laptop. Bank transfer record and the sale chat attached.'
- Good: 'Deposit on [date], round amount, repayment of a loan from a relative. Loan message and bank record attached.'
- Good: 'Funds received on [date] came from a peer-to-peer trade. I did not choose the sender and do not know their history. Order page attached.'
- Not acceptable: a line that names a source you cannot document, or one that changes between messages.
A worked example: a self-audit that found three questions
Here is one invented case. A customer traded peer to peer for a few years and kept coins on two platforms and a personal wallet. Before a planned large deposit, they built the list and found three rows that needed a line. One was a deposit from a sender they could not name. One was a round-number deposit that they had forgotten. The third was an address that a tracing tool showed as having touched a mixer a few steps before reaching them.
The unknown sender turned out to be a trade counterparty, and the order page proved it. The round deposit was a relative repaying a loan, and a message and a bank record showed that. The mixer exposure was the hard one: the customer had not chosen it and could not remove it, so the line said exactly that and pointed to the trade record for the coins.
When the platform later asked about the deposit, all three questions arrived in one request. The answers were already written, each with a document. The reviewer still made its own decision, but nothing in the file was a surprise.
What if you cannot explain an item?
Say so, and do the work that is left. Ask the other party for a confirmation, request older records from the platform or bank, and write a note that describes what you remember and what you checked. Do not delete, edit or move anything to make an entry disappear. Moving funds in the middle of a review adds new entries that also need an explanation, and a reviewer treats an effort to hide the origin of funds as a serious matter.
If you suspect that an item connects to a scam or another crime, pause before you write to the platform. That is a point for an independent licensed lawyer in your country, because what you say in writing can matter later.
When is an independent report worth having?
A self-audit organizes your records. It cannot show how funds moved across public ledgers, and some cases need that. Independent blockchain specialists can trace transfers and write a report from public data, which a reviewer may find easier to read than a spreadsheet. We are an intake and coordination service: we help scope the question, connect you with independent specialists and, where legal points arise, with licensed lawyers, and we help you turn the results into a package.
A report can show a path of funds. It cannot prove who owned an address or oblige a platform to accept it, and no result is guaranteed. The first assessment is free. Tracing works from public addresses, so nobody needs your seed phrase, private keys or passwords, and anyone who asks for them is a warning sign.
Common questions
What should I export before an exchange review?
Export the full transaction history from every platform you used for the relevant period, list the wallet addresses and transaction hashes, and gather bank statements for the fiat legs. Keep the originals untouched and work on copies.
Is contact with a mixer always a problem?
Not always, but screening tools often treat it as higher risk and the platform decides what it means. Describe it truthfully, say whether you knew about it and point to the record of how the coins reached you.
How far back should I audit my history?
Far enough to reach a documented origin for the funds in question. Start with the period around the deposit or transfer that matters, then extend. If the platform names a period, follow it, and if not, ask what it expects.
Can a self-audit replace a professional report?
No. A self-audit organizes your own records and prepares your explanations. A traced report from independent specialists shows how funds moved on the public ledger. A reviewer may still accept or ignore either one.
How we can help
- Blockchain analytics report. A source-of-funds report from transaction tracing, ready for a compliance team.
- Source of funds and source of wealth packs. Build a clear source of funds and source of wealth pack for exchanges, banks and processors.
- Digital evidence preparation for crypto cases. Capture, log and organise chats, screenshots and records so police, platforms or lawyers can use them.
Keep reading
Scammed, and Your Own Exchange Account Was Frozen
Why a scam victim's account is restricted, how the exchange sees it and the three documents that show you were deceived.
→Wallets and access · 9 min readWithdrawing to Your Own Wallet During a Review
Why withdrawals are normally blocked during a review, even to your own wallet, and why workarounds backfire.
→Frozen and blocked accounts · 9 min readAccount Frozen After Travel or a VPN Login
Why a new login location can restrict an account, how it combines with other signals and what shows the login was you.
→Information on this page is general and not legal advice.
