A wire sent to fund a Japan IOR (Importer of Record) duty and tax advance arrives short when the SWIFT payment instruction used a shared-cost code (SHA) instead of OUR: under SHA, each intermediary bank in the correspondent chain can deduct its own handling fee before the balance reaches the recipient, so the amount credited is lower than the amount sent.
Why Does a SWIFT Wire Arrive Short of the Amount Sent?#
A wire arrives short when the charge-code instruction on the payment allows a bank somewhere in the chain to take a cut before passing the balance through. International wires do not move directly from the sender's bank to the recipient's bank. They pass through one or more correspondent banks, and each charge-code setting decides who absorbs the fee at each hop.
There are three conventions. Under OUR, the sender's bank commits to covering every fee along the route, including any correspondent bank charge, so the full amount quoted lands in the recipient's account. Under SHA (shared), the sender pays their own bank's outgoing fee and the recipient's bank charges its own incoming fee separately, but an intermediary bank in between can still deduct a handling fee from the principal in transit, and neither party controls that deduction in advance. Under BEN, the recipient absorbs every fee in the chain, including the sender's own bank charge, which is the least common setting for a business payment and the worst fit for a duty advance.
SHA is the default setting on most online banking wire forms unless the sender changes it. That default works fine for a general invoice payment where a small variance does not matter. It does not work for a payment where the recipient needs an exact figure on a fixed deadline.
Why Does a Short Wire Create a Problem for an IOR Duty and Tax Advance?#
A short wire is a bigger problem on an IOR duty advance than on an ordinary invoice because the IOR must hold the full estimated customs duty and import consumption tax in hand before the import declaration (輸入申告) is filed, and there is no partial-filing option. Japan Customs collects duty and import consumption tax at the moment of clearance, calculated against the customs value (課税価格) and the applicable line in the tariff schedule. The IOR funds that payment from the client's advance, not from its own balance sheet, so the advance has to land at the figure quoted, not approximately that figure.
If a SHA-coded wire loses a portion to an intermediary deduction, the shortfall surfaces at the worst possible moment: after the goods have arrived, after the declaration has been prepared, and often within the clearance window the shipment needs to meet to avoid demurrage or storage charges at the port. A small deduction on a large advance looks trivial against the total, but customs does not accept a declaration funded at a fraction short of the required amount. The IOR either has to chase a top-up wire against the clock or cover the gap itself temporarily, and neither option exists by default under a standard advance arrangement.
This is the specific reason a duty and tax advance is treated differently from a routine commercial payment. A late invoice payment is a relationship issue. A short customs advance is a clearance-timing issue, and clearance timing carries real cost once a shipment is sitting at a Japanese port waiting on funds that have not fully arrived.
How Do You Make Sure the Full Amount Arrives?#
Two things fix this reliably. First, specify OUR on the wire instruction: full amount to recipient, sender bears all charges. This is a field on the SWIFT MT103 instruction, or the equivalent on a bank's online wire form. Most sending banks will apply it if the sender asks explicitly; it is simply not what most forms pre-select by default. It costs the sender a somewhat higher upfront fee in exchange for certainty that the figure specified reaches the recipient in full.
Second, where available, route the payment through a local payment rail instead of a SWIFT wire. A local rail settles over a country's domestic payment network. It does not pass through a chain of correspondent banks, so there is no intermediary deduction to worry about. Does your bank support direct customs duty payment for a Japan IOR import covers which banks and payment structures support this for a Japan clearance.
Either fix solves the problem for a single wire. Neither changes the fact that an IOR advance has to be funded again for each shipment under a standard pay-as-you-clear structure. A client running frequent shipments who wants to reduce how often this funding step happens at all should look at whether a Japan IOR can defer customs duty instead of paying at each clearance, which addresses the funding cadence, a separate question from the wire mechanics covered here.
(a) OUR means the sender's bank absorbs every fee in the chain, so the full amount quoted arrives. (b) SHA means each side pays its own bank, but an intermediary bank in between can still deduct a fee from the amount in transit, and that deduction is what causes a short IOR advance. (c) BEN means the recipient absorbs every fee, including the sender's own bank charge, and is rarely the right setting for a duty advance. (d) A local payment rail avoids the issue structurally: it removes the correspondent-bank chain instead of instructing around it.
Does a Large Duty Advance Trigger a Bank of Japan Reporting Obligation?#
A payment or receipt into Japan whose single-transaction amount exceeds JPY 30,000,000 (or the foreign-currency equivalent) triggers a reporting obligation to the Bank of Japan under the Foreign Exchange and Foreign Trade Act (外為法), with a narrow exception for a payment that is part of a trade transaction procedure already completed. Whether a large IOR duty and tax advance itself qualifies for that trade-transaction exception is an open question this article does not resolve, and treating it as settled either way would be a mistake.
The advance is not payment for goods, and it is not the invoice-settlement transfer the exception appears to have been written around; it is a pre-funding transfer for a tax and duty obligation that has not yet crystallized at the moment the wire is sent. Whether that distinction matters for the reporting trigger depends on how the receiving bank and the reporting rule treat a pre-clearance tax advance specifically, and there is no single public answer that applies uniformly across every receiving bank. For a shipment where the duty and tax advance alone approaches or exceeds the JPY 30,000,000 line, ask the receiving bank directly how it will classify the inbound transfer before the wire is sent. Aplash assesses this individually before any scope or terms are set, because the answer can turn on the specific structure of the underlying import and the bank's own reporting practice.
This threshold question sits alongside, not instead of, the charge-code issue above. A wire can be coded correctly as OUR and still raise the reporting question if the amount is large enough, and both need to be checked before a large advance goes out.
How Do You Confirm the Right Amount to Wire?#
Confirm the exact figure with the IOR provider shortly before sending the wire. A quote given days or weeks earlier is not reliable at that point, because the duty amount is calculated against the customs value and the tariff schedule at the time of filing, and either input can move between quoting and the declaration date. A shift in the declared value, a currency movement affecting the customs weekly rate, or a tariff line correction after a closer review of the goods can each change the final duty figure by more than a SHA deduction would have cost anyway.
Building in a small buffer on top of the confirmed figure is standard practice for this reason. Any amount above what is owed is applied against the next line item or refunded. A reconfirmed figure sent with an OUR-coded wire, or routed through a local payment rail, closes both sources of shortfall at once: the bank-fee deduction and the stale-quote gap. For a buyer structure where the overseas supplier is paid directly, separate from the IOR's own duty-and-tax advance flow, the funding mechanics differ again; see can a Japan IOR buyer settle by paying the overseas supplier directly for how that structure handles the payment side. Where the goods portion and the duty-and-tax portion are separated like that, the duty advance itself is the smaller, more predictable figure of the two, which narrows this exposure.
Aplash's IOR service builds the confirmed duty and tax figure into the advance request as a matter of course, to avoid a client funding a stale number.
Frequently Asked Questions#
Why did my wire arrive for less than I sent?
The most common cause is a SWIFT charge-code setting of SHA (shared costs) instead of OUR (sender pays all costs). Under SHA, an intermediary correspondent bank somewhere in the chain can deduct a handling fee from the principal before it reaches the recipient, and neither party controls that deduction directly. Specifying OUR on the wire instruction, or using a local payment rail that avoids correspondent banks, prevents this.
Does a short wire matter if the shortfall is small?
Yes, specifically for a customs duty and import consumption tax advance, because Japan Customs requires the exact estimated amount to be in hand before the import declaration is filed and does not accept a partial funding figure. A shortfall that would be trivial on an ordinary invoice can delay clearance on a duty advance, which carries its own cost in demurrage or storage at the port.
Is there a reporting threshold I should know about for a large advance?
A payment into Japan whose amount exceeds JPY 30,000,000 triggers a Bank of Japan reporting obligation under the Foreign Exchange and Foreign Trade Act (外為法), subject to a narrow exception for payments tied to an already-completed trade transaction. Whether a duty-and-tax advance of that size qualifies for the exception is not settled in general terms, so ask the receiving bank directly; Aplash assesses this individually before any scope or terms are set.
This article is informational only and does not constitute legal, tax, or regulatory advice. Consult a qualified advisor before acting on the content. Last updated: October 2026.