International payments for agencies: collections, costs, and cash flow

A client pays in USD. The creative team invoices in EUR. A specialist contractor expects GBP. The project is profitable on the proposal, yet the agency struggles to make the final payment on time.

That can happen when the commercial budget ignores the payment workflow. Revenue, cash availability, currency conversion, and supplier obligations are related, but they are not the same thing.

A practical international-payment process connects the client agreement, the receiving route, the project ledger, and the outgoing schedule. It also defines who can change instructions and approve a payment.

This guide is for agencies and service businesses working across borders. The operating practices below can be implemented with appropriate internal tools; they are not claims that any particular payment platform supplies accounting, payroll, or team-management features.

Build the project payment map before work starts

For each project, identify the contracting client, the agency entity issuing the invoice, and the suppliers or contractors providing services.

Then record what each party owes, in which currency, and when. Avoid using a single “project currency” field to hide different contractual obligations.

A simple map might show a USD 12,000 client engagement, EUR contractor costs, and domestic operating expenses. The incoming USD receipt does not automatically satisfy the outgoing EUR invoice. Someone needs to arrange a supported conversion and payment at the appropriate time.

Add the receiving account or provider, the accepted incoming method, and the intended outgoing destination. Check customer and transaction eligibility before putting a route into the client contract.

Separate commercial approval from payment approval

A project manager can confirm that work was delivered. A finance owner can check that the invoice matches the agreement. An authorised person can release the payment through the appropriate service.

In a small agency, one person may perform more than one role. The important point is to keep the decisions visible rather than treating a chat message as proof of all three.

Decision	Evidence to keep	Common mistake
Work accepted	Agreed deliverable or milestone approval	Paying for an unapproved scope change
Invoice approved	Supplier identity, amount, currency, and contract reference	Approving a duplicate invoice
Destination verified	Current approved payment details and verification record	Trusting a last-minute email change
Payment released	Provider confirmation and transaction identifier	Marking an invoice paid before submission
Payment reconciled	Actual debit, fees, and resulting status	Recording an outgoing transfer twice

The process should be proportionate to the payment and team. It should also work when the usual finance person is away.

Agree on client billing milestones

Tie invoices to clear commercial events: a project start, an accepted phase, a defined delivery, or a recurring service period.

Avoid a milestone such as “when the client is happy” without an acceptance process. Vague billing triggers make collections harder even when the transfer method works perfectly.

For a fictional USD 12,000 engagement, the parties might agree USD 4,000 at commencement, USD 4,000 at an approved intermediate stage, and USD 4,000 at final delivery. The exact split is a commercial choice, not a standard required by payment providers.

Now compare those dates with supplier obligations. If a contractor must be paid before the second client instalment becomes available, the agency has a funding gap to plan for. Do not silently transfer that gap to the contractor by delaying an agreed payment.

Make receiving instructions easy for client finance teams

Client finance teams need the correct legal supplier name, invoice reference, amount, currency, and compatible payment instructions. They may also need purchase-order or vendor-registration information.

Provide the receiving details for the agreed currency and method. Preserve the exact beneficiary name and any mandatory allocation reference shown by the provider.

If the client requires evidence of account ownership or a supplier verification process, resolve it before the invoice falls due. A virtual receiving arrangement can have requirements that differ from a conventional business deposit account. See virtual accounts explained.

Our international payment handover guide includes a structure for presenting the instructions clearly without exposing login credentials or unnecessary identity documents.

Complete the vendor-onboarding checks for suppliers before the first payment deadline, including the legal party, approved route, and destination-change process.

Use local collection where the full route fits

A client may find a supported local bank-transfer method easier to use than entering international intermediary details. That is useful only if the agency’s receiving arrangement accepts the client, currency, payment purpose, and route.

For example, an eligible EUR collection arrangement may use SEPA instructions. A GBP arrangement may specify Faster Payments. Do not assume the same details support every other domestic or international service in that currency.

The local collection leg is also only part of the cost. Conversion and the later payout can change the final project income. Compare the complete journey using local versus international transfers, rather than choosing on the collection fee alone.

Build a cash schedule alongside the profit estimate

Profit asks whether revenue exceeds the relevant costs. A cash schedule asks when usable funds are available relative to obligations.

For operational planning, separate these stages:

• Invoice issued but not yet paid.
• Client says payment has been sent.
• Payment received but still awaiting review or allocation.
• Funds available for an eligible payout.
• Payout requested but not yet completed.
• Funds credited to the destination account.

Only the stages relevant to your next obligation should be treated as usable for that obligation. A receipt in one currency may still require conversion before a supplier can be paid.

Build the schedule using the provider’s current service estimates and applicable banking calendars. Leave room for exceptions without advertising a universal “safe” number of days for every route.

For a detailed forecast in original currencies, use multi-currency cash-flow planning. It includes a worked conversion schedule and delayed-receipt scenarios.

