‘Pay USD 100,000’ does not answer which account must receive what amount, which banks may deduct charges, or who carries the exchange difference when the payment and invoice currencies diverge.
The buyer sends the invoice amount and its bank confirms a successful transfer. The supplier receives less. The remittance message shows fees, but it is unclear whether the deduction came from the sending bank, an intermediary or the receiving bank; meanwhile the supplier converted the funds at a different rate and books a shortfall. The dispute is not solved by writing ‘all fees for buyer’. The contract and payment instruction need separate fields for currency, charge allocation, intermediaries, conversion, reconciliation and exception handling.
1. Define the contract amount, transfer amount and credited amount separately
Record the contract and invoice currency first. Then identify the debit account currency, instructed transfer currency and beneficiary account currency. A single payment can involve conversion before dispatch, within a bank chain or on receipt. Each conversion can use a different rate, spread, time and fee; do not label an unexplained difference simply as a bank charge.
Use three amount fields: the contractual amount due, the amount instructed into the payment rail and the amount actually credited to the verified beneficiary account. Add the invoice balance after credit and any agreed tolerance. ‘Net receipt’ must identify which of those values it means and whether receiving-bank charges, taxes or conversion differences sit inside or outside it.
Do not promise that selecting a particular fee instruction forces every intermediary outcome. Correspondent institutions may participate when the sending and receiving banks lack a direct relationship, and actual routing can depend on the institutions, currency and payment infrastructure. Ask both banks what they can control and what evidence they can provide for the proposed route.
| Field | Evidence source | Do not assume |
|---|---|---|
| Contract amount/currency | Signed contract, variation and invoice | Same as debit or beneficiary account currency |
| Transfer instruction | Approved bank instruction and payment record | Same as amount ultimately credited |
| Conversion event | Bank quotation/confirmation with time and currency pair | Public reference rate equals executable customer rate |
| Credited amount | Beneficiary bank statement/advice | Shortfall cause from amount alone |
| Open invoice balance | Agreed reconciliation record | Automatic debt, waiver, credit or set-off |
2. Map the payment chain and charge responsibility before the due date
Ask the sending and receiving banks to map the expected route as far as they can: payment rail/message type, sending bank, possible correspondents, receiving bank, beneficiary account and currency. Record SWIFT/BIC, clearing or routing details only in the organisation's protected payment system and verify changes through the independent callback control; do not publish sensitive account data in the procurement file.
Separate sending-bank charges, intermediary deductions, receiving-bank charges, conversion spread, repair/investigation charges and return-payment costs. A contractual allocation between buyer and seller does not bind a third-party bank. It may instead create a reimbursement or gross-up obligation between the parties, whose wording and legality require professional review.
ISO 20022 payment messages can carry structured charge and party information, but implementation varies by market and bank. The business team should request the bank's actual field definitions and post-payment evidence rather than treating a code label as a universal commercial result.
| Possible cost | Who imposes it | Contract question | Evidence after payment |
|---|---|---|---|
| Sender fee | Ordering customer's bank | Inside or outside invoice amount? | Debit advice/fee schedule |
| Intermediary deduction | Correspondent/intermediary | Who carries an uncontrollable deduction? | Payment trace/message where available |
| Receiver fee | Beneficiary's bank | May it be deducted from credit? | Credit advice/account statement |
| FX conversion | Bank/provider performing conversion | Which party chooses timing and accepts spread? | Executed rate and transaction confirmation |
| Repair/return | One or more banks | Who bears errors in whose instruction? | Case reference and itemised bank evidence |
3. Replace ‘exchange rate on payment date’ with an auditable event
If conversion is contractually required, define the currency pair, amount basis, named source or provider, rate type, observation or execution timestamp and time zone, business-day convention, rounding precision, unavailable-source fallback and who executes. A central-bank or IMF reference rate may be useful for analysis but may not be an executable commercial rate.
Match the conversion trigger to the payment milestone. Deposit, progress and final payments may fall on different dates, so a single project rate can shift risk substantially. If the parties choose a fixed rate, band, adjustment formula or hedging route, authorised treasury and legal teams should document cost, authority and accounting treatment; procurement should not improvise a financial product.
Keep price escalation, exchange movement and bank fees as separate variables. A supplier's material-price change is not an FX calculation, and a lower credited amount may arise without any exchange at all. Reconcile each difference against source evidence before issuing a debit note, credit note or payment demand.
| Field | Controlled entry | Fallback question |
|---|---|---|
| Currency pair/direction | For example, units of quote currency per base currency | Can users invert it consistently? |
| Amount basis | Invoice, milestone, transfer or credited amount | What happens after a partial payment? |
| Rate event | Named executable or reference source and timestamp | What if unavailable or a non-business day? |
| Spread/fees | Included, separately quoted or unknown | How is the difference evidenced? |
| Rounding | Precision, level and residual treatment | Who approves a residual balance? |
4. Reconcile the payment without normalising unexplained shortfalls
Before release, verify beneficiary identity and instructions through the controlled process, confirm invoice and milestone approval, and capture the bank's payment reference. After release, compare debit evidence, transfer message or trace where available, beneficiary credit evidence and the invoice ledger. Never use a beneficiary bank screenshot alone to authenticate changed payment instructions.
Classify any difference: sender fee, intermediary deduction, receiver fee, FX amount, rounding, tax/withholding, erroneous instruction, return, unexplained or disputed. Do not automatically send a second payment; first verify that the first transfer is not pending, held or recoverable and repeat the fraud, sanctions and authority controls for any revised route.
Close only through an authorised reconciliation: balance paid, documented reimbursement, agreed credit, lawful withholding, corrected invoice, or formally open dispute. Retain bank case references and itemised evidence while protecting sensitive data. Update the next payment instruction only after the root cause and authorised control change are recorded.
FAQ
Do OUR, SHA or BEN guarantee who ultimately bears every fee?
No universal outcome should be promised. Meanings and support vary by payment type and bank, and intermediary or receiving-bank treatment may differ. Obtain written route-specific guidance from both banks.
Can the buyer simply add an estimated fee to the transfer?
Only under an agreed and bank-confirmed method. An estimate can overpay or still leave a shortfall, and it does not explain how the invoice is reconciled.
Which exchange rate should a window contract use?
There is no universal best rate. The parties need an auditable source or execution event, time, currency direction, spread/fee treatment, fallback and professional review.
Is a central-bank reference rate the rate a bank must execute?
Generally no. A reference rate is not necessarily a customer-dealing rate and may omit spreads, timing and transaction costs.
What should happen when the supplier receives less than invoiced?
Hold conclusions, trace the payment, classify the difference from bank evidence, apply the signed allocation and obtain authorised accounting/legal treatment before sending more money.
Can payment instructions be stored in the article's worksheet?
No sensitive bank details should be placed in a general procurement document. Use the organisation's protected vendor-master and payment systems, with independent change verification.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
BIS — Correspondent banking, Committee on Payments and Market Infrastructures ↗SWIFT — ISO 20022 for financial institutions ↗Federal Reserve — Fedwire Funds Service message format and ISO 20022 resources ↗IMF — Exchange Rates data and metadata ↗UNCITRAL — Model Law on International Credit Transfers (1992) ↗Related buyer guides
This article is general procurement and payment-control education, not banking, legal, foreign-exchange, hedging, tax, accounting, sanctions, anti-money-laundering or investment advice. It does not prescribe charge codes, payment rails, exchange sources, rate locks, gross-up clauses or accounting treatment; guarantee the credited amount or timing; interpret a bank message; or state any Cavorlen currency, account, fee or payment policy. Bank capabilities, terminology, laws and fees vary by institution, jurisdiction, currency, route and date. Use verified beneficiary instructions and current written advice from the buyer's and beneficiary's banks plus authorised finance, treasury, tax, accounting and legal professionals.