Last week a manufacturing team building out a US entity under a European parent asked us a question we hear often: is Business Central enough, or do we need the bigger Dynamics 365 platform? They assumed the answer came down to company size. It usually doesn't.
If you're weighing Microsoft's two ERP options, here's how we think about it, and the two questions that tend to make the decision for you.
It's not about how big you are
There are multi-billion-dollar businesses running on Business Central. Scale alone rarely forces the jump to Dynamics 365 Finance & Operations (often shortened to F&O). So set the headcount and revenue debate aside for a moment. The real dividing line tends to be about how your finance operations work across entities and currencies.
The two questions that usually decide it
- Do you need highly automated intercompany transactions? Business Central can hold any number of legal entities. Where it gets messy is automating the transactions between those entities. If that automation is a hard requirement, that pushes you toward F&O.
- Do you need automated multi-currency translation? If you're consolidating financials across, say, a US and a European entity and you want the platform handling currency translation automatically, that's another strong pull toward F&O.
For the team we spoke with, multi-currency was a clear yes. The intercompany automation question was a maybe, because it depended on how consolidation would work in practice, which is exactly the kind of thing worth confirming with your finance stakeholders before you commit.
| If this is true | Leans toward |
|---|---|
| Multiple entities, but simple or manual intercompany posting | Business Central |
| Automated intercompany transactions across entities | Finance & Operations |
| Single currency, or occasional manual conversion | Business Central |
| Automated multi-currency consolidation | Finance & Operations |
What the manual path looks like
Both questions get read as yes or no, and that reading overstates the gap. Neither capability is missing from Business Central. Business Central posts intercompany transactions and handles multiple currencies. What it does differently is leave more of the work with a person, and past a certain volume that work stops being small.
So the more useful question is what the manual path costs each month, and at what point it outgrows itself.
Intercompany transactions
Business Central ships with intercompany functionality. Each legal entity is set up as an intercompany partner with a mapped intercompany chart of accounts and dimensions. When one entity bills another, someone raises the intercompany document in the originating company (a journal line, a sales invoice, or a purchase invoice) and it lands in the partner company's intercompany inbox. A person in that company reviews it and posts it, and the due-to and due-from entries land correctly on both sides.
The handoff works. What sits outside it is the manual part:
- A person on each end, every batch. Nothing posts in the receiving company until someone opens the inbox and accepts it. Most teams run this weekly or at close, which means intercompany balances are stale in between.
- Transfer pricing is maintained by hand. Markups on intercompany sales live in price lists you maintain separately in each company. When pricing changes, you change it in every company.
- Cross-entity fulfillment takes two documents. A sale booked by one entity and shipped by another needs a sales order in one company and a matching purchase order in the other, created and linked by a person or by a small customization.
- Reconciliation is an export. Confirming that entity A's due-from matches entity B's due-to means pulling both sides and matching them, usually in Excel. Timing and rate differences surface there rather than in the system.
- Eliminations are a journal someone writes. Business Central's consolidation feature imports each business unit into a consolidation company. The entries that cancel intercompany revenue, expense, and balances are prepared each period.
Multi-currency
Transaction-level multi-currency is well covered. Business Central holds an exchange rate table that can update from a rate service, posts customer and vendor documents in foreign currencies, runs an adjustment batch that books realized and unrealized foreign exchange gains and losses, and can carry a second reporting currency in parallel on every posting.
The manual work shows up at consolidation, when a subsidiary's full trial balance has to be translated into the parent's reporting currency at different rates by account type:
- Rates are loaded per period, per business unit. Business Central lets you set a translation method per general ledger account (closing rate, average rate, historical rate, or equity), but someone enters and checks the rates before each run.
- The translation adjustment gets reviewed by hand. The balancing difference translation creates has to land in the right equity account, and someone has to confirm that number is correct rather than an artifact of a wrong rate or a missed account mapping.
- Intercompany balances translated at different rates don't net to zero. This is the usual month-end surprise in a two-currency group, and it clears with a plug journal and a note for the auditors.
- Late adjustments mean re-running. A subsidiary correction after the fact means re-importing and re-translating that business unit, then re-checking the elimination and translation entries that depended on it.
How much effort is involved
Effort scales with transaction volume, not with entity count. Two entities moving 500 documents a month between them is more work than five entities that barely touch each other. The rough shape:
| Your volume | What the manual path costs |
|---|---|
| A handful of intercompany documents a month, a few entities, two currencies | An hour or two during the month, plus half a day to a day at each close. |
| Dozens of intercompany documents a month, or entities that fulfill for each other | Several hours a week, and intercompany reconciliation becomes a named task with an owner rather than something the controller absorbs. |
| Daily cross-entity shipping, several currencies, or a group close on a tight deadline | Effectively a role, and the close date starts moving because of it. |
There is one-time effort as well, and it lands during implementation rather than at the first close: mapping the intercompany chart of accounts and dimensions across entities, building the consolidation business units, and agreeing the translation method for each account.
The other side of the trade is that F&O automates most of the above and asks for a heavier implementation, more configuration surface, and more ongoing administration in return. That exchange pays off when the manual work is large enough, or the close deadline tight enough, that hours at month-end are the constraint.
Four questions for your finance team
The answers below tell you which side of the line you are on more reliably than the yes or no does:
- How many intercompany documents a month at steady state, and what does that look like in two years?
- Does either entity ship, deliver, or invoice on behalf of the other?
- How many days do you have to close, and who is doing the work?
- Does the group report under a standard where the translation adjustment and eliminations need a system audit trail rather than a spreadsheet?
If those come back as low volume, no shared fulfillment, a comfortable close, and no audit-trail requirement, the manual path in Business Central usually costs less than the platform that removes it. If they come back the other way, F&O earns its overhead.
Cost and complexity are part of the trade-off
F&O is a different beast. It carries more cost, more implementation complexity, and more ongoing overhead than Business Central. That's not a reason to avoid it, it's a reason to be sure you need it. If two entities and a currency conversion are your whole story, reaching for the heavier platform can be more machine than the job calls for. If automated intercompany posting across a growing set of legal entities is on your roadmap, the heavier platform earns its keep.
Before you spend real cycles on demos and discovery, get clear yes or no answers on intercompany automation and multi-currency. Those two answers point you at the right door faster than anything else.
Talk it through
We work in Business Central every day and know when a project belongs there and when it belongs on F&O instead. If you're staring at the same fork in the road, reach out and we'll help you sort out which platform actually fits before you invest in a full evaluation.