# How to get paid by an overseas client without fees eating it How freelancers collect from foreign clients without losing a chunk to conversion and transfer fees, and how funds arrive in full. --- ## How to get paid by an overseas client without fees eating it You closed the work, delivered on time, and sent the invoice. The client confirms payment. Then the money arrives — and it's short. Not by a rounding error. By real money. That gap between what you invoiced and what you received is not a mistake; it's the predictable cost of using the wrong payment infrastructure for the wrong corridor. If you work with overseas clients and you haven't engineered your collection setup deliberately, you're absorbing costs that you shouldn't be, repeatedly, on every payment. This article is about closing that gap. Not theoretically — with the specific mechanics that determine how much you keep from an international invoice, where each dollar or euro disappears, and what you can do structurally to stop the leakage before it starts. ## The money doesn't travel in a straight line Before you can fix the problem, you need to understand the plumbing. Most freelancers assume that when a client clicks "send payment," the money moves from their bank account to yours in one clean step. It does not. SWIFT itself moves no money at all — it only moves instructions. The actual settlement happens separately through correspondent accounts. This distinction matters enormously in practice. For your funds to move physically from the sending bank to their destination, the sending and receiving banks must have a direct relationship with each other. That isn't always the case, so when making an international transfer via the SWIFT network, your money will often pass through one or several correspondent or intermediary banks before reaching its final destination. Correspondent fees are what those correspondent banks charge you inside the SWIFT network. The money travels from one country to another, and if the sender's bank and the recipient's bank don't have a direct relationship, it also travels from bank to bank. These banks charge their own fee, and those fees impact the amount the recipient gets. The correspondent fee can be deducted at any stage of this process. It could be an outgoing transfer fee charged by your own bank, an intermediary fee from a correspondent bank, or even an incoming fee charged by the recipient's bank. The critical phrase there is "deducted at any stage." You have no visibility into which banks sit in the chain on any given payment, nor do you know exactly what each one will take. The numbers are not trivial. Your sending bank charges an upfront wire fee, typically $20 to $50. Each correspondent bank in the routing chain may then deduct a processing fee of $10 to $30 directly from the principal, and the receiving bank may add a lifting fee on top of that. Intermediary bank charges alone can reduce the payment amount by 10 to 30%. On top of those structural fees sits a second, less visible cost: the exchange rate markup. Commercial banks rarely offer the interbank mid-market rate; they apply a markup of 2% to 4% above it. Unlike the wire fee, this cost is not disclosed as a line item — it's baked into the rate you're quoted, which makes it easy to overlook and hard to forecast. Put those together on a real invoice. A $5,000 payment moving from a US client through SWIFT to a freelancer in Southeast Asia might involve: a $30–50 sending fee from the client's bank; one or two correspondent hops each taking $10–30; an incoming fee from the receiving bank; and then a 2–4% exchange rate markup applied somewhere along the chain. A $3,000 invoice can land as $2,941 after fees and FX — and neither side budgeted for the gap. At higher invoice values, the proportional losses are the same but the absolute dollar figures are worse. ## Three types of fee leakage — and which ones you can control Not all cross-border fee loss is created equal. Understanding which category each cost falls into tells you where to apply pressure. ### Structural transmission fees These are the SWIFT correspondent charges and receiving bank fees described above. Multiple intermediary banks take fees during international transfers, creating hidden costs that vary by currency and destination. You don't control which banks sit in the chain. But you can choose payment rails that avoid SWIFT entirely for many corridors. ### Exchange rate spread This is the markup a bank or platform applies above the mid-market rate when converting currencies. It doesn't appear as a line item on any statement. It's simply built into the rate. Currency conversion represents one of the largest hidden costs in international payments. Traditional banks typically add markups to the mid-market exchange rate, effectively reducing your payment by several percentage points. For freelancers receiving regular international payments, these conversion costs can significantly impact annual earnings. ### Platform and withdrawal fees Payment platforms typically charge a percentage-based fee per transaction and may apply withdrawal fees or currency conversion markups. These are more visible than the SWIFT chain fees, but they compound with conversion costs. For smaller invoices, percentage-based fees may be manageable. For larger amounts, the total cost becomes more noticeable. Of these three, the structural transmission fees are hardest to negotiate with and easiest to route around. The exchange rate spread is negotiable by choosing the right platform. Platform fees are knowable upfront and can be factored into your pricing. Most of the damage done to freelance payments happens in the first two categories, and most of it is preventable. ## The OUR/SHA/BEN question on wire transfers If your client is paying by wire transfer, one of the most impactful decisions you can make is which charge code governs the payment — and most freelancers never think to ask. There are three main options: OUR means the sender pays all fees, including intermediary charges — this ensures the recipient receives the full amount sent. BEN (Beneficiary) means the recipient pays all fees — intermediary banks deduct their charges from the transfer amount before it reaches the destination. SHA (Shared) means the sender pays their bank's outgoing fees, while the recipient pays incoming and intermediary charges. The default on most international wires is SHA. Under the common SHA charge code, you, the freelancer, pay both correspondent charges and lifting fees, often losing 3–5% of each payment. That's the default position you're in if you've never had this conversation. The fix is direct: request OUR charge code and confirm its execution with the sender. Put this language in your contract and on every invoice. Something as simple as "Payment should be sent OUR (sender covers all charges) so that the full invoiced amount is received" removes ambiguity and shifts responsibility where it should be. Wire transfer fees can reduce your earnings if not discussed upfront. Before work begins, confirm the fee arrangement in writing. A simple line in your agreement or email can help — for example: "Please ensure payment covers all applicable transfer fees so the full invoiced amount is received on my end." One important caveat: regardless of correspondent bank charges, any recipient bank fees will still be owed by the beneficiary and likely deducted from their receiving total, as you're rarely able to cover these fees as a sender. OUR protects you from most correspondent chain fees but may not eliminate every receiving bank deduction. Know what your own bank charges on inward international wires and factor it in. ## The currency decision: who carries the FX risk? Before you ever send an invoice, you make a decision that determines how much FX risk you carry — whether you make it consciously or not. The currency on the invoice is a business choice, not an administrative detail. There are two clean approaches and several hybrid positions. **Invoice in your own currency.** When you bill in your local currency, the client's bank or payment platform does the conversion on their side. Invoicing in your local currency where possible is ideal. Not all clients will agree to this, but it's worth raising. When a client pays in your base currency, the FX risk shifts to them entirely. You know exactly what will land in your account. The downside is friction — some clients are confused by or resistant to paying in a currency that isn't their own, particularly in markets where USD dominates. **Invoice in USD or another major reserve currency.** USD is the most widely accepted international billing currency. Most international freelancers working with U.S. clients invoice in USD. A common practice is to invoice in USD and manage FX exposure through thoughtful conversion timing and pricing buffers. If you're billing a client in Australia, Germany, or Singapore and you invoice in USD, the client pays USD, their bank handles their end of the FX, and you receive USD — which you then convert when conditions suit you. **Invoice in the client's local currency.** This minimizes friction for the client and may increase conversion rates on high-value proposals. But if you create an invoice in another currency, you and your client risk getting hit by exchange rate fluctuations. A Japanese client billed in yen and a 3% swing in the JPY/USD rate between invoice date and payment date can meaningfully change what you receive. If you do invoice in the client's currency, you need a buffer built into your rate and a multi-currency account that lets you hold the foreign currency until you convert at a favorable moment. **The pricing buffer approach.** If you regularly take a 3–5% hit on conversions, factor that into your rates. Build currency risk into your pricing. Charge what you need to net your target income after fees. This is more negotiating art than science, but it's the honest answer: if you can't eliminate FX costs, price so that absorbing them still leaves you whole. There's a practical middle ground most experienced international freelancers eventually land on: bill in USD or another reserve currency for almost all clients, hold the received funds in a multi-currency account rather than converting immediately, and convert in batches when rates are favorable. The strategic value is straightforward: hold your income in the currency it arrives in, then convert when conditions are favorable. Avoid unnecessary back-and-forth conversions that each carry their own fees and rate exposure. ## Choosing the right collection rails for your corridor The payment method you ask your client to use determines most of what happens to the money before it reaches you. This is the single most consequential infrastructure decision you make as a freelancer with overseas clients. ### Traditional SWIFT wire transfers Bank-to-bank international transfers processed through the SWIFT network are one of the most established payment methods. Many businesses already use wire transfers, which can make the option convenient for clients. However, fees apply on both ends: the sending bank may charge the client, and the receiving bank may also charge a fee. Exchange rates may include a markup, and transfers typically take two to five business days. Wire transfers make sense for large, high-value invoices where the flat correspondent fees represent a smaller percentage of the total, and where corporate clients are accustomed to the process. They're harder to justify on invoices under $2,000 where a $60 combined fee load represents 3% off the top before you've converted anything. ### Fintech platforms using local rails Modern global business accounts work differently than traditional banks. Instead of sending money across borders via SWIFT, they establish local banking details in multiple markets. When a payment is funded, the platform collects it locally and instructs its entity in the destination country to pay out using that country's domestic clearing network. Both legs stay local — no SWIFT, no correspondent bank chain, no intermediary fees. This is the architecture that platforms like Wise, Payoneer, and similar fintech services use to offer better rates and faster transfers than traditional wires. Newer banking solutions offer the security of traditional banks with improved speed and lower costs. These services often provide better exchange rates and faster processing times. For a freelancer, the practical implication is this: if you can give your client payment instructions that let them pay via a local transfer in their country — an ACH in the US, a SEPA transfer in Europe, a Faster Payment in the UK — the money never routes through SWIFT's correspondent bank chain. It moves domestically on the sending side, the platform holds the float, and pays out domestically on your receiving side. The fee structure is almost always better. Some platforms operate by maintaining local accounts in multiple countries. Your client pays in their currency and you receive funds in yours, which may help streamline the process. ### Digital wallets and payment platforms Platforms like PayPal are ubiquitous and familiar to clients, which matters when a client's accounts payable department prefers a recognizable name. But the fee structure compounds aggressively on larger payments. International transfers can carry percentage fees plus currency-conversion markups, typically in the 3–4% range for FX. For many freelancers, that blend exceeds what they expect, especially at scale. Some platforms may also place temporary holds on funds, which can affect timing. This is worth flagging to clients upfront — not just the cost but the cash flow implication of a platform hold on a large payment. ### Multi-currency accounts as a strategic receiving layer Multi-currency accounts are one of the most practical tools available to freelancers with foreign income. They allow you to receive, hold, and convert funds in multiple currencies — USD, EUR, GBP, and others — without being forced to convert immediately upon receipt. Digital banks and fintech platforms have made this increasingly accessible. Many offer competitive exchange rates with low fees, local account details in multiple countries, and easy transfers between currency balances. The architecture that works well for many established freelancers is a two-layer setup: a multi-currency receiving account that gives you local bank details in your clients' major geographies, plus your domestic bank account where you transfer converted funds as needed. Your US client sends a domestic ACH; your EU client sends a SEPA; your UK client sends a Faster Payment. None of those transactions ever touches the SWIFT correspondent chain. You receive each in its native currency, convert when you choose, and transfer domestically to your operating account. ## Crypto and stablecoins: where they fit and where they don't Stablecoins — dollar-pegged tokens like USDC — have become a genuinely practical option for some freelancers, particularly those working with crypto-native clients or in markets with limited traditional banking access. Stablecoin transfers arrive within minutes regardless of geography, compared to days or weeks for traditional bank wires. Operational costs become almost non-existent. For freelancers in countries with weak banking infrastructure, high inflation, and financial turmoil, receiving payment in USDC or USDT provides financial stability and protection against local currency devaluation. But stablecoins carry real operational complexity. Crypto is complex, and technical literacy is non-negotiable. Lack of knowledge may lead to tricky situations. Freelancers must understand digital wallets, private key management, and basic blockchain mechanics. If your client isn't already comfortable with crypto payments, introducing it creates friction rather than removing it. And there are tax reporting requirements in most jurisdictions that add administrative overhead. For freelancers whose clients are established businesses paying from corporate accounts, stablecoins remain a niche option rather than a mainstream solution. They make most sense when speed is critical, when the client initiates the suggestion, or when you operate in a corridor where traditional rails are genuinely poor. ## The tax and compliance layer you cannot ignore Cross-border payments exist at the intersection of two tax jurisdictions. What your client's country requires of them — and what your own country requires of you — are both live questions, and the answers differ enough between corridors to warrant specific attention. In many countries, income earned from international clients is taxable and must be reported. Rules around currency conversion and reporting timelines can vary, so consulting a tax professional familiar with self-employment income may be helpful. For US-based clients specifically, if you are not a US person, you will almost certainly need to provide a W-8BEN before the first payment clears. The W-8BEN is a certificate of foreign status used for US tax purposes. You provide it to your client — not directly to the IRS. Without a W-8BEN, withholding may apply. With a valid form on file, withholding may be reduced or eliminated depending on applicable tax treaties and your country of residence. Most countries require you to report foreign income at the exchange rate on the date it was received. Some jurisdictions also tax currency gains — the difference between the rate at receipt and the rate at conversion. Keep detailed records of every conversion, including dates and rates used. This record-keeping requirement is a good reason to route all international payments through a dedicated account rather than a personal one. It gives you a clean audit trail, separates business income from personal funds, and makes tax season materially less painful. ## Structuring the deal up front: what goes in the contract and invoice Every dollar you lose on a bad payment setup could have been protected by a clear agreement at the start of the engagement. The terms that govern payment are not administrative boilerplate — they are the financial engineering of your income. Specify in writing, before work begins: The invoicing currency. State it explicitly, including the ISO 4217 code. "USD" is not ambiguous. "Dollars" can mean four different things to clients in four different countries. The preferred payment method and the specific account details they should use. If you want the client to use a local ACH because you've set up a US receiving account through a fintech platform, say so on the invoice. Don't assume they'll figure it out. Fee responsibility. State clearly whether the client is expected to send OUR (covering all correspondent charges) or whether you've built a buffer for SHA. Ambiguity here produces short payments and awkward reconciliation emails. Payment timing and any late payment terms. US companies often operate on Net-30 billing cycles — meaning they pay invoices 30 days after receipt. For freelancers, that can feel like a long time to wait. Knowing this in advance lets you plan cash flow rather than chase payments. Contracts should clearly specify payment timelines, currency, accepted methods, and any applicable late fees. Clear documentation reduces ambiguity and provides a reference point if questions arise. A client's corporate accounts payable department is not your adversary. They follow what the contract says and what the invoice instructs. Give them complete, unambiguous instructions and most of the friction disappears. ## How invoice size changes the calculus The right collection method for a $500 invoice is not the right method for a $15,000 invoice. Fee structures interact with payment size in ways that shift which option wins. On smaller invoices, flat-fee SWIFT charges hurt proportionally more. A $30 correspondent fee on a $400 invoice is 7.5%. The same $30 on a $5,000 invoice is 0.6%. This is why for one-off projects under $2,000, freelance marketplaces remain convenient despite higher fees — the convenience and simplicity of a platform that handles everything may be worth the percentage cost when the absolute dollar loss is modest. On large retainers or milestone payments, platform percentage fees become the enemy. A 3% PayPal fee on a $10,000 invoice is $300. A SWIFT wire with OUR charges and a well-chosen fintech receiving account might cost $15 total in fixed fees. At that scale, the fixed-cost infrastructure pays for itself many times over. Whenever possible, bill for a little extra to cover the exchange rate losses, especially for small batch or one-off projects. Also think about billing a client less often and for a larger total. This can affect per-transaction fees, which some payment processors charge in addition to percentage-based fees. Batching invoices is an underused lever. If you have a recurring client who pays weekly, moving to monthly billing halves the number of transactions touching the correspondent chain. The FX conversion timing remains your choice; the number of transmission events is cut by three-quarters. ## When payments go wrong: the trace process Even well-structured international payments occasionally go missing or arrive short without explanation. Start by confirming that the client has initiated the transfer and request the transaction reference number. If the delay continues, contact your bank or payment provider for clarification. Delays are often related to processing timelines or compliance reviews. For SWIFT wires specifically, your bank may be able to initiate a trace through the SWIFT network. The MT103 document — the SWIFT payment confirmation — is your primary tool. It shows the full chain of banks that processed the payment, the charge code used, and any fees deducted at each stage. If your payment arrived short, the MT103 tells you where the money went. Ask your bank and ask the client's bank to produce it. Lifting fees usually appear on your statement as a line item. Correspondent charges are hidden — you only see a short credit upon arrival. The MT103 makes those correspondent charges visible after the fact. If you see a pattern of consistent short credits from a specific client corridor, that tells you the SHA default is being applied and that OUR instructions or a rail change is the fix. ## Where Shaka fits in the professional payment stack For freelancers who work on structured deals — project completions, milestone payouts, multi-party disbursements — the administrative overhead of coordinating international payments can compound quickly. When a deal involves more than one recipient, or when the work closes in one step and payment is meant to distribute across parties simultaneously, coordinating that through manual wire instructions and separate bank transactions introduces delay and reconciliation risk. Shaka handles that layer. A professional creates a payment link, sets the recipient wallets and the split percentages, and everyone involved receives their share instantly and directly when the deal closes — in a single transaction that doesn't require multiple manual disbursements. The deal closes; the money lands where it's supposed to, in full, at the same moment, without chasing separate confirmations from separate banks. For the freelancer collecting from an overseas client on a complex engagement, that certainty is not a small thing. The client initiates once. The routing is done. The payment is final. ## The professional's checklist before the first invoice goes out Before you send invoice one to any new overseas client, the infrastructure decision should already be made. Not later. Not when the payment is late and you're scrambling. Before the engagement starts. Know which currency you're billing in and why. Decide based on who carries the FX risk most efficiently, not based on which is most convenient to type. Know which payment rail you want the client to use. Give them explicit instructions — the account number, IBAN, routing details, or payment link — for the method that benefits you, not the default their accounts payable system reaches for first. Know who is covering transmission fees and put it in writing. OUR if they're wiring. A buffer built into your rate if you've agreed SHA. Never silent on this point. Know your receiving account setup before the money moves. A multi-currency account that gives you local receiving details in your clients' main geographies eliminates most of the SWIFT correspondent chain cost for the corridors that matter to your business. Know the tax requirements in both directions before payment one. A W-8BEN filed late, a withheld amount you didn't plan for, a conversion gain taxed at a rate you forgot about — these are all predictable if you've done the homework. They're surprises only if you haven't. The professionals who keep the most of what they invoice aren't lucky. They've built the infrastructure deliberately, specified the terms clearly, and chosen the rails that suit their volume, their corridors, and their clients. The fees that eat other freelancers' payments don't disappear — they just get routed to someone who wasn't paying attention. Stop being that person on the first invoice, not the fifth.