In this article
A cross-border payment is rarely just a wire transfer. By the time funds leave the sender's bank, they have triggered currency conversion decisions, correspondent-bank routing choices, compliance screening queues, and — if multiple parties are waiting for their share at the other end — a disbursement workflow that can stretch over days. Every one of those steps generates, or should generate, a paper trail. When that trail is thin, incomplete, or assembled from memory after the fact, the accounting entries become guesswork, the tax position becomes defensible only with effort, and an auditor's questions become very expensive to answer.
This article is a practical field guide for the professionals who sit at the center of these transactions: settlement agents, closing attorneys, escrow officers, title companies, OTC desks, and the accountants who serve them. It covers what to collect, why each document matters, how to handle the foreign exchange layer, and what the accounting entries look like at each stage. It also explains how the structure of the payout itself — whether one party receives the full amount or multiple parties receive simultaneous shares — changes the documentation burden in ways that are easy to underestimate.
Why Cross-Border Payments Create a Distinct Documentation Problem
Cross-border payments move through a series of coordinated steps involving messaging networks, correspondent banks, and settlement systems. While the experience may feel simple from the sender's side, multiple institutions participate before funds reach the recipient — typically, the payment message travels through a messaging network such as SWIFT, intermediary banks route the funds, and the recipient's bank credits the account only once settlement is complete.
Each of those handoffs is a potential documentation gap. The sender has a SWIFT confirmation. The correspondent bank has its own internal log. The receiving bank has a credit advice. None of these documents automatically finds its way into a single, coherent accounting file unless someone at each end deliberately assembles it.
For domestic transactions, the gap is small — a single bank confirmation typically tells you almost everything your accountant needs. For cross-border transactions, the gap is wide, because:
- The currency conversion introduces a second event, with its own rate, its own timestamp, and its own gain-or-loss implication.
- The multi-institution routing means partial delays and fees can be stripped at any intermediate hop, causing the received amount to differ from the sent amount in ways that must be explained.
- The multi-party disbursement — where one incoming sum is allocated to several payees — multiplies the number of ledger entries that need to be tied back to a single source event.
- The jurisdictional overlap means each party is subject to its own local reporting rules, which may not align with each other.
Over half of finance teams surveyed in one major industry report spent more time on international business in 2025 than in previous years, and 43% said they are dealing with more compliance issues than ever before. For settlement professionals, that pressure is real and growing.
The Core Document Set: What Every Cross-Border File Needs
Before addressing the nuances of specific transaction types, it helps to establish the baseline. A properly documented cross-border payment file should contain, at minimum, the following items.
1. The Instructing Contract or Agreement
Every payment has a legal basis. That basis — whether it is a purchase agreement, a service contract, a commission agreement, a distribution waterfall schedule, or a fee letter — is the first document in the file. It establishes the obligation, the currency in which the obligation is denominated, the parties involved, and the amounts each party is entitled to receive.
Without the instructing document, every downstream accounting entry is floating. The accountant must justify the payment from evidence; the auditor must trace the payment to a business purpose. Supply that context at the start, not under pressure.
2. Wire Instructions and Pre-Closing Confirmation
Most lenders and title companies require the wire confirmation receipt, bank statement showing the outgoing debit, and escrow confirmation showing the incoming credit. International wires also usually require the SWIFT MT103 document and currency-conversion receipt if the funds were converted into USD.
The SWIFT MT103 is the single most important wire-level document for a cross-border file. It is the standardized message that identifies the ordering institution, the beneficiary institution, the value date, the currency, the amount, and the reference codes used to trace the payment. Collect it from the sending bank immediately after transmission — it is not always automatically provided, and it becomes difficult to retrieve once the transaction ages in the bank's systems.
ISO 20022, the global standard now mandated across the SWIFT network, supports richer payment data, including invoice and remittance details, enhanced transparency for compliance and fraud monitoring, and improved reconciliation and automation across the payment chain — and all financial institutions connected to SWIFT must send cross-border messages in this format. This means that well-structured ISO 20022 messages now carry far more embedded documentation than older MT-format messages did. Instruct your bank to provide the structured data extract alongside the human-readable confirmation.
3. Foreign Exchange Documentation
If the payment crosses currency boundaries — USD sent, AUD received; AUD sent, USD received — the foreign exchange event is a separate accounting transaction from the payment itself. It needs its own documentation.
At the date a foreign currency transaction occurs, each asset, liability, revenue, expense, gain, or loss arising from the transaction is recorded in the functional currency of the recording entity using the exchange rate in effect at that date.
That means the file needs to capture:
- The spot rate at the moment of conversion (not a rate rounded to the prior business day, not a rate from a public data source — the actual rate at which the conversion was executed)
- The spread or markup applied by the bank or FX provider, which represents an implicit cost even when it is not itemized as a fee
- The value date (the date on which funds actually move, not the booking date)
- The converted amount in the receiving currency
IAS 21 requires initial recognition at the spot rate and remeasurement of monetary items at each subsequent reporting date. Under US GAAP, ASC 830 requires all monetary transactions to be re-measured to the month-end accounting exchange rate. In practice, this means a payment initiated late in an accounting period — where the trade date and the value date straddle a month-end — may need two separate rate references: one for initial recognition, one for period-end remeasurement. The documentation must support both.
Practical example: A US-based seller receives USD 850,000 (approximately AUD 1,295,000 at a mid-market rate of 0.6562 at time of writing) from a buyer in Australia. The buyer converts AUD to USD through their bank. The seller's accountant needs the USD amount received, the AUD amount debited from the buyer, and the exchange rate applied by the bank. If that rate differs from the spot rate on the contract date, a foreign exchange gain or loss must be recognized. The sale proceeds, the FX gain or loss, and the payment cost are three separate line items — not one.
4. Bank Debit and Credit Advices
Collect the debit advice from the sending bank (confirming funds left the account) and the credit advice from the receiving bank (confirming funds arrived). These are not the same document as the SWIFT MT103. They are the bank's confirmation to their own customer that the movement occurred. Both are needed to close the loop — the MT103 proves the payment was dispatched; the credit advice proves it landed.
Keep transaction records, due diligence files, and monitoring logs for a minimum of five years as required by most jurisdictions. Document decision-making processes for risk assessments, transaction approvals, and escalation protocols.
5. AML Screening and Compliance Records
Large cross-border transfers frequently move through OFAC review, Bank Secrecy Act compliance screening, anti-money-laundering verification, and correspondent-bank review before receiving parties can access usable funds — and these reviews can delay international wires by roughly 3–7 business days even when funds are fully legitimate and properly documented.
The compliance screening that your institution or your counterpart's institution performed is part of the audit trail. Retain a record of any compliance hold, the reason for it, the information provided to resolve it, and the date on which the hold was lifted. If a regulator later asks whether the payment was reviewed, a documented resolution — not a verbal recollection — is the only adequate answer.
The Multi-Party Disbursement Layer
One of the most underappreciated documentation challenges in cross-border transactions is the multi-party close: a single incoming payment that must be distributed simultaneously or near-simultaneously to several payees, each in potentially different jurisdictions, each booking the receipt under their own local accounting rules.
Title companies and settlement agents routinely disburse funds during a real estate closing — paying county recording fees, transfer taxes, and inspection costs on behalf of the buyer or seller. These amounts flow through the settlement agent's accounts but belong to the parties in the transaction, not the agent.
The moment more than one party is waiting for funds from a single incoming wire, the accounting documentation problem multiplies. Consider a commercial real estate closing involving a cross-border buyer:
- The seller receives net proceeds after payoff
- The listing broker receives a commission
- The buyer's broker receives a co-commission
- The closing attorney receives a closing fee
- The title company receives an underwriting premium
- The lender receives a payoff balance
Each of these is a separate disbursement, each must be tied back to the same source payment, and each recipient will book the receipt as income (or partial income) under their own local accounting framework. Platform accounting documentation reflects this complexity by separating user shares, commissions, payment fees, taxes, payouts, refunds, and other balance movements — and split payment reconciliation is the process of verifying every financial obligation created when one incoming payment is divided across multiple parties, accounts, or purposes.
The Sequential vs. Simultaneous Problem
Traditional wire-based disbursement is sequential. The settlement agent receives the full incoming wire, then issues separate outgoing wires to each party in sequence. Each outgoing wire has its own timestamp, its own confirmation number, and potentially its own FX conversion if the recipient is in a different country. This means:
- The seller's net proceeds land at 10:47 AM on day one
- The broker's commission clears at 2:15 PM on day one
- The title premium reaches the underwriter at 9:30 AM on day two (because the wire was initiated after 4 PM cut-off)
Now multiply this across jurisdictions. The seller is in the US. The listing broker is in the US. The buyer's broker is in Australia. The attorney is in the US. The FX rate applicable to the Australian broker's AUD receipt is the rate at 9:30 AM on day two — which is different from the rate on the contract date, different from the rate when the buyer's funds left Australia, and different from the rate the seller's accountant used to record the transaction.
For each party, the documentation bundle is different. For the Australian broker, the file needs the USD disbursement amount, the AUD credit amount, the exchange rate applied, and the value date — all referenced back to the parent closing transaction.
Reconciliation must verify the total and each obligation within it. Every obligation needs the correct recipient, allocation rule, settlement status, payout destination, ledger treatment, and link to its source transaction.
How Onchain Routing Changes the Documentation Structure
The operational and documentary complexity described above is a function of the infrastructure being used, not an inherent property of multi-party disbursement. When a payment is routed onchain — where the logic for splitting the total amount among parties is encoded into the routing layer before the transaction executes — the sequential problem disappears.
Smart contracts can route, split, or release funds based on verified conditions, matching invoice and delivery data, milestone completions, or multiparty approvals, so execution and approval are captured in one step. For documentation purposes, this matters enormously.
When shaka.deal is used to route a cross-border payment, the distribution logic — which party receives what share of the incoming amount — is defined before the transaction occurs. The total amount enters the protocol, and all parties receive their preset shares in the same Ethereum transaction. There is one transaction hash. There is one block timestamp. Every disbursement happened at the exact same moment, with the exact same block-level FX reference point, under the exact same settlement event.
Every state change is cryptographically chained to the prior one, so auditors can look at Merkle proofs, trace value flows, and confirm completeness without assembling disparate threads.
This translates directly into a simpler, stronger accounting file:
- One timestamp for all parties. The Australian broker and the US seller received their disbursements at the same block. There is no question of which FX rate applies to which disbursement — the reference event is singular.
- One immutable record. Finality on the blockchain is the guarantee that past transactions cannot be altered, reversed, or canceled — providing absolute certainty to users, merchants, and smart contracts that a transaction is permanently settled and digital assets are secure. That permanence is exactly what an auditor looks for.
- One source of truth. Onchain settlement replaces the multi-day, intermediary-heavy process of moving money and assets with a single blockchain transaction that transfers value and records final ownership at the same time. Settlement is the moment ownership legally and finally changes hands — and onchain settlement makes the blockchain ledger the authoritative record of that change, rather than a downstream copy of it.
For settlement agents and closing attorneys, the practical benefit is a documentation file that closes cleanly. Instead of assembling five separate wire confirmations from five separate banks over two days, the file contains one transaction record from the Ethereum network, with the distribution to each party readable from the same block explorer.
Building the Accounting Entries: A Step-by-Step Walkthrough
Let us work through a concrete example using the scenario of a cross-border commercial deal.
Scenario: A buyer based in Australia wires USD 1,200,000 (approximately AUD 1,829,000) to close on a US commercial property. The settlement agent coordinates disbursements to four parties:
| Payee | Disbursement | Share of the incoming wire |
|---|---|---|
| Seller | USD 960,000 | 80% |
| Listing broker | USD 120,000 | 10% |
| Buyer's broker (Australian) | USD 60,000 (approx. AUD 91,450) | 5% |
| Closing attorney | USD 60,000 | 5% |
| Total | USD 1,200,000 | 100% |
Step 1: Record the Incoming Payment
The settlement agent's trust account receives USD 1,200,000. The journal entry:
Debit: Trust Cash Account — USD 1,200,000 Credit: Funds Held in Trust (Liability) — USD 1,200,000
This is not income for the settlement agent. The liability account tracks the obligation to disburse.
Step 2: Record Each Disbursement
As each party is paid out, the liability is reduced:
Debit: Funds Held in Trust — USD 960,000 Credit: Cash (Outgoing Wire to Seller) — USD 960,000
Repeated for each payee. The total debits to the trust liability account must equal USD 1,200,000 at the end of the process.
For each disbursement, the file must contain the corresponding wire confirmation (or onchain transaction reference), the recipient's name and account, and the amount.
Step 3: Handle the FX Layer for the Australian Broker
The Australian broker receives USD 60,000 but books income in AUD. Their accounting file needs:
- The USD amount received (USD 60,000)
- The exchange rate at the value date of their receipt
- The AUD equivalent booked in their general ledger
- Any FX gain or loss if the rate differs from the rate used in the underlying contract
Any transaction not in the company's functional currency must be recorded in that currency, and gains and losses from changes in the exchange rate are recognized directly in net income.
If the broker contracted to receive AUD 91,450 but the USD 60,000 converts to AUD 92,100 on the value date, the broker has a realized foreign exchange gain of AUD 650, which must be recognized in income, separately from the commission income itself.
Step 4: Period-End Remeasurement (If Applicable)
If the transaction straddles a reporting period — the contract was signed in June, the payment lands in July — any USD-denominated receivable that existed at June 30 must be re-measured at the June 30 closing rate. Subsequent remeasurements at each reporting period use the current exchange rates, with gains/losses impacting earnings. The documentation file needs both the transaction-date rate and the period-end rate, along with the computed adjustment.
Jurisdiction-Specific Reporting: What to Overlay
The core documentation described above applies universally. On top of it, each jurisdiction where a party is tax-resident imposes its own overlay.
United States: US-based parties must adhere to OFAC sanctions screening, meet FinCEN requirements for anti-money-laundering compliance, and ensure proper IRS reporting for international transactions. For real estate, FIRPTA withholding rules apply whenever a foreign person disposes of a US real property interest — the closing attorney or settlement agent is typically the withholding agent, and the documentation of that withholding calculation and remittance is part of the closing file.
Australia: The ATO requires that foreign currency gains and losses on cross-border transactions be reported in Australian dollars, translated at the applicable rate, and disclosed in the business income tax return. A broker receiving USD commissions must document not just the USD amount but the AUD equivalent used for reporting, and must retain that documentation for five years.
European Union: The EU's Anti-Money Laundering Authority enforces the Travel Rule, requiring detailed sender/receiver data for cross-border transfers. Parties in EU jurisdictions must ensure their documentation reflects the originator and beneficiary information required under the Travel Rule — not just what arrived in the bank, but the full structured data trail.
Companies must track both domestic reporting thresholds and international payment documentation requirements to ensure comprehensive compliance.
The Reconciliation Discipline: Closing the Loop
A documentation file is complete only when the total of all received amounts — across all parties — can be reconciled back to the single source payment, after accounting for any FX conversion and any legitimate deductions.
Split payment implementation guidance warns that split amounts can become impossible to reconcile individually when references are missing. Each child record should retain the parent transaction ID along with its own obligation type and status — this structure supports reconciliation without losing the relationship between one customer action and multiple financial outcomes.
For onchain transactions routed through shaka.deal, the parent transaction hash serves as the universal reference that every party can independently verify. Each party's accounting department can query the same transaction, confirm the same block timestamp, and derive their own functional-currency equivalent using the same reference rate. The reconciliation starts from a shared, immutable source rather than from a patchwork of individual bank statements that may not agree in their timestamps or reference numbers.
For traditional wire-based transactions, impose a manual discipline:
- Assign a deal reference numberAssign it at the start, and include it in every wire instruction as the payment reference field.
- Require it on every confirmationRequire every receiving bank confirmation to include that reference number.
- Build a reconciliation ledgerMap each outgoing disbursement to the parent incoming receipt, noting the amount, the value date, and the confirmation number.
- Resolve any discrepanciesAmounts short-shipped by correspondent banks, FX conversion differences: resolve them before closing the file, not months later.
Common Documentation Failures and How to Prevent Them
Missing the FX conversion receipt. The SWIFT MT103 often does not include the exchange rate applied. If your bank converted currency before transmitting, request a separate foreign exchange confirmation or dealing ticket that shows the rate, the spread, and the converted amount. This is the document your accountant needs to book the gain or loss.
Using the wrong date for FX recognition. Transactions denominated in foreign currencies are translated into the functional currency using the spot exchange rate on the transaction date. The transaction date is not when you signed the contract, not when your client wired the money, and not when you received the bank statement — it is the value date on which the currency conversion occurred. Use the rate for that specific date.
Failing to retain the disbursement authorization. The written instruction that authorizes each disbursement — signed by the appropriate party, referencing the amounts, the payees, and the bank details — is a legal document and an accounting record. It is the connection between the trust liability and the outgoing payment.
Assembling the file retroactively. Running smooth, compliant payout cycles requires a mix of stringent risk management, robust internal controls, and the right technology. Cross-border activities are much easier to manage with organized, repeatable processes. A documentation checklist completed at the time of each transaction is faster and more reliable than reconstruction from memory. Build the checklist into your closing workflow, not your post-closing remediation.
Losing the parent-child link in multi-party distributions. Every disbursement sub-entry must reference the source payment. If an auditor presents the Australian broker's AUD receipt and asks where it came from, the answer should be traceable through your records in under a minute: the broker received USD 60,000 from a wire disbursed by the settlement agent on [date], drawn from the incoming wire from the buyer's bank on [date], reference number [MT103 ref], which was the settlement payment for [deal reference].
What a Complete File Looks Like
For any professional managing the documentation for a cross-border payment, the completed file should contain:
- The instructing document (purchase agreement, contract, commission letter, distribution schedule)
- The incoming payment confirmation (SWIFT MT103 or onchain transaction hash, with value date and amount)
- The FX dealing ticket or bank conversion confirmation (rate, value date, converted amount, spread)
- The debit advice from the sending bank and credit advice from the receiving bank
- The disbursement authorization (signed instruction covering all payees and amounts)
- Individual outgoing wire confirmations or onchain sub-receipts for each payee
- The period-end remeasurement calculation if any monetary item was open at a reporting date
- The compliance documentation for any screening hold, resolution, or withholding calculation
When shaka.deal routes the disbursement, items five and six collapse into a single transaction record — one hash, one block timestamp, all payees confirmed simultaneously. The accountant's work is shorter. The auditor's verification is faster. The file closes with fewer moving parts.
Final Thought: Documentation Is the Deal
Settlement professionals understand that the closing is not complete when the keys change hands or when the wire clears — it is complete when the file is closed and defensible. The same principle applies to the accounting file for a cross-border payment. The payment may move in seconds. The documentation obligation it creates lasts for years.
The growing use of onchain payment routing is shifting the burden of proof from a manual assembly job — collecting bank confirmations from multiple institutions across multiple time zones — to a verification exercise against a single, immutable ledger. That shift makes the lives of settlement agents, closing attorneys, and their accountants meaningfully easier. But the underlying discipline remains the same: every dollar that crosses a border needs a paper trail that begins with the obligation that created it and ends with the receipt that extinguished it.
Build that trail in real time, store it systematically, and make it retrievable on demand. That is what cross-border payment documentation means in practice — and it is the standard every professional in this space should be working toward.
