The documented record produced for a counterparty across an instruction: contract, AML/KYC record, payment confirmation, Allocation Record, vault placement or delivery documentation, and the instruction log. Where the funds originate in digital assets, two further records attach to that set: a screening record and a conversion record. Both are produced by the licensed digital-asset platform that performs the conversion, under its own licence, before the seller sees anything. What binds them to the rest of the file is the order reference the payment carries.
The two records the funding leg adds
A bank-funded instruction is documented end to end by one party. A digital-asset funding leg is not: its first two events happen inside a second compliance perimeter, and the records they generate stay there.
| Record | Produced by | What it evidences | Form the counterparty holds |
|---|---|---|---|
| Screening record | the platform, under its own licence | that the address, the transfer and its on-chain history were assessed before conversion | confirmation that screening cleared; the wallet-level analytics remain with the platform |
| Conversion record | the platform | the sale of the digital assets and the national currency remitted against them | the record the platform issues to its own customer |
| Payment confirmation | the seller | receipt of the settlement against the stated order reference | issued as part of the Evidence Set |
| AML/KYC record | the seller | a dated verified-counterparty decision carrying an internal reference | verified status, date and reference; the screening report itself stays internal |
The first two rows are not seller artefacts and cannot be reissued as such. The counterparty is a customer of both parties and is therefore the only party positioned to hold the complete file.
Where the boundary sits
The platform operates the payment gateway, screens the transfer, converts, and remits the proceeds. Golden Ark Reserve is settled in national currency, holds no digital assets, and issues no token or claim on metal. Two consequences follow for the file. Wallet-level analytics are held under the platform’s licence and do not cross the boundary. The Allocation Record and everything downstream of it exists only on the seller’s side, because only the seller allocates bars. A request addressed to the wrong side of that line returns nothing — not because the record is withheld, but because it was never generated there.
How the set assembles, in order
- Counterparty verification. Onboarding produces a documented counterparty file and a dated eligibility decision carrying an internal reference. It precedes contractual binding and precedes any order reference.
- Contract and pro forma. The sale agreement fixes asset, quantity, delivery structure and settlement condition. The pro forma invoice for advance payment states the amount and the order reference. From this point the reference exists and every later record can carry it.
- Screening. The platform assesses the address, the transaction and its on-chain history. Cleared screening is the condition of the conversion, not of the allocation — the two gates sit on opposite sides of the boundary and are cleared by different parties.
- Conversion. The platform sells the assets and produces the record of that event. This is an off-ramp event: assets out, national currency in, priced at the moment the platform executes rather than at the moment the quote was issued.
- Settlement and payment confirmation. The proceeds reach the seller’s bank carrying the order reference. The seller books the credit against that instruction and issues the payment confirmation. An arriving amount that cannot be matched at this point is an unattributed credit, and no downstream document repairs it.
- Allocation. Specific bars are allocated by serial number, weight, fineness, producer and location, recorded in the Allocation Record. The commercial invoice is issued against those actual bars, not against the pro forma figure.
- Placement or delivery. Vault placement documentation, or delivery documentation where the counterparty takes release.
- Instruction log. The sequence of events with their times. It is the item that makes the set reconstructable by someone who was not present for any of it.
What the counterparty receives, and what stays internal
Screening produces two internal documents and one disclosable fact. The platform’s analytics on the origin of the assets sit under its licence; the seller’s sanctions and adverse-media output sits in its counterparty file. What is disclosed on the seller’s side is the verified status, its date and an internal reference — not the report behind it. The conversion record is obtained from the platform by its own customer. Everything from payment confirmation onward is issued by the seller.
The consequence surfaces at the point where the compliance file is assembled: a file built only from what the seller issues is complete on the metal and silent on the origin of the funds. That is a property of the structure, not an omission in the documentation.
What a reviewer asks for, and which record answers it
| Question | Record | Held by |
|---|---|---|
| Where did the money come from? | source-of-funds file, plus the platform’s screening and conversion records | counterparty and platform |
| Was the payer verified? | dated verified-counterparty decision with internal reference | seller |
| Was the transfer screened before conversion? | screening record | platform |
| What arrived, and against what instruction? | payment confirmation against the order reference | seller |
| What was bought? | Allocation Record — serial number, weight, fineness, producer, location | seller |
| Where is it, and under whose control? | vault placement documentation or delivery documentation | seller and the vault operator |
| In what order did this happen? | instruction log | seller |
Where the set breaks
The reference is lost. If the settlement arrives without the order reference, the credit cannot be attributed at receipt, and the link to the instruction has to be rebuilt afterwards from amounts and dates. Amounts do not help: the figure sent in digital assets and the figure received in national currency are different numbers with a conversion between them, and they never reconcile arithmetically.
The request goes to the wrong party. A demand on the seller for wallet-level analytics has no answer on that side of the boundary. A demand on the platform for the Allocation Record has no answer on its side either. Both look like refusals and are neither.
There is no provider at the far end. A transfer between two regulated providers carries originator and beneficiary information; a transfer from a self-hosted wallet does not, and there is no message to obtain. FATF’s Targeted Report on Stablecoins and Unhosted Wallets: Peer-to-Peer Transactions, published 3 March 2026, treats exactly this case — a transfer with no obliged intermediary in it — as the structural gap in the regime. Where a transfer originates that way, the assessment rests on the platform’s analytics and on the counterparty’s own record of how the assets were acquired.
Timing is mistaken for inconsistency. Quote, conversion, settlement and allocation happen at four different moments, and the documents state different figures at each while being correct at each. What reconciles them is the reference and the log, not the arithmetic.
How it differs from the documents it is taken for
Proof of funds evidences that a payer holds the money; source of funds evidences where the money came from. The Evidence Set is neither: it records what happened to one instruction. An attestation is an independent party’s report on what it observed at a stated moment, and an audit opinion addresses the fairness of financial statements; the Evidence Set is a transaction file issued by the parties themselves and carries no opinion. An assay certificate or bar list states attributes of metal; the Allocation Record inside the set attributes those specific bars to a named counterparty.
Two structured records that do not share an identifier
Both halves of a digital-asset funding leg became machine-structured within twelve months of each other, and the two structures do not meet.
On the national-currency side, Swift’s coexistence period between MT and ISO 20022 ended on 22 November 2025, and cross-border customer credit transfers now travel as pacs.008 rather than MT103. Two fields matter here. End-to-end identification is supplied by the payer and, under the CBPR+ usage rules, passes unchanged along the chain and is reported to the creditor. The UETR identifies the transaction uniquely for its whole life. Between them, the order reference no longer depends on surviving as free text in a narrative field that someone retypes — it has a field of its own, and the same value can appear on the settlement instruction and on the recipient’s statement. From November 2026 the same programme stops accepting fully unstructured postal addresses in those messages, which raises the quality of the party data travelling with the credit again.
On the digital-asset side the equivalent structure is travel-rule data — originator and beneficiary information exchanged between regulated providers — and its coverage is uneven in a way the payment side is not. FATF’s seventh targeted update, published 16 July 2026, records that 83% of surveyed jurisdictions (91 of 109) now have travel-rule legislation in force, up from 73% a year earlier, with a further 11 implementing; and that close to half of the jurisdictions that have legislated have taken no supervisory or enforcement action. Legislated is not the same as exchanged. Whether a particular transfer generated a travel-rule record depends on where both providers sit, and on whether a provider sits at the far end at all.
Neither record references the other. The travel-rule message identifies the parties to a transfer of digital assets; the pacs.008 identifies the parties to a transfer of national currency; the conversion between them is an event inside the platform, and no identifier crosses. The only value that can appear in both halves of the file is the order reference, and it appears there because the parties put it there — the payer states it, the platform carries it into the settlement, the seller books the credit against it. No infrastructure supplies it. A file whose two halves share no value is not visibly incomplete: every document is present and internally correct. It is unreconcilable, and that is normally discovered during a review, long after the point at which the reference could have been stated.
The control gates that produce these records, and the retention framework they sit in, are set out in Compliance and Legal Architecture. The funding route itself is at Buy Gold with Crypto; the conversion and settlement steps are defined at payment gateway and off-ramp, and the remaining defined terms are held in the glossary.