Work through a project-margin example

Assume a fictional agency collects USD 12,000. Its planning currency is EUR. The following numbers exclude taxes and many possible business costs; they illustrate payment effects rather than a complete accounting statement.

Item	Calculation	EUR outcome
USD available for conversion	USD 12,000 minus USD 40 receiving cost	USD 11,960 before conversion
Converted receipt	USD 11,960 × EUR 0.90 per USD	EUR 10,764
Final payout cost	EUR 10 deduction	EUR 10,754 net receipt
Project contractors	EUR 6,200	EUR 4,554 remaining
Allocated operating costs	EUR 1,800	EUR 2,754 contribution

If the eventual conversion rate were EUR 0.87 per USD, the same receipt would deliver EUR 10,395.20 after the payout cost. The contribution under the same expense assumptions would be EUR 2,395.20, a difference of EUR 358.80.

The agency has not necessarily undercharged the client, but its outcome differs from the planning case. This is why exchange-rate assumptions belong in the project budget, with a clear distinction between estimates and completed transactions.

Avoid converting the same commercial value unnecessarily

Map where conversion happens before moving money between services. A workflow can incur more than one conversion if the client pays in one currency, a marketplace or provider settles in another, and the agency pays expenses in a third.

A supported same-currency receipt and expense may reduce the need for a conversion. Whether retaining or using that currency is possible depends on the product and legal arrangement. Do not assume receiving details include a general-purpose multi-currency treasury account.

Also consider operational complexity. A slightly better quoted rate may not justify a fragile process that makes reconciliation or timely payment difficult.

Record every conversion’s input amount, output amount, rate, fees, and transaction identifier. The payment-fees guide explains how to compare final outcomes consistently.

Keep client receipts and contractor payments distinct

An incoming client payment and an outgoing contractor payment are separate transactions with separate permissions, destinations, and records.

Do not redirect a client to pay an unrelated third-party account merely because it seems to reduce one transfer. The commercial, provider, tax, and compliance implications need to be understood and permitted.

Similarly, a platform that helps an agency receive payments does not necessarily offer payroll, contractor management, bulk payouts, or payment services on behalf of others. Evaluate outgoing needs independently.

Our guide to paying international contractors focuses on the buyer-side process: approved invoices, verified destinations, schedules, and evidence of payment.

Protect destination changes and high-value approvals

A fraudulent payment instruction can arrive in a real-looking client or supplier email thread. Treat changes to beneficiary details as a separate verification event.

Contact the counterparty using a previously established channel, not the phone number included in the change request. Where practical, require a second authorised person to review important changes or unusual payments.

The FBI’s business-email-compromise guidance recommends independent verification of payment changes and stronger account security. These are useful controls even for a small team; they do not guarantee that every fraudulent request will be detected. FBI: Business email compromise.

Keep the verification record with the destination record so the next person does not have to reconstruct the decision from memory.

Reconcile at the project and currency level

A provider balance and a project ledger answer different questions. The balance shows an amount held or available under that service’s terms. The project ledger explains which commercial activities created the amount.

Match each receipt to invoices, including partial payments and combined payments. Record fees separately from the client’s gross payment. Match outgoing payments to approved supplier invoices without counting an internal transfer as a new expense.

For a multi-currency project, keep the original transaction currencies and the conversion records. Do not add USD 1,000 and GBP 1,000 as if they form a meaningful “2,000” balance.

Use the cross-border reconciliation guide for a worked ledger and exception process.

Review the process with a few useful measures

You do not need a complicated dashboard to identify recurring problems. Start with measures that lead to specific actions:

• Invoices overdue under the agreed terms.
• Receipts waiting for allocation or documents.
• Payments returned because of incorrect instructions.
• Total payment costs by route and currency.
• Supplier payments released after the planned date.
• Unreconciled items and how long they have remained open.

Distinguish client delays from provider processing delays. They require different fixes. Better invoice approval may solve one; better route selection or documentation may solve the other.

Review the process when entering a new market, changing a contracting entity, or adding a new currency. An arrangement that worked for one client should not be assumed to fit every future project.

Frequently asked questions

Should an agency invoice every client in its home currency?

Not necessarily. Choose currencies deliberately based on the client agreement, costs, supported routes, and currency exposure. Consistency helps, but a single rule can create unnecessary friction for some clients.

Does a multi-currency receiving product replace accounting software?

No. Payment records support reconciliation, but they do not automatically provide complete accounting, revenue recognition, tax treatment, or project profitability reporting.

Can we pay contractors directly from client receipts?

Only through an arrangement that permits the intended flow and parties. Check the relevant service capabilities and obligations rather than assuming that receiving access includes third-party payout functionality.

Which issue should a small agency fix first?

Start with unclear invoice terms, incompatible receiving instructions, unverified destination changes, and a missing cash schedule. These gaps can disrupt an otherwise profitable project regardless of provider choice.