Recording a crypto transfer when there is no invoice.
A crypto transfer can have a transaction reference and explorer page without a conventional invoice. The operational record still needs the entity, business context and evidence behind that explanation. Technical activity and business purpose are different claims.
Written by the Fundamental View editorial team. Updated 28 October 2026. Examples are deliberately fictional and are not blockchain proof, accounting treatment or tax advice.
Separate the movement from its purpose
An on-chain entry describes activity between addresses. It does not by itself establish the legal identity behind an address or explain whether a movement relates to a purchase, reimbursement or internal transfer. Start with available information and label what remains unresolved. A missing document should become an explicit exception, not an empty field another person assumes was checked.
Record enough detail to find the same transaction
A useful record includes network, full transaction reference, token or asset identifier, amount and timestamp with time zone. Keep the explorer link with the reference. If one transaction contains several relevant movements, identify the particular movement being recorded. Preserve the original denomination; reporting-currency conversion is a separate step with its own rate source, date and convention.
| Field | Illustrative value | Why it remains necessary |
|---|---|---|
| Record identifier | EXAMPLE-001 | Connects operational context and evidence |
| Entity | Example Holding A | Defines the structure whose record is affected |
| Network | Recorded from source | A reference without network context is incomplete |
| Transaction reference | Full verified reference, not shortened label | Allows exact retrieval and duplicate checking |
| Asset and amount | Recorded in original denomination | Prevents a converted value replacing the source amount |
| Business purpose | Pending confirmation | Keeps an unsupported explanation from becoming fact |
| Evidence | Explorer reference and related correspondence | Combines technical and operational sources |
| Review status | Open: supporting context required | Prevents technical success being mistaken for full review |
Add supporting context
Depending on the operation, context may come from an agreement, approval, correspondence, custodian statement or another source record. Link that material to the same identifier used in the register. A screenshot can support review, but should not replace the searchable transaction reference and network. Retain enough provenance to explain where the file came from and when it was collected.
Review controls specific to crypto records
- Network match: confirm the explorer and record refer to the same network.
- Full identifier: compare the complete reference, not a shortened display value.
- Relevant movement: identify the exact output or event where a transaction contains several.
- Duplicate check: search the register for the same network and transaction reference.
- Original denomination: retain token and amount before any reporting conversion.
- Business context: link separate evidence for purpose and entity attribution.
What the record still does not prove
A valid explorer result does not establish beneficial ownership, valuation, accounting classification, tax treatment or the legitimacy of a transaction. A confirmed timestamp does not confirm the business purpose. Keep these professional judgements with the responsible people and avoid collapsing them into one “verified” checkbox.
How Fundamental View handles the record
Fundamental View crypto records keep TXID, token and network with a duplicate check, alongside entity, currency and linked documents. A person confirms fields before they are saved. This supports operational traceability; it does not replace professional review or prove every off-chain fact. Record unresolved attribution separately from the observed on-chain movement.
Related guides
- Define transaction and review fields
- Place digital assets in the wider register
- Run the evidence exception checklist
- Keep documents connected to records
Discuss your workflow
Describe the record-keeping problem you want to solve. Please do not include confidential financial information or documents in the enquiry.
Discuss implementation