AHoosh
Book a Discovery Call
FX & Trade

The USD Invoicing Trap: Why It's Costing EU–Iran Importers More Than They Think

When you invoice Iranian trades in USD and sell to European buyers in EUR, you're stacking two separate currency risks in one transaction. Here's what that costs and how to fix it.

10 June 2026

Invoice and currency documents

Most cross-border trade defaults to USD invoicing. It’s the global reserve currency, it’s what Iranian suppliers have historically invoiced in, and it’s what trade finance documentation often requires.

The problem is that for a European importer buying from Iran, USD invoicing stacks two separate currency risks into a single transaction: the IRR/USD risk on your cost side, and the EUR/USD risk on your revenue conversion. In a year where those two rates are moving in different directions — sometimes sharply — the compounding effect on margins is not trivial.


The Stack Problem

Here’s the transaction chain for a typical EU importer working with an Iranian supplier:

  1. Iranian supplier prices goods in USD (based on their IRR-to-USD conversion)
  2. Importer pays in USD
  3. Importer resells to European customer and invoices in EUR
  4. Importer converts USD proceeds to EUR for financial reporting

There are two conversion steps where exchange rate risk lives:

Step A: IRR → USD — Your supplier’s cost base is in IRR. When the rial weakens, their costs in IRR rise (for USD-priced inputs) but their USD export price may stay flat for a period. This creates pricing pressure that eventually manifests as a USD price increase.

Step B: USD → EUR — Your USD cost gets converted to EUR at the prevailing EUR/USD rate. When EUR strengthens against USD (EUR/USD rises), your EUR-denominated cost goes up. When it weakens, costs fall. This move is entirely independent of what the rial is doing.

In a quarter where the rial is weakening AND EUR is strengthening against USD, both risks compound on your cost base simultaneously. The importer holding USD-priced Iranian goods in that environment has absorbed a double hit without having made a single operational decision.


What the Compounding Looks Like

A simplified example with June 2026 data:

  • Goods priced at $10,000 USD from an Iranian supplier
  • EUR/USD at 1.08 (midpoint, ECB Frankfurter)
  • EUR cost: €9,259

If EUR/USD moves to 1.12 (a 3.7% EUR strengthening — plausible over a quarter):

  • Same $10,000 goods
  • EUR cost: €8,929
  • Saving: €330 per €9,259 transaction — a 3.6% margin gift

But if EUR/USD moves to 1.04 (USD strengthening, also plausible):

  • EUR cost: €9,615
  • Extra cost: €356 per transaction — 3.8% margin hit

Now layer the IRR move on top: if the Iranian supplier reprices their goods from $10,000 to $11,000 to catch up with rial depreciation (a 10% increase), the combined effect in a USD-strengthening scenario:

  • Old cost: €9,259
  • New cost: $11,000 at 1.04 = €10,577
  • Impact: +€1,318, or +14.2% in EUR terms

This is the stacking problem. A 10% USD repricing plus a 3.8% EUR/USD move becomes a 14% EUR cost increase — from two sources neither of which you controlled.


The Fix: EUR-Based Invoicing

The structural solution is to shift supplier invoicing to EUR wherever possible.

When your supplier invoices in EUR:

  • You eliminate the USD intermediary entirely
  • Your cost is directly in EUR, matching your revenue currency
  • EUR/USD fluctuations no longer compound into your cost base
  • The only remaining FX variable is the IRR/EUR rate — which is still volatile, but it’s one variable instead of two

Objections from suppliers:

  • “We price in USD because that’s what our inputs cost.” — Their USD-priced inputs are converted at some IRR/USD rate internally. You can agree on an EUR equivalent with a regular review cadence, effectively sharing the FX management responsibility.
  • “We don’t want EUR exposure.” — Iranian suppliers who export to Europe often have EUR revenues from other European customers. EUR is frequently more natural for them than USD on EU-facing transactions.

In practice, EUR invoicing is more achievable than importers assume. It requires a direct conversation — usually with the owner or CFO rather than the sales contact — and a willingness to share the FX tracking methodology you’re using (TGJU for the IRR side, ECB Frankfurter for EUR/USD).


When USD Invoicing Is Unavoidable

There are categories where USD invoicing is harder to change: commodity trades, oil-linked products, and transactions that pass through third-country intermediaries where USD is embedded in the trade finance structure.

In those cases, the management options are:

  • FX forward contracts (if your bank offers them for EUR/USD) to lock in a conversion rate for known future USD purchases
  • Netting: hold USD across multiple payables and receivables to reduce the net exposure before converting
  • Shorter contract terms with explicit price-review triggers linked to EUR/USD movement exceeding a threshold (e.g., ±3%)

None of these eliminate the USD risk — they manage it. The EUR invoicing fix eliminates it at source.


The Simple Version

If you’re importing from Iran and selling to European buyers, check your invoicing structure:

  • Are you paying your Iranian supplier in USD? → Consider renegotiating to EUR
  • Are you tracking EUR/USD alongside IRR/USD? → If not, you have half the cost picture
  • Do your supplier contracts have price-review clauses that trigger on FX moves? → If not, you’re absorbing all the move silently

The compounding risk is real. It’s also fixable — with a supplier conversation that most importers have never had.


Sources: EUR/USD: ECB Frankfurter API | USD/IRR: TGJU — tgju.org/profile/price_dollar_rl

Follow the daily FX briefing at t.me/ahooshai — or reach us at ahoosh.ai/contact.

← All Articles