Optional cookies require your permission.Privacy & cookies

What belongs in a Vanuatu source-of-funds exhibit index?

An applicant buys Bitcoin through an exchange using funds held at a bank. The index should take a reviewer from the bank debit to the purchase, then to the holding selected for payment.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (1)
A binder, financial charts, a pencil, and a calculator are arranged on a desk.
In this essay12 sections
  1. Begin with the recipient’s requirements.
  2. Keep identity and financial history connected.
  3. Tell the wealth story and the transaction story separately.
  4. Make the fiat-to-Bitcoin handoff legible.
  5. Use custody evidence without overstating it.
  6. Write the explanation after the evidence is understood.
  7. Index the exhibits before merging the documents.
  8. Finish by testing the story, not the folder’s size.
  9. Build the register around questions a reader can answer.
  10. Request the missing record with enough precision to retrieve it.
  11. Plan for questions after the first submission.
  12. The Bitcoin Lawyer take

Begin with the recipient’s requirements.

A source-of-funds file can be technically impressive and still fail to answer the questions in the actual application. Before collecting hundreds of screenshots, identify the route, the responsible recipient, the current document request, and the proposed funding transaction. That gives the evidence a purpose.

The Vanuatu Financial Intelligence Unit (FIU) notice dated 14 January 2025 lists a passport copy with more than six months’ validity, valid police clearance, notarized curriculum vitae, and government-payment evidence among the required submission documents. It describes a submission and acknowledgment process. Read it as a dated official baseline and confirm current instructions for the case.

A wallet map, exchange export, or explanatory letter can be useful supporting material without appearing word for word in that notice. Distinguish official requirements from editorial preparation suggestions. Neither a private checklist nor a well-designed PDF changes what the authority ultimately considers sufficient.

Keep identity and financial history connected.

Start with the person whose funds are being used. Names, dates of birth, previous names, and relevant nationalities should agree with the civil and identity evidence. A bank statement in a former name may be perfectly explicable, but the name-change record needs to connect it to the current applicant.

Give each adult family member a distinct document history where required. A spouse, adult dependent, parent, or child may need different civil or dependency evidence under the applicable route. Do not assume that a shared surname proves the relationship, or that a different surname undermines it. Use the underlying records.

Where divorce, adoption, guardianship, or custody affects the application, identify the actual legal document, and the question it answers. Explain the relationship plainly without adding an unsupported legal conclusion. If authority to apply or consent is uncertain, that issue should be resolved through appropriate advice rather than concealed by arranging the pages more neatly.

Tell the wealth story and the transaction story separately.

Source of wealth concerns how the applicant accumulated assets. Source of funds concerns the particular value intended for the application. The stories should fit together, but one should not be used as a substitute for the other. A successful career does not explain an unexplained incoming transfer, and a traceable transfer does not establish its lawful economic origin.

For employment, the relevant trail may include contracts, payslips, tax records, and receipts. For a business, it may include ownership, accounts, invoices, distributions, and a sale agreement. For an inheritance, the estate’s authority and distribution records matter. For mining, operating records and payout evidence explain a different kind of economic activity.

Describe gifts, loans, and distributions as what they actually are. If company money becomes personal money, identify the event that made the applicant entitled to it. A board resolution alone may not prove that the payment occurred; a payment alone may not establish that it was properly authorized. The evidence should support both sides of the explanation.

Make the fiat-to-Bitcoin handoff legible.

An exchange trade history can show a purchase inside an account. The bank-side evidence explains where the funds credited to that account came from. Connect the account holder, payment date, amount, provider, and relevant trade record rather than assuming the reviewer will recognize a payment description.

Suppose a hypothetical applicant receives business-sale proceeds, transfers part through a second bank and then buys Bitcoin. The sale-closing record, both bank movements, account identity, and exchange history each perform a different job. Omitting the intermediate bank because it seems uninteresting creates an avoidable break in the chain.

Explain differences caused by currency conversion, fees, or several purchases rather than forcing totals to match. Preserve the original currency and amount alongside any conversion used in the summary, with its method and date. A current market value can describe today’s holdings; it should not be used as if it proved the historic acquisition price.

Use custody evidence without overstating it.

Follow the relevant withdrawals, deposits, and material changes in custody into the funds proposed for the application. An on-chain transaction identifier helps locate a transfer. It does not, by itself, identify all owners, establish legal authority, or explain the commercial event behind it.

For multisignature or collaborative custody, describe the actual arrangement: who owns the value, who can authorize a transaction, and what records support those roles. Do not describe one signer as having unilateral control if that is not how the wallet works. For Lightning, distinguish channel funding and closing records from the separate off-chain activity history.

Keep seed phrases and private keys out of the file. If a reviewer asks for proof of control, clarify the exact evidence and safe procedure before doing anything. A file can explain custody without collecting the material that would let a recipient spend the funds. The aim is attribution and understanding, not indiscriminate exposure.

Write the explanation after the evidence is understood.

A narrative should follow the chronology and refer to the supporting exhibit where each fact is introduced. It should say how the wealth arose, how the relevant value was acquired, what material changes in ownership or custody occurred and which funds are proposed for payment. Its length should follow the complexity rather than a fixed page target.

