Glossary

Wire Transfer Charge Codes (OUR, SHA, BEN)

Wire transfer charge codes are the three values, OUR, SHA and BEN, that the sender of an international SWIFT wire picks to say who pays the banks’ transaction charges: the sender, both sides, or the recipient.

Also called: OUR SHA BEN, SWIFT charge codes, field 71A, details of charges, wire charge option

14-day free trial · card required · cancel anytime

Definition

Every international wire sent over SWIFT as an MT 103 message carries a mandatory field, 71A, Details of Charges. SWIFT’s own MT 103 reference guide defines it in one line: “This field specifies which party will bear the charges for the transaction.” Exactly one of three codes must be used.

SWIFT’s definitions are short. BEN: “All transaction charges are to be borne by the beneficiary customer.” OUR: “All transaction charges are to be borne by the ordering customer.” SHA: “All transaction charges other than the charges of the financial institution servicing the ordering customer account are borne by the beneficiary customer.”

Translated: the ordering customer is whoever sends the money, which for an invoice is your customer. The beneficiary is whoever receives it, which is you. Under OUR the sender pays every bank in the chain. Under SHA the sender pays their own bank and you carry everyone else’s charges. Under BEN you carry all of them, including the sender’s own bank.

The code is chosen by the sender, on their bank’s payment form, not by you. That is why one customer’s wire can arrive to the cent while another customer pays the same invoice and arrives short.

Key points

  • +Field 71A, Details of Charges, is mandatory in every MT 103 and takes exactly one of BEN, OUR or SHA.
  • +OUR: the sender bears all transaction charges.
  • +SHA: the sender pays their own bank, and every other bank’s charges fall on the recipient.
  • +BEN: the recipient bears all charges, including the sender’s bank’s fee.
  • +Under SHA and BEN, the amount credited to the recipient is lower than the amount the customer instructed.
  • +Stripe says international wires “might incur fees when they’re sent to Stripe”, and the cash balance shows the amount Stripe actually received.
  • +In QuickBooks Online, Intuit books a deposit that is short because of bank fees to an expense account with the Bank charges detail type.

The same wire under OUR, SHA and BEN

SWIFT’s MT 103 guide works through one payment under all three codes, and the numbers make the difference concrete. The customer pays the equivalent of EUR 1,000.00 in GBP to a beneficiary in the United Kingdom, at 1 EUR to 0.61999 GBP. Charges on the sender’s side are EUR 5.00 (GBP 3.10). Charges on the receiver’s side are GBP 4.00 (EUR 6.45).

Under OUR, the customer’s account is debited EUR 1,011.45: the EUR 1,000.00 instructed plus both sides’ charges. The beneficiary is credited GBP 619.99, the full converted amount.

Under SHA, the customer is debited EUR 1,005.00, the instructed amount plus their own bank’s charge. The beneficiary is credited GBP 615.99, because the receiving side’s GBP 4.00 comes out of the payment.

Under BEN, the customer is debited exactly EUR 1,000.00. The beneficiary is credited GBP 612.89, with both sides’ charges deducted, and SWIFT notes that “The beneficiary is also advised of the Sender’s charges of GBP 3,1.”

Same instruction, three different amounts in your account, a spread of GBP 7.10. The example has one bank on each side. A real wire can route through intermediary banks too, and SWIFT’s sender’s charges field “may be repeated to specify to the Receiver the currency and amount of charges taken by preceding banks in the transaction chain.”

Reading the charges on the message: 33B, 71F and 71G

Three other MT 103 fields tell you who took what. Field 33B is the instructed amount, which SWIFT says “has to be transported unchanged through the transaction chain.” Field 71F is the sender’s charges, one occurrence per bank that deducted something, where “the last occurrence always gives the Sender’s charges.” Field 71G is the receiver’s charges.

SWIFT ties them together in one formula: “The instructed amount in field 33B, adjusted with the exchange rate in field 36, plus the Receiver’s charges in field 71G, minus the Sender’s charges in field(s) 71F, equals the interbank settled amount in field 32A.”

The charge code limits which of those fields can appear. Under OUR, 71F is not allowed and 71G is optional. Under SHA, 71F is optional and 71G is not allowed. Under BEN, at least one 71F is mandatory and 71G is not allowed.

