How to receive EUR payments as an international freelancer: invoice, details, fees and reconciliation

Start with the entity that owes the money. A client brand, a project manager, and the legal company shown on a contract are not always the same person or entity. The contract or written agreement should identify the payer, the service or deliverable, the agreed amount, the currency, the due date, any milestone conditions, and the address or tax details that the parties genuinely need. If the client pays through an agency, marketplace, employer-of-record, or another entity, ask which name will appear in the remittance information so the payment can be matched later.

The invoice then repeats the payment facts in a format the payer can process: invoice number, issue date, due date, EUR amount, description of work, tax treatment only where it is accurate for your situation, beneficiary name, and the current payment instruction. Do not describe an invoice as paid because a client says finance will handle it. Payment is an operational event with an instruction, approval, submission, processing and settlement trail. A concise instruction reduces ambiguity without pretending to control the bank route.

Open the official account interface and verify the exact receiving feature you intend to use. Confirm the account holder name, whether the account is personal or business, whether it can receive EUR under its current terms, whether the displayed details are current, and whether the feature fits the type of payer and work you are invoicing. A provider can change eligibility, request further verification, limit a route, or remove a currency feature. Do not treat an old payment confirmation, a friend’s account, or a marketing page as permission to accept a client payment.

Keep the beneficiary name exact. A client finance team may reject a mismatch between an invoice name and the account-holder name, while a payment sent to the wrong or stale details can be difficult to correct. If your legal business name, trade name, tax registration, or residence has changed, update the necessary records through official procedures before you issue a new instruction. Never borrow another person’s account to bypass an eligibility or verification question; that can create compliance, ownership, tax, and recovery problems for everyone involved.

For a first payment, send one version-controlled message from the business channel you normally use. Attach or link the invoice, repeat the beneficiary name and required account identifiers, specify the invoice reference, and state the amount in EUR. If the client uses a portal, upload the same current document there and retain the submission confirmation. Avoid answering a last-minute request to change bank details only through an unexpected email, messaging account, or voice call; payment-instruction substitution is a common fraud pattern.

Tell the payer how to verify a change. For example, ask them to use a previously known business email address or a scheduled call with a known contact, not a phone number contained only in the change request. This protects both sides. You are not asking the client to reveal their banking credentials; you are creating a simple authentication step before funds are routed. If finance needs fields you do not understand, ask what the field means and check it in your own official account documentation rather than improvising data.

SEPA is a group of payment schemes and participating jurisdictions, not a universal synonym for any EUR transfer. A client may have an IBAN-based instruction and still use a route, charges option, approval process, or institution configuration that is different from what you expected. The payer’s bank or provider determines what options it offers; your receiving institution determines what it accepts; other institutions may be involved depending on the transaction. Ask the payer to select the route their institution supports and use the details your own account explicitly shows for receiving EUR.

For a client outside the usual SEPA context, the route may require additional information or travel through a different correspondent or provider network. That does not automatically mean it is unsafe or expensive, and it does not prove the funds will arrive unchanged. It means the instruction deserves a pre-flight check: currency sent, beneficiary name, account identifier, required routing data, charges treatment if the payer can choose it, and the client’s internal approval timing. Do not claim a fixed cost or speed unless the relevant institutions state it for the exact transaction.

When a payment has not appeared, separate three questions: was the invoice approved, was a payment instruction submitted, and has the receiving institution credited the funds? Ask the client for the sending date, amount and currency, payer legal entity, beneficiary name used, payment reference, route selected, and the official trace or reference available through their institution. Compare those facts with your invoice and the account details you supplied. A screenshot saying “completed” can be useful context, but it is not a substitute for the transaction reference that the sending institution can trace.

Do not ask the client to send a duplicate payment while the first payment is unresolved unless both sides have agreed a controlled process for the risk of double payment. Likewise, do not send a refund based only on an email that claims a payment was made or reversed. Work through the official support channels and keep the case reference, dates, and non-sensitive documents in one folder. Delays can come from ordinary cut-offs, checks, corrections, or other route-specific events; they are not enough by themselves to establish fraud or a service failure.

If you invoice in EUR but spend, pay tax, or hold reserves in another currency, there are at least two separate decisions: whether you accept EUR into the receiving account and when, how, and at what disclosed rate you later convert it. A visible transfer fee is only one possible cost. There may also be an exchange-rate margin, an intermediary deduction, a receiving charge, a payment-platform charge, or a contractual withholding. Which of these applies depends on the exact providers, account types, route, countries, and transaction at the time.

Handle a shortfall using the agreement and evidence. If the contract says the client owes a fixed EUR invoice amount, show the invoice, payer confirmation, account statement, and any identified deduction before discussing a balance. If the contract says a platform or payment method settles net of its charges, record that treatment rather than relabelling it later. Do not use a generic online fee table as proof. For future invoices, revise the payment clause or route only after both sides understand the actual result.

Treat invoices and payment instructions as sensitive business documents. They can reveal your name, address, tax identifier, account identifiers, work relationship, and payment cadence. Send them through a channel where you already know the client contact, restrict access to shared folders, and remove unnecessary personal data from templates. A client needs enough information to pay the invoice; they do not need your account login, balance, full statement, recovery code, passport scan, or a broad screen recording of the banking app.

Be especially careful when someone asks to change beneficiary details, resend an invoice to a new address, or use a new finance contact shortly before a payment. Verify the request using a known contact path that predates the message. Turn on account protections offered by the institution, use a unique password and strong authentication, and preserve recovery options securely. These steps reduce risk but do not guarantee that a payment or account will be safe; if you suspect account compromise, contact the institution through a verified official route promptly.

Create one record per invoice: client and legal payer, contract or order, work period, invoice number, EUR amount, issue date, due date, payment instruction version, payer confirmation, receiving statement entry, any conversion record, and correspondence about a discrepancy. Reconcile the paid or credited date separately from the invoice date. This gives you a practical view of cash flow and makes it easier to answer a genuine request from an accountant, tax professional, institution, or client without mixing unrelated transactions.

This guide is general information, not financial, tax, legal, or compliance advice. Your obligations can depend on residence, business structure, VAT or similar tax treatment, client location, services supplied, currencies held, and reporting thresholds. Do not hide income, alter invoices to misdescribe work, or use someone else’s account to avoid a requirement. If you are unsure how to invoice, report income, or document a foreign-currency payment, use current official guidance and a qualified professional who can assess your actual facts.