Pillar Guide · Cross-Border Invoicing

The Freelancer's Guide to Cross-Border Invoicing

By Santanu Sarma — Mathematical Economics & Public Finance · Updated June 2026

Most freelancers treat international payments as a black box: you send the invoice, the client initiates a transfer, and money appears — eventually, and sometimes less of it than expected. The gap between "amount invoiced" and "amount received" is not random. It is the compound product of correspondent bank fee chains, FX spread extraction, settlement timing mismatches, and withholding tax obligations that neither party understood at the contract stage. This guide opens the black box.

How International Payments Actually Move: The SWIFT Network

The Correspondent Banking Model

When a US client sends a wire to a UK freelancer, the money does not travel directly from Chase Manhattan to HSBC London. There is almost certainly no direct settlement account relationship between those two institutions. Instead, the payment traverses a correspondent banking chain — a series of pre-existing nostro/vostro account relationships between banks that have chosen to hold balances in each other's currencies.

The mechanics: Chase holds a USD-denominated account at its own correspondent for GBP destinations — typically a large UK clearing bank or a global custodian. That correspondent debits Chase's nostro account, credits a GBP amount to a vostro account it holds for Lloyds (or whichever bank holds the freelancer's account), and Lloyds credits the freelancer's account. Each institution in this chain may deduct a handling fee — typically USD 5–25 per institution — from the payment principal before passing it on. A payment routed through three correspondent nodes can arrive USD 30–75 short of the invoice amount with no advance warning to either party.

The SWIFT network itself (the Society for Worldwide Interbank Financial Telecommunication, headquartered in La Hulpe, Belgium, operating under Belgian law and the oversight of the G-10 central banks under the Oversight Framework agreed in 2012) is purely a messaging system. SWIFT carries the instruction — "pay X amount to account Y" — but does not move money. The actual settlement happens through the correspondent accounts. Understanding this distinction is important when a payment goes missing: the SWIFT message may have been sent successfully while the actual funds are sitting in a suspense account at a correspondent bank awaiting a compliance check.

SWIFT Message Types Relevant to Freelancers

Message TypePurposeRelevance
MT 103Single customer credit transferThe standard wire transfer instruction your client's bank sends. You can request the MT 103 reference number from your client as proof of dispatch.
MT 202 COVFinancial institution transfer (cover payment)Used when the remitting bank sends funds ahead via an interbank route — the MT 103 and MT 202 COV travel separately and must be matched at the receiving end.
MT 199 / MT 299Free format messagesUsed for investigations, queries, and amendments once a payment is in transit. If your bank needs to trace a missing SWIFT payment, they initiate an MT 199 query.
gpi (Global Payments Innovation)SWIFT's enhanced tracking layerIntroduced in 2017; provides end-to-end payment tracking with a Unique End-to-End Transaction Reference (UETR). Banks that participate in SWIFT gpi (the majority of major banks as of 2026) can track a payment's position in the correspondent chain in near-real time. Ask your client for the UETR when chasing a late SWIFT payment.

SWIFT Timing and the Cut-Off Problem

SWIFT cross-border payments are not 24/7. Each bank in the correspondent chain operates within its own domestic settlement window — typically aligned with its central bank's RTGS (Real-Time Gross Settlement) system. The US Fedwire system operates 21:30–19:00 ET (with a maintenance window from 19:00–21:30 ET Monday through Friday). The UK's CHAPS system operates 06:00–17:30 London time. A USD-to-GBP wire initiated at 15:00 ET (20:00 London) arrives after CHAPS has closed for the day — adding a full business day to settlement time. For freelancers quoting a payment due date on a cross-border invoice, Net 14 (rather than Net 7) is the minimum sensible window to avoid a technically on-time client sending a payment that arrives a day late through no fault of their own.

SEPA: The EU's Domestic-Grade International System

What SEPA Is and Is Not

