A finance director recently inherited three subsidiaries over 18 months. One came through an acquisition, two through international expansion. Each entity was set up properly in Business Central, with its own currency and clean month-end close.
The payment side was a different story. One entity used a legacy gateway, another had a separate account set up to get payments running quickly, and the third still collected checks.
The general ledger told one unified story. The payment infrastructure told three separate ones.
Business Central handles multi-currency accounting well. Its native multicurrency functionality supports sales and purchases in different currencies, with exchange rates that can be updated as needed.
The challenge is multi-entity payments in Business Central. That is a payment infrastructure problem, not an accounting problem.
The Gap Between the Ledger and the Gateway
Multi-currency accounting determines how transactions are recorded after money moves. Multi-entity payment processing determines how that money is collected, in the right currency and attributed to the right legal entity.
The common setup is one gateway account per entity. Each subsidiary gets its own merchant ID, dashboard and settlement schedule. Gateway compatibility requirements can also make separate merchant IDs necessary for different entities.
That becomes increasingly difficult as the organization grows. A customer paying two subsidiaries may have to enter their card information twice. Treasury teams may need to reconcile deposits across several gateway reporting systems. A processor change becomes a separate project for every entity.
Why Growth Makes the Problem Worse
Acquisitions often mean inheriting an existing payment setup alongside the acquired business. International expansion adds new currencies, local payment preferences and, in some cases, regional gateway requirements.
That complexity is becoming more relevant as digital B2B payments continue to expand. Juniper Research projects the global value of B2B payments to grow 40% between 2024 and 2028, with cross-border payments representing a significant part of that growth.
Business Central add-ons can address parts of the accounting challenge. For example, multi-entity management tools can consolidate intercompany transactions and reporting. But a clean consolidated ledger does not automatically solve disconnected payment relationships.
A Connector-First Approach to Multi-Entity Payments
A more scalable approach is to separate payment acceptance from the entity-and-gateway relationship.
A gateway-agnostic connector supporting more than 120 gateways can allow organizations to extend their existing payment infrastructure as new entities or currencies are added.
That also makes it possible to keep an existing merchant account when it makes sense, rather than replacing a working relationship simply because a new entity needs to be connected.
Independent card vaulting adds another layer of flexibility. When tokenized card data sits in a vault outside any individual gateway, payment methods can move across entities and processors without forcing customers to re-enter their card information.
What Business Central Teams Should Ask
If your organization operates multiple companies or currencies in Business Central, a clean ledger does not necessarily mean the payment infrastructure is scalable.
Start with a simple inventory: How many gateway relationships exist today? Where does the card data live? What happens when you add another entity or currency?
The goal is straightforward: multi-entity payments in Business Central should scale with the organization, rather than requiring every new entity to start over.
To see the full discussion, read on USTPay's website.