Multi-currency in QuickBooks Online: stuck toggles and locked currencies

Multi-currency in QuickBooks Online generates a steady stream of community questions, and most of them pile into three familiar walls. The feature toggle fails with a vague error. The option is missing entirely on some plans. And a currency already assigned to a customer or supplier cannot be changed. The formally accepted guidance, drawn from a vendor FAQ covering the Canadian edition, treats each wall separately; most of the frustration comes from mixing them up.

The feature exists so a business can bill an overseas customer or pay a foreign supplier in that party’s own currency. Around that promise sit hard rules, and users keep finding them the hard way.

The toggle fails and the message says almost nothing

Users flipping the multi-currency switch are sometimes stopped by an on-screen notice that something is not quite right, and nothing more. The wording is generic, appears elsewhere in the product, and sends people hunting for account trouble that is not there.

The accepted fix is small. Clear the browser’s cache and cookies, sign in from a private or incognito window, or use a different browser altogether. Our suggested order starts with the private window, because it cleanly separates a stored-cache problem from an account problem. If the switch works there, stale session data was the cause and a cache clear finishes the job. If it still refuses in a second browser, move on to the plan check below.

Is the plan the real blocker?

Not every subscription includes the feature. In the vendor’s documentation, multi-currency is limited to the Essentials and Plus tiers of QuickBooks Online. Canadian subscribers on the entry-level EasyStart plan have no working toggle to troubleshoot at all; for them the path is an upgrade, not a cache clear. Accountants working in QuickBooks Online Accountant meet the same rules, according to the same FAQ.

Diagnosis therefore comes first. A browser fix achieves nothing when the plan simply lacks the feature, and an upgrade changes nothing when the culprit is a stale cache. Confirm the tier before spending effort on either.

Why can’t a customer’s currency be changed?

This is the rule that surprises the most people. Once a customer or supplier profile exists, its currency is locked. There is no edit field and no supported override, because that currency underpins how every recorded transaction for the name is valued.

The workaround is a rebuild. The accepted answer describes it: note the profile’s details, make it inactive from the list’s action menu, then create a replacement and pick the new currency from its dropdown. The same steps apply to customers and suppliers alike; only the starting list differs. The answer also suggests adding the currency to the display name, a tip that matters more than it looks. Lists sort alphabetically, and two near-identical names invite misposting during data entry.

A few consequences deserve a warning. Inactive does not mean deleted, so history stays attached to the old profile and reports will show one real-world customer under two entries. Where the timing is flexible, run the swap at a period boundary so the split reads cleanly afterward.

The setting only runs one way

The deeper constraint explains the rest. Enabling multi-currency permanently changes how the file calculates amounts, and it cannot be switched back off. The vendor’s guidance on plan changes reflects that permanence: move only between subscriptions that support the feature, in either direction.

Treat the decision as a commitment, in other words. Settle the question before the first foreign-currency transaction, not after it.

Our read

Three complaints share one headline. The browser error is a session problem wearing an accounting costume. The missing toggle is a plan gate. The locked currency is a data rule, and a defensible one: rewriting the currency on a name with history would rewrite what those transactions are worth. The rebuild is clumsy, but it is honest about that.

Our suggested order, assembled from the accepted answer: test in a private window, confirm the subscription tier, and schedule any profile rebuild for a clean period end. None of it requires outside help, and every step is faster than chasing a ghost problem through the books.