Is dual-currency accounting the same as inflation accounting?

No. Dual-currency accounting is a systems choice for recording transactions in two currencies, typically a local operating currency and a group reporting currency. Inflation accounting is a statutory requirement (IAS 29 under IFRS, or the equivalent ASC 830 guidance under US GAAP) that applies when an entity's functional currency belongs to a hyperinflationary economy. A business can need one without the other.

What triggers the requirement to apply IAS 29?

IAS 29 applies when an entity's functional currency is that of a hyperinflationary economy. IFRS describes qualitative and quantitative characteristics for identifying this — such as cumulative inflation over three years approaching or exceeding roughly 100%, and a population that prefers to hold wealth in a stable foreign currency rather than local money — rather than a single fixed percentage threshold.

Does having a multi-currency POS or ERP system mean my books are inflation-compliant?

No. A dual-currency ledger feature, like the one described in Microsoft Dynamics 365 Finance documentation, lets a business track parallel currencies for reporting convenience. It does not perform the restatement of non-monetary items or the net monetary position adjustments that IAS 29 or ASC 830 require. Those are statutory accounting exercises typically done by an accountant, not a POS feature.

What retail items get restated under inflation accounting, and what doesn't?

Monetary items — cash, receivables, payables — are generally not restated because they're already expressed in current money terms; instead, holding them during inflation generates a net monetary gain or loss. Non-monetary items, especially inventory and fixed assets, are restated using a general price index, which matters enormously for retailers because it directly affects reported margins and inventory valuation.

What's the most useful thing a small shop can do about this without hiring a full finance team?

Keep clean, timestamped, dual-currency transaction and inventory records at the point of sale, and hand that data to whoever prepares statutory accounts. Reliable transaction capture is a POS problem; inflation-adjusted restatement is an accounting judgment problem, and conflating the two is where many shops get into trouble.

When Does a Hyperinflation Economy Actually Force New Accounting Rules? A Guide for Retailers

TL;DRDual-currency tracking and inflation accounting solve different problems: one is a systems design choice for running a shop in two currencies, the other is a financial reporting rule (IAS 29 or ASC 830) triggered when a country's inflation crosses recognized thresholds. Small retailers often need both, but having a dual-currency POS does not, by itself, satisfy inflation-adjusted reporting requirements. This post walks through what actually triggers the accounting rules, what gets restated, and what that means for a shop's day-to-day books.

We build Pultrack, a point-of-sale and inventory app for small retailers in emerging markets, many of whom operate in two currencies every single day. So when accountants and standard-setters talk about "hyperinflationary economies," we read closely — because the gap between what a POS system can track and what a set of financial statements must legally do is a gap a lot of shop owners fall into without realizing it.

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

These two ideas get conflated constantly, but they answer different questions.

Dual currency is a systems and reporting design choice. It means a business records the same transaction in two currencies — often a local operating currency and a group or reporting currency — so daily sales, purchases, and settlements can happen in one currency while management or head-office reporting happens in another.
Inflation accounting is a financial reporting requirement that kicks in when an entity's functional currency belongs to an economy classified as hyperinflationary. Under IFRS, that requirement is IAS 29; under US GAAP, the equivalent trigger is covered under ASC 830.

A shop can run a clean dual-currency ledger for years without ever needing to touch inflation accounting — and a shop can be legally required to apply IAS 29 even if it only ever transacts in one currency. The two things move independently, even though in countries like Zimbabwe, Argentina, or Venezuela they tend to show up together.

What actually triggers inflation accounting?

