Why price data needs currency context before comparison

A spreadsheet with columns called “Price” and “USD price” can look ready for analysis. Yet those headings often conceal the information that determines whether a comparison is sound.

Did the conversion use the transaction date, the latest available exchange rate, a monthly average, or an internal planning assumption? Does “price” include tax and freight? Is it a list price, a negotiated quote, or the amount actually paid?

Currency is not a display setting added after the fact. It is part of the measurement context. Converting two figures into one currency may be necessary, but it does not make the figures comparable by itself.

First, decide what question the comparison is meant to answer

Two common questions call for different treatments of currency.

The first is about cash: What will we pay a supplier? What will we receive from a customer? What is our payroll exposure when reported in a headquarters currency? For these questions, a documented market exchange rate or contractual rate is usually the relevant tool. The rate should reflect the payment timing and any applicable treasury or hedging policy.

The second is about relative local price levels: What does a salary represent in one country compared with another? How do broad operating conditions or economic output compare across places? Purchasing-power-parity, or PPP, measures can be useful here. They are designed to adjust for differences in national price levels, rather than to translate currency units at the prevailing foreign-exchange rate.

Those are both legitimate uses of conversion, but they do not answer the same question. A market rate addresses the cash cost of exchanging one currency for another. PPP addresses purchasing power for defined baskets or expenditure categories across economies. Neither is a universal replacement for the other.

Consider a company planning a local marketing budget abroad. A market-rate conversion can show how much funding is needed in the company’s reporting currency. It does not establish whether local advertising, labor, or agency services are relatively expensive. That requires price-level context, often broader than one exchange-rate calculation can provide.

The date is part of the number

Exchange rates change. A historical local price converted at today’s rate blends two separate movements: a change in the item’s local price and a change in the currency’s value.

That may be appropriate for a current revaluation exercise, but it is not the same as reporting the price as it was understood when observed. Keep the observation date separate from the conversion-rate date, and label the rate type. A spot rate, end-of-period rate, period average, budget rate, and contractual rate can each be defensible in different settings.

A supplier comparison makes the risk clear. Suppose Quote A is 10,000 CAD and Quote B is 7,400 USD. A conversion based on an undocumented rate produces a precise-looking ranking. It does not establish which quote is cheaper until the team confirms the quote dates, payment terms, expected settlement date, taxes, freight, quantity, and product configuration.

The arithmetic may be correct while the decision is wrong.

A currency symbol is not enough

A dollar sign does not identify a currency. Several currencies use it, and a symbol alone is easily separated from its original context when data moves between systems.

Use an ISO 4217 currency code, such as CAD or USD, alongside the original amount. ISO 4217 provides standardized alphabetic and numeric codes and records currency-specific minor-unit relationships. That last detail matters: systems should not assume every currency uses two decimal places.

Most importantly, retain the source amount and source currency after conversion. The converted figure is an analytical derivative, not a replacement for the observed price. Preserving both lets a later reviewer update a rate, test a different scenario, or trace an apparent discrepancy without reconstructing the source record.

Conversion cannot repair a mismatched price basis

Before debating the right rate, establish whether the prices describe the same thing.

A tax-inclusive consumer price and a tax-exclusive business quote should not share a straightforward ranking. The same applies to delivered versus ex-works terms, annual subscriptions versus one-time purchases, different quantities, different contract durations, and different discount assumptions. A national PPP measure is not a substitute for a quote on a specific product with specific terms.

PPP estimates also deserve careful interpretation. They rely on defined baskets, expenditure categories, and reference periods. They are statistical estimates, not exact product-level exchange rates or proof that one currency is correctly valued. Small differences between PPP-adjusted figures may not support a confident ranking.

For a specific procurement decision, match the product and commercial terms first. For a broad comparison of wages, affordability, or economic quantities, consider whether a relevant PPP or price-level measure better fits the question. For cash settlement, use a documented market or contract rate.

A small record that holds up later

A comparison-ready price record does not need to be elaborate. It should include:

• price_original
• currency_iso
• price_observed_date
• price_basis
• fx_rate
• fx_rate_date
• fx_rate_type
• price_converted
• comparison_notes

The price_basis and notes fields carry much of the practical meaning: tax treatment, delivery terms, quantity, configuration, discount status, and contract duration belong there or in their own structured fields.

Before ranking prices, ask five questions: Is it the same thing? Under the same terms? On the same currency basis? At the same time basis? For the same decision?

If any answer is no or unknown, the result may still be useful. It just needs a qualifier instead of false certainty.