Does showing prices in two currencies on my POS count as inflation accounting?

No. Dual-currency pricing or reporting is a display and record-keeping feature — showing amounts in a local currency and a reference currency like USD. Inflation accounting under IAS 29 or ASC 830 is a separate measurement issue about how inventory, revenue, and monetary balances are valued when prices are moving fast. A shop can have one without the other.

Do small, informal retailers actually need to follow IAS 29 or ASC 830?

Almost never directly — those standards apply to formal financial statements, typically for entities with statutory reporting or consolidation obligations. But the underlying problem they address, historical costs becoming misleading during high inflation, affects any business tracking margin and inventory value, regardless of formal reporting requirements.

What's the practical difference between IFRS and US GAAP here?

IFRS (IAS 29) restates financial statements for local inflation using a general price index before any currency translation, and recognizes a gain or loss on net monetary position. US GAAP (ASC 830) skips local inflation restatement and instead remeasures the entity's accounts as if the parent's reporting currency were the functional currency, once a three-year cumulative inflation threshold is crossed.

What should a shop owner track if they can't do formal inflation accounting?

Focus on replacement cost of inventory rather than historical purchase price, monitor margin against a stable reference currency, watch how much cash or receivables you're holding in a depreciating local currency, and pay attention to the lag between rising costs and updated shelf prices.

Can POS software like Pultrack handle inflation accounting for me?

POS software can give you clean, timestamped cost and price data in multiple currencies, which is useful raw input for a bookkeeper or accountant. But it does not perform formal IAS 29 restatement or ASC 830 remeasurement — those require professional accounting judgment applied to full financial statements.

Why Your Corner Store's "Books" Break Down During Inflation — Even With Two Currencies on the Shelf

TL;DRShowing prices in local currency and dollars (or euros) on your shelf tags is a pricing tactic, not an accounting fix. Inflation accounting — how you value inventory, cost of sales, and monetary balances — is a separate problem that IFRS (IAS 29) and US GAAP (ASC 830) solve differently, and neither was written with a single corner shop in mind. We build Pultrack, a POS for small shops, so we look at how these rules actually translate to a shopkeeper's daily reality.

We build Pultrack, a point-of-sale and inventory app for small retailers in emerging markets, many of whom price in two currencies and operate offline for hours or days at a time. So when accounting standards bodies publish updated guidance on hyperinflationary economies, we read it — not because most shop owners will ever open IAS 29, but because the effects of that guidance eventually show up in the price of a bag of rice, the margin on a phone case, or how confused a bookkeeper is at month-end. This post is about a distinction that gets blurred constantly: dual-currency pricing and inflation accounting are not the same thing, and mixing them up costs small shops real money.

What does "dual currency" actually mean in accounting terms?

In most retail software and ERP systems, "dual currency" is a display and reporting feature — you record or show transactions in one accounting currency while also presenting balances in a second currency for management or statutory purposes.[6] Microsoft's Dynamics 365 documentation, for instance, describes dual currency as maintaining a second reporting currency alongside the primary ledger currency, not as a mechanism for handling price instability.[15] Multi-currency accounting platforms aimed at small e-commerce and retail businesses describe similar functionality: convert, display, reconcile, but the underlying logic assumes exchange rates move in relatively normal ranges.[13]

That matters because a shop that prices in both local currency and US dollars on the shelf tag is solving a different problem than a shop whose accountant needs to restate financial statements because the local currency lost half its value in a year. The first is a customer-facing pricing choice. The second is a measurement problem that standard-setters have spent decades formalizing.

How do IFRS and US GAAP actually differ on inflation accounting?

This is where the real complexity lives, and it's genuinely different depending on which framework applies to your business or your parent company:

Under IFRS (IAS 29): once an economy is classified as hyperinflationary, financial statements — including comparatives — are restated for changes in a general price index. Non-monetary items, income, and expenses get adjusted, and a gain or loss on the net monetary position is recognized in profit or loss. Only after this restatement are the statements translated into another presentation currency if needed.[3][7]
Under US GAAP (ASC 830): a foreign entity operating in a highly inflationary economy doesn't restate for inflation at all. Instead, once the three-year cumulative inflation threshold is crossed, the entity is remeasured as if the parent company's reporting currency were its functional currency — effectively a remeasurement (temporal method) approach starting the first day of the next reporting period.[16][1]

