Map Payment Operations Across Several Entities Before Discussing Consolidation

A merchant with several legal entities may have local finance teams, different storefronts, and separate reconciliation habits that do not fit a single summary.

Draw the organization on a simple page: legal entity, storefront, bank relationship, finance owner, and reporting recipient. Ask the customer to correct it. This exercise frequently exposes a local exception that matters more than the desire for consolidation. It also gives the AE a clean agenda for a follow-up, where each person can confirm the portion they actually own.

Ask which entities accept payments, who owns reporting, and whether leadership wants central visibility or local control. A fictional restaurant group may use one legal entity per region while its loyalty program crosses those boundaries.

Do not assume contracting, settlement, or reporting can be consolidated. Those details need validated scope. Have a buyer say, “We need one dashboard.” Coach the seller to ask what decisions the dashboard must support.

Propose a mapping session that lists entities, systems, owners, and unresolved questions.

Coach the AE to ask one regional finance lead to correct the entity map. Observable progress is a newly identified owner or exception that helps the team evaluate each local requirement. A useful follow-up question is whether each entity closes its books on the same calendar, since reporting deadlines often expose hidden local differences.