Shopify OSS Exchange Rates: Reconcile Multi-Currency EU VAT Without Mixing FX Rules

Separate the four currency layers before you reconcile VAT

Shopify's current currency documentation distinguishes store currency, local or presentment currency, and payout currency. The store currency is used for product pricing in the primary market and for Shopify reporting. The presentment currency is what the customer sees and pays in at checkout. The payout currency is what reaches your bank through Shopify Payments. A fourth layer belongs in an OSS workflow: the currency in which the VAT return must be completed under the rules that apply to your scheme and Member State of identification.

Those layers should remain visible in your working data. If a Swedish customer pays in SEK, do not throw away the SEK taxable amount simply because Shopify also gives you a store-currency value. If Shopify later pays you in EUR, do not replace the order amount with the payout amount. Settlement FX, card fees and payout timing answer a cash question. The OSS return answers a tax-reporting question.

Shopify also states that currency conversion can happen at transaction events such as payment capture, refund or chargeback, using the rate at the time of that transaction. That behavior is important for payment reconciliation, but it is not evidence that the same transaction-time rate is the one required for an OSS VAT return. Keep the two rule sets separate from the start.

• Presentment currency: what the customer sees and pays.
• Store currency: the administrative and reporting currency used by Shopify.
• Payout currency: the currency deposited through the payment flow.
• OSS return currency: the return currency required by the applicable special-scheme rules and Member State process.

For Union OSS, the legal conversion rule is tied to the end of the tax period

The current consolidated EU VAT Directive is specific. Article 369h says the Union-scheme VAT return is made out in euro, while Member States that have not adopted the euro may require the return in their national currency. If supplies were made in other currencies, the taxable person uses the exchange rate applying on the last date of the tax period for the purpose of completing the return. The conversion uses the European Central Bank rate published for that day, or the next day of publication if no rate was published on the period-end date.

The non-Union scheme contains the same basic pattern in Article 366. For the quarterly Union and non-Union schemes, that means the tax-return conversion is a period-end rule, not a instruction to use whatever rate Shopify used for each order or payout. If the final day of the quarter has no ECB publication, the Directive points to the next day on which the rate is published.

Do not turn this into a claim that every merchant files an OSS return in euro. A Member State that has not adopted the euro can require its national currency, so the actual Member State portal and instructions still matter. Also keep IOSS separate: it has a monthly tax period and a parallel currency rule under Article 369u. This guide focuses on quarterly Union and non-Union OSS reconciliation rather than monthly import-scheme reporting.

Build a source table that preserves the original order values and the return conversion

A clean multi-currency reconciliation needs two layers of numbers rather than one overwritten total. The first layer is the commercial source record: order identifier, date, Member State of consumption, supply classification, transaction or presentment currency, taxable amount and VAT collected. The second layer is the reporting transformation: OSS tax period, applicable return currency, ECB source date, exchange rate used and converted taxable and VAT amounts where conversion is required.

Preserving both layers makes review possible. If finance sees an unexpected EUR total in the quarter, it can trace the amount back to the original SEK, DKK or other currency instead of trying to reverse-engineer a conversion from a rounded report. It also prevents a later Shopify payout conversion from silently changing the tax trail.

Add exception fields rather than editing source data when something needs investigation. Useful statuses include VAT-rate mismatch, unresolved customer-location evidence, B2B status under review, refund after the original sale and prior-period correction. The related /blog/shopify-oss-vat-record-keeping-workflow guide covers the wider quarter-close record set; this guide focuses on the FX layer inside that process.

• Order ID and supply date
• Member State of consumption and OSS scope decision
• Original transaction currency
• Original taxable amount and VAT collected
• Tax period and required return currency
• ECB rate date and rate used when conversion is required
• Converted taxable amount and VAT amount
• Refund, correction and exception status

Reconcile by tax logic first, then currency, rather than converting one grand total

Do not begin by converting the entire store's quarterly revenue into one currency. First isolate the supplies that belong in the OSS scheme you are reporting. Then group them according to the return structure, including the relevant Member State of consumption and VAT rate. Only after the scope and tax categories are correct should you apply the return conversion rule to values that were made in other currencies.

Consider a Shopify store that presents prices in EUR for France and in SEK for Sweden. The French orders may already be denominated in the return currency, while the Swedish supplies require a conversion for the return. Shopify can still show both sets of orders in store currency for analytics, and the payment provider can still calculate settlement amounts using transaction-time FX. Neither convenience changes the period-end conversion rule used to complete the OSS return where Article 369h applies.

This sequencing also makes country-rate checks more meaningful. A VAT mismatch should be investigated in the context of the original transaction and Member State before a currency conversion obscures it. Fixing the arithmetic of a converted total cannot repair a wrong tax classification, wrong customer-location decision or incorrectly treated B2B sale.

Use Vatuno as the record and report layer, then verify the FX assumptions before filing

Vatuno's current official listing says every EU order becomes a VAT record and that the app compares VAT collected with the official rate for the buyer's country, flags mismatches, validates B2B VAT numbers through VIES, creates sequential PDF invoices, tracks the EUR 10,000 threshold and exports quarterly OSS reports as CSV. Those functions can reduce the amount of order-by-order assembly needed at quarter close for a store that matches the app's advertised digital-product use case.

The important boundary is what the listing does not currently say. It does not publicly describe whether the OSS CSV converts non-return-currency transactions, which FX source or date would be used, or whether the merchant should perform that conversion outside the app. Therefore, do not invent an automatic ECB conversion feature. Open the export, identify its currency fields, reconcile a sample to the underlying Shopify orders and document the conversion method that will be used for the official return.

