Multi-currency invoicing is a structural feature of international business. A Spanish exporter invoices an American buyer in dollars. A German manufacturer invoices a British distributor in pounds. An Italian winery invoices a Japanese importer in yen. A Portuguese tourism operator invoices a Brazilian travel agency in reais. Across the European Union, billions of euros of transactions are denominated in foreign currencies every year, and the new electronic invoicing mandates treat them through specific rules that the invoicing system must respect to remain compliant.
The principle: local currency for tax purposes, foreign currency for the contract
Every European jurisdiction shares a common principle on multi-currency invoicing: the invoice must express the taxable amount in the local currency of the issuer for VAT and tax declaration purposes, regardless of the currency that the parties have agreed for the commercial transaction. The foreign currency amount can —and frequently must— appear alongside the local currency amount, but the fiscal record is denominated in the local currency.
This principle reflects the architecture of national VAT systems. Each tax administration declares VAT in its own currency, processes refunds in its own currency, levies penalties in its own currency. A Spanish exporter that sells to an American buyer for ten thousand dollars must declare a Spanish VAT amount calculated on the euro equivalent of those ten thousand dollars; the dollar amount serves the commercial relationship but does not appear in the Spanish VAT return.
The electronic invoice format must support this dual representation natively. The Factur-X standard includes fields for both the document currency —the currency in which the invoice is denominated commercially— and the tax currency —the currency in which the VAT amount is expressed for tax purposes—. The ZUGFeRD and XRechnung formats follow the same logic. The Italian FatturaPA distinguishes the divisa from the imponibile in the corresponding fields. The Portuguese SAF-T includes the exchange rate among the mandatory data.
The exchange rate: which one and at which moment
The conversion from the commercial currency to the tax currency requires an exchange rate. The choice of the rate and the moment of the conversion are not free; each jurisdiction defines specific rules that the issuer must follow.
The most common approach in the European Union is the rate published by the European Central Bank or by the national central bank, applied on the date of the chargeable event for VAT purposes. The chargeable event is typically the date of delivery of the goods, the date of completion of the service or the date of payment when payment precedes delivery —the rules vary by transaction type and by jurisdiction—.
The Spanish framework, for example, allows the use of the rate published by the Banco de España on the day of the chargeable event. The German framework offers the issuer a choice between the rate of the European Central Bank and the rate published by the Federal Ministry of Finance, the latter being a monthly average that simplifies operations for high-volume issuers. The Italian framework refers to the rates published by the Banca d'Italia. The French framework refers to the European Central Bank rate, with specific provisions for currencies not covered by the ECB.
The electronic invoicing system must record both the rate used and the source of the rate, so that any future verification can reconstruct the conversion. Some platforms allow the issuer to configure the default source and the default moment of conversion; others require manual selection for each invoice. The choice depends on the volume and the variability of the firm's international transactions.
VAT calculation in the multi-currency invoice
The VAT amount on a multi-currency invoice is calculated on the local currency equivalent of the foreign currency taxable base. The arithmetic is straightforward: convert the foreign currency amount into local currency using the applicable exchange rate, apply the VAT rate to the local currency amount, record the local currency VAT amount in the structured invoice.
The complication arises when the invoice includes multiple lines at different VAT rates, multiple currencies in the same document or partial payments that may shift the chargeable event. In practice, the most common pattern is a single-currency invoice with single or multiple VAT rates; the multi-rate case is the most frequent complexity and the structured formats handle it natively. Multi-currency invoices —where different lines are denominated in different currencies— are rare; most firms issue a separate invoice per currency to simplify the fiscal treatment.
The presentation of the VAT amount on the invoice should clearly indicate the local currency amount, with the foreign currency amount shown informatively if relevant. Some clients prefer to see the VAT amount in their own currency for budgeting purposes; the invoice can show both, as long as the fiscal field of the structured format carries the local currency value.
The intra-EU dimension: reverse charge and the foreign currency
For invoices between EU businesses where the reverse charge applies —the recipient is responsible for declaring the VAT in its own jurisdiction— the multi-currency treatment is somewhat different. The issuer does not apply VAT and does not need to convert the foreign currency amount for VAT purposes; the invoice carries the foreign currency amount and the reverse charge indication. The recipient, in its own VAT return, converts the foreign currency amount into its own local currency using the exchange rate applicable in its own jurisdiction.
This bilateral conversion can produce small mismatches between the amounts that the issuer reports in its VIES recapitulative statement and the amounts that the recipient declares in its own VAT return. The mismatches are usually immaterial and the tax administrations accept them; the structured invoice should record the foreign currency amount precisely so that the recipient can perform its own conversion accurately.
The non-EU dimension: exports, third countries and the customs interface
For invoices to non-EU recipients —exports— the multi-currency treatment intersects with customs procedures. The export is typically exempt from VAT in the issuer's jurisdiction, subject to proof of dispatch outside the EU customs territory. The invoice can be denominated in any currency agreed between the parties; the customs declaration uses the same amount, converted to euros for the customs purposes using the rate published for customs use.
The customs exchange rate may differ from the VAT exchange rate. Most jurisdictions accept the same source —ECB or equivalent— but the date of conversion may differ. The customs declaration is typically based on the rate of the month of acceptance of the declaration, while the VAT rate is based on the date of the chargeable event. For exports where the two events coincide, the difference is negligible; for exports where they diverge —invoice issued before shipment, shipment before customs clearance— small differences may appear.
The structured invoice format records the commercial currency and the local currency equivalent. The customs system, separately, converts the customs value into euros using its own rate. The reconciliation between the two values is the responsibility of the issuer and is verified by the tax administration through cross-checks between the VAT return and the customs records.
Currency hedging and the timing of the invoice
International businesses frequently hedge foreign currency exposures through forward contracts, options or natural hedges. The hedging instrument is a separate financial transaction from the underlying commercial transaction; it does not appear on the invoice. The invoice reflects the commercial transaction at the applicable exchange rate; the hedging gain or loss is recorded separately in the financial accounts.
The timing of the invoice is sometimes adjusted to align with the maturity of a hedge or with the desired exchange rate. From a fiscal perspective, the issuer cannot freely choose the invoice date; the date must reflect the actual chargeable event. Issuing the invoice early to capture a favourable rate, or delaying it to wait for a better rate, can produce fiscal anomalies that an inspection would flag.
The honest approach is to invoice at the moment that the chargeable event occurs and to accept the resulting exchange rate. The hedging strategy operates in the financial dimension; the invoicing operates in the fiscal dimension; the two should be designed in coordination but should not interfere with each other.
The corporate group dimension: intercompany invoicing in foreign currencies
Multinational corporate groups generate substantial intercompany invoicing across jurisdictions and currencies. A Spanish subsidiary may invoice its German parent for shared services; the German parent may invoice the Spanish subsidiary for centralised IT licenses; the Italian sister company may invoice the French sister company for cross-border project participation. Each of these intercompany flows is a multi-currency invoice with full fiscal implications.
The corporate group structure does not exempt intercompany invoices from the e-invoicing mandates. Each intercompany invoice must comply with the electronic invoicing requirements of the issuer's jurisdiction and must be intelligible to the recipient. The currency treatment follows the same rules as third-party invoices: local currency for VAT purposes, foreign currency for the commercial relationship.
Transfer pricing considerations add another layer. The arm's-length principle requires that intercompany transactions be priced as they would be between independent parties; the documentation of this pricing is a separate fiscal obligation. The electronic invoice is one element of the transfer pricing documentation; the intercompany agreement, the benchmarking study and the cost allocation methodology complete the picture.
Cryptocurrency invoicing: a frontier area
Some businesses increasingly issue or receive payments in cryptocurrency. The fiscal treatment of cryptocurrency for VAT purposes was clarified by the European Court of Justice in the Hedqvist judgment, which classified bitcoin exchange as a VAT-exempt financial service. For the invoicing of goods or services paid in cryptocurrency, the principle is similar to fiat foreign currency: the invoice is denominated in the commercial currency —the cryptocurrency— with the local currency equivalent recorded for tax purposes.
The exchange rate is the spot rate at the date of the chargeable event, drawn from a recognised exchange or index. The volatility of cryptocurrency makes this conversion more delicate; small movements between the moment of the invoice and the moment of payment can produce material gains or losses, recorded separately in the financial accounts.
The structured invoice formats are gradually adapting to cryptocurrency. The currency field accepts the standard ISO codes for fiat currencies; cryptocurrencies require either an extension of the field or the use of a fiat-equivalent representation. The technical evolution is ongoing, and businesses with cryptocurrency invoicing should follow the development of the standards.
The technological infrastructure: rates, conversions and traceability
The e-invoicing platform that handles multi-currency operations needs an integrated exchange rate engine. The engine retrieves the rates from the configured sources, applies them according to the configured rules and records both the rate and the source for each conversion. The audit trail must allow a future verification to reconstruct exactly how each amount was calculated.
The integration with the firm's accounting system is critical. The accounting system records the foreign currency amount, the local currency equivalent and the realised exchange gain or loss when the payment arrives at a different rate. The reconciliation between the invoice and the payment, accounting for the exchange difference, is a recurring task that the platform should automate.
For high-volume issuers, the use of average monthly rates simplifies the operational burden. Many jurisdictions allow this approach with appropriate documentation; the platform should support the choice between daily rates and monthly averages and apply the choice consistently.
The presentation to the customer
Beyond the fiscal compliance, the multi-currency invoice must be intelligible to the customer. International customers often prefer to see the amount in their own currency, even when the contractual currency is different. The structured format records the contractual currency and the local-currency-of-the-issuer equivalent; some platforms add the local-currency-of-the-customer equivalent as an informative line, calculated at the applicable rate.
The presentation of multiple currencies in the same document requires clarity. The invoice should indicate which currency is the contractual one —and therefore the binding amount for payment—, which currency is the tax currency of the issuer and which currency, if shown, is the informative currency of the customer. Ambiguity at this point produces payment disputes that are tedious to resolve.
The Factur-X format with its embedded PDF is well suited to multi-currency presentation: the XML carries the structured data with full fiscal precision, while the PDF allows the visual representation that the customer expects. ZUGFeRD offers a similar balance. Pure XML formats like XRechnung require a separate presentation layer if the customer expects a visually formatted document.
Common pitfalls in multi-currency e-invoicing
Several errors recur in multi-currency implementations. The first is failing to record the exchange rate source and date in the invoice. Without this metadata, any future verification cannot reconstruct the calculation, and the inspection may apply a different rate that produces a different VAT amount.
The second is applying inconsistent rate sources across invoices. A firm that uses ECB rates for some invoices and commercial bank rates for others creates artificial differences that complicate the reconciliation and may flag inconsistencies to the tax administration.
The third is confusing the chargeable event date with the invoice date for the exchange rate calculation. The two dates may differ —the chargeable event may occur before the invoice is issued, especially for services that span several months— and the rate to apply is the one at the chargeable event, not the invoice issue.
The fourth is ignoring the customs dimension on exports. The discrepancy between the VAT exchange rate and the customs exchange rate can produce small but cumulatively significant differences that surface during customs audits.
The fifth is failing to plan for the payment-side exchange differences. The amount actually received in local currency at the moment of payment usually differs from the local currency amount invoiced; the accounting system must recognise this difference correctly to avoid double-counting or under-reporting.
The strategic dimension
For internationally active businesses, the design of the multi-currency e-invoicing flow is part of the broader treasury and finance architecture. The choice of contractual currency, the hedging strategy, the payment terms and the exchange rate management interact with the invoicing infrastructure to determine the cash flow predictability of the firm.
A well-designed multi-currency e-invoicing system gives the finance team real-time visibility into the foreign currency exposure embedded in the open receivables. This visibility is the foundation for effective treasury management, hedging decisions and pricing reviews. The compliance investment is therefore an enabler of broader financial management, not a parallel obligation.
Professional guidance for the transition
Multi-currency e-invoicing is a domain where the technical details have real fiscal and financial consequences. A structured assessment of the firm's currency exposure, the regulatory framework of each relevant jurisdiction and the integration with treasury and accounting systems is the foundation for a robust design.
If your internationally active business is preparing for the e-invoicing mandates and you want to see how Invoseal handles multi-currency operations, exchange rate management and the fiscal precision required across European jurisdictions, you can review the functionalities and the deployment options at invoseal.es.
Want to sort it out today?
InvoSeal complies with RD 1007/2023 in VeriFactu and Non-VeriFactu mode from day one. Statement of Responsibility published.
Try InvoSeal →