Managing virtual cards across multiple ERPs and legal entities

Virtual cards are one of the most effective tools in managing enterprise payments, 76% of large corporations now use them, up from 55% in 2022. The reasons are compelling: transaction-specific controls, 1–2% rebate income, 30–60 days of additional float, and a 75% reduction in card fraud rates versus physical corporate cards.

But there is a gap between virtual card adoption and virtual card management at enterprise scale. And that gap appears the moment a programme crosses entity boundaries.

A single-entity virtual card programme is relatively simple. One ERP. One chart of accounts. One approval hierarchy, and one banking relationship. One issuer, and one reconciliation process. The card is generated, the invoice is paid, and the settlement is matched.

Now consider the reality of a large enterprise: 8 legal entities across 3 countries. SAP in the parent company and two subsidiaries. Oracle NetSuite in the APAC entities. Dynamics 365 in the Middle East operation. Four banking relationships. Five currencies. Different tax jurisdictions. Different approval authorities. Different chart of accounts structures.

Deploy a virtual card programme into that environment entity by entity, and every benefit the card was supposed to deliver, automated reconciliation, unified controls, real-time visibility, fractures along the same lines as the ERP it sits on.

This article examines why virtual card programmes break in multi-ERP, multi-entity environments, what it costs when they do, and what the architectural fix looks like.

Gartner estimates that at least 50% of the largest enterprise ERP buyers employ multiple ERP vendors, not by choice, but through acquisition history, regional requirements, and functional fit.

The entity count compounds it. Research from Harvard Law and the European Corporate Governance Institute found that the top 100 U.S. public companies average 204 major subsidiaries, with a median of 116. Many have structures six or seven levels deep. Even mid-market enterprises commonly operate across 5 to 15 legal entities spanning multiple jurisdictions.

Modern Treasury’s 2025 State of Payment Operations report, surveying financial decision-makers at companies with 500+ employees, found that companies use an average of 6.6 systems to manage payment operations. Forty-nine percent use five or more systems; 13% operate across ten or more.

And 88% of financial decision-makers describe their payment operations as problematic, manual (47%), complicated (35%), slow (27%), or inefficient (26%).

This is the environment into which virtual card programmes are being deployed. Not a clean, single-system landscape where the card can operate as designed, but a fragmented, multi-system, multi-entity reality where every new payment capability inherits every existing integration gap.

When a virtual card programme is implemented entity by entity, each entity with its own issuer relationship, its own ERP integration, its own card management portal, the administrative burden multiplies with every new integration.

Here is how that fragmentation plays out in practice:

Issuer and banking fragmentation

Each legal entity typically maintains its own banking relationships. The AFP’s bank relationship survey found that over 40% of organisations work with 2 to 5 banks, and one in four work with 6 to 10. In multi-entity enterprises, these relationships are often established at the entity level.

When virtual card programmes are tied to these entity-level banking relationships, the enterprise ends up managing multiple card issuer integrations:

• Different card management portals per issuer, each with its own interface, reporting format, and settlement schedule.
• Different interchange rates and rebate structures per issuer, with no consolidated view of total programme economics.
• Different settlement cycles, one issuer settles at 30 days, another at 45, making cash flow forecasting unreliable.
• No cross-entity spend visibility. The parent company can see its own card programme. It cannot see the subsidiary’s. A supplier receiving virtual cards from three different entities appears as three separate relationships.

The result is that your enterprise is running several virtual card programmes, with no way to optimise across them.

Approval hierarchy inconsistency

Every legal entity has its own approval authorities, delegation matrices, and spending thresholds. In theory, these should be governed by a group-wide policy. In practice, they diverge.

Entity A requires two approvals for card transactions above $10,000. Entity B sets that threshold at $25,000. Entity C has no card-specific threshold, it defaults to its general procurement approval policy, which hasn’t been updated in years. Nobody at the group level knows these discrepancies exist, because each entity’s card programme operates in separately.

Seventy-nine percent of organisations were victims of attempted or actual payment fraud in 2024 (AFP). Larger enterprises, those with $1 billion or more in annual revenue, were disproportionately targeted. Inconsistent controls across entities are exactly the kind of structural gap that fraud exploits. An entity-specific control simply highlights the structural vulnerabilities in the rest of your enterprise.

Chart of accounts divergence

Virtual cards deliver their reconciliation advantage by pre-coding each card with GL account, cost centre, and project data derived from the approved invoice. The card settles, and the journal entry is ready. No manual coding is required.

But this only works when the chart of accounts is consistent across entities. In multi-ERP environments, it rarely is.

A standard office supply purchase hits GL 6100 in Australia, GL 5200 in the UAE, and an entirely different ledger at the parent company level. Even entities on the same ERP often maintain divergent charts of accounts, the result of local customisations, historical mergers, or simply different teams making different decisions years apart.

Deloitte identifies chart of accounts design as a foundational challenge in multi-entity finance, and one that most organisations underestimate until it blocks a consolidation, an audit, or a programme like virtual cards that depends on consistent data structures.

When the chart of accounts is inconsistent, every virtual card transaction that crosses entity boundaries requires manual GL mapping or reclassification during consolidation. The “automated” journal entry is only automated within a single entity. At the group level, the mapping problem returns.

Reconciliation multiplication

In a single-entity environment, virtual card reconciliation is straightforward, each card maps to an invoice, the settlement confirms the match, the ERP is updated. The 90% reconciliation effort reduction that organisations report comes from this one-to-one link.

In a multi-entity environment, reconciliation multiplies across every dimension:

• Per-entity bank feeds from different issuers with different settlement formats and schedules.
• Per-ERP posting, the SAP entity posts through a different integration path than the NetSuite entity.
• Intercompany transactions, when one entity pays a supplier on behalf of another, the intercompany journal must be created, matched, and eliminated during consolidation. Sixty to eighty percent of global trade flows through intercompany channels (OECD), and each of these transactions adds a reconciliation layer.
• Multi-currency settlement. A virtual card issued in AED for a supplier who invoices in USD generates an FX conversion that must be captured, recorded, and reconciled across both the card settlement and the invoice record.

Fifty-seven percent of controllers cite multi-entity reporting as the most time-consuming aspect of their financial close. Eighty-eight percent of CFOs say they are blocked from strategic work by manual reconciliation and data cleanup. Virtual cards are supposed to reduce this burden. Deployed without a unified layer across entities, they add to it.

Reporting and visibility blind spots

The most damaging consequence of fragmented virtual card management is the loss of consolidated visibility.

When each entity manages its own card programme through its own portal, the CFO and financial controller have no single view of:

• Total virtual card spend across the enterprise.
• Total rebate income and whether the enterprise is maximising its programme economics.
• Supplier overlap, how many suppliers are receiving cards from multiple entities, and whether consolidating those relationships would improve terms.
• DPO impact, the net working capital effect of card float across all entities combined.
• Fraud patterns that span entities. A fraudulent supplier targeting two subsidiaries in two countries would appear as two isolated incidents in siloed card programmes. In a consolidated view, the pattern is obvious.

This is the issue: virtual cards generate more data per transaction than any other payment method, supplier, amount, time, merchant category, approval chain, settlement status. But when that data is scattered across entity-specific programmes with no aggregation layer, the enterprise knows less about its card spend than it would about a consolidated bank transfer programme.

Three structural variables are amplifying the multi-entity virtual card management challenge.

Virtual card volume is accelerating

B2B virtual card payments will reach $14.6 trillion by 2029. Virtual cards are the fastest-growing B2B payment channel. As adoption increases, the volume flowing through fragmented entity-level programmes will grow proportionally, and every operational problem described above will scale with it.

Entity structures are not simplifying

Global enterprises are not consolidating into fewer entities. If anything, regulatory requirements, tax structuring, and geographic expansion are adding entities. UAE free zone structures, Australian subsidiary requirements for government contracts, New Zealand’s separate regulatory environment, each creates another legal entity that needs its own banking, its own ERP instance or configuration, and its own payment infrastructure.

ERP consolidation is slow and expensive

The obvious solution, consolidate all entities onto a single ERP, is precisely what most enterprises have been trying and failing to do for decades. Fifty-five to seventy-five percent of ERP projects fail to meet their objectives, and most exceed their budgets by three to four times (Panorama Consulting/Gartner). Waiting on a multi-year, nine-figure ERP consolidation simply serves as an excuse to delay modernizing your virtual card programme.

The reality is that most enterprises will operate across multiple ERPs and entity structures for the foreseeable future. The virtual card management strategy must work within that reality, and not wait for it to change.

The alternative to entity-by-entity card management is an orchestration layer that sits above the ERP landscape, connecting to every entity’s ERP, every banking relationship, and every card issuer from a single governed platform.

The orchestration layer reduces the number of handoffs, portals, and manual processes by centralising the functions that are fragmented.

Five capabilities define the model:

1. Multi-ERP connectivity. The platform should integrate with every ERP in the landscape, SAP, Oracle, Dynamics, NetSuite, Sage, through pre-built connectors, not custom development. Invoice data flows in. Payment confirmations and journal entries flow back. Each entity’s ERP maintains its own chart of accounts and posting rules. The orchestration layer handles the mapping.
2. Multi-issuer card access. Entities stop negotiating individual issuer relationships. The platform connects to a broad network of card issuers across geographies and currencies. Card selection is driven by supplier acceptance, interchange economics, and currency, the bank that happens to serve a given entity is irrelevant.
3. Centralised policy enforcement. Approval hierarchies, spending thresholds, merchant restrictions, and fraud rules are defined once and applied consistently across all entities. Entity-specific variations, different approval thresholds for different jurisdictions, for example, are configured as rules within the policy.
4. Consolidated reconciliation. Every virtual card transaction across every entity is matched to its source invoice at the moment of settlement, regardless of which ERP processed the invoice, which issuer settled the card, or which currency the transaction used. Intercompany transactions are identified and flagged automatically. The close becomes a single consolidated view.
5. Enterprise-wide visibility. Total card spend, rebate income, DPO impact, supplier overlap, and fraud indicators are visible across the entire entity structure, in real time, not assembled from entity-level exports during quarterly reporting.

SpendConsole’s payables orchestration platform was designed for exactly this environment, enterprises operating across multiple ERPs, multiple entities, and multiple geographies that need unified payment execution without replacing their existing systems.

Multi-ERP integration without consolidation

SpendConsole connects to SAP (ECC and S/4HANA via certified ABAP transport), Oracle NetSuite, Microsoft Dynamics 365, Workday, and other enterprise systems through pre-built integrations. Each entity continues to operate its own ERP. SpendConsole sits above the ERP layer, receiving invoice data from every system, executing payments through a unified workflow, and posting confirmations back to each entity’s general ledger in its own format, using its own chart of accounts.

No ERP consolidation or custom middleware is required. Each entity’s system is respected. The orchestration layer provides the unified governance that the ERP landscape cannot.

Virtual cards from 75+ global issuers

Entities no longer manage separate card programmes. SpendConsole connects the enterprise to virtual card programmes from over 75 global issuers across 50+ currencies. Card issuance is governed centrally, each card is generated at the point of invoice approval with spending limits, expiry dates, and merchant restrictions derived from the approved transaction data.

The entity that processed the invoice determines the posting. The orchestration layer determines the optimal card, issuer, and settlement terms, based on supplier acceptance, currency, interchange rates, and cash position. The enterprise runs one programme, not eight.

Centralised controls, entity-level configuration

Approval workflows, fraud detection, duplicate payment checks, and segregation of duties are enforced consistently from a single platform. Entity-specific rules, different approval thresholds for different jurisdictions, different GL mappings, different tax treatment, are configured within the unified policy framework, not managed as separate programmes.

SpendConsole has helped clients prevent over $18 million in unauthorised payments through these embedded controls, because fraud detection that spans the full entity structure catches patterns that siloed programmes miss entirely.

Automatic reconciliation across all entities

Every virtual card payment, regardless of the issuing entity, the ERP that processed the invoice, or the card issuer that settled the transaction, is automatically linked to its source invoice, purchase order, and approval chain at the moment of execution. Bank feed integration confirms settlements in real time, updating invoice statuses in each entity’s ERP without manual intervention.

The result is a 90% reduction in manual reconciliation effort across your enterprise. Intercompany transactions are flagged and categorised automatically. Multi-currency settlements are captured with FX rates at the point of transaction.

Consolidated reporting and working capital visibility

With every entity’s card programme operating through a single platform, SpendConsole provides real-time visibility across the full enterprise: total card spend by entity, by currency, and by supplier.

Rebate income across all issuer relationships. DPO impact by entity and consolidated. Supplier overlap analysis. Cash flow forecasting that incorporates card settlement timing across all entities, with 95%+ prediction accuracy.

Why do virtual card programmes fail in multi-entity environments?

Virtual cards work by linking each payment to a specific invoice with pre-coded data, GL account, cost centre, supplier, amount. This linkage is straightforward when one ERP and one issuer are involved. In multi-entity environments with multiple ERPs, multiple issuers, and different chart of accounts structures, the linkage breaks. Each entity ends up running a separate card programme, and the benefits of automated reconciliation, unified controls, and consolidated visibility are lost.

Can virtual cards work across different ERPs without consolidation?

Yes, when a payables orchestration platform sits above the ERP landscape and handles card issuance, payment execution, and reconciliation centrally. Each entity continues to use its own ERP. The orchestration layer integrates with each system, maps data between them, and provides the unified governance that no single ERP can deliver across a multi-system environment.

How does multi-entity virtual card management affect reconciliation?

It multiplies the reconciliation burden. Each entity has its own bank feeds, settlement schedules, GL structure, and ERP posting requirements. Intercompany transactions add another layer. Without a unified platform, the finance team must reconcile per entity, per issuer, per currency, then consolidate manually. Fifty-seven percent of controllers cite multi-entity reporting as the most time-consuming aspect of their close.

What is the fraud risk of managing virtual cards across multiple entities?

The primary risk is inconsistency. When each entity manages its own card programme, approval thresholds, merchant restrictions, and fraud detection rules vary. A pattern that spans entities, a fraudulent supplier targeting multiple subsidiaries, for example, is invisible in siloed programmes. Seventy-nine percent of organisations experienced payment fraud in 2024, and larger enterprises were disproportionately targeted. Unified controls across all entities are the difference between entity-level detection and enterprise-level prevention.

How many banking relationships does a multi-entity virtual card programme typically involve?

Over 40% of organisations work with 2 to 5 banks, and one in four work with 6 to 10 (AFP 2024). In multi-entity enterprises, banking relationships are often established at the entity level, meaning the number of issuer integrations for a virtual card programme scales with the number of entities. Platforms that connect to multiple issuers from a single integration point eliminate this scaling problem.

Does SpendConsole replace entity-level ERPs?

No. SpendConsole integrates with each entity’s existing ERP, SAP, Oracle, Dynamics, NetSuite, Workday, and provides a unified orchestration layer above them. Each ERP continues to serve as the entity’s system of record. SpendConsole handles invoice capture, payment execution, reconciliation, and reporting across all entities, posting back to each ERP in its own format using its own chart of accounts.