---
title: "The customer pays in another currency: documenting the settlement difference"
canonical: https://www.billabex.com/en/blog/foreign-currency-payment-settlement-difference/
lang: en
alternate: https://www.billabex.com/fr/blog/paiement-devise-differente-ecart.md
alternates:
  fr: https://www.billabex.com/fr/blog/paiement-devise-differente-ecart.md
  en: https://www.billabex.com/en/blog/foreign-currency-payment-settlement-difference.md
  es: https://www.billabex.com/es/blog/pago-en-otra-divisa-documentar-diferencia-de-pago.md
updated: 2026-10-28
index: https://www.billabex.com/llms.txt
---

# The customer pays in another currency: documenting the settlement difference

You are expecting EUR 10,000 and the customer announces a transfer of GBP 8,500. Your bank account then shows an amount in euros below the invoice value. Before requesting the difference, establish which currency was owed, what was actually received and who accepted the conversion. The bank balance alone cannot answer all three questions.

Payment in an unexpected currency may reveal a customer error, a forgotten commercial agreement or confusion between the invoice currency and your accounting currency. Treating it as a minor shortfall can turn an exchange loss into a customer receivable, or erase a genuine amount still owed. A sound follow-up needs to explain each component of the difference.

## Identify the currency of the obligation

Collect the invoice, the accepted contract or order and any correspondence about settlement. An invoice for GBP 8,500 recorded in your accounts at its euro equivalent is different from an invoice for EUR 10,000. The currency displayed in a dashboard may be your reporting currency without changing what was agreed with the customer.

