How to Invoice a Foreign Client: a Step-by-Step Guide for Ukrainian FOPs

Currency supervision: what the bank checks

Every foreign-currency payment landing on a FOP account passes through your bank’s currency supervision. The bank is obliged to understand where the money comes from and on what basis, so it may request supporting documents — most often the contract and the invoice, sometimes an act of services rendered. This is routine procedure, not suspicion: the tidier your documents, the less often the bank asks anything at all.

Limits, crediting timelines and settlement deadlines change periodically and depend on the current NBU regulations and your specific bank’s policy. That is why this guide deliberately avoids numbers that would be stale in six months: before the first sizeable payment, write to your bank’s support and ask directly which documents they want to see and at which amounts. Ten minutes of chat saves weeks of unblocking.

The one practical principle is consistency. The name on the invoice equals the name at the bank. The payment amount equals the invoice amount. The payment reference mentions the invoice or contract number. The service description matches the contract and your KVEDs. Most currency-control "freezes" are not violations — they are mismatches that could have been removed at the drafting stage.

How the money travels: SWIFT, Wise, Payoneer, marketplaces

There is no universally best route — only trade-offs between speed, fees and paperwork. The four most common options for Ukrainian FOPs.

English invoice template (copy and fill in)

A complete invoice template for a foreign-currency payment. Copy it, replace the bracketed placeholders with your details — field-by-field notes follow below.

INVOICE No. [2026-014]

Date:     [July 25, 2026]
Due date: [August 8, 2026] (Net 14)

FROM (Contractor)
Individual Entrepreneur [Olena Shevchenko]
(ФОП [Шевченко Олена Петрівна])
Tax ID (RNOKPP): [1234567890]
Address: [12 Peremohy Ave., apt. 34, Kyiv, 03057], Ukraine
Email: [[email protected]]

TO (Client)
[Acme Software GmbH]
Registration No.: [HRB 123456]
Address: [Beispielstrasse 7, 10115 Berlin, Germany]

Under the Services Agreement No. [3] dated [February 2, 2026]

---------------------------------------------------------------------
 DESCRIPTION                             QTY     RATE        AMOUNT
---------------------------------------------------------------------
 [UI/UX design services for the Acme
 web application, June 2026:]
   [Dashboard redesign (Figma)]         [46 h]  [USD 40.00] [USD 1,840.00]
   [Design system components]           [22 h]  [USD 40.00] [USD   880.00]
---------------------------------------------------------------------
                                        TOTAL DUE:          [USD 2,720.00]
---------------------------------------------------------------------

PAYMENT DETAILS
Beneficiary: [FOP Shevchenko Olena Petrivna]
IBAN: [UA_________________________]
Bank: [bank name], [Kyiv, Ukraine]
SWIFT/BIC: [________]
Correspondent bank (for USD, if required by your bank):
[correspondent bank name, SWIFT]
Payment reference: Payment for services under Invoice No. [2026-014]

All bank charges outside the beneficiary bank are borne
by the Client (OUR).

Contractor: ______________________ [Olena Shevchenko]

Field-by-field notes

Invoice No. / Date / Due date

Sequential numbering (a year-number format like 2026-014 works well), the issue date and the payment deadline. Net 14 means payment within 14 days of the invoice date.

FROM

You: name in Latin script exactly as at your bank, the Individual Entrepreneur status, address, RNOKPP as Tax ID. The Ukrainian spelling in brackets is optional but keeps your document set consistent.

TO

The client: legal name, registration number and address — word for word as in the contract.

Agreement reference

The contract number and date tie the invoice to the legal basis of the payment — the link your bank looks for first.

Description / Qty / Rate / Amount

Service lines: a concrete description, the quantity (hours, items, months), the rate and the line amount. The summary line is TOTAL DUE with the currency.

PAYMENT DETAILS

Beneficiary — your name in Latin script; IBAN — your FOP foreign-currency account (UA…); bank name and SWIFT/BIC; for USD, the correspondent bank if your bank requires one. Take the details from your online banking — they are already in the right format there.

Payment reference

