Source-of-funds pack for business stablecoin buys: documents treasury should file
What a source of funds business stablecoin file actually contains
A source of funds business stablecoin file is the internal record your treasury team keeps every time it converts fiat into USDT or USDC to fund a supplier payout. At minimum, it ties together four things: the bank account that funded the buy, a short purpose memo explaining why the business needed stablecoins, the invoice batch or payable run the purchase supports, and the quote or execution evidence from the exchange or OTC desk. This is not a personal wealth history and it is not investment research — it is an operations artifact that lets you answer a CASP request, a bank query, or an internal audit within minutes rather than days.
Businesses that settle invoices in crypto on a recurring basis tend to build this pack as a repeatable template rather than a one-off memo, because the same four elements appear in almost every transaction regardless of size or corridor.
Why treasury needs this before, not after, the buy
Waiting until a CASP or bank asks the question is the most common operational mistake. If you assemble the fiat origin, purpose memo, and invoice link only after a request arrives, you are reconstructing history under time pressure, often across people who were not involved in the original decision.
Building the file at the time of purchase has three practical benefits:
- It matches the purchase to a specific business need while the context is fresh, reducing guesswork later.
- It gives your CASP a consistent, pre-formatted answer, which can shorten review cycles on future requests.
- It creates an audit trail that supports your own internal controls, separate from any external inquiry.
- It helps finance reconcile the stablecoin buy against the invoice batch during month-end close.
- It reduces reliance on institutional memory when staff turnover affects the treasury or compliance function.
A corporate treasury program that pairs crypto purchases with invoice payouts — the workflow described in corporate crypto treasury basics — generally treats this documentation step as part of the standard purchase-to-pay cycle, not as an exception process.
The four core components of the file
1. Fiat origin evidence
This section answers a simple question: which bank account funded the buy, and is that account consistent with the entity's normal operating activity? Typical supporting items include the account statement or screenshot showing the debit, the account holder name matching your registered legal entity, and a one-line note describing the account's role (operating account, payroll account, dedicated treasury account).
2. Purchase memo (business purpose)
The purchase memo is a short, dated note — often two or three sentences — explaining why the business bought stablecoins on that date, in that amount, through that venue. It should state the business reason (for example, funding a supplier payout cycle) and reference the relevant payable run or invoice batch.
3. Payable run or invoice batch link
This ties the purchase to the obligation it funds. For a single large invoice, this might be an invoice number and supplier name. For a batch payout, it is the payable run reference, the number of invoices in the batch, and the total payout amount in both fiat and stablecoin terms.
4. Quote or fill evidence
The execution record — a quote, a trade confirmation, or a fill report from your exchange or OTC desk — documents the price, timestamp, and counterparty for the conversion. For larger transactions, businesses often use an OTC desk rather than an order book; the process for sizing and documenting those trades is covered in when businesses use OTC crypto desks.
A sample file structure
The table below shows how a typical file is organized, with each row representing a document or data point treasury should capture.
| File section | What it contains | Typical source |
|---|---|---|
| Fiat origin | Account statement, account holder name, account role note | Business bank portal or statement export |
| Purchase memo | Short dated note on business purpose and amount | Treasury or finance lead, internal template |
| Invoice batch link | Invoice numbers, supplier names, payable run reference | AP system or payable run export |
| Quote / fill evidence | Trade confirmation, timestamp, price, counterparty | Exchange or OTC desk confirmation |
| CASP request log | Record of any prior requests and how they were answered | Internal compliance tracker |
This structure works whether you are paying a single supplier invoice or funding a weekly payable run across multiple corridors, a distinction also discussed in pay business invoices with USDT.
How this differs from a personal source-of-wealth statement
A business source of funds pack for a single stablecoin purchase is narrower and more transactional than a personal source-of-wealth statement. Source of wealth typically explains how an individual accumulated assets over years — through salary, business ownership, inheritance, or asset sales. A business purchase file, by contrast, documents one transaction: which account paid, why, for what invoice obligation, and at what price. Treasury teams should avoid conflating the two; a CASP request for a business transaction's source of funds is usually answered with the four-part file above, not with a personal financial history.
Global guidance on customer due diligence and the broader purpose of source-of-funds checks is published by the Financial Action Task Force (FATF) at fatf-gafi.org, and can serve as useful background when you design internal templates, though you should confirm specific obligations with your own counsel and your CASP's onboarding team.
Choosing between USDT and USDC affects documentation style
The stablecoin you choose can slightly change what your quote or fill evidence looks like, since liquidity venues, settlement rails, and attestation references differ between USDT and USDC. A side-by-side comparison of these operational differences is covered in USDC vs USDT for supplier payments, which is worth reviewing before you finalize your file template so the "quote or fill evidence" section matches the asset you actually use.
Cross-border context: why the invoice link matters more here
When the stablecoin purchase funds a cross-border supplier payout rather than a domestic one, the invoice batch link becomes more important, because it shows the purchase corresponds to a real international payable rather than an unexplained outbound transfer. The operational trade-offs between crypto settlement and traditional bank wires for cross-border payables are discussed in cross-border crypto vs bank wires, including how documentation needs shift when payments cross jurisdictions.
For businesses operating under EU rules, it is also worth tracking how the Markets in Crypto-Assets Regulation (MiCA) framework affects CASP obligations toward business customers; official EU institution pages provide current overviews of scope and timelines.
Accounting handoff: linking the file to your books
Once the stablecoin purchase is executed, finance needs the same file to record the transaction correctly — matching the fiat outflow, the stablecoin inflow, and the eventual supplier payout across your ledger. The IFRS Foundation publishes general materials on how digital assets are being considered in financial reporting discussions at ifrs.org, which can help frame internal accounting policy conversations, though you should confirm treatment with your auditor given that standards in this area continue to evolve.
Risks and limits of a source of funds pack
A source of funds file reduces friction with CASPs, banks, and auditors, but it has limits you should keep in mind:
- It does not guarantee approval of a CASP's onboarding or transaction monitoring decision; CASPs apply their own risk-based review regardless of how complete your file is.
- It is not a substitute for legal or tax advice on how a jurisdiction classifies or taxes stablecoin purchases and payouts.
- Requirements vary by country and by CASP, so a template that satisfies one counterparty may need adjustment for another.
- Record-keeping obligations change over time as AML and crypto-asset rules evolve, so templates should be reviewed periodically rather than treated as fixed.
- The file documents a single transaction's facts; it does not replace broader AML/KYB policies your business maintains at the entity level.
Practical checklist for treasury
Before executing a stablecoin purchase intended to fund supplier payouts, confirm the following:
- The funding bank account is identified and its statement or screenshot is saved.
- A one-paragraph purchase memo states the business purpose and references the amount.
- The invoice numbers or payable run reference are attached or linked.
- The quote or trade confirmation from your exchange or OTC desk is saved with timestamp and price.
- The file is stored in a location your compliance team can retrieve without delay.
- A note is added to your CASP request log if this purchase was prompted by an external query.
- The retention period for this file matches your internal policy and applicable local rules.
Treating this checklist as a standard step in every purchase — rather than an exception handled only when asked — is the practical difference between a treasury function that can answer a CASP request same-day and one that cannot.
Open a Cryptobus business account to buy crypto, pay invoices, and settle cross-border.
This material is for informational and educational purposes only. It is not legal, tax, investment, or financial advice. Cryptocurrency transactions involve operational, market, and compliance risk. Outcomes depend on your policies, counterparties, corridors, and applicable law. Readers should verify primary sources and internal controls as of the action date.