Before an investor opens your data room, run this check yourself.
This guide expands on the readiness questions in How to Prepare Your Web3 Treasury for Investor Due Diligence. That article explains why on-chain transparency is not the same as diligence-readiness. Here, we turn each question into work you can actually do: what investors are testing, what a diligence-ready answer looks like, and how to close the gap if you cannot produce one today.
Work through all seven items. Starting with recipient identity and payment purpose will make the later reconciliation considerably easier.
A note on materiality: There is no universal dollar threshold. A payment may be material because of its value, frequency, recipient, relationship to core intellectual property, or connection to a founder or related party. Set your review threshold with your finance and legal advisors, document it, and apply it consistently.
1. Identify the person or entity behind each material payout wallet
What investors are testing: Whether company funds went to known counterparties—or to addresses no one can reliably account for.
What a diligence-ready answer looks like: For every wallet that received material or recurring payments, you can name the legal person or entity behind it and show how that association was established. The recipient may have provided and verified the address through authenticated onboarding, an invoicing system, a signed document, or a wallet-signature flow.
“Our former operations lead remembers whose wallet that is” is not a durable record. It is an answer that may disappear when the employee does.
How to close the gap: Export your treasury outflows and sort recipient wallets by total value and payment frequency. Start at the top of that list, not the bottom.
For each unattributed wallet, ask the recipient to confirm it through an authenticated process and, where practical, prove control by signing a message with the wallet. Written confirmation from a known email account can support the record, but it is weaker than direct proof of wallet control. Record the confirmation date and method.
For wallets you cannot attribute, document what is known, when the payments occurred, and what they appear to have covered. Flag them for counsel before diligence begins rather than presenting an unsupported conclusion as fact.
2. Explain the business purpose of each material transfer
What investors are testing: Whether treasury funds were spent on the business—and whether management understands and controls its own spending.
What a diligence-ready answer looks like: Each material payment maps to a purpose that an informed third party can understand: a development milestone, monthly retainer, grant decision, security audit, marketing engagement, customer refund, or another defined obligation. The purpose is preserved in a retrievable record rather than inferred from the recipient's identity.
Knowing who received a payment does not explain why the company made it.
How to close the gap: For each attributed wallet from step one, write a one-line purpose for every payment or recurring payment series. Link that purpose to any supporting invoice, milestone, proposal, grant decision, or internal request.
Where the purpose is genuinely unclear, say so internally and investigate. Do not backfill the ledger with a plausible story simply because it fits the recipient. If an investor discovers one reverse-engineered explanation, every other answer becomes less trustworthy.
3. Produce the agreement, invoice, milestone, or approval behind each payment
What investors are testing: Whether payments had a documented legal and business basis—and, critically, whether the company owns what it paid for.
What a diligence-ready answer looks like: Material relationships have signed agreements. When the recipient produced code, designs, content, or other intellectual property, the relevant agreement addresses ownership and assignment. Invoices, milestone confirmations, or approved payment requests connect individual transfers to the underlying relationship.
You should be able to move from a material payment to its supporting paperwork in minutes.
How to close the gap: Build a simple index containing:
the recipient;
the governing agreement;
where the agreement is stored;
the payments or payment period it covers;
the related invoices, milestones, or approvals;
the status of any required intellectual-property assignment.
Missing agreements may be remediable, but do not improvise the cure. Counsel may recommend documenting the existing relationship, confirming prior terms, or executing an assignment covering previously created work. The appropriate approach depends on the facts and jurisdiction.
A core protocol component built by someone with no written intellectual-property assignment deserves immediate attention. Treat it as a pre-raise priority, because investor counsel is likely to do the same.
4. Show how applicable identity, screening, and tax requirements were handled
What investors are testing: Whether the company has a compliance process—and whether the process was actually applied rather than merely written.
What a diligence-ready answer looks like: The company has a short, practical policy that scales its requirements to the recipient, payment, and risk. It explains, for example:
which recipients undergo identity verification;
when recipient or wallet screening is performed;
when checks must be repeated;
from which recipients the company collects a W-9, the applicable form from the W-8 series, or other required tax documentation;
who reviews exceptions and higher-risk cases;
how evidence of completed checks is retained.
The records then show that the policy was followed: applicable forms, verification status, screening results, review dates, and documented exceptions.
The goal is not to collect every possible document from every person. A $50 community reward and a $100,000 development contract may reasonably require different controls. The goal is to apply a defensible policy consistently.
How to close the gap: If no policy exists, document the process the company actually follows and give it an effective date. Then review it with legal and tax advisors and strengthen it prospectively.
Do not write an aspirational policy and imply that it governed historical payments when it did not. Identify recipients for whom required documentation or checks may be missing, and let the appropriate advisor determine how remediation should be sequenced.
5. Distinguish operating expenses, token grants, founder transactions, and other movements
What investors are testing: Whether treasury categories accurately describe the company's activity—and whether related-party transactions are visible rather than buried among ordinary expenses.
What a diligence-ready answer looks like: Every material outflow has a clear category, such as:
operating expense;
employee or contractor compensation;
token grant;
founder or related-party transaction;
customer refund;
inter-wallet transfer;
investment or treasury-management transaction.
Related-party transactions are separately identifiable and supported by their business rationale and approval.
How to close the gap: Categorize historical outflows beginning with the largest and most frequent. Isolate anything involving a founder, officer, director, major tokenholder, or an entity they control. Preserve a clear explanation and supporting approval for each.
A related-party payment disclosed and explained proactively is context. The same payment discovered unexpectedly by the investor is a finding.
6. Demonstrate who initiated and approved high-value payments
What investors are testing: Whether spending authority is governed—or whether one person can move treasury funds without meaningful review.
What a diligence-ready answer looks like: The company has a written approval policy explaining:
who may request a payment;
who verifies that the obligation or milestone is valid;
who may approve and execute the transfer;
which thresholds require additional review or signers;
how exceptions and urgent payments are handled;
how conflicts and related-party transactions are escalated.
For significant historical payments, the record contains the business decision—the request, review, and confirmation that the payment was due—not merely the multisig signature set.
A multisignature wallet proves that particular keys authorized an on-chain action. It does not necessarily explain who requested the payment, what was delivered, or why the company approved it.
How to close the gap: Document the company's actual current process and give the policy an effective date. Do not present a newly written policy as if it governed earlier transactions.
Compare the current process with historical payment activity and record where practice differed. When a major payment lacks a traceable request or review, reconstruct only what can be supported by existing messages, invoices, agreements, and participants. Preserve the result in one place and label any remaining uncertainty honestly.
Going forward, capture the requester, reviewer, approver, and delivery confirmation when the payment occurs. That record is inexpensive to create in real time and difficult to reconstruct months later.
7. Reconcile the payout ledger with the blockchain and financial records
What investors are testing: Whether the company's books and its on-chain activity describe the same business.
What a diligence-ready answer looks like: A reconciled schedule in which every material payment contains:
transaction date;
asset and token amount;
fiat value and the valuation methodology used;
recipient;
business purpose and category;
supporting-document reference;
initiator and approver;
transaction hash;
accounting-entry reference.
From a financial record, you can reach the underlying payment and transaction hash. From a hash, you can reach the supporting documents and accounting treatment. Both directions, without searching manually across several systems.
How to close the gap: This is where the previous six steps come together. Build the reconciled schedule with your accountant. Agree on a defensible valuation methodology and apply it consistently in accordance with the company's accounting policy. Investigate every material transaction present on-chain but absent from the financial records—and every accounting entry that cannot be connected to an underlying transaction.
Do not force unmatched items into convenient categories. Every difference needs to be investigated, explained, and documented.
The pattern behind all seven
Each item follows the same pattern: evidence is inexpensive to capture when a payment is made and expensive to reconstruct afterward.
A treasury operated through ad hoc transfers accumulates diligence debt with every payout. A treasury in which recipient onboarding, documentation, purpose, approval, execution, and recordkeeping happen as one workflow accumulates a diligence record instead.
That is the model Pvium is built around.
Pvium is a non-custodial coordination and compliance layer over your existing treasury wallets—it never holds your funds—and it anchors each payout record to a payee rather than a bare wallet address.
The recipient's identity profile, wallet association, verification status, applicable tax documentation, and screening results remain connected. The payment's purpose and approval are captured during the payout workflow, and the transaction details complete the record.
Pvium does not replace counsel, determine whether an agreement adequately assigns intellectual property, or reconcile your complete financial statements. It does make much of the underlying payout evidence easier to preserve when money moves instead of reconstructing it during a fundraise.
The blockchain already proves that money moved. Pvium preserves the identity, purpose, documentation, approval, and transaction history that explain why.
See how Pvium makes non-custodial stablecoin payouts diligence-ready at Pvium.com.