Multi-entity corporate cards: group management

Financial consolidation, by definition, means combining the accounting data of a parent company and its subsidiaries into a single group-level statement^[3]. A multi-entity corporate card applies the same principle to payments: instead of opening one contract per legal entity, you set up a single group-level solution with a tiered structure. At the top sits the group account, the consolidated view. Below that, as many sub-accounts as there are legal entities or sites. At the edges, physical and virtual cards, each tied to a cardholder and an entity.

The difference from a standard corporate card lies in that hierarchy. A single-entity card records a transaction, full stop. A multi-entity card records the same transaction and knows it belongs to subsidiary X, site Y, and business unit Z's budget, and that it needs to roll up, aggregated, into the group view. This dual read (detailed by entity and consolidated at group level) is what makes the month-end spreadsheet unnecessary.

Below a certain size, a standard corporate card is enough: one company, one perimeter, one set of books. The need for multi-entity structure kicks in once several conditions stack up: a holding company with operating subsidiaries, geographically dispersed sites, business units with distinct economic models, or a presence across multiple countries. This is the core use case covered in the corporate card and business payments white paper.

In France, this profile corresponds to what is officially called an ETI (entreprise de taille intermédiaire, or mid-market company), defined as 250 to 4,999 employees with annual revenue not exceeding €1.5 billion, or a balance sheet not exceeding €2 billion^[2]. Beyond that threshold, you enter large-enterprise territory, where the organizational complexity is the same but at greater scale: several hundred cardholders, dozens of entities, daily cross-border flows.

In both cases, the problem is identical: the more entities you add, the faster manual management falls apart. Finance departments in multi-entity organizations spend a disproportionate amount of time consolidating spend at period-end. Real-world accounts routinely cite more than fifteen working days per month when the process remains manual^[1]. A card built for multi-entity structure attacks that problem at the root.

When evaluating a multi-entity corporate card, five capabilities separate a genuine platform from a bundle of separate contracts:

1. Card hierarchy. The solution must mirror the group's org chart: group → entities → sites → cardholders. Each level inherits the rules of the level above and can add its own. Without this tree structure, you're back to managing in silos.

2. Per-BU and per-site budgets. Being able to allocate a spend cap per business unit or per site, and to revise each independently, is the baseline for managing a group. It is the direct extension of a clear spend policy per corporate card: limits are no longer set only at cardholder level but at entity and spend-category level.

3. Reporting by entity AND consolidated. This is the capability that wins over finance. Reporting must be readable at two levels: detailed per entity for each subsidiary's management controllers, and consolidated at group level for the CFO. Without that dual output, the card doesn't solve the close problem.

4. Multi-country rollout. For groups that cross borders, the card must handle multiple currencies, accept international payments, and ideally issue in the local language and currency, while consolidating into the group's reference currency. Solutions limited to the domestic market undermine the whole point of a single solution.

5. Accounting export and ERP integration. A group has an ERP, a consolidation tool, and an expense management platform. The card should connect to all of them, ideally via API, with a chart of accounts configurable per entity. CSV files sent by email belong to a different era.

Many solutions advertise "multi-entity" on the product page but deliver only a basic consolidation: transactions are aggregated, nothing more. That's not enough. A group needs both reads: the logistics subsidiary's controller needs to see its expenses in isolation, with its own limits and its own chart of accounts; the group CFO needs to see the same transaction consolidated, and be able to trace intercompany flows when one subsidiary paid on behalf of head office.

This is exactly the logic of financial consolidation applied to payments: combining the statements of the parent and its subsidiaries into a single set^[3], while preserving entity-level traceability. Modern consolidation tools do this work in real time rather than at month-end^[1]; a serious multi-entity corporate card applies the same principle to spending, at the moment it happens.

The moment a group has an entity abroad, the solution must handle three complications that domestic-only offerings ignore. First, currencies: the card pays in local currency, but the expense must be converted and consolidated into the group's reference currency, ideally at the transaction-day rate, not a monthly average that masks variances. Second, local regulation: some jurisdictions impose specific rules on card issuance or invoicing. Third, language and local expectations: a receipt in German, an invoice in Spanish, a cardholder who doesn't read French. The interface and support must keep up.

For large enterprises operating across multiple countries, this criterion often becomes a deal-breaker: a card that forces you to manage one provider per country reintroduces exactly the fragmentation that a multi-entity solution was supposed to eliminate. The common-sense rule: one group contract, multiple countries, one consolidated view.

Beyond pricing, five practical questions distinguish the strong offerings from the rest:

On the product side, the Greenway corporate card is built for this kind of structure: a solution that spans from group level down to the individual cardholder, with consolidated reporting and measurable impact. Every transaction also feeds CSR reporting through the 1%ForAll® programme, which counts double for groups making the corporate card a lever for sustainable finance.

The most common mistake among growing groups is settling for a solution that "roughly gets the job done." You open one contract per subsidiary with the same provider, assume consolidation will follow, and three years later your management controllers are still spending month-end reconciling exports. The hidden cost isn't in the subscription fee. It's in the management time and the poor visibility into what the group is actually spending.

The question to ask before signing: will this solution survive the acquisition of a new subsidiary, the opening of a foreign site, or crossing a regulatory threshold? If the answer is "we'd need to rethink the setup," then it's not a multi-entity card: it's a single-entity card in disguise.