A 2026 CFA Institute refresher reading summarizes this cleanly: IFRS restates for local inflation before translation, while US GAAP skips local inflation restatement and remeasures directly using the parent's currency as the functional basis.[18] Deloitte's accounting roadmap and KPMG's hyperinflationary-economies guidance both walk through the mechanical consequences for multinational reporting entities — designation of the highly inflationary economy, the effective date of the change, and how monetary versus non-monetary balances get treated differently going forward.[2][20]

Why does this matter for a shop that isn't a multinational at all?

Most small retailers reading this are not consolidating subsidiaries under IFRS or GAAP. They're single legal entities, often informally structured, and their "accounting" is a notebook, a spreadsheet, or a POS export. So why does any of this apply?

Because the underlying economic problem — inventory and cost figures becoming meaningless when prices move fast — is exactly the same problem IAS 29 and ASC 830 exist to fix, just without the formal restatement machinery. A shop that bought stock at last month's prices and is now recording sales at this month's prices, using a bookkeeping system that treats currency units as stable, will systematically understate its true cost of replacing inventory. Academic work on inflation accounting effects on organizational decisions makes this exact point: without some adjustment, historical-cost figures mislead managers about real margins and real capital erosion, even at a small-business scale.[19] Research specifically on Zimbabwean dollar depreciation found that financial statements prepared without inflation adjustment gave management and investors a distorted picture of performance during rapid currency loss.[8]

The IMF's work on currency substitution in high-inflation countries also explains a related, practical phenomenon retailers live with directly: in high-inflation economies, businesses and households often shift pricing and even day-to-day transactions toward a harder currency well before any formal dollarization, precisely because local-currency figures stop being a reliable unit of account.[9] That's the real-world origin of dual-currency shelf pricing — it's a coping mechanism for measurement breakdown, not a substitute for it.

What should a small shop actually track, separate from formal accounting standards?

You don't need to apply IAS 29 or ASC 830 to run a shop well during inflation, but you do need to track the things those standards are designed to protect against distortion:

Replacement cost of inventory, not just historical purchase price — know what it costs to restock today, not what you paid weeks ago.
Margin in real terms, checked regularly against a stable reference (often a hard currency), since local-currency margin percentages can look healthy while actually shrinking.
Monetary balances at risk — cash and receivables held in local currency lose purchasing power the longer they sit; payables in local currency, conversely, can benefit you if inflation is high enough.
Timing of price updates

Formal inflation accounting under IAS 29 exists partly to make this lag visible in financial statements through the net monetary position gain or loss.[3] A shop without formal restatement obligations can still borrow the concept: periodically check whether your cash position, in real terms, is growing or shrinking.

Where does software fit — and where doesn't it?

This is the one place we'll speak directly about what we build, because it's a fair question readers will have. Pultrack supports dual-currency pricing and offline-first operation because that's what shops in unstable-currency environments actually need day to day — the ability to price and sell in two currencies without needing constant connectivity. But we're careful not to oversell this as "inflation accounting." A POS system showing two currencies on a receipt is a pricing and record-keeping convenience; it does not perform IAS 29 restatement or ASC 830 remeasurement, and no small-shop POS honestly should claim to. What good POS data can do is give a shop owner or their accountant clean, timestamped records of cost and sale prices in both currencies — the raw inputs a bookkeeper or accountant would need if formal inflation adjustment ever becomes relevant, for example if the business grows into a group structure with foreign reporting obligations.

Is any of this guidance actually new, or just newly summarized?

It's worth being honest here: most of the material behind this topic isn't breaking news. IAS 29 has existed for decades,[3] ASC 830's highly-inflationary provisions are longstanding US GAAP,[2] and much of what's circulating are refreshed practitioner summaries — PwC's foreign currency guide, KPMG's handbook, Deloitte's roadmap, and a 2026 CFA Institute refresher reading — rather than new rules.[1][16][20][18] There's also a body of academic and vendor-adjacent material (SAP documentation, Brightpearl help articles, a Selinger multi-currency accounting tutorial) describing system mechanics rather than presenting new empirical findings.[6][13][11] We're citing these because they're the clearest current explanations of a persistently confusing topic, not because something changed this month. The genuinely fresh item is the 2026 CFA Institute restatement of the IFRS/GAAP distinction, which is useful mainly as a clean, current reference point.[18]