Getting paid in Japan: salary, freelance & remote work

Getting paid in Japan - or from abroad while living there - is where freelancers and remote employees keep or lose margin. This page owns receive architecture.

Receive path matrix

Local context

Salary and client funds into Japan should terminate on Zengin / Furikomi in JPY whenever the payer can support it. If your employer still “only does wires,” ask for multi-currency account details or a fintech payout that lands locally at MUFG and SMBC without correspondent haircuts. Freelancers living in Tokyo should put currency, fee ownership, and receive method on every invoice — not in a follow-up email after the wire already left. Japan still runs a hybrid cash + contactless culture; carrying yen is practical even if you mostly use cards in cities.

Rails you will hear:

• Zengin is how Japanese bank transfers are addressed/settled domestically. Tourists rarely initiate Furikomi; residents need it for rent and salary.
• Furikomi is how Japanese bank transfers are addressed/settled domestically. Tourists rarely initiate Furikomi; residents need it for rent and salary.

Invoice mechanics

1. State currency and exact receive method on the invoice
2. Define who pays transfer fees
3. Add terms that cover FX windows on late payers
4. Reconcile receipts weekly with exportable statements

Stablecoin / crypto-native income

USDC-style collection can remove the long-haul wire - you still need a clean offramp into JPY for rent and tax. Multisig matters once balances exceed coffee money.

Tax admin (high level)

Not tax advice. Living in Japan may create home, host, or dual reporting duties. Keep tidy inbound/conversion records. Hire a cross-border-aware accountant before year-end.

Numbers that matter

Mid-market FX vs the board you are shown

The mid-market rate is the midpoint between buy and sell on wholesale markets — the number Google and major FX feeds show for JPY. Airport desks, hotel cashiers, and many bank boards price far away from that midpoint. A “0% commission” offer in Tokyo almost always hides the markup inside the rate.

Dynamic currency conversion (DCC) is the terminal prompt that offers to charge your home currency “for convenience.” In Japan, refuse it: choose JPY / local currency so your issuer converts near its published FX rules instead of the merchant’s padded rate.

True-cost matrix (illustrative)

Ignore “$0 fee” headlines. For money into or inside Japan, rank options by total funded to deliver a fixed JPY outcome — including FX distance from mid-market, flat fees, intermediary lifting, and time risk.

Domestic rails worth understanding

Inside Japan, everyday bank value usually rides Zengin and sibling domestic systems — not SWIFT. Tourists meet these rails indirectly (hotel deposits, local contractors). Residents and long-stay expats should treat them as the default once a local account exists.

• Zengin is how Japanese bank transfers are addressed/settled domestically. Tourists rarely initiate Furikomi; residents need it for rent and salary.
• Furikomi is how Japanese bank transfers are addressed/settled domestically. Tourists rarely initiate Furikomi; residents need it for rent and salary.

Week-one money calendar

1. Before you fly: enable issuer travel/security controls; order a backup card; save MUFG ATM brands on a map around Tokyo
2. Landing day: skip full-budget airport FX; keep a tiny JPY float if you already hold near-mid-market notes
3. Day 1–2: test a small card purchase in JPY; refuse DCC; confirm your backup card also works
4. Day 3+: map where cash is still required (markets, tips, intercity desks) and refill only at bank lobby ATMs
5. If staying 30+ days: start local-account checklist early — tourist KYC often fails at MUFG

Fee stack anatomy (read this before any big transfer)

Every cross-border move into or out of Japan is a stack of (1) FX distance from mid-market, (2) explicit send fees, (3) intermediary or network fees, and (4) time risk if the payment misses a payroll or rent cut-off. Marketing that highlights only one of the four is incomplete.

If a card freezes in Japan

1. Freeze the failed card in your issuer app; do not keep retrying and burning authorizations
2. Switch to the backup card on a different network/issuer — test a small purchase first
3. Withdraw a modest JPY float from a MUFG lobby ATM if cash is required
4. Use a pre-arranged emergency top-up (partner, multi-currency balance, or stablecoin offramp) — not airport desks for large amounts
5. If both cards fail, contact issuer travel support with merchant name + city; document every fee for dispute

Decision checklist before you commit

1. Write the outcome first: “Recipient holds ¥X JPY by date Y.”
2. Quote at least two paths (local-rail fintech vs bank SWIFT vs card-funded cash) using the same outcome sentence
3. Confirm the beneficiary can actually receive on Zengin — if not, SWIFT may be forced
4. Refuse DCC on every terminal; screenshot rate screens when amounts are large
5. Document fees for expense reports and future disputes

What good looks like

• You can explain the mid-market JPY rate vs the board in front of you
• You never accept DCC on POS or ATM prompts in Japan
• Local outcomes ride Zengin when the counterparty can receive them
• Emergency funding does not depend on a single card or airport cash
• Teams use approval controls (multisig) for treasury-scale balances
• You know which MUFG (or peer) ATMs you will actually use in Tokyo

Worked example (illustrative — not a live quote)

Suppose the recipient in Japan must receive exactly ¥100,000 JPY (rent slice, tuition installment, or family support). Fix that delivered amount first, then compare providers on what you must fund in your home currency.