What it means
A customer signs an agreement priced in euros, but the billing account defaults to dollars and the first invoice uses the wrong currency. This metric checks whether each relevant customer charge is denominated in the currency authorised for that product and term.
Define the authoritative currency from the accepted order, amendment or self-service purchase terms, since a quote shown during negotiation may not be final. Stripe documents multi-currency invoicing and notes that invoice items and credits can be currency-specific, so the billing setup must reflect the intended currency for the right customer.
Identify the legal entity, account, subscription and product, because a group may buy one service in one currency and a separate service in another. Distinguish contract currency, payment currency and accounting presentation currency, as a bank may convert a payment even when the invoice currency is correct.
If conversion is allowed, specify the approved exchange-rate source, date and who bears conversion costs. If a contract has an indexed price, check that indexation changes the amount in the agreed currency and does not silently replace the currency.
For taxes, verify whether the invoice needs tax shown in another reporting currency under the relevant local rules, and do not guess. Currency-specific credits need checking too, because one balance may not offset another automatically.
For a subscription migrated between currencies, verify the effective date and treatment of unused time, and if several invoice lines have different currency origins, follow the accepted billing terms and supported invoice mechanics rather than merging incompatible amounts. Where an order form lists two currency values, clarify which one controls before final billing, since an exchange estimate may be included for convenience without changing the binding price.
Check price-book setup and product rate, since selecting a similarly named USD price is a common operational cause of mismatch. If a salesperson promises a local-currency figure, confirm whether it is binding or merely an estimate.
For a manual invoice, preview the final document before issue and inspect the visible currency symbol and code, because a symbol alone can be ambiguous, and for an automated invoice test the subscription configuration and monitor the actual finalised charge. Define a match at invoice level or line level, state whether one wrong line makes the whole invoice fail, and compare finalised in-scope invoices or lines with the accepted currency effective on the billing date.
Show mismatch causes by order data, product catalogue, account default, manual override and migration. If a mismatch is discovered after issue, use the appropriate credit and replacement process instead of editing historical records invisibly, preserve the agreement and final invoice for audit, recheck the currency at each renewal rather than copying the prior invoice, and where a payer settles in another currency show the conversion or shortfall separately from the vendor's invoice.
In practice
Real-world examples.
Example
A signed order specifies EUR and the first invoice lists the agreed EUR charges. It matches, and the preview step records the visible currency code.
Example
A customer pays a EUR invoice from a USD account and the bank converts the payment. The invoice currency itself still matches, and the conversion is reported separately.
Example
A USD credit balance does not automatically clear a CAD invoice. Billing reviews the currency-specific treatment before applying anything.
Formula
Calculation
Illustrative match rate = finalised in-scope invoice lines with contract-correct currency / all finalised in-scope invoice lines x 100.
Worked example: an invented cloud seller finalises 120 in-scope invoice lines in a month, and 114 are in the currency required by the accepted order. The match rate is 114 / 120 x 100 = 95%. The 6 mismatches trace to 3 account defaults, 2 manual overrides and 1 migration, which tells the team which controls to fix first.Case study
Seen in the real world.
This fictional case follows Lantern Cloud, an invented software company. A global customer's new order was accepted in EUR, but billing copied a USD price from an older account. A pre-finalisation check caught it; the team changed the price configuration and verified the actual EUR invoice.
Afterwards the team searched the price book for other similarly named USD and EUR entries and added the currency code to each price name. The next quarter's sample showed no repeat of the error. The case is invented.
Watch out
Common mistakes.
- Treating bank payment currency as the invoice's contractual currency.
- Using a customer account default instead of the accepted order.
- Assuming a credit in one currency offsets a bill in another.
Questions
People also ask.
Can a customer have more than one billing currency?
It depends on the contract and system setup; map each charge carefully.
Does a matching currency prove the bill is right?
No. Check price, quantity, dates and tax separately.
What if the contract permits conversion?
Use the specified exchange-rate method and disclose the result.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related
