Short-Paid Payment

A short-paid payment (also called a short payment or underpayment) is a payment that arrives in the beneficiary's account for less than the amount the payer intended or the invoice required. In international wire transfers, the shortfall usually arises because one or more banks in the chain deducted fees from the principal, because the funds were converted into another currency along the way, or because the payer chose a charge option that left the beneficiary to bear costs it did not expect.

Short payments are a routine source of friction in trade and cross-border business. They create unpaid balances on the seller's books, disputes about who should bear the cost, and extra work in reconciliation and collections.

Charge codes

Every SWIFT customer transfer carries a charge instruction, explained in OUR, SHA and BEN charge codes. Under OUR, the payer bears all charges; under SHA, the payer pays its own bank's fee and the beneficiary bears the rest; under BEN, all charges, including the sending bank's, are deducted from the amount. With SHA or BEN, any fee taken along the way reduces what arrives.

Intermediary and receiving bank deductions

A payment between two banks without a direct relationship passes through one or more intermediary banks or correspondent banks, each of which may take a processing fee from the principal. The beneficiary bank may also charge an incoming-payment fee. Even an OUR instruction does not always prevent deductions, because some banks in the chain do not honor it or bill the charges later.

Currency conversion

If a payment is sent in one currency and credited in another, the conversion rate and any FX markup determine the amount received. A payment can also be converted twice, for example from euro to dollars by a correspondent and back to the account currency by the receiving bank, a situation described as double currency conversion.

Payer errors

Some short payments have nothing to do with banks: the payer may deduct withholding tax, apply an unagreed discount, pay against an old version of the invoice, or net off a credit note.

An exporter issues a commercial invoice for USD 10,000. The buyer instructs its bank to send USD 10,000 with charge code SHA and pays its own bank's USD 30 fee separately. An intermediary bank in New York deducts USD 20, and the beneficiary's bank deducts USD 15 on receipt. The exporter is credited with USD 9,965 and records an unpaid balance of USD 35. Had the payment been sent with OUR, and had every bank honored it, the full USD 10,000 would have arrived and the buyer would have paid all charges.

In a SWIFT MT103 message, field 33B records the original instructed amount and fields 71F and 71G show charges taken or due, allowing the beneficiary's bank to see what was deducted. In the newer ISO 20022 formats, equivalent charge information is carried in structured fields. SWIFT gpi tracks each payment by its unique end-to-end transaction reference (UETR) and records the deductions taken at each hop, making it easier to identify which bank took a fee. Where the cause is unclear, the beneficiary can ask its bank to open a payment investigation or a payment trace.

• Agree in the contract who bears bank charges, and state the required charge code and the currency of payment on the invoice.
• Ask payers to use OUR where the full amount must arrive, and accept that some deductions may still occur on certain corridors.
• Send payments in the currency of the beneficiary's account to avoid unexpected conversion.
• Use local payment rails or providers with local accounts in the destination country, which avoid correspondent chains; within Europe, SEPA euro transfers are not subject to intermediary deductions.
• Compare total cost, not just the headline fee, using an all-in cost view of each payment corridor.

Short payments are distinct from a returned payment, in which the funds are sent back to the payer, and from a payment recalled by the sender.