Neither IFRS nor US GAAP relies on a single, fixed inflation percentage as a hard legal trigger, but both frameworks describe qualitative and quantitative indicators — things like cumulative three-year inflation approaching or exceeding roughly 100%, a population that prefers to hold wealth in a stable foreign currency, and prices quoted in that foreign currency rather than local money. The IFRS standard itself, IAS 29, lays out these characteristics for identifying a hyperinflationary economy [1]. The Institute of Chartered Accountants of Zimbabwe has published detailed guidance applying this exact standard in a real hyperinflationary setting, which is a useful read for any retailer trying to understand how the theory plays out in practice [2]. Under US GAAP, the relevant guidance sits in ASC 830, and PwC's foreign currency guide walks through how a foreign entity operating in a highly inflationary economy is treated for consolidation and translation purposes [3]. Deloitte's accounting roadmap covers the specific mechanics of what changes in the accounting once an economy crosses into "highly inflationary" territory under US GAAP [4].

What gets restated, and what doesn't?

This is the part that matters most for a retailer's actual books, and it trips people up constantly.

Monetary items — cash, receivables, payables — are generally not restated under inflation accounting because they're already expressed in current monetary units. Instead, holding monetary assets or liabilities during a period of inflation creates a gain or loss on the net monetary position, which flows through profit or loss.
Non-monetary items — inventory, fixtures, equipment, property — do get restated, using a general price index, to reflect the purchasing power of money at the reporting date. For a retailer, this matters enormously because inventory valuation and margin reporting are the backbone of how a shop understands its own performance.
Under US GAAP, the treatment is different in mechanics but similar in spirit: a foreign entity in a highly inflationary economy has its financial statements remeasured as though the reporting currency were the functional currency, with the remeasurement effect hitting profit or loss rather than being restated for a general price index the way IAS 29 does it.

Both approaches exist because inflation distorts historical-cost accounting in ways that make inventory turns, gross margin percentages, and even simple "are we making money" questions misleading if left unadjusted.

Does dual-currency POS or ERP functionality satisfy this requirement?

No — and this is the single most important point for a small retailer to understand. A system that tracks parallel currency ledgers is a bookkeeping convenience, not a compliance mechanism. Microsoft's Dynamics 365 Finance documentation describes a "dual currency" feature that lets the reporting currency function as a second accounting currency, so parallel currency calculations flow into general ledger consolidation [5]. That's genuinely useful for a retailer whose local sales and vendor settlements happen in one currency while group reporting happens in another. But repurposing a reporting currency inside an ERP ledger is not the same operation as restating non-monetary balances for a general price index under IAS 29, or remeasuring a subsidiary's functional currency under ASC 830. One is a data-structure feature; the other is a statutory adjustment that typically involves an accountant, a chosen price index, and judgment calls about what counts as monetary versus non-monetary. We'd add — and this is squarely our own view, not something drawn from the sources above — that most small shops don't need to solve inflation accounting inside their day-to-day POS at all. The practical move is to keep clean, timestamped, dual-currency transaction records at the point of sale (so nothing is lost or estimated after the fact), and hand that clean data to whoever prepares the statutory accounts, whether that's a bookkeeper, an accountant, or a franchisor's finance team. Pultrack is built around that first job: reliable dual-currency transaction capture that works offline and reconciles cleanly. We don't do IAS 29 restatement, and we're upfront that no POS product should claim to.

What should a retailer actually do differently?

Separate the two conversations explicitly: "how do we record transactions in two currencies" versus "does our jurisdiction require inflation-adjusted statutory reporting."
If a country's inflation is climbing toward hyperinflationary territory, talk to an accountant about whether IAS 29 or ASC 830 thresholds apply — this is a judgment call informed by cumulative inflation, public behavior, and index availability, not a single number a POS system can flag.
Keep inventory costing data clean and dated, since non-monetary restatement depends heavily on knowing when items were acquired.
Don't assume a "multi-currency" label on any software means inflation-compliant accounting — check what the feature actually does under the hood.

Also worth noting honestly: several of the documents underlying this piece — vendor documentation from Microsoft, and detailed technical guides from PwC and Deloitte — are written for accounting professionals and enterprise finance teams, not corner-shop owners. They're accurate and directly relevant, but they're not consumer-facing explainers, so some translation into small-shop reality (like we've done here) is necessary rather than something to take at face value from a vendor blog.