A customer wants to be billed in GBP. Another wants EUR. Your US customers pay in USD. For Microsoft CSPs, multi-currency billing is not simply about displaying the right currency symbol on an invoice — it is keeping supplier cost, pricing currency, billing currency, customer price, exchange rates and margin aligned as subscriptions change over time. A CSP can send a perfectly accurate customer invoice and still lose margin.
What is multi-currency CSP billing?
Multi-currency CSP billing is the process of managing subscription costs, customer pricing, invoicing, reconciliation and margins when transactions involve more than one currency. For a Microsoft CSP, several currencies can matter at once:
- Pricing currencyThe currency in which a product or service is priced.
- Billing currencyThe currency in which Microsoft or another provider invoices the partner.
- Customer pricing currencyThe currency used to establish the customer's selling price.
- Invoice currencyThe currency in which the customer is ultimately billed.
- Accounting currencyThe functional or reporting currency used by the CSP's legal entity.
These are not always the same. Microsoft's reconciliation data itself distinguishes between PricingCurrency and the exchange rate used to convert pricing currency to billing currency, and Microsoft generates CSP invoices in the partner's billing currency. That distinction matters once partners operate across multiple countries, entities, distributors or customer currencies.
Why multi-currency billing becomes complicated for CSPs
Imagine a CSP headquartered in the UK but selling across Europe and North America. It may have:
| Operation | Currency |
|---|---|
| UK customers | GBP |
| European customers | EUR |
| US customers | USD |
| Microsoft billing | GBP |
| Azure pricing | USD |
| European distributor | EUR |
Now add Microsoft 365 subscriptions, Azure consumption, reserved instances, third-party products, managed services and different distributors. The finance team is no longer simply converting currencies. It has to answer:
What did this service actually cost us?
What did we charge the customer?
Which exchange rate was used, and when was it applied?
Did our margin change?
Does the supplier reconciliation match the customer invoice?
Microsoft's own billing model shows why those questions matter. CSP invoices are issued in the partner's billing currency, while Azure plan services are priced in USD and can therefore require conversion for billing.
The point that is easy to miss: currency movement can become margin movement
Consider a simplified example. A European service costs the partner €90 per month. The CSP sells it to a UK customer for £85 per month. Assume €90 converts to £76.50 when the customer price is established.
Now suppose the exchange rate changes and the same €90 supplier cost converts to £80.00. The customer is still charged £85. Nothing changed on the invoice, the subscription or the contract. Yet:
Gross margin fell from £8.50 to £5.00, a reduction of more than 40% in this simplified example. Currency exposure can quietly become margin exposure.
A finance team can confirm the customer was invoiced correctly and still not know whether the expected margin was earned. Those are two different controls. Traditional billing processes tend to answer the first. Growing CSPs increasingly need to answer both.
Answering both means connecting the whole chain:
When those elements live across Partner Center exports, distributor systems, spreadsheets, CRM records and accounting tools, identifying margin variance becomes much harder than it needs to be.
Where multi-currency CSP billing tends to break down
There are several common points where complexity enters the process.
Microsoft pricing and billing currencies differ
Pricing currency and billing currency are separate concepts. Microsoft's CSP billing documentation notes that Azure plan services are priced in USD while partners receive invoices in their applicable billing currency, so conversion becomes part of the billing calculation where those currencies differ. Microsoft reconciliation files include fields such as PricingCurrency, PCToBCExchangeRate, EffectiveUnitPrice and BillingFrequency.
Customer currency differs from supplier currency
Microsoft may invoice the partner in one currency while the CSP sells to its customer in another. That creates two commercial relationships to reconcile — Microsoft or distributor to CSP, and CSP to customer — and the partner needs visibility across both.
Exchange rates change
If customer pricing is fixed while supplier cost moves with currency, margin can change without an obvious billing exception. This matters most for longer commitments and customer agreements where pricing cannot simply be adjusted every month.
Different suppliers use different pricing models
A modern CSP may source products from Microsoft directly, an indirect provider, Marketplace publishers and other ISVs. Each source can introduce its own price list, currency, billing frequency, effective dates, discounts, credits and adjustments — part of a broader multi-provider reconciliation picture.
Different legal entities add another layer
A CSP operating through separate US, UK and European entities may need different invoice currencies, price lists, tax treatment, payment details, accounting systems and reporting currencies. That is financial governance across the business, not simply localization.
Why spreadsheets struggle with multi-currency CSP operations
A spreadsheet can convert EUR to GBP. That is not the difficult part. The challenge is knowing which exchange rate should apply to which transaction at which point in time, and preserving that relationship for reconciliation and audit.
Imagine a CSP with 500 customers, 5,000 subscriptions, three currencies, two distributors, multiple price lists, monthly Microsoft reconciliation files, customer-specific discounts and mid-term seat changes. That is thousands of relationships between supplier cost and customer revenue. When prices or exchange rates move, a simple conversion column cannot tell you which customers are affected, which subscriptions lost margin, which price list should change, or which contracts prevent a customer price change. This is why multi-currency billing eventually becomes a data and controls question.
What finance teams should actually track
A useful multi-currency reconciliation model should connect at least the following:
| Field | Why it matters |
|---|---|
| Customer | Who is being billed |
| Subscription / SKU | What is being billed |
| Supplier | Microsoft, distributor or ISV |
| Supplier pricing currency | Currency behind the product cost |
| Supplier billing currency | Currency charged to the CSP |
| Supplier cost | Actual cost |
| FX rate | Conversion used |
| FX effective date | When that rate applies |
| Customer currency | Currency used for selling |
| Customer price | Amount charged |
| Expected margin | Commercial assumption |
| Actual margin | Realized margin |
| Variance | Difference worth investigating |
The objective is not merely faster reconciliation. It is making exceptions visible. Rather than asking finance to inspect thousands of transactions by hand, the operating model should surface the subscriptions where expected cost does not equal actual cost, or expected margin does not equal actual margin. Those are the transactions that deserve attention.
Multi-currency product catalogs matter too
The challenge begins before invoicing. It begins with pricing. If a CSP sells the same product in USD, GBP and EUR, maintaining three unrelated spreadsheets creates three potential sources of truth. A stronger model starts with a centralized product catalog that can support a clear line from product to price:
This matters most when Microsoft or another supplier updates pricing. Instead of asking which spreadsheet holds the European Microsoft 365 prices, the business can identify which products, currencies, customers and subscriptions a cost or pricing change affects. That turns the product catalog into part of the financial control system rather than simply a list of SKUs.
What good multi-currency CSP operations should look like
A scalable model connects four areas.
Centralized product and pricing control
Products, supplier costs, currencies, price lists and pricing strategies are governed centrally rather than maintained across disconnected files.
Currency-aware billing
Customers are billed using the appropriate currency, pricing rules, billing schedules and commercial terms.
Supplier-to-customer reconciliation
The business can compare what Microsoft and other suppliers charged against what customers were billed.
Margin visibility
Finance can see when supplier costs, exchange-rate movements, discounts or customer pricing move margin away from expectations.
Together, these controls turn multi-currency billing from an administrative process into a financial operating capability.
How Work 365 approaches multi-currency CSP billing
Work 365 recon-based multi-currency billing
Work 365 brings subscription management, billing and financial operations together, so multi-currency is handled as part of the revenue process rather than as an isolated invoice setting. Partners can manage invoicing across currencies, regions and legal entities, apply pricing and tax by market, and reconcile customer billing against charges coming from Microsoft and integrated distributors, so differences can be identified before invoices go out. Customers can also self-serve upgrades, renewals and seat changes through Engen, the customer-facing app included with Work 365.
For CSPs operating across markets, the objective is straightforward: one governed revenue process, even when the currencies are not the same. You can explore the CSP billing platform, reconciliation and Azure usage billing to see how the pieces connect.
Multi-currency is not really about currency
Currency conversion is arithmetic. The difficult part is everything around it. Which price was valid? Which exchange rate applied? Which supplier cost was received? What did the customer contract specify? What was ultimately invoiced? And did the transaction produce the margin the business expected?
For Microsoft CSPs expanding across markets, those questions become more important, not less. The opportunity is to know, with confidence, that the invoices are correct and the economics behind them are too.