The Single Euro Payments Area (SEPA) is a payment integration initiative of the European Payments Council (EPC), operative across 36 countries: the 27 EU member states plus Iceland, Liechtenstein, Norway, Switzerland, Andorra, Monaco, San Marino, Vatican City, and — critically — the United Kingdom (which retained SEPA membership post-Brexit). SEPA payments are euro-denominated only. A GBP-denominated transfer between two UK accounts is a domestic Faster Payments or BACS transaction, not a SEPA transaction. A EUR-denominated transfer from a UK Wise account to a German business account, on the other hand, uses SEPA Credit Transfer (SCT).

SEPA Instruments and Their Timing

InstrumentAcronymSettlementFeeMax Amount
SEPA Credit TransferSCTNext business dayZero (by regulation)None
SEPA Instant Credit TransferSCT Inst10 seconds (24/7/365)Typically zero to minimal€100,000 per transaction
SEPA Direct Debit (Core)SDD CoreD+1 after collectionZeroNone
SEPA Direct Debit (B2B)SDD B2BD+1 after collectionZeroNone

SEPA Credit Transfer is governed by EU Regulation 260/2012 on cross-border payments, which mandates that euro transfers within SEPA carry the same fee structure as equivalent domestic transfers — meaning banks that offer free domestic euro transfers must also offer free SEPA Credit Transfers. Under the EU Instant Payments Regulation (Regulation 2024/886), which entered into force in April 2024 and applies fully from October 2025, PSPs in the eurozone are required to offer SCT Inst and must not charge more for it than for standard SCT. This effectively mandates instant cross-border euro payments at zero marginal cost across the eurozone from late 2025 onward — a significant shift that makes euro-denominated invoicing between EU counterparties considerably more attractive than USD wire.

The practical implication for a freelancer in Berlin invoicing a client in Amsterdam: request payment by SCT Inst, quote a due date of Net 7, and expect cleared funds within seconds of the client initiating the transfer on business days — and within minutes on weekends under the new mandatory SCT Inst regime.

The IBAN: Anatomy and Common Errors

Structure

An International Bank Account Number (IBAN) is defined by ISO 13616:2020. It consists of:

[2-letter ISO 3166-1 country code] + [2 check digits] + [BBAN (Basic Bank Account Number)]

Example (UK): GB29 NWBK 6016 1331 9268 19
· GB = United Kingdom
· 29 = check digits (computed by MOD 97-10 algorithm per ISO 7064)
· NWBK = 4-character bank identifier (NatWest)
· 60 16 13 = sort code (60-16-13)
· 31 92 68 19 = account number

Total length: 22 characters for UK IBANs. Varies by country (DE: 22, FR: 27, IT: 27, NL: 18, IN: not used).

India does not use IBAN. The US does not use IBAN. For payments to Indian accounts, the required fields are the IFSC (Indian Financial System Code) — an 11-character alphanumeric identifier allocated by the RBI, consisting of the bank's 4-character code, a zero, and a 6-character branch code — plus the account number. For payments to US accounts, the required fields are the ABA routing number (9 digits) and the account number, or for international wires, the bank's BIC/SWIFT code. Providing IBAN details to a client sending from the US will cause confusion because their bank's wire form expects routing number + account number, not IBAN. Tailor your payment instructions to the client's banking jurisdiction.

The BIC/SWIFT Code

The Bank Identifier Code (BIC), standardised as SWIFT BIC under ISO 9362, identifies the receiving bank in the correspondent network. Its structure:

[4-character bank code] + [2-character country code] + [2-character location code] + [optional 3-character branch code]

Example: HBUKGB4BXXX
· HBUK = HSBC UK
· GB = United Kingdom
· 4B = London (location code)
· XXX = primary office (branch codes are optional; XXX denotes head office)

Always provide the full 11-character BIC (including the XXX suffix) rather than the 8-character short form on cross-border invoices. Some correspondent bank systems reject 8-character BICs as ambiguous when the branch code is omitted.

FX: Where the Real Cost Hides

The Spread Is the Fee