Keep sentences factual. “The statement records a transfer on this date” is stronger than a broad assertion that every transaction has been verified. If a statement supports only part of the conclusion, say what else supplies the connection. Recollection, independent corroboration, and a formal record are different kinds of support.

In a hypothetical old-exchange case, the explanation might identify the missing trade export and the bank record, email, and chain history that survive. It should not recreate the missing export or present an estimated trade as an exact fact. The reader should be able to locate the uncertainty without discovering it through contradiction.

Index the exhibits before merging the documents.

An exhibit number, descriptive title, and date make a large file easier to navigate. Use the same identifiers in the narrative and filenames. Keep the original records separately from a combined review copy so later questions can be answered without losing the underlying evidence or its provenance.

Check certification, translation, validity, and completeness against the recipient’s actual instructions. A translated extract may omit context; a cropped image may remove the account holder; a scan may conceal the back of a document. Ask what form is needed rather than assuming that a readable digital copy satisfies every formal requirement.

Version control also matters. If an explanation changes after a new record is found, retain the earlier submitted version and document the correction. Do not quietly replace a file already sent and later assume everyone is reading the same material. A request, the response, and the acknowledgment should stay connected.

Finish by testing the story, not the folder’s size.

Read the narrative as someone who has never met the applicant. Can you identify the people and entities, follow the relevant economic events, and locate the exhibits? Do names, dates, and amounts agree, and are any gaps described honestly? Can the proposed payment be connected to funds the applicant is entitled to use?

A large merged PDF is not evidence of completeness. A small, well-supported file may be clearer, while a complex history may genuinely require more material. The right amount is the amount needed to answer the actual questions, with a path to further evidence if requested.

Keep settlement separate from clearance. The ability to send Bitcoin or another accepted payment does not explain how the wealth arose or establish citizenship eligibility. The prepared file supports the official review; it does not clear itself.

Build the register around questions a reader can answer.

Consider a fictional applicant whose funds originate in a business sale. Exhibit A might establish the applicant’s ownership interest before sale. Exhibit B might contain the executed agreement. Exhibit C might show completion and the allocation of proceeds. Exhibit D might show receipt into the applicant’s account. The exhibit letters are arbitrary; the relationship among the records is what matters.

If the agreement states a headline price but the personal receipt is smaller, the register should lead the reader to the explanation: other owners, debt repayment, retained consideration, or another documented adjustment. Do not leave the reviewer to infer that the difference is harmless. Equally, do not add an explanation simply because it is common in other sales. Use the actual completion documents.

Then connect the personal receipt to the funds intended for the application. If only part of the proceeds was used to acquire Bitcoin, identify that part. If the proposed funds come from a different source, say so and document the correct path. The wider sale may explain wealth without being the source of this payment. Keeping that distinction visible makes a complex file easier to read.

Request the missing record with enough precision to retrieve it.

A request to a former bank or exchange should identify the relevant account, period, and record type through the provider’s proper secure process. A general request for everything can take longer and still fail to retrieve the particular entry needed. Before contacting the custodian, identify the proposition the missing record must support and the records already available.

Keep the request and response in the working history. If the provider cannot supply a record, preserve that response and describe what survives. A search failure is a fact about the evidence; it is not proof that the underlying transaction never happened. Conversely, the holder’s confidence that it happened does not transform an unavailable document into verified evidence.

Where records arrive in a new format, retain the original download. A useful review copy can be labeled, translated, or reorganized while preserving the source separately. Record the preparation method so a later reader can distinguish the provider’s content from the applicant’s annotations. An annotation should point to evidence rather than silently change it.

Plan for questions after the first submission.

A follow-up request should be answered against the version the recipient actually saw. Identify the requested issue, the new material supplied, and whether it corrects an earlier statement or adds detail. If a correction is necessary, state it clearly. Quietly replacing the old narrative can create two inconsistent records without explaining why they differ.

Use proportionate disclosure without obscuring required context. A reviewer may need the account holder’s name, relevant period, and surrounding entries to understand a transaction. Removing those details can make a document less useful. At the same time, a request for financial evidence does not justify sending signing secrets. Clarify the recipient’s requirements and use an appropriate channel for the material actually required.

Finally, preserve the completed record in a form the applicant can retrieve. The file may be useful when a later institution asks about the same history, although that institution makes its own assessment. Keeping the original exhibits, submitted versions, questions, and responses together prevents the next review from beginning with an inbox search and a half-remembered explanation.

The whole picture

The Bitcoin Lawyer take

Give each exhibit a specific factual job and identify missing links openly. Additional screenshots help only when they establish something the reviewer cannot see in the existing file.

Give missing evidence the same care as the documents that exist. A precise gap, a preserved request, and a candid explanation are more valuable than a polished packet that hides uncertainty. The applicant should leave preparation with a record they understand and can maintain.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “What belongs in a Vanuatu source-of-funds exhibit index?” https://www.bitcoinlawyer.com/journal/organising-a-vanuatu-funding-file