Does displaying prices in two currencies automatically trigger IAS 29 inflation accounting?

No. IAS 29 applies based on whether your entity's functional currency operates in a hyperinflationary economy, not based on how you display or peg your prices. A shop can use dual-currency pricing for years without being subject to inflation accounting, and a shop pricing in only one currency can still be required to restate its books if that currency's economy is classified hyperinflationary.

What actually changes in a shop's books if the economy becomes hyperinflationary?

Financial statements must be restated in current measuring units using a general price index, and any gain or loss arising from the entity's net monetary position (cash and receivables versus payables) is recognized in profit or loss. This is a formal reporting adjustment separate from day-to-day pricing decisions.

Why do formal small retailers get hit harder than informal traders under dual exchange rates?

Research on Zimbabwean retail markets finds that dual exchange-rate regimes and rapid depreciation disadvantage formal retailers more than informal ones, partly because formal shops carry compliance obligations — fiscalized receipts, statutory books, VAT reporting — that slow down repricing, while informal traders can adjust prices immediately without the same reporting burden.

If I price inventory off a foreign currency, what happens to my records when the exchange rate moves?

The local-currency retail price typically has to change to reflect the new rate, and your accounting records need to capture the revised price and markup at that point. This happens independent of whether hyperinflation restatement rules apply — it's a routine consequence of foreign-currency-linked pricing.

What should a small shop track daily to make year-end accounting easier under dual currencies?

Keep the exchange rate used per transaction, inventory cost layers in the currency actually paid to suppliers, a separate log of FX-driven price changes versus other price changes, and your net monetary position. Keeping these distinct makes it far easier for an accountant to determine later whether inflation-adjusted reporting is required.

Why the Exchange Rate You Price At Isn't the Exchange Rate You Should Report At

TL;DRDisplaying prices in two currencies is a pricing choice, not an accounting rule. Whether you're legally required to restate your books for inflation depends on one thing: whether your functional currency sits in a hyperinflationary economy under IAS 29. New research on Zimbabwean retailers shows dual exchange-rate regimes and fast depreciation squeeze formal shops harder than informal ones — which is exactly why the pricing layer and the reporting layer need to be tracked separately, not treated as the same problem.

We build Pultrack, a point-of-sale and inventory app for small retailers who operate offline-first and often price in more than one currency, so we spend a lot of time on the question shopkeepers actually ask us: "if I'm already showing two currencies on the shelf tag, do I still need to worry about inflation accounting?" It's a fair question, and it's also where a lot of confusion sits — because the two things sound like the same problem but aren't.

What's the actual difference between dual-currency pricing and inflation accounting?

Dual-currency pricing is an operational and commercial decision: you display or peg prices in a second, more stable currency (often USD) because your local currency is volatile, and customers or suppliers expect it. Inflation accounting is a financial-reporting obligation that kicks in only when your entity's functional currency operates inside a hyperinflationary economy. Guidance from the Institute of Chartered Accountants of Zimbabwe makes this distinction explicit: showing two currencies at the till doesn't itself change what your ledgers must legally reflect [1].

Under IAS 29, once an economy is classified as hyperinflationary, entities must restate their financial statements in current measuring units using a general price index, and any gain or loss on their net monetary position flows through profit or loss [1]. That's a books-and-statements requirement. It has nothing to do with whether your shelf tag says "ZWL 45,000 / US$3" — it's triggered by the state of the economy your functional currency belongs to, not by how you choose to price goods.

So does pricing in a foreign currency ever trigger inflation accounting?

Not by itself. The ICAZ guidance is blunt on this point: the trigger is whether your entity's functional currency operates in a hyperinflationary economy — not whether you happen to peg prices to something stable [1]. A shop can run dual-currency pricing indefinitely in a moderately inflationary environment without ever needing IAS 29 restatement. Conversely, a shop that prices everything in one local currency can still be required to restate its books if that economy is formally hyperinflationary. The pricing mechanism and the reporting trigger are decided independently.

Where the two do interact is at the operational level. Oracle's documentation on dual-currency inventory systems notes that businesses in inflationary markets often keep books in both a local currency and a stable currency, with inventory cost layers tracked in both simultaneously [2]. That's a system design choice made to cope with volatility — not evidence that inflation accounting has been "activated." Many ERPs and POS systems support this by maintaining parallel currency amounts, particularly for inventory costing and sales pricing, precisely because retailers need both views without conflating them [1].

What does this look like on an actual shop floor?

A concrete, common case: a shop prices its retail inventory off a foreign-currency cost basis. When the exchange rate moves, the local-currency shelf price has to move too, and the accounting records need to reflect the revised retail price and markup — even before anyone touches a hyperinflation adjustment [3]. This is the daily reality dual-currency retailers already live with:

Supplier invoices arrive in one currency, sales happen in another (or both).
Every FX movement forces a repricing decision — reprint tags, update the register, recalculate margin.
Inventory cost layers need to be tracked in whichever currency you actually paid, not just the one you sell in [2].
None of this, on its own, means your year-end financial statements need general-price-index restatement — that's a separate legal test [1].

Keeping these two layers cleanly separated in day-to-day records is what makes year-end work possible at all. If a shop's till system and bookkeeping blur "the price I charged in USD today" with "what my accountant needs for IAS 29 purposes," reconciling the two later becomes a forensic exercise instead of a routine close.

Why does this matter more for formal small retailers than informal ones?

This isn't just a theoretical accounting distinction — it has real competitive consequences. Recent research on Zimbabwean retailers finds that dual exchange-rate regimes and rapid local-currency depreciation directly disadvantage formal retailers relative to informal ones, and amplify how quickly inflation passes through into consumer prices [4]. Formal shops carry the compliance burden — VAT, fiscalized receipts, statutory books — while informal traders can reprice on the spot without the same reporting overhead. That asymmetry means the shops most exposed to needing correct inflation accounting are also the ones under the most pricing pressure to move fast, creating a structural tension between "reprice today" and "record it correctly."

The practical implication: if you're a formal, registered small retailer operating where dual exchange rates exist, you're simultaneously fighting margin erosion from depreciation and carrying a reporting obligation your informal competitors don't have. Understanding that the reporting obligation is separate from the pricing mechanism at least lets you solve them as two problems instead of one tangled mess.

What should a small shop actually track, operationally, to stay ready either way?

Whether or not your economy is currently classified hyperinflationary, a shop that prices in more than one currency benefits from keeping four things distinct and dated:

The exchange rate used for each transaction, timestamped, not just a daily average pulled from memory.
Inventory cost layers in the currency actually paid to suppliers, separate from the currency displayed to customers.
A running log of price changes triggered by FX movement, distinct from price changes made for other reasons (promotions, seasonal demand).
Net monetary position — cash and receivables versus payables — since that's what IAS 29's gain/loss calculation depends on if restatement is ever required [1].

This is exactly the kind of ledger discipline we think about when designing how Pultrack records dual-currency sales offline: the app logs the rate and both currency amounts at the moment of sale so that if your accountant later needs to separate "pricing decisions" from "reporting adjustments," the underlying data already distinguishes them, rather than needing to be reconstructed from paper receipts or memory. We're not an accounting firm and this isn't a substitute for professional advice on whether IAS 29 applies to your entity — that determination depends on your specific jurisdiction and functional currency, which is a call for your accountant, informed by frameworks like the one ICAZ publishes [1].

What's the honest state of the research here?

It's worth being direct: much of the technical material on dual-currency systems comes from ERP vendor documentation describing how their own software handles parallel currencies [2], which is useful for understanding mechanics but isn't independent evidence of a broader retail trend. The stronger, independent evidence is the accounting standard itself [1] and the academic research on Zimbabwean retail behavior under dual exchange rates [4], both of which point to the same conclusion: pricing flexibility and reporting obligations are governed by different rules, and conflating them is a common — and costly — mistake for small formal retailers.