When a US client sends USD and you receive GBP, a currency conversion happens somewhere in the correspondent chain. The question is not whether you pay for that conversion — you do — but where in the chain it happens and how much spread the converting institution extracts. The mid-market rate (also called the interbank rate, or "Reuters rate") is the rate at which banks trade currency between themselves. It is not the rate you get. The difference between the mid-market rate and the rate applied to your conversion is the FX spread — the implicit fee that banks and payment providers charge for the conversion.

As of June 2026, approximate FX spreads for a GBP/USD conversion on a £5,000 equivalent transaction:

ProviderApproximate SpreadCost on £5,000 equiv.Additional Fees
High-street bank (domestic SWIFT)2.5–4.0%£125–£200£15–£30 SWIFT fee
PayPal (business)3.5–4.0%£175–£2002.99% transaction fee on top
Wise (formerly TransferWise)0.35–0.65%£17–£33Small fixed fee (~£0.80–£3)
Airwallex0.5–1.0%£25–£50None on many corridors
OFX0.5–1.5%£25–£75None above ~USD 10,000
Revolut Business0% (within plan limits)£0Monthly plan fee; weekend markup of ~0.5%

The arithmetic matters. A freelancer converting £60,000 of annual USD billings through a high-street bank at a 3% average spread is paying approximately £1,800 per year in FX costs — more than most freelancers pay for their entire software stack. Switching to a provider at 0.5% spread saves approximately £1,500 annually on the same volume with no change in the underlying work or client relationships.

The OUR / SHA / BEN Instruction

SWIFT wire transfers carry a fee instruction code that determines who bears the correspondent bank charges:

Most banks default to SHA on international wires. Always specify on your invoice: "Please send as OUR (sender bears all charges). Payments received net of bank charges are not accepted as full settlement." This does not guarantee OUR — the client's bank may charge additionally for it — but it establishes the agreed term and gives you contractual ground to issue a supplemental invoice for any shortfall caused by SHA deductions.

Settlement Risk and Value Dating

Settlement risk in FX is the risk that one leg of a currency exchange completes while the other fails — a phenomenon known as Herstatt risk after the 1974 collapse of Bankhaus Herstatt, which failed mid-afternoon on a day when it had received DEM payments but before it had made the corresponding USD payments, leaving counterparties holding unreciprocated delivery obligations. For a freelancer, Herstatt risk in its systemic form is not a direct concern, but the underlying timing mismatch is: on a USD-to-GBP conversion, the USD leg may settle in New York during US business hours while the GBP leg settles through CHAPS in London. If your client's bank initiates the transfer late in the US day, the GBP leg may not credit until the following London business day.

Value dating is a related concept: the date on which cleared funds are actually available in your account versus the date they appear as a pending credit. Under the EU Payment Services Directive 2 (PSD2, Directive 2015/2366/EU), Article 87 requires that, for euro-denominated payments within the EEA, the receiving PSP must ensure the credited amount is available on the value date — the date it is credited to the payee's account. For non-euro cross-border payments, this protection does not apply uniformly and receiving banks may apply a value date one business day after the credit date.

Currency Choice: The Strategic Decision on Your Invoice

The Economic Framework

Denominating an international invoice in a specific currency is a financial decision with a payoff structure that can be expressed precisely. Let S₀ be the spot exchange rate at invoice date, S₁ be the spot rate at payment date, P be the invoice principal in the invoiced currency, and r be your operating currency equivalent. If you invoice in your own currency (say GBP) to a USD client:

Your receipt in GBP = P (fixed, no FX risk to you)
Client's cost in USD = P × S₁ (varies with exchange rate movement)

If GBP/USD appreciates (sterling strengthens), the client pays more USD than budgeted.
If GBP/USD depreciates, the client pays less — you absorb no gain or loss.

If you invoice in the client's currency (USD):

Your receipt in GBP = P ÷ S₁ (varies with exchange rate movement)
Client's cost in USD = P (fixed)

If GBP/USD appreciates between invoice and payment date, you receive fewer GBP.
If GBP/USD depreciates, you receive more GBP.