Ask the client to quote the invoice number in the payment reference — the simplest way for the bank to immediately understand what the money is.

Bank charges (OUR / SHA)

OUR — the sender covers all banks’ fees; SHA — fees are shared. On smaller amounts the difference is noticeable: agree on OUR in the contract if you want to receive the invoice amount without deductions.

Five mistakes that get payments stuck

1. 1

   No SWIFT or incomplete bank details

   An IBAN without the bank name and SWIFT/BIC — and the client’s payment system refuses to send, the client writes to you, you hunt for details, minus two days. Ship the full PAYMENT DETAILS block the first time.

2. 2

   A description that says "services under the contract"

   The bank sees a payment "for services" with no substance — and requests documents. The tax office sees a mismatch with your KVEDs — and requests explanations. A concrete description with the period closes both questions before they are asked.

3. 3

   The amount disagrees with the contract

   One rate in the contract, another on the invoice; or the invoice total does not reconcile with the act. Every mismatch multiplies the correspondence with the bank. Keep the contract, the invoice and the act in sync — or generate them from the same data.

4. 4

   No due date

   An invoice without a payment deadline creates no deadline — and gets paid last in the queue. An explicit due date plus a polite reminder a few days before it measurably shortens the average time to payment.

5. 5

   Inconsistent spelling of your name

   Olena / Elena / Оlena with a Cyrillic "О" — the same person to a human, three different people to bank compliance. Check the spelling in your passport, bank, contract and invoice once, and keep it as the single standard everywhere.

Invoicing without the manual work: how CrewDriven does it

The second invoice to a foreign client is easier than the first. The tenth is hard again: the numbering drifts, different clients have different rates, someone pays in EUR and someone in USD, and at the end of the month you need to know who paid, who is overdue and how much you actually earned per client.

CrewDriven closes that cycle: invoices in USD, EUR or hryvnia with automatic sequential numbering, logged hours flowing into invoice lines at each client’s rates, payment statuses tracked, and every payment landing in a per-client P&L with the exchange rate captured. You see not just "how much was invoiced" but "how much was earned" — after fees and currency differences.

For Ukrainian corporate clients you will also need an act of services rendered — keep our work completion act guide and template with a ready Ukrainian and bilingual template at hand. For how the full free invoicing cycle works in the platform, see the free invoicing system overview. And you can create your workspace in a minute — free during the launch period.

Frequently asked questions

Does an invoice need a stamp and a signature?

In international practice — no: an invoice is valid without a stamp or a signature, and banks accept it that way. A seal is not mandatory for a FOP at all. A signature is optional — it adds weight to the document and some corporate clients like it. If the client’s accounting team asks for a signed copy, it is easier to sign than to argue.

What is the difference between a proforma and a regular invoice?

A proforma invoice is a preliminary bill issued before the services are delivered — for a prepayment, to agree the amount, or for customs formalities. It is not a basis for booking income. A regular (commercial) invoice is issued for services actually rendered, and it is the one that figures in currency supervision and reporting. If you take a prepayment, issue a proforma first and follow up with the final invoice once the work is done.

What language should the invoice be in?

English is the standard of international practice, and Ukrainian banks work with it. If you want full compatibility with Ukrainian paperwork, use a bilingual UA/EN format with every field duplicated. Ukrainian-only for a foreign client is not an option — they need to understand what they are paying for.

Can I invoice a foreign client in hryvnia?

Technically yes — the payment currency is set by the contract, and a non-resident can pay in UAH. In practice it is rare: a hryvnia transfer from abroad is inconvenient and expensive for the client, and most service-export settlements run in USD or EUR. If the client insists, ask your bank how it credits UAH payments from non-residents before agreeing.

What if the client pays in installments?

Two working options. First — a separate invoice per installment (50% prepayment — invoice No. 1, the final 50% — invoice No. 2): the cleanest for currency supervision, because each payment equals its own invoice. Second — one invoice and several payments referencing it; then every payment reference must quote the invoice number, and the parts must add up to the total. Avoid the situation where the client pays "approximately" — remainders and overpayments are what you end up explaining to the bank.