Skip to main content
Metrics type: Card
Revenue split by transaction currency. Highlights FX exposure for multi-currency accounts.

​
At a glance

Revenue split by transaction Currency Code. Highlights FX exposure on multi-currency Companies.

​
Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

UK apparel parent on BC, 30D window 14 Mar to 12 Apr 26. Reporting currency GBP. USD = 29% of revenue → 1% USD movement = ~£14K monthly P&L impact. Treasury can size FX hedges from this view.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Business Central:
Reports > Finance > Currency-wise Trial Balance Currency Exchange Rate table for rates used Adjust Exchange Rates batch log for revaluation history
Why may differ: Cross-connector reconciliation: Pair with stripe.currency_breakdown and paypal.currency_breakdown for payment-side currency mix.

​
Known limitations / merchant FAQs

Single-currency Companies? Card hides if only one Currency Code present. Local Currency vs Reporting Currency? Card shows both. Local is where the transaction posted; Reporting is the consolidated view. FX hedging input? Yes, Treasury teams use this card to size monthly FX hedges by exposure. Currency Exchange Rate cadence? BC’s Currency Exchange Rate table holds daily rates by default. The Adjust Exchange Rates batch can revalue for reporting. Crypto / non-standard currencies? Excluded by default. Configurable.

​
Tracked live in Vortex IQ Nerve Centre

Revenue by Currency is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.