If your bank shows you the details of an incoming wire, compare the instructed amount with what was credited. The difference, broken out by 71F occurrence, is the fee trail. It is also your evidence when a customer insists they sent the full amount, because under SHA or BEN they did.

Why a wire to Stripe arrives short

Stripe accepts domestic and international wires for US accounts through its bank transfers payment method, and Stripe says those accounts support SWIFT transfers in USD only. Its documentation is direct about fees: “International wire transfers might incur fees when they’re sent to Stripe, which can result in an amount received that’s less than what the customer originally sent. The amount shown in the cash balance is the amount that Stripe received from the customer.”

For a Stripe invoice, a short wire does not pay part of the invoice. Stripe’s invoicing docs say “Invoices won’t be partially funded and remain open until incoming funds cover the full invoice amount.” The money waits in the customer’s cash balance, and the invoice still shows the full amount due.

You have three ways to close the gap. Ask the customer to send the balance. Issue a credit note for the difference. Or turn on Stripe’s setting to mark an invoice paid when it is “partially paid within the set amount”, which the Stripe underpayment threshold guide linked below covers in detail.

Prevention is cheaper. OUR is the only code under which, by SWIFT’s definition, all transaction charges fall on the sender. If you invoice customers abroad, ask for OUR in the payment instructions on the invoice, so their accounts payable team picks it on the bank form.

Recording the shortfall in QuickBooks

A wire that arrives short under SHA or BEN is a cost of collecting the payment, not a discount and not bad debt. The customer sent what you asked. The banks took a cut on the way.

Intuit’s QuickBooks Online article for this case is written for exactly the situation “If you received less than the due amount on invoice because of bank fees.” It has you create an account with the account type Expenses and the detail type Bank charges. Then, when you match the deposit in the bank feed, you tick the invoice, open the “If needed, resolve the difference” dropdown and choose the bank fees account. QuickBooks fills in the difference.

That method fits an invoice that lives in QuickBooks and a deposit that lands in your bank account. When the invoice lives in Stripe, close the gap in Stripe first, with a credit note or the underpayment setting, so the two systems agree about what the customer still owes. A gap resolved in QuickBooks while Stripe still shows the invoice as open is the same fee recorded in one system and still owed in the other.

Frequently asked questions

What do OUR, SHA and BEN mean on a wire transfer?

They say who pays the banks’ charges on an international SWIFT wire. OUR means the sender pays all charges. SHA means the sender pays their own bank and the recipient pays every other bank. BEN means the recipient pays all charges, deducted from the amount in transit.

Which charge code should I ask customers to use?

OUR, if you want the invoice paid in full. By SWIFT’s definition it is the only code where all transaction charges fall on the sender. It costs the customer more: in SWIFT’s own example, the same payment debits EUR 1,011.45 under OUR and EUR 1,005.00 under SHA. Put the request in the payment instructions on the invoice.

Why did a wire arrive short when the customer sent the full amount?

The customer most likely chose SHA or BEN. Under SHA, the receiving side’s bank charges come out of the payment. Under BEN, every bank’s charges do, including the sender’s own bank. Intermediary banks on the route can deduct charges too, each recorded as a separate sender’s charges entry on the message.

What is field 71A in an MT 103?

Field 71A, Details of Charges, is the mandatory MT 103 field that “specifies which party will bear the charges for the transaction,” in SWIFT’s words. It must contain one of BEN, OUR or SHA, and the code decides whether fields 71F and 71G may or must appear.

How do I record wire fees deducted from a customer payment in QuickBooks Online?

Intuit’s method is to create an Expenses account with the Bank charges detail type, then match the short deposit to the invoice in the bank feed and use the resolve-the-difference dropdown to put the gap in that account. If the invoice was raised in Stripe, close the gap in Stripe first so both systems agree.

What customers say about running Stripe through Acodei

Stripe Verified Partner BadgeIntuit QuickBooks
★★★★★
“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”
RyanOwner at Indie Music Academy
★★★★★
“Works well and is really helpful for massive transactions. The support is really fast and helpful. 100% recommended.”
AndresCo-founder and CEO at Kanguro Collections and Reinsurance

Related reading

More glossary terms

See the full glossary

Ready to try Acodei?

Connect Stripe to QuickBooks Online in minutes and let the fees, refunds, and payouts land where your accountant expects them.

14-day free trial · card required · cancel anytime