As verified on September 15, 2026, the Shopify App Store lists Vatuno Starter at $49 per month, Growth at $99 and Enterprise at $149, each with a 14-day free trial. Vatuno is available in English, German, French, Spanish, Italian and Portuguese (Portugal). The ShopRadar CTA uses the authentic cross-border-vat-compliance App Store slug with locale=en; that parameter selects the English listing view and does not change the installed app's language settings.

Do not let refunds and settlement FX rewrite the original tax trail

Shopify explains that a foreign-currency refund is converted using the exchange rate at the time of the refund, so the amount affecting your payout currency can differ from the amount associated with the original sale. That is a payment and cash-reconciliation fact. It should not cause you to overwrite the original sale's tax record or assume that the payout difference itself is an OSS correction.

Keep the original transaction values, the refund event and the tax correction as connected but separate records. Then apply the correction procedure that belongs to the affected OSS period. ShopRadar's /blog/shopify-oss-refunds-corrections guide goes deeper into prior-period correction handling. The practical rule here is simpler: never use a changing payout conversion to erase the source values you may need to explain later.

The same principle applies to chargebacks or later payment events. Finance may need one reconciliation for cash received and another for VAT reporting. Combining them into a single number creates a neat spreadsheet at the cost of an auditable trail.

Run a quarter-end FX checklist before the OSS file leaves finance

A disciplined quarter close should make the conversion reproducible by another reviewer. Freeze the covered order population, resolve material scope and VAT-rate exceptions, identify which source currencies differ from the required return currency, record the legally relevant period-end date, capture the applicable ECB publication and preserve the rate evidence with the working file. If the period-end date has no ECB publication, document the next publication date used under the Directive rule.

Then compare the converted country-and-rate totals with the OSS report you intend to submit. If Vatuno is your reporting layer, reconcile its CSV against the source table rather than assuming an export is self-validating. Keep report preparation, official portal submission and tax payment as separate completion steps. A CSV can be complete while a return remains unsubmitted.

Finally, archive enough information to reproduce the numbers later: the source export, Vatuno report, conversion worksheet or system output, ECB rate evidence, exception resolutions and submission confirmation. The existing OSS record-keeping guide explains the broader 10-year record-retention requirement. The goal of this FX checklist is to ensure the currency transformation remains explainable throughout that retention period.

• Confirm the OSS scheme and tax period before selecting an exchange-rate date.
• Keep original transaction currency and converted return values side by side.
• Use the period-end ECB rule where the applicable OSS provisions require it, not a Shopify payout rate by habit.
• Check the Member State portal when a non-euro Member State of identification can require national-currency filing.
• Reconcile Vatuno CSV totals to Shopify source orders and document any FX step not described by the app listing.
• Keep report preparation, submission and payment as separate statuses.

When Vatuno is the right fit for this workflow

Vatuno is a strong fit when the operational problem is assembling a reviewable EU VAT record trail for a Shopify store selling digital products, especially when country-rate mismatches, VIES checks, invoice sequencing, threshold monitoring and quarterly OSS CSV preparation are otherwise spread across several manual files. It gives finance one focused layer around the VAT records that need attention.

It is not a reason to stop understanding the return mechanics. The current public listing does not promise tax registration, automatic filing, tax payment or an explicit ECB exchange-rate engine. Likewise, VIES validation alone is not proof that every transaction qualifies for reverse charge. Keep those legal decisions and submission responsibilities in the workflow rather than turning a useful reporting app into a claim it does not make.

For a merchant with many local currencies, the most valuable test is not whether the dashboard looks polished. Take one completed quarter, trace a sample from Shopify's original transaction currency through the applicable period-end conversion and into the OSS totals, then confirm that your adviser or filing owner can reproduce the result. If the evidence chain is clean, the process can scale without turning FX into a quarter-end guessing game.

Apps mentioned in this guide

Frequently asked

Which exchange rate should I use for a Shopify Union OSS return?

Under Article 369h of the current EU VAT Directive, supplies made in other currencies are converted for the Union-scheme return using the exchange rate applying on the last date of the tax period, based on the European Central Bank rate published for that day or the next publication day if none is published on the period-end date. Check the rules and portal requirements for your actual scheme and Member State of identification.

Can I use Shopify's payout exchange rate for OSS?

Do not assume so. Shopify's payout and transaction conversions serve payment and reporting purposes, while the OSS return has its own legal conversion rule. Preserve the original transaction values and apply the return rule separately where required.

Does Vatuno automatically convert OSS sales using ECB rates?

The current public Shopify App Store listing does not document an automatic OSS FX conversion method or specify an ECB rate source and date. It advertises quarterly OSS CSV reports, so verify the export's currency fields and conversion assumptions before filing.

Does Vatuno file the OSS return or pay the VAT?

The current listing advertises VAT records, invoices and quarterly OSS CSV reports. This guide does not treat those features as automatic registration, filing, portal submission or tax payment.

What if my Member State of identification does not use the euro?

The EU VAT Directive allows Member States that have not adopted the euro to require the special-scheme VAT return in their national currency. Check the current instructions for the Member State portal you actually use.

Is Vatuno available in English?

Yes. Vatuno is available in English. Its current Shopify App Store listing also shows German, French, Spanish, Italian and Portuguese (Portugal).