The [French Ministry of the Economy explains the exchange risk associated with invoicing in a foreign currency](https://www.economie.gouv.fr/entreprises/gerer-son-entreprise-au-quotidien/gerer-sa-comptabilite-et-ses-demarches/comment-facturer-dans-une-monnaie-etrangere): movements between invoicing and payment may produce a gain or loss. That distinction matters before requesting more money. Tax conversion rules have their own purpose; they do not establish that a customer agreed to use your chosen rate to settle an invoice issued in euros.

Check the entity as well. A British subsidiary may pay on behalf of another group company, but its operating currency does not automatically change the latter's debt. [Mapping the payer separately from the customer](https://www.billabex.com/en/blog/payer-versus-customer-entity-mapping/) helps preserve that distinction during reconciliation. For European contracts, establish the actual agreed terms rather than inferring them from the customer's location.

## Reconstruct the bank transaction without inventing a rate

Request the information needed to trace the transaction: amount and currency sent, amount and currency received before identifiable fees, conversion applied, charges debited and transaction reference. Depending on the banking route, obtaining some of these details may require an enquiry with the bank. A screenshot from the payer cannot replace this reconstruction.

The [ECB's euro reference exchange rates](https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html) are published for information, and the ECB discourages their use for transactions. They are not a guaranteed price for your bank conversion. Do not retrospectively choose whichever reference rate makes the spreadsheet difference disappear.

Record the quotation direction. If one euro equals GBP 0.86, converting GBP 8,500 into euros requires dividing 8,500 by 0.86. Multiplying would give EUR 7,310, which does not follow that quotation convention. Check the units as carefully as the digits. Preserve the initial precision before final rounding, following the applicable accounting rules, so another person can reproduce the calculation.

## Compare three cases with the same bank credit

Consider a simulation using invented exchange rates for clarity. An invoice is issued for GBP 8,500. Its initial accounting value is EUR 10,000, based on an assumed rate of GBP 0.85 per euro. The customer pays the full GBP 8,500 due. At conversion, one euro equals GBP 0.86, producing EUR 9,883.72 after rounding.

If the bank then charges the beneficiary EUR 20, the net effect on the account is EUR 9,863.72. The difference from the original EUR 10,000 is EUR 136.28: EUR 116.28 from the conversion movement and EUR 20 in fees. Under these assumptions of full payment of the GBP debt and beneficiary-borne fees, that total is not a remaining customer balance to chase.

In the second case, the invoice is instead for EUR 10,000, and the customer sends GBP 8,500 without an agreement being found. The identical bank credit of EUR 9,863.72 does not establish the answer by itself. Check the settlement terms, any acceptance of the alternative currency and the allocation of charges before deciding what balance can be claimed. An arithmetic difference is an investigation lead, not a contractual conclusion.

In the third case, a verified agreement expressly states that GBP 8,500 settles this EUR 10,000 invoice and that the beneficiary bears its own conversion and charges. If those conditions are met, automatically requesting EUR 136.28 would contradict the agreement. The three cases show why “invoice amount minus net bank credit” cannot be a sufficient decision rule.

## Keep exchange differences, fees and partial payments separate

[Odoo 18's multicurrency documentation](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/get_started/multi_currency.rst) distinguishes the company's main currency, the document currency and the amounts displayed during reconciliation. It also describes dedicated entries for exchange differences. This illustrates a requirement to check in your own system: retain several relevant values without merging them into an incorrect collection request.

The accounting team must determine the appropriate treatment of the difference. The customer-facing team needs an actionable outcome: debt settled, a confirmed remaining amount or an ongoing investigation with specified missing evidence. It should not select an exchange-loss account merely to remove a task, or reopen an invoice because its value in a euro report has changed.

[Bank charges reducing an incoming transfer](https://www.billabex.com/en/blog/bank-fees-transfer-remaining-balance/) are a separate issue. Identify what belongs to your bank, the payment route or a deduction made by the payer. While allocation remains uncertain, pause the disputed supplementary request and continue following up on other invoices whose balances have been confirmed.

## Ask a question the customer can answer

In the second case, avoid immediately demanding EUR 136.28. A clarification might say: “The invoice is denominated in EUR 10,000. We have identified a transfer of GBP 8,500. Could you share the reference for any agreement allowing settlement in GBP and the details of the amount sent? We are also checking the conversion and charges with our bank.”

This states the facts without inventing a customer error. It does not promise to accept any proposed exchange rate either. Once the terms have been checked, confirm the amount allocated, the currency of any remaining balance and the approved method for paying the difference. If the payment settled the obligation, say so clearly and correct any reminders already prepared.

For bilingual correspondence, place the currency code beside each value and avoid ambiguous dates. The [tests for factual consistency in French and English reminders](https://www.billabex.com/en/blog/bilingual-reminders-ai-agent-context-errors/) help check that translation does not turn GBP into EUR or an assumed conversion into a confirmed agreement. These checks matter in the recorded summary as well as in the outgoing message.

## Make the next payment less ambiguous

After resolving the case, record the expected currency, approved destination account and any conversion or fee conditions actually agreed. For recurring business, have the commercial framework reviewed before the next invoice. A preference expressed in one email should not be generalised to every group company or every future payment.

Retain the calculation with its source, date, quotation direction and rounding. A colleague should be able to explain why the case is closed even though euro cash differs from the initial accounting value. That explanation prevents the same investigation being repeated during the next review or after a change of staff.

[Conversation tracking in Billabex](https://www.billabex.com/en/product/follow-ups-conversations/) helps your team find the customer's explanations and previous decisions before preparing the next action. Accounting treatment and the agreement on currency still require verification by the appropriate people. An accurate reminder requests an explained amount in the correct currency, supported by a case file whose conversions can be traced.

## Sources

- [French Ministry of the Economy, invoicing in a foreign currency](https://www.economie.gouv.fr/entreprises/gerer-son-entreprise-au-quotidien/gerer-sa-comptabilite-et-ses-demarches/comment-facturer-dans-une-monnaie-etrangere), 5 September 2025.
- [ECB, euro foreign exchange reference rates](https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html), methodology and warning consulted in September 2026.
- [Odoo 18, multicurrency system](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/get_started/multi_currency.rst), official documentation.