The choice is therefore a choice about who bears exchange rate variance. Neither is inherently better — it depends on the relative volatility tolerance of each party, their existing currency exposures, and the likely direction of FX movement over the payment window.

The USD Convention and Its Rationale

USD remains the world's dominant invoicing currency for cross-border B2B services, for reasons rooted in the Bretton Woods legacy and maintained by network effects: most international commodity contracts, aircraft leases, and capital market instruments are USD-denominated, meaning the global supply of USD liquidity is deep and persistent. For a freelancer whose clients span multiple countries — some in EUR, some in USD, some in GBP — invoicing all clients in USD simplifies revenue management: you hold one foreign currency balance and convert it periodically at times of your choosing, rather than managing three or four currency exposures simultaneously.

The counterargument: if your operating costs are predominantly in a non-USD currency and you have no natural hedge (i.e., no USD-denominated liabilities), the USD revenue creates a one-way FX exposure that costs you implicitly on every conversion. The optimal choice depends on the magnitude of your annual FX flows. At £50,000+ annual equivalent in cross-border revenues, the difference in conversion strategy becomes material enough to warrant a formal FX management approach — batch conversions, forward contracts, or natural hedging by building a USD reserve to fund USD-denominated software subscriptions and tools.

What to Write on the Invoice

Always write the full ISO 4217 currency code before the symbol on international invoices. "USD $2,000" is unambiguous. "$2,000" alone is not — the dollar sign is used by over 20 currencies including USD, CAD, AUD, HKD, SGD, MXN, and NZD. A client who wires CAD 2,000 instead of USD 2,000 has technically paid a sum — just not the right one. The ISO code removes the ambiguity entirely.

Withholding Tax: The Cost That Arrives Deducted

What Withholding Tax Is

Several countries require the paying party to deduct a percentage of the invoice amount at source and remit it directly to the tax authority before paying the net amount to the foreign supplier. This is withholding tax (WHT) — sometimes called "tax at source" or, in Indian law, Tax Deducted at Source (TDS). It is a mechanism for the payer's government to tax foreign income at the point of payment rather than relying on the foreign supplier to self-report and remit.

For a UK freelancer receiving payment from an Indian client, the standard WHT rate on fees for technical services under Indian domestic law (Section 194J of the Income Tax Act, 1961) is 10%. A USD 5,000 invoice will arrive as USD 4,500, with USD 500 remitted to the Indian Income Tax Department on your behalf. You are still liable for this income in the UK; the USD 500 withholding is a foreign tax credit you can claim against your UK tax liability under the UK-India Double Taxation Convention (DTC), signed 1993.

Tax Treaty Network: The Key Rates

Most countries have bilateral Double Taxation Conventions (DTCs) or Tax Information Exchange Agreements (TIEAs) that reduce or eliminate WHT on services paid to residents of treaty partners. The operative rate is the lower of the domestic WHT rate and the treaty rate. Treaty rates for "fees for technical services" (FTS) or "business profits" from the key corridors:

Payment FlowDomestic WHT (Services)Treaty Rate (if applicable)Key Treaty / Provision
India → UK freelancer10% (s.194J ITA 1961)15% (FTS art.); 0% if "business profits" art. applies and no PEUK-India DTC 1993, Art. 13 / Art. 7
India → US freelancer10% (s.194J ITA 1961)15% (FTS); 0% if Art. 7 applies (no PE)US-India DTC 1989, Art. 12 / Art. 7
USA → UK freelancer0% (no general WHT on services)N/AUS does not withhold on B2B services to treaty partners generally
USA → Indian freelancer30% (IRC § 1441 on FDAP income)0% if "business profits" Art. 7 applies (no US PE)US-India DTC 1989, Art. 7; Form W-8BEN-E required
Germany → non-EU freelancer0–15% (§ 50a EStG; varies by income type)Reduced or 0% under applicable DTC§ 50a EStG; specific DTC
Singapore → foreign freelancer17% standard CIT rate applied to service fees; s.45 ITAVaries; many Singapore DTCs reduce to 0–5%Singapore ITA, s.45; applicable DTC
Australia → foreign freelancer0% (no WHT on service fees generally)N/AITAA 1997; WHT applies mainly to royalties, dividends, interest

