International wires for a US LLC: bank instructions, fees and tracking

Prepare international receipts and payments with complete bank instructions, a clear fee calculation and tracking through to the LLC's account credit.

An international wire lets a US LLC send or receive funds between banks in different countries through a complete banking instruction. An account number alone is not enough. The ordering party may need the beneficiary, the beneficiary bank, the currency, the payment purpose and, where the route requires it, an intermediary bank connecting the institutions.

The payment is most predictable when everyone uses the exact instructions issued for that account and currency. Reusing EUR details for USD, shortening the LLC's beneficiary name or adding an intermediary from an old payment can alter the route. Current bank documents, a clear invoice reference and a final review make wires a strong tool for international business.

What an international wire is

A wire is a bank transfer processed through instructions exchanged between financial institutions. Cross-border wires commonly use the SWIFT network, while certain currencies may also travel through local payment rails offered by the account provider.

It is different from:

• ACH, which moves dollars through the US domestic clearing system;
• SEPA, used for qualifying euro transfers;
• a card payment;
• an internal movement between balances at the same provider.

One LLC can use all of them. A US client may pay by ACH, a European customer may use SEPA to an approved EUR account and a supplier in another corridor may be paid through SWIFT.

The parties in the payment chain

An international wire can involve:

1. Ordering customer: the person or company sending the money.
2. Originating bank: accepts and sends the payment instruction.
3. Intermediary or correspondent bank: bridges institutions or provides settlement in the chosen currency.
4. Beneficiary bank: services the destination account or handles the final credit.
5. Beneficiary: the LLC, supplier or person receiving the payment.

Not every wire asks the user to enter an intermediary. If the official receiving instructions provide one, copy it exactly. If they do not, do not add a bank merely because it appeared on a previous transfer. Correspondent routes can differ by currency, product and current banking agreement.

Fields in complete wire instructions

A receiving-details document or bank letter may contain:

• exact beneficiary legal name;
• beneficiary physical address;
• account number or IBAN;
• beneficiary bank name and address;
• SWIFT/BIC;
• intermediary bank name, address and BIC, if shown;
• currency accepted through those details;
• payment reference, memo or “for further credit” text;
• country, name or payment-purpose instructions.

Not every country uses IBAN. A US account may use an account number plus routing or SWIFT information depending on the rail. Australia may use a BSB, while other destinations have their own local identifiers. The sender should map each value to the correct field rather than placing every available code into whichever box is open.

The beneficiary name must match

When the LLC receives payment into a directly held account, the payment instructions should identify the legal or otherwise accepted beneficiary name held by the financial institution. The payer should not replace it with the founder's name, a brand or an abbreviation unless the provider explicitly accepts that name.

Addresses matter as well. Some international-wire products ask for a verified business physical address and will not use a PO Box. That operating address can be outside the United States when it reflects the verified reality of the business. It is not automatically the Registered Agent address.

Before the first payment, compare:

• invoice issuer;
• beneficiary shown on bank instructions;
• beneficiary entered by the sending bank.

They should describe the same commercial counterparty.

What the intermediary bank does

An intermediary bank provides correspondent access when the originating and beneficiary banks do not settle directly with one another in the relevant currency.

It may receive the payment message and funds, perform its controls, deduct a charge and pass the payment to the next institution. It does not become the customer or vendor; it is one part of the payment route.

Instructions can therefore show three distinct sections:

• Intermediary bank: correspondent name, SWIFT/BIC and address.
• Beneficiary bank: destination institution, SWIFT/BIC and address.
• Beneficiary: LLC legal name, account or IBAN and physical address.

The hierarchy matters. Entering the LLC's account as though it belonged to the intermediary, or using the correspondent BIC as the beneficiary-bank BIC, creates a different instruction.

Currency-specific details

Multi-currency access does not always mean one set of details works for every currency.

An account may provide:

• US domestic details for ACH and domestic wire;
• separate SWIFT USD receiving instructions;
• an IBAN for local EUR receipts;
• GBP or CAD local details;
• international details that convert funds on receipt.

Relay, for example, distinguishes Local Network details for selected currencies from SWIFT receiving details and directs customers to use the live information shown for the chosen currency. Slash allows business users to retrieve bank documents and deposit details from their account. In either case, the current provider document should control over an old saved template.

Under Relay's currently documented incoming route, receipts in other currencies convert to USD: EUR receiving details do not mean the account retains EUR.

Products, partners and eligibility can evolve. Exentax can design the banking and payment architecture, prepare the file and follow the application, while the provider retains final control over approval, activation and account instructions.

