Multi-Currency and Multi-Entity Consolidation in QuickBooks Online
QBO handles multi-currency transactions reasonably well. It does not consolidate entities. Intuit Enterprise Suite does, and it is a separate product with a separate price tag, not a setting you switch on. Those are two different problems and people confuse them constantly.
Turning on Multicurrency is a one-way door. It cannot be switched off, your home currency is locked, and every customer, vendor, and bank account you create gets a currency assigned to it permanently.
Most of the damage I get called in to fix comes from one decision made badly on day one: nobody determined the functional currency before setting up the file.
Start with functional currency, not with software
Functional currency is the currency of the primary economic environment where an entity operates. It is not the currency of the country the entity is registered in, and it is not whatever the parent reports in. It is a determination, and it drives everything downstream.
The factors are cash flow, sales price, sales market, expenses, financing, and intercompany transactions. A subsidiary in the Dominican Republic that bills US customers in dollars, pays its suppliers in dollars, and gets funded by a US parent probably has a US dollar functional currency even though it files taxes in pesos. A subsidiary that sells locally, hires locally, and finances locally does not.
Get this wrong and you will apply the wrong method for years, and it is painful to unwind because it touches every prior period.
Translation versus remeasurement
People use these interchangeably. They are not the same thing and the difference lands in a different place on your financials.
| Translation | Remeasurement | |
|---|---|---|
| When | Books are kept in the functional currency, and you are converting to the parent's reporting currency | Books are kept in a currency that is not the functional currency |
| Assets & liabilities | Closing rate | Monetary items at closing rate, non-monetary at historical rate |
| Equity | Historical rates | Historical rates |
| Income statement | Average rate for the period | Average rate, except items tied to non-monetary balances |
| Where the difference goes | Cumulative translation adjustment, inside equity | Straight through net income |
That last row is the one that matters to an owner. Under translation, currency swings park in equity and leave your earnings alone. Under remeasurement, they hit the P&L every single period. Same business, same currencies, completely different-looking income statement, decided entirely by a determination somebody made once.
What QBO actually does
Once Multicurrency is on, QBO does three things well and one thing not at all.
- Transaction-level conversion. Invoice a customer in euros, QBO records it in euros and converts to your home currency at the rate on the transaction date.
- Realized gain and loss. When that euro invoice gets paid at a different rate, QBO posts the difference to an Exchange Gain or Loss account automatically. This part is fine.
- Home currency adjustments. A separate function that revalues your open receivables, payables, and foreign bank balances at a rate you pick, which is how you get unrealized gain and loss at period end. Most people never run it, which is why their foreign balances drift for years.
- Consolidation. Not in QBO. Each QBO company is its own island, one entity per subscription, with no parent, no subsidiary, no eliminations, and no consolidated trial balance. That is what Intuit Enterprise Suite was built to fix, and it is covered further down.
The consolidation gap, and how people fill it badly
If you run five entities on plain QBO, you have five files and no built-in way to combine them. What most people do is export each trial balance to Excel every month and paste them side by side. That works right up until it doesn't, and here is where it fails:
- Intercompany balances never agree. Entity A says it is owed 40,000 from Entity B. Entity B says it owes 38,500. The difference is usually timing, sometimes an FX rate, occasionally a transaction one side never booked. You cannot eliminate what does not tie.
- The eliminating entries live nowhere. They get typed into a spreadsheet each month and re-typed the next month. Nobody can reconstruct last March.
- The chart of accounts is different in every file. Five entities, five people who set them up, five versions of what "Professional Fees" means. Mapping is manual and it changes when someone adds an account.
- The translation adjustment becomes a plug. If your CTA is whatever makes the balance sheet balance, you do not have a CTA. You have a rounding error with a formal name.
The fix is not a better spreadsheet. It is a uniform chart of accounts across every entity, an intercompany matrix that gets reconciled monthly before anything is combined, and a consolidation workbook where the eliminations are documented entries rather than typed numbers. Build it once and it runs in a couple of hours a month. Build it never and it takes a week and still doesn't tie.
Intercompany transactions are where it usually goes wrong
Two things to get right. First, every intercompany transaction needs a matching entry on both sides in the same period. That sounds obvious. In practice one entity books the invoice in March and the other books the payment in April, and now your eliminations are off by the amount in transit. Run an intercompany reconciliation before close, not after.
Second, the FX treatment of intercompany balances depends on what the balance actually is. A short-term trade payable between entities generates ordinary gain and loss. A long-term advance that is effectively part of the parent's net investment in the subsidiary, with no plan for settlement in the foreseeable future, gets its exchange difference pushed into the translation adjustment instead of earnings. Classify these on purpose. Nobody does it by accident.
Intuit Enterprise Suite, and whether it is worth it
Intuit launched Enterprise Suite in September 2024 to sit in the gap between QBO and a real ERP. Multi-entity management is built into the core rather than bolted on. Consolidated balance sheets and P&Ls run across entities, intercompany transactions generate the matching receivable and payable automatically instead of by journal entry, and you manage a shared chart of accounts with mapping rules and elimination settings in one place.
It also brings Dimensions, which is Classes and Locations taken several steps further. Up to 20 of them, one class plus nineteen custom fields, with unlimited values in a hierarchy. If you have ever run out of room trying to slice by entity and department and project at the same time, that is the fix.
Two things to be clear about. It is a different product, not an upgrade button. Intuit says plainly it is not a cloud version of QuickBooks Desktop Enterprise, and moving to it is a migration. And Intuit does not publish list pricing. Independent estimates put it somewhere around $8,000 per year for a single entity and $12,000 to $15,000 or more for multi-entity, against roughly $25,000 to $30,000 and up for NetSuite. Two entities are included and you can add up to 50.
So which tier are you?
Stay on QBO with a disciplined consolidation if you have two or three entities, a monthly reporting cycle, and a uniform chart of accounts. At $8,000 to $15,000 a year, Enterprise Suite has to save you a lot of hours to pay for itself, and for three entities a well-built consolidation workbook usually wins on cost.
Look hard at Enterprise Suite when the entity count climbs, intercompany volume is heavy enough that manual matching is eating real time, you need consolidated numbers more often than monthly, or auditors want an elimination trail a spreadsheet cannot produce. Its own users describe saving ten to fifteen hours a month per account manager on multi-entity work, and at those volumes it stops being a luxury.
Skip it if you are inventory-heavy. This is the honest limitation. Inventory support is basic, and manufacturers, distributors, and product businesses hit that ceiling fast. Reviewers say it directly: strong for service-based mid-market groups with multiple entities, a clear pass for anyone whose operations depend on inventory depth. Also be aware that intercompany setup is more involved than the marketing suggests.
One caveat that applies at every tier, and it is the one I care most about. Enterprise Suite automates the consolidation. It does not create the discipline underneath it. Shared chart of accounts, mapping rules, and elimination settings are all things somebody has to define correctly. If your five entities currently use five different versions of the chart of accounts, buying software does not fix that. It just gives the mess a faster engine. Fix the structure first, then decide whether you still need the platform. I have watched companies spend six figures migrating to solve what was really a chart of accounts problem, and arrive at the same problem in the new system.
What to fix first
- Document the functional currency for each entity, with the reasoning. One page per entity. If nobody has ever done this, everything below it is guesswork.
- Standardize the chart of accounts across every entity, same numbers, same names, same meanings.
- Reconcile intercompany monthly, before you consolidate, not after.
- Run home currency adjustments at each period end so unrealized positions are actually on the books.
- Move the eliminations out of freehand cells into documented entries you can point at a year from now.
Questions I get asked
If you are combining entities in a spreadsheet and the translation adjustment is whatever makes it balance, that is worth a look. Thirty minutes, no charge, and I will tell you straight whether the structure is sound or whether you are papering over something.
Book a Free Call