The Permanent Establishment Test: Why It Matters

Most bilateral DTCs allocate taxing rights over "business profits" to the country of the service provider's residence — meaning the UK freelancer pays UK tax on their income and the Indian client owes no WHT — unless the freelancer has a Permanent Establishment (PE) in the client's country. PE is defined under Article 5 of the OECD Model Tax Convention and in each bilateral treaty. For a freelancer working remotely from their home country, the PE threshold is almost never triggered: a PE typically requires a fixed place of business, an agent with authority to conclude contracts on the supplier's behalf, or a construction site exceeding a defined duration (typically 12 months under the OECD Model). A freelancer who visits a client's office in Mumbai for a two-week discovery sprint and then completes the work in London does not have a PE in India.

The practical implication: if you are receiving payments from India and your Indian client is deducting WHT at 10% under s.194J, you may be entitled to 0% under Article 7 of the UK-India or US-India DTC on the grounds that your income is "business profits" with no Indian PE. To claim this, you must provide your client with a Tax Residency Certificate (TRC) — issued by HMRC (UK) or the IRS (US) — and a Form 10F declaration (as prescribed by the Indian Income Tax Department), confirencing your treaty eligibility. With these documents, your Indian client is legally entitled to deduct 0% WHT rather than 10%. Without them, the 10% deduction is mandatory under Indian domestic law regardless of the treaty.

Claiming the Foreign Tax Credit

Where WHT is deducted despite your best efforts — because the client's finance team is unfamiliar with treaty provisions, or because the documentation arrived after the payment was processed — the amount withheld is not lost. It is a foreign tax credit claimable against your domestic tax liability, subject to the credit limit rules of your home jurisdiction:

To claim the credit you will need: (1) documentary evidence of the WHT deducted (typically a TDS certificate — Form 16A in India — issued by the client), (2) confirmation that the income on which WHT was deducted is the same income being taxed in your home jurisdiction, and (3) the relevant entries on your domestic tax return. Keep all TDS certificates, withholding receipts, and cross-border payment confirmations for at least six years (the UK's standard HMRC enquiry window) or longer if the relevant DTC's MAP (Mutual Agreement Procedure) provisions contemplate longer periods.

What the Invoice Must Contain for Cross-Border Compliance

The Mandatory Fields

A cross-border invoice has more required fields than a domestic one. The exact requirements depend on your jurisdiction and the client's, but the following represent a robust standard that satisfies audit requirements in the UK, EU, India, and Australia simultaneously:

FieldWhy It Is Required
Your full legal name and addressEstablishes your tax residency — the foundation of any treaty claim
Your tax registration number (VAT no., GST no., ABN, PAN/GSTIN)Required by client's AP for their own input tax claims; also proof of your registration status
Client's full legal name, address, and tax numberRequired for reverse charge and zero-rating documentation; India requires client PAN for TDS returns
Invoice number (sequential)Required for GST/VAT audit trail in every jurisdiction
Invoice date and payment due dateDue date triggers statutory interest in UK/EU/SG; invoice date determines the exchange rate for accounting
Description of servicesMust be specific enough to confirm the supply is a "service" not a "royalty" — the distinction affects WHT rates under most DTCs
ISO 4217 currency code + amountAvoids dollar-symbol ambiguity; required by most jurisdictions' tax legislation for invoices in foreign currency
Tax treatment statementZero-rating basis (VAT: "outside scope — s.7A VATA 1994" / "reverse charge — Art. 44 EU VAT Directive"); or "VAT not applicable — below registration threshold"
Your bank details (IBAN + BIC, or routing + account, or IFSC + account)Tailored to client's banking jurisdiction; include OUR instruction
Late payment clause referenceRequired for statutory rate to apply (UK/EU/SG); required for contractual rate to be enforceable (USA/CA/AU)
Governing law statementOne line; removes ambiguity in multi-jurisdiction disputes

The "Service vs. Royalty" Distinction

This is the most practically important characterisation question in cross-border freelance invoicing, and the one most frequently ignored. Under most bilateral DTCs following the OECD Model, "royalties" — defined in Article 12 as payments for the use of, or the right to use, intellectual property — are subject to WHT at a reduced treaty rate (typically 10–15%), whereas "business profits" from services (Article 7) are taxable only in the service provider's country of residence when there is no PE. The distinction determines whether WHT applies to your invoice at all.

If you transfer copyright in a deliverable to the client — as most freelance creative contracts do — and the client characterises that transfer as a "royalty" (payment for the right to use IP), they may deduct WHT even where it would not apply to a pure service fee. The counter-characterisation, which is legally supportable in most cases, is that a one-time lump-sum payment for a bespoke deliverable with full copyright assignment is a service fee, not a royalty — because you are being paid for the work of creating the deliverable, not for licensing a pre-existing right. Your invoice description reinforces this: write "Professional services: [specific deliverable]" rather than "Licence fee for [deliverable]" or "Copyright transfer fee." The former characterisation points toward Article 7; the latter invites an Article 12 royalty analysis with associated WHT.

Common Cross-Border Payment Failures and Their Causes

The Payment Arrives Short

Cause: SHA fee instruction (correspondent banks deducted their fees from principal) or FX spread extracted at an unfavourable rate by the sending bank. Resolution: issue a supplemental invoice for the shortfall, citing the OUR instruction in the original invoice terms. For large recurring clients, negotiate an OUR fee arrangement at the contract stage.

The Payment Does Not Arrive

Cause: compliance hold at a correspondent bank; incorrect IBAN or BIC; name mismatch between the beneficiary name on the SWIFT instruction and the account name at the receiving bank (a common issue where the freelancer trades under a business name that does not match their personal account name). Resolution: ask the client for the SWIFT UETR reference and request an MT 199 trace from your receiving bank. If the hold is compliance-related, your bank will need to provide the correspondent with documentation confirming the payment's legitimate commercial purpose — a copy of the contract and invoice is typically sufficient.

The Payment Is Returned

Cause: invalid IBAN (failing the MOD 97-10 check digit), wrong BIC, or the receiving bank has rejected the payment due to a compliance flag. SWIFT return codes appear in the MT 103 return message — code AC01 indicates an invalid account identifier; code AC04 means the account is closed; code DUPL indicates a suspected duplicate. Resolutions depend on the code: AC01 requires verifying and reissuing your bank details; DUPL requires confirming with the client that both payments were intended.

The Payment Attracts Unexpected WHT

Cause: client's finance team applied domestic WHT rates without checking the applicable DTC, or your treaty documentation was not provided in advance. Resolution: provide TRC and Form 10F (for India) or equivalent documentation retroactively; request a revised TDS certificate and claim the foreign tax credit on your domestic return. For future invoices, issue the treaty documentation before the payment date — Indian withholding obligations crystallise at the time of payment or credit, whichever is earlier, and retroactive correction is administratively burdensome for the client's finance team.

Practical Payment Rail Recommendations by Corridor

CorridorRecommended RailWhy
UK ↔ EU (EUR)SEPA SCT / SCT InstMandatory zero-fee, next-day or instant; no FX cost if both parties hold EUR accounts
UK ↔ EU (non-EUR)Wise Business or AirwallexBest mid-market FX rate; faster than SWIFT; lower fee than bank
UK / EU → USAWise or Airwallex (outbound); SWIFT OUR (inbound)For inbound USD: client wires in USD to your Wise USD account, you convert at mid-market rate on your schedule
USA → UK / EUWire to Wise USD account; convert to GBP/EUR via WiseAvoids bank FX spread on conversion; SWIFT gpi trackable
India → AnySWIFT (most common); Razorpay/Payoneer for smaller amountsSWIFT for large invoices (FIRC issued by bank — required for GST zero-rating proof); Payoneer acceptable for sub-$1,000 with appropriate documentation
Any → IndiaSWIFT with IFSC + account numberIndia does not use IBAN; IFSC is required; receiving bank issues FIRC/FIRA as proof of foreign remittance receipt
Singapore ↔ AnyFAST (domestic, SGD); Wise or Airwallex (cross-border)Singapore's domestic FAST system (PayNow) is instant; cross-border SGD transfers still predominantly SWIFT
Australia ↔ AnyNPP (domestic, AUD); Wise or OFX (cross-border)Australia's New Payments Platform (NPP) provides instant domestic AUD; OFX offers competitive rates for AUD cross-border at higher volumes

The FIRC: Why Indian Freelancers Need It

A Foreign Inward Remittance Certificate (FIRC) — now more commonly issued as a Foreign Inward Remittance Advice (FIRA) in electronic form by authorised dealer banks under the Foreign Exchange Management Act 1999 — is the documentary proof that foreign currency was received by an Indian exporter of services. It is not optional. Without a FIRC/FIRA:

The FIRC is issued by the authorised dealer bank (AD bank) that credits your account with the foreign remittance — typically within 2–5 business days of the credit. Request it proactively rather than waiting for the bank to issue it. If you receive payment through Payoneer or a similar wallet rather than a direct bank SWIFT transfer, the AD bank does not issue a FIRC; instead, you receive a payment certificate from Payoneer, which the GSTN portal and many export benefit administrators accept as an equivalent — but confirm with your GST consultant that this is acceptable in your specific context before relying on it.

Structuring the Cross-Border Invoice: A Worked Example

A UK freelance UX designer invoicing a US startup client for a four-week engagement:

INVOICE
Invoice No.: 2026-047
Invoice Date: 23 June 2026
Payment Due: 7 July 2026 (14 calendar days)

FROM:
Jane Smith (trading as Smith Design Studio)
14 Clerkenwell Road, London EC1M 5PA, United Kingdom
UTR: [your Unique Taxpayer Reference]
Not VAT registered (below £90,000 threshold — no VAT charged on this invoice)

TO:
Acme Inc.
500 Third Avenue, New York, NY 10016, United States
EIN: [client's Employer Identification Number — request from client]

SERVICES:
Professional UX design services — user research, wireframing, and prototype delivery for the Acme onboarding flow (2 June – 20 June 2026)
USD $8,400.00

TAX: This supply is outside the scope of UK VAT. No VAT is charged.

TOTAL DUE: USD $8,400.00

PAYMENT INSTRUCTIONS:
Please wire in USD to:
Account Name: Jane Smith
Bank: Wise (formerly TransferWise), 6th Floor, One London Wall, London EC2Y 5EB
IBAN: GB[XX] TRWI [sort code] [account no.]
BIC/SWIFT: TRWIGB2LXXX
Routing No. (ACH/Wire): 026073150 (for US-originated wires to Wise UK)
Reference: Invoice 2026-047
Please send as OUR (sender bears all bank and correspondent charges).
Payment received net of charges is not accepted as full settlement.

LATE PAYMENT: Overdue amounts accrue interest at 1.5% per month (18.00% per annum), calculated daily. Governing law: England and Wales.

INTELLECTUAL PROPERTY: All IP rights in deliverables transfer to Acme Inc. upon receipt of cleared payment in full.

This guide reflects SWIFT network mechanics, FX market structures, tax treaty provisions, and payment legislation as of June 2026. FX spreads are indicative and change with market conditions. Withholding tax rates and treaty provisions are subject to renegotiation; always verify the current treaty text and applicable domestic rate with a qualified tax adviser before relying on a specific WHT rate. Indian GST zero-rating rules, FIRC/FIRA issuance procedures, and LUT renewal requirements reflect CBIC guidance as of June 2026 and are subject to amendment. Nothing here constitutes legal or tax advice.