Receiving and sending use different evidence

To receive, the LLC gives a customer or counterparty its approved instructions, identifies the currency and requests a useful invoice reference.

To send, the LLC obtains the supplier's receiving details before adding the payee. A portal download or bank-issued letter is more reliable than numbers pasted into an informal message.

The first payment to a new beneficiary deserves a disciplined review:

• confirm the details through an independent channel;
• make sure the invoice belongs to that supplier;
• verify the contractual currency;
• ask whether the bank account has recently changed;
• agree who bears the charges;
• consider an appropriate test amount where the context permits.

Once the payee has been verified, future payments can reuse a controlled beneficiary record while still checking for notified changes.

Design my banking structure

Fees: sent amount and received amount can differ

Several costs may appear in one wire:

• originating-bank fee;
• intermediary deduction;
• receiving fee;
• FX conversion;
• spread between a reference rate and the executed rate;
• subscription or provider pricing.

Some bank forms offer OUR, SHA or BEN charge options. Broadly, OUR is intended to charge the sender, SHA shares charges and BEN deducts them from the beneficiary. Availability and final treatment depend on the institutions, route and currency. Even an OUR selection should not be treated as a universal guarantee of the exact net amount without bank confirmation.

If the beneficiary must receive EUR 10,000, agree the currency, route and allocation of charges first. A EUR 9,975 credit leaves EUR 25 to explain: it might be a documented bank fee, a partial payment or a conversion difference. Check the statement and payment confirmation. Do not automatically reduce the invoice or book a fee simply because the two amounts differ.

Invoice currency, sent currency and credited currency

A cross-border payment can involve three numbers:

• amount invoiced;
• amount ordered;
• amount credited after fees or conversion.

The LLC may invoice in EUR and elect to receive converted USD, or invoice and retain USD. The key is knowing where the conversion occurs and which institution sets the executed rate.

Keep the invoice, instruction, separate charges, deductions and final credit together. The worked example below shows how to connect them without counting a fee twice.

A good payment reference

The memo should let the beneficiary recognise the commercial purpose. INV-2026-184 / customer name is more useful than “payment” or a long sentence that may be truncated.

If the receiving bank supplies mandatory “for further credit” text, a virtual-account reference or another identifier, it should come before the optional invoice memo. Omitting it can leave the bank holding the funds while it determines the final account.

The LLC can standardise:

• invoice-number format;
• maximum memo length;
• labels for owner contributions;
• labels for own-account transfers;
• documentation required from suppliers.

An owner funding the LLC should not use a customer invoice reference. The record should identify the real transaction as a contribution, loan or another supported category.

Tracking an international wire

To trace a SWIFT wire, ask the originating bank for its payment confirmation, the UETR and the beneficiary-credit status. The pacs.008 message uses ISO 20022; MT103 still appears in historical records and some banks' customer confirmations. A document carrying either name is not, by itself, proof that the LLC has available funds.

Those records can identify:

• value date, amount and currency;
• ordering party;
• beneficiary;
• participating banks;
• payment reference;
• payment tracking identifier and status.

When an expected timeline has passed, the investigation normally begins with the originating bank because it created the instruction. The beneficiary provides the expected account, amount, date and reference. Keeping one bank reference throughout the conversation prevents separate teams from investigating different transfers.

Why a wire may be delayed or returned

An exception does not make international wires an unreliable business tool. It normally identifies a field that needs correction or a transaction review that needs evidence.

Common causes include:

• unsupported beneficiary name;
• incomplete address or a PO Box where a physical address is required;
• incorrect IBAN or account number;
• beneficiary-bank BIC entered incorrectly;
• required intermediary omitted;
• receiving details for the wrong currency;
• country or business activity outside current provider coverage;
• unclear purpose of payment;
• request for an invoice, contract or source-of-funds explanation.

The effective response is to rebuild the instruction from the current bank document and answer the specific question, rather than resending the same unverified fields.

Two worked examples

European customer pays a USD invoice

The LLC invoices USD 12,000 and shares current USD SWIFT instructions listing beneficiary, beneficiary bank and intermediary. The customer enters the invoice reference and applies the agreed charge option.

In this illustrative example, the LLC keeps the invoice, instructions, bank confirmation and account credit. If USD 11,975 arrives and the record identifies a USD 25 fee, it separates that fee from the receipt and checks who agreed to bear it. Without that evidence, USD 25 remains an unexplained difference.

LLC pays a supplier in EUR

The supplier invoices EUR 4,800 and provides its legal name, address, IBAN and BIC. Before choosing SWIFT, the LLC checks whether its banking setup offers a suitable local EUR rail.

