Is dual-currency bookkeeping the same as inflation accounting under IAS 29?

No. Dual-currency bookkeeping means recording transactions in a local currency and a stable currency in parallel, mainly for operational clarity on pricing and margin. IAS 29 inflation accounting is a formal financial reporting standard requiring restatement of entire financial statements using a general price index, plus recognition of a gain or loss on net monetary position, once an economy is classified as hyperinflationary.

Does a small shop need to apply IAS 29?

Almost always no. IAS 29 and equivalent US GAAP highly-inflationary-economy guidance apply to entities that produce formal, audited financial statements — typically larger companies, subsidiaries of multinationals, and listed businesses. A small retailer without statutory audit requirements isn't obligated to restate its books this way, though the underlying currency depreciation still affects its real margins.

What triggers 'highly inflationary' treatment under US GAAP?

Guidance summarized by major accounting firms generally treats an economy as highly inflationary once cumulative inflation over a three-year period reaches roughly 100% or more, at which point foreign entities operating there are remeasured as if the reporting currency were their functional currency.

Why would a small shop bother tracking a second currency if it isn't required to?

Because local-currency profit figures can be misleading when the currency is depreciating quickly. Tracking sales and stock value in a stable currency alongside the local currency gives a more honest, immediate read on real margin and purchasing power, which matters for restocking and pricing decisions long before any formal accounting standard comes into play.

Is there a recent regulatory change affecting dual-currency or inflation accounting rules?

Not a new standards change in the recent period reviewed here. The most relevant recent development is retail-focused research examining how sustained inflation is reshaping pricing, assortment, and margin management — a research signal about ongoing pressure, not a new accounting rule.

Dual Currency vs. Inflation Accounting: What Small Shops Actually Need to Track

TL;DRDual-currency bookkeeping (recording sales in local money plus a stable currency) and inflation accounting (formally restating financial statements under standards like IAS 29) solve different problems. Most small shops in volatile economies need the first every day; only larger, formally audited businesses in hyperinflationary economies are required to do the second. Confusing the two — or assuming one substitutes for the other — is where shopkeepers and bookkeepers get into trouble.

We build Pultrack, a point-of-sale and inventory app used by small retailers across markets where prices move fast and customers pay in more than one currency. That means we spend a lot of time on a question that sounds academic but isn't: what's the actual difference between "keeping books in two currencies" and "accounting for inflation," and does a corner shop need to worry about both?

Short answer: yes, but not in the same way, and not with the same urgency. This post walks through the distinction, why it matters for margin and pricing decisions on the shop floor, and where the formal accounting standards actually apply versus where they're irrelevant to how most small retailers run day to day.

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

Dual currency is a bookkeeping and systems design choice. A shop records transactions in its local currency and, in parallel, in a second, more stable currency — often the US dollar — so that stock value, prices, and daily takings stay legible even as the local currency slides. Enterprise software vendors like Oracle describe this as maintaining parallel currency values in the same ledger so a business can report and reconcile in either currency without re-entering data [3].

Inflation accounting is something else: a formal financial reporting treatment. Under IAS 29, entities operating in a hyperinflationary economy must restate their financial statements — not just note a second currency, but actually adjust historical figures — into units of current purchasing power at the reporting date, using a general price index [5]. That's a materially heavier lift than just showing two currency columns on a receipt.

The two are related in that both respond to the same underlying problem — a currency losing value fast — but one is an operational workaround and the other is a compliance and audit requirement.

When does a business actually have to apply IAS 29?

IAS 29 applies once an economy is judged hyperinflationary, and it requires restating the whole set of financial statements, not just prices, plus recognizing a gain or loss on the entity's net monetary position in profit or loss [5]. That last part trips people up: holding cash or receivables in a rapidly devaluing currency itself creates a loss that has to show up in the accounts, separate from normal trading profit or loss.

