{"id":12352,"date":"2026-09-13T03:40:37","date_gmt":"2026-09-13T01:40:37","guid":{"rendered":"https:\/\/paucitas.com\/questions\/documents-bank-needs-money-from-crypto\/"},"modified":"2026-09-13T04:11:52","modified_gmt":"2026-09-13T02:11:52","slug":"documents-bank-needs-money-from-crypto","status":"publish","type":"page","link":"https:\/\/paucitas.com\/en\/questions\/documents-bank-needs-money-from-crypto\/","title":{"rendered":"Which documents does my bank need for money that came from crypto?"},"content":{"rendered":"
\n\u2190<\/span>Back to Questions<\/a><\/p>\n
\n

Which documents does my bank need for money that came from crypto?<\/h1>\n<\/div>\n

By S.E. (Simcha) Schrijver<\/a>, blockchain investigator at Paucitas<\/p>\n

Paucitas bundles the documents bank needs for a payment out of crypto into one file that can be followed. Those are as a rule an overview of your holdings, the transaction history and the substantiation of the first purchase.<\/div>\n

What Paucitas does<\/h2>\n

We establish which documents your bank has actually asked for and fill the gaps between them with investigation on the blockchain. The file consists of five parts: a summary of one page, a timeline of the origin, a transaction table with a source reference per line, the account of the method, and the annexes holding your own documents.<\/p>\n

Dutch banks tend to ask in a fixed order, so the file follows that order. That alone removes most of the back and forth, because nothing has to be looked for.<\/p>\n

We establish which documents bank needs in your specific case and fill the gaps between them with investigation on the blockchain. The file has five parts: a summary of one page, a timeline of the origin, a transaction table with a source reference per line, the account of the method, and the annexes holding your own documents.<\/p>\n

What you supply<\/h2>\n

You supply the question from your bank exactly as you received it, the addresses of your wallets, the exports from your exchanges and the bank statements of your original deposits. If a document is missing, say so at the start rather than at the end.<\/p>\n

Where your holdings passed through more than one exchange, add the statements of each of them. A bank reviewer reads the chain from end to end, and a single missing link is enough to keep a question open.<\/p>\n

Where your holdings passed through more than one exchange, add the statements of each. A reviewer reads the chain from end to end, and a single missing link keeps the question open.<\/p>\n

What you receive<\/h2>\n

You receive the complete file in a single document, plus a short covering text you can use when you submit it. The covering text is deliberately plain: it names what is enclosed and what it establishes, without arguing a case.<\/p>\n

A standard file is normally ready within three working days after we receive your data.<\/p>\n

For an international reader the order is the point. Dutch banks tend to ask in a fixed sequence, and a file that follows that sequence removes most of the back and forth because nothing has to be looked for. A standard file is normally ready within three working days after we receive your data.<\/p>\n

You also receive a short covering text to use when you submit the file. It names what is enclosed and what it establishes, without arguing your case, which is the tone a compliance reviewer responds to best.<\/p>\n

How to get started<\/h2>\n

You contact us and send the question from your bank with it. We will tell you which of the five parts your situation actually needs, because not every question requires the full file. The contact page<\/a> is the place to start.<\/p>\n

Not every question needs the full file. Send the request as you received it and we will tell you which of the five parts your situation actually calls for.<\/p>\n

If a document no longer exists, say so at the start rather than at the end. On-chain data fill a surprising number of those gaps, but only if we know which ones to look for.<\/p>\n

Whether a particular bank accepts the file remains for the bank itself.<\/p>\n

Further reading<\/strong><\/p>\n