If it uses a wire, it retains the executed FX rate, USD amount debited, charges and invoice reference. The cost of the purchase consists of the supplier invoice plus documented banking costs.

Pre-send checklist

• Does the beneficiary match the invoice and account?
• Is the physical address complete?
• Does the currency match the selected details?
• Is the IBAN or account number exact?
• Does the SWIFT/BIC belong to the stated bank?
• Is an intermediary listed in the bank document?
• Is all mandatory reference text included?
• Have the parties agreed who bears the charges?
• Does the purpose describe a real business transaction?
• Has the approver reviewed both payee and amount?

A worked example: separate charges from deductions

This illustration uses EUR throughout, with no currency exchange. The originating bank charges the sender EUR 15 separately, and the confirmation records a EUR 10 intermediary deduction from the principal. The invoice reference is INV-2026-184.

The sender's calculation is 8,500 + 15 = EUR 8,515. The beneficiary's calculation is 8,500 − 10 = EUR 8,490. Subtracting the EUR 15 again from the credit would deduct a charge already paid separately. For a different charging arrangement, rebuild the calculation from that bank's confirmation.

The invoice and credit still differ by EUR 10. If the customer agreed to bear every charge, that amount may remain receivable. If the LLC bears the evidenced fee, the revenue and bank expense may instead be recorded separately. The commercial agreement and supporting records determine the treatment; selecting OUR does not settle that accounting question.

Receiving account versus final beneficiary: reading FFC

With a directly held account, the bank beneficiary will normally be the LLC. Some collection routes instead use an intermediary's account and for further credit, or FFC, instructions to allocate the receipt to the final customer. The receiving account holder and the LLC may therefore belong in different fields.

Do not overwrite the provider's stated beneficiary with the LLC's name merely to match the invoice. Keep evidence linking the collection arrangement to the business, reproduce the mandatory reference and ask the sending bank how to enter it if the form has no suitable field. The invoice identifies the actual seller; the receiving instructions explain the collection route.

A correspondent bank and a collection account are not interchangeable concepts. A correspondent BIC is neither the LLC's account number nor a subaccount reference. Each field has a purpose. Exentax helps you choose the route and prepare instructions that customers and suppliers can use without guessing.

ISO 20022 and addresses: preparing the next payments

Swift's MT/ISO 20022 coexistence period for CBPR+ interbank payment instructions ended on 22 November 2025. In 2026, request the confirmation the bank actually provides rather than insisting on an MT103 alone.

The next milestone is 14 November 2026. The announced CBPR+ change permits structured or hybrid addresses with the town and country identified. This is preparation for that date, not a requirement to move the LLC's operations to the United States or a rule determining its tax residence.

Use the recipient's verified name, street, town, postal code and country in their proper fields. Do not put the bank's town in the company's address or assume the Registered Agent address is the operating address. Your bank specifies the details needed for the selected route.

Review saved payees before the next recurring payment and obtain any missing information from the supplier. A current instruction sheet supports both the first wire and repeat payments. The business owner does not need to build a banking message: they need complete recipient details that their bank can transmit correctly.

Common questions about international wires

Is an intermediary bank always required?

No. Use it when the official instructions show one or the originating bank requires it for the route. Do not invent one.

Does a routing number replace a SWIFT/BIC?

No. They serve different networks and contexts. Follow the destination instructions.

Can a US LLC receive EUR?

Yes, when it has an approved EUR receiving route. That may be an IBAN using SEPA or an international route with conversion, depending on the provider.

What should I request when a SWIFT payment has not arrived?

Ask the ordering party for the available bank confirmation and UETR, plus amount, currency, value date and credit status. Depending on its channel, the bank may provide a pacs.008 confirmation or a receipt labelled MT103.

Must the intermediary bank appear on the invoice?

Not necessarily. The invoice documents the commercial relationship; the bank instructions describe the payment route. They should identify the same final beneficiary.

Is a wire the best rail for every payment?

No single rail is. Currency, amount, urgency, fees and local alternatives determine whether SWIFT, ACH, SEPA or another route is most efficient.

A banking structure that expands the LLC's reach

International wires give a US LLC access to customers, suppliers, investment accounts and currencies beyond one domestic network. They are one component of a broader operating structure.

The strongest setup gives each rail a role: ACH for domestic dollars, SEPA for local euro movements when available, SWIFT for international corridors and consistent evidence across all of them. With current instructions, useful references and bank-issued tracking, the LLC can move funds internationally with control and explain every transaction professionally.