US GAAP guidance, as summarized by the major accounting firms, uses a rougher trigger: an economy is generally treated as highly inflationary once cumulative inflation over three years reaches roughly 100% or more, at which point a foreign subsidiary's books are remeasured as though the parent's reporting currency were its functional currency [2][6]. Guidance from the Zimbabwe Institute of Chartered Accountants on IAS 29 walks through this restatement process in detail for economies that have lived through extreme, sustained currency depreciation [1].

In practice, this level of formal restatement is done by companies with statutory audits — banks, listed companies, multinationals with local subsidiaries. A single-till grocery shop is not filing IAS 29-compliant financial statements. But the shop is still exposed to the same underlying economics: cash sitting in local currency loses real value between the morning open and the evening count.

Why does a small shop use two currencies without doing formal inflation accounting?

Because the shop's actual problem is simpler and more immediate than financial reporting: it needs prices, margins, and stock value to stay meaningful from one day to the next. If a shopkeeper prices in local currency only, and that currency depreciates between restocking and selling through the shelf, the "profit" on paper can be an illusion — the local-currency total might be higher, but it may not buy back the same amount of stock.

Recording a stable-currency value alongside the local price — the dual-currency approach — gives an immediate, informal check on real margin without needing a price-index restatement. This is why dual currency shows up as a practical feature in general ledger and ERP systems aimed at businesses operating across currency zones, as documented in Oracle's own product guidance [3]. It's a systems answer to a cash-flow and pricing problem, not a substitute for statutory inflation accounting — but for a small retailer, it's the layer that actually matters operationally.

What does current research say about inflation's effect on retail pricing?

Academic literature on retail pricing under sustained inflation is still catching up to the scale of recent currency volatility in several markets. A recent review of retailing research during periods of high inflation notes that inflation is actively reshaping how retailers set prices, manage assortments, and protect margins — pointing to open questions about how retailers should respond operationally rather than settled, universal answers [8]. It's worth being direct about the evidence base here: this is a research review synthesizing what's known and unknown, not a new standard or regulatory change, and there isn't a fresh accounting-standards update in the last month that changes how dual currency or IAS 29 should be applied. The practical pressure on small shops — repricing shelves multiple times a week, quoting in two currencies, and protecting margin against a moving exchange rate — is real, but it's a continuation of long-standing dynamics rather than a new policy shift.

How should a small shop think about this without an accounting department?

Most small retailers don't need to resolve the IAS 29 question at all — that's a concern for their accountant or auditor if and when the business grows into audited financial statements. What they do need is discipline around three things:

Recording each sale's value in both local and stable currency at the time of sale, not after the fact, since exchange rates can move within the same trading day.
Valuing stock on hand in the stable currency as well as local currency, so restocking decisions reflect real purchasing power rather than a nominal local-currency profit.
Keeping a simple, consistent exchange rate policy — even an imperfect one applied consistently beats an ad hoc rate changed customer by customer, which makes margin tracking meaningless.

This is the specific gap we designed Pultrack's offline-first, dual-currency ledger to close: every sale, stock movement, and cash count is captured in both currencies at the point of transaction, so a shop owner can see real margin in a stable currency without waiting for a bookkeeper to reconcile it weeks later. That's a product design choice on our part, not a claim that it satisfies any formal accounting standard — for statutory reporting under IAS 29 or highly-inflationary-economy rules under US GAAP, a shop still needs its accountant [1][2][5][6].

What should shopkeepers and bookkeepers take away from this?

Dual currency and inflation accounting solve adjacent but distinct problems, and conflating them leads to two common mistakes: assuming that quoting prices in US dollars is itself a form of inflation-proof accounting (it isn't — it's an operational hedge), or assuming that because a shop isn't a multinational subject to IAS 29, currency depreciation doesn't need tracking at all (it does, informally, every single day). Getting the distinction right lets a small retailer make sharper pricing and restocking decisions now, while leaving the formal restatement work to the accountants who actually need to produce audited statements under standards like IAS 29 or US GAAP's highly-inflationary-economy guidance [1][2][5][6].