1. Why legal entity structure matters in everyday banking
Corporate clients often speak about themselves as one group: “Guna Manufacturing,” “Malla Holdings,” “our European business,” or “the treasury company.” A bank cannot stop at that language. Banking rights and obligations attach to legal persons and legal arrangements. The entity that owns an account, borrows under a facility, issues a guarantee, grants security, authorises a payment or enters a cash-pooling agreement matters. The group brand provides commercial context; the legal entity establishes legal capacity and operational authority.
This distinction appears in almost every corporate banking process. During onboarding, the bank identifies the entity that is becoming a customer and the people who ultimately own or control it. During account opening, the account is booked in the name of a particular entity or recognised branch according to the bank's legal and product model. During payments, the debtor account has an owner and the initiating user must have authority connected to that owner. During lending, the borrower and guarantors are named parties to legal documents. During liquidity management, balances may move between entities, creating intercompany positions and legal consequences. During reporting, statements and tax information must be attached to the correct customer.
The errors created by weak entity understanding can be severe. A bank can open an account for the wrong entity, accept a mandate signed by someone without authority, apply a parent's pricing to an unrelated joint venture, sweep cash between companies without appropriate agreement, treat a branch as a separate company when it is not, or rely on a parent guarantee that was never legally executed. These are not cosmetic data-quality problems. They can affect enforceability, financial crime controls, accounting, tax, credit risk and customer rights.
For this reason, mature corporate banks maintain a client hierarchy that distinguishes the economic group from the individual legal customers. The relationship manager sees one group and coordinates the overall strategy. Onboarding, legal, account, credit and transaction systems preserve entity-level truth. Both views are necessary. Group-only thinking loses legal precision; entity-only thinking fragments the relationship.
2. Economic group, accounting group and legal customer are not the same thing
An economic group is a collection of entities connected through ownership or control and managed as a broader enterprise. Consolidated financial statements may present that group as one reporting unit. A relationship manager may negotiate with group treasury on behalf of many subsidiaries. Yet the bank's contracts are still executed with specified legal parties.
Consider Guna Manufacturing plc as the listed parent. It owns Guna Sweden AB, Guna Germany GmbH and Guna USA Inc. The group publishes one consolidated annual report. Group treasury in Sweden manages liquidity for Europe. The bank may call the relationship “Guna Group.” But the Swedish company and German company remain different legal persons. A payment from the German company's account is not automatically a payment by the parent. A loan to the Swedish entity is not automatically an obligation of the German entity unless a guarantee or other legal arrangement creates that obligation.
Accounting consolidation can also differ from legal control. Joint ventures and associates may appear in group reporting under equity accounting or other methods while not being wholly owned. Special-purpose entities may be consolidated for accounting purposes even though their assets and liabilities are contractually ring-fenced. Banking systems should not infer legal rights from accounting treatment alone.
The customer hierarchy therefore needs explicit relationship types. Parent-of, subsidiary-of, branch-of, beneficially-owned-by, jointly-controlled-by, guarantor-of and treasury-service-provider-for are different relationships. A single “related party” flag loses too much meaning. Clear relationship semantics allow downstream processes to make the correct decisions.
Group identifiers are useful for relationship reporting and risk aggregation. They can help the bank see total revenue, total credit exposure, total deposits and all service incidents across a multinational group. But group identifiers should not replace entity identifiers in transaction processing. A payment engine needs the actual account owner. A KYC process needs the actual customer entity. A credit system needs the actual borrower and obligors.
3. Parent companies and holding companies
A parent company controls one or more subsidiaries through share ownership or other governance rights. A holding company may exist primarily to own investments rather than conduct operating activity. These entities often play important roles in corporate banking because debt, guarantees, dividends and capital flows can be concentrated at parent level.
The bank should understand whether the parent is an operating company or a pure holding company. An operating parent may generate its own revenue and cash. A pure holding company may depend on dividends, management fees or upstream distributions from subsidiaries. That difference is central to credit analysis. A holding company can look strong on consolidated accounts while having limited direct cash unless subsidiaries are able and permitted to distribute funds.
Parent entities often provide guarantees for subsidiary borrowing. A guarantee can strengthen the bank's position, but only if it is valid, properly authorised and enforceable under relevant law. Relationship teams should not assume that “group support” is legally equivalent to a guarantee. Letters of comfort, keepwell agreements and formal guarantees can have very different legal effects.
Parents may also centralise treasury policy. They may set bank counterparty limits, approve borrowing, manage hedging and dictate payment controls. The parent can therefore be commercially central even when accounts are legally owned by subsidiaries. The bank must distinguish policy authority within the corporate group from legal authority over a bank account.
In some groups, the parent holds no operating bank accounts and uses a treasury subsidiary instead. In others, the parent owns the main concentration account. The structure should be understood rather than assumed from the corporate name.
4. Subsidiaries: separate legal persons within one group
A subsidiary is generally a separate legal entity controlled by another entity. The precise legal concept depends on jurisdiction, but the banking implication is consistent: the subsidiary has its own legal identity. It may own assets, employ staff, sign contracts, hold accounts and incur debt in its own name.
Wholly owned subsidiaries often create a false sense of simplicity. Staff may say, “It is 100% owned, so the parent can sign.” That is not automatically correct. The subsidiary's directors or authorised representatives must act according to local company law, constitutional documents and approved mandates. The parent shareholder may control board appointments but does not necessarily have direct signing authority over the subsidiary's bank account.
Subsidiaries also matter for cash. If group treasury sweeps excess cash from a subsidiary to the parent or treasury company, the movement can create an intercompany loan or receivable. Local law, tax, thin-capitalisation rules, corporate-benefit principles and insolvency considerations can affect whether the arrangement is permissible. Banks usually require appropriate agreements and legal review for cross-entity liquidity structures.
From a payment perspective, subsidiary identity affects debtor information, account ownership and reporting. A shared-service centre can prepare a payment on behalf of the subsidiary, but the underlying debtor may still be the subsidiary whose account is debited. Systems should capture initiating party and debtor distinctly where the product and message format support that model.
Credit exposure may be separate by subsidiary but aggregated for group risk. A bank may lend to Guna Germany GmbH and Guna Sweden AB under separate facilities while managing a consolidated group limit. Parent guarantees may support both. Credit systems need obligor-level and group-level views simultaneously.
5. Branches: operational presence without a separate company
A branch is generally an establishment of the same legal entity in another location or jurisdiction rather than a separate incorporated company. This distinction is easy to misunderstand because a branch can have its own address, employees, local registration, tax number and bank accounts. Operationally it looks separate; legally it is often part of the head-office entity.
If Guna Manufacturing plc opens a German branch, the branch may be registered locally and operate a German account. But depending on the legal structure, the contracting customer may still be Guna Manufacturing plc acting through its German branch. The bank's customer master needs to represent that relationship correctly. Treating the branch as an unrelated legal person can distort ownership and credit data.
Branches create specific KYC questions. The bank may need documentation for both the head office and local branch registration. Ownership is usually traced through the head-office legal entity. Authorised branch representatives may have local powers, but the bank needs evidence of how those powers arise. The exact requirements depend on jurisdiction and bank policy.
Credit exposure to a branch is typically exposure to the same legal entity as head office, although regulatory, booking and resolution considerations can be more complex for banks and financial institutions. Corporate systems should therefore avoid double-counting the branch as an independent group company unless the risk methodology explicitly requires a separate view.
Branches also affect payment data. The branch may be shown in account names or addresses, while the legal entity remains the account owner. Reporting and tax systems may require branch-specific attributes. A strong data model can represent both without forcing one concept to replace the other.
6. Special-purpose vehicles and financing entities
Special-purpose vehicles, or SPVs, are entities created for a defined transaction, asset, financing or risk-isolation purpose. They are common in project finance, securitisation, real estate, structured finance and acquisition structures. An SPV may have few employees and little conventional revenue while holding substantial assets or debt. That makes ordinary corporate segmentation metrics misleading.
In project finance, an SPV may own the project and borrow against projected project cash flows. Lenders rely on contracts, security, sponsor support and the economic viability of the project rather than the SPV's historic operating record. Bank accounts may be tightly controlled under financing documents, with waterfalls that determine how revenue is applied to operating costs, debt service and distributions.
In securitisation, an SPV may acquire receivables or assets and issue securities backed by those cash flows. Accounts can be subject to strict control agreements. The bank must understand whether it acts as account bank, paying agent, trustee-related service provider or lender, because each role carries different obligations.
SPVs also create ownership and beneficial-owner complexity. An entity can be legally owned by a trust or nominee structure while economically connected to a sponsor. KYC teams must follow applicable rules for identifying ownership and control rather than assuming the sponsor is automatically the customer.
Relationship managers need to recognise that an SPV's apparent simplicity can hide complex legal documentation. Account opening may require review of financing agreements, security interests and permitted account movements. Service teams need to know whether normal account changes require lender or security-agent consent.
7. Joint ventures, associates and minority ownership
Joint ventures are especially important because two or more parties share control. A bank may have strong relationships with all owners, but the joint venture is still its own customer. One shareholder cannot necessarily instruct the bank merely because it owns a large percentage.
Authority may be intentionally balanced. The joint-venture agreement may require directors appointed by both shareholders to approve major actions. Bank mandates can reflect this through signing combinations. Systems and operations must enforce the agreed authority rather than defaulting to the practice used for wholly owned subsidiaries.
Pricing and relationship attribution can also become complicated. Should the joint venture inherit the parent company's global pricing? That is a commercial and contractual decision, not an automatic consequence of ownership. Other shareholders may have their own banking arrangements and expectations.
Credit analysis should consider sponsor support carefully. Shareholders may be willing to inject equity, but that expectation is not equivalent to a binding guarantee. Lenders should assess the joint venture's standalone repayment sources and any formal support arrangements.
Minority-owned associates create similar issues. The parent may include the company in strategic discussions but lack control. Customer hierarchies should record the economic relationship without giving the parent inappropriate access to account information or authority.
8. Treasury companies, finance companies and in-house banks
Many multinational groups create dedicated treasury or finance entities to centralise cash, funding, FX and intercompany finance. These entities can become the bank's most operationally important counterparties even though they do not manufacture or sell the group's products.
A treasury company may own concentration accounts, borrow externally and lend internally to subsidiaries. It may execute FX hedges for the group, operate a payment factory or manage an in-house bank. The bank needs to understand the treasury entity's mandate within the group because transaction volumes can be large relative to its own financial statements.
An in-house bank is not necessarily a licensed bank. It is an internal treasury model in which subsidiaries maintain internal accounts or positions with group treasury. External payments may be centralised while intercompany settlement occurs on internal ledgers. The relationship manager should avoid using “bank” terminology in a way that implies regulatory status where none exists.
Payments-on-behalf-of and collections-on-behalf-of structures can create complex party data. A treasury entity may initiate payments from an account it owns for obligations economically belonging to subsidiaries, or the group may use structures where the subsidiary remains the debtor while a shared service centre initiates. The exact model affects message fields, reconciliation, tax and legal analysis.
Treasury entities also concentrate counterparty exposure. A single treasury company can hold large deposits and execute substantial derivatives. Credit and market-risk teams may view it differently from operating subsidiaries. Group guarantees or cross-default provisions may connect exposures.
When treasury moves jurisdiction, the bank must reassess the structure. Accounts, contracts, KYC, tax documentation, payment setups and liquidity arrangements may all change. A relationship manager should treat treasury relocation as a major corporate event, not an address update.
9. Ownership and control: the bank needs both
Legal ownership tells the bank who holds shares or equivalent interests. Control can arise through ownership, voting rights, agreements, board appointment rights or other mechanisms. Financial-crime frameworks require banks to understand beneficial ownership and controlling persons according to applicable law and policy. Credit and relationship management also need a clear group-control view.
Ownership chains can be simple or deeply layered. A local operating company may be owned by a regional holding company, which is owned by an international holding company, which is ultimately owned by a listed parent. Private groups can end with individual beneficial owners. Trusts, partnerships and foundations can require different analysis.
The bank should record percentages and relationship dates where meaningful. A company that was wholly owned yesterday may become 60% owned after a sale. That change can affect control, guarantees, cash pooling, pricing and KYC. Historical ownership data helps explain why earlier decisions were made.
Control should not be inferred only from percentage ownership. A 50/50 joint venture may have shared control. A shareholder with less than half the shares may have contractual control. Public companies may have no individual shareholder with a large percentage. KYC rules define how to identify controlling persons in such cases.
Complexity itself is not wrongdoing. Multinational groups use holding companies and SPVs for many legitimate commercial, tax, regulatory and financing reasons. The bank's responsibility is to understand the structure sufficiently to assess risk and comply with requirements, not to treat every layered structure as suspicious.
10. How legal structure drives KYB and onboarding
Know Your Business onboarding starts by identifying the precise entity requesting banking services. The bank collects legal name, registration number, registered address, constitutional documents, business purpose, tax information and other required data. It then identifies ownership and control, authorised representatives and expected activity.
Group relationships can reduce duplication only where policy allows. If the parent has already provided ownership evidence that is still valid, the bank may be able to reuse verified data for a subsidiary. But the subsidiary still needs entity-specific documentation and risk assessment. Reuse should be controlled and traceable rather than assumed.
Branches require a tailored approach because the branch may not have shareholders of its own. The onboarding record needs to link the branch to the head-office entity and capture local registration and authorised representatives. SPVs may require transaction-specific documents. Joint ventures require analysis of all relevant owners and control rights.
Expected account activity should reflect the entity's actual role. A treasury company may legitimately send very high payment volumes compared with its operating revenue. An SPV may receive only project revenues and make scheduled debt-service payments. An operating subsidiary may receive customer collections and pay suppliers. Generic expectations based on industry alone can produce poor monitoring.
Onboarding should capture the reason an entity needs each product. This is useful both commercially and for controls. A newly created subsidiary asking for a high-volume cross-border payment service should have an understandable business context. Relationship managers can provide that context; onboarding teams validate it under policy.
11. Account ownership and account purpose
Every corporate account should have a clear legal owner. The display name used in a portal may be friendly, but the bank's core records must identify the contracting customer. This matters for rights to funds, statements, fees, tax reporting, set-off, insolvency and legal process.
Groups often use multiple account purposes: operating accounts, payroll accounts, tax accounts, collection accounts, concentration accounts, escrow accounts, restricted accounts and project accounts. Purpose can influence who should have access and what transactions are expected. The entity owner and business purpose should be captured separately.
Virtual accounts add another layer. A virtual account number can help identify incoming payments without necessarily representing a separate deposit account. The underlying physical account still has a legal owner. Client and bank systems should distinguish virtual identifiers from actual account ownership to avoid confusion in reconciliation and documentation.
Escrow and fiduciary structures require particular care because the account holder may hold funds for a defined purpose or other beneficiaries. Normal corporate-account assumptions may not apply. Legal documentation should determine how funds can be released.
Account closures also depend on entity authority. If a subsidiary is sold, the former parent should not automatically retain access to its accounts. Ownership change triggers review of mandates, digital entitlements and group reporting visibility.
12. Mandates, signatories and corporate authority
Corporate authority is layered. Company law and constitutional documents determine how the entity can act. Board resolutions may authorise account opening or appoint signatories. Powers of attorney may delegate authority. Bank mandates specify who can operate particular accounts. Digital entitlements translate those rights into system permissions.
A person can be a senior executive without being an authorised bank signatory. Conversely, an employee in treasury operations may have authority to approve payments within limits. Systems should enforce documented authority rather than organisational title alone.
Maker-checker structures are common. One user prepares a payment and another approves it. Large amounts may require two approvers or a higher-authority user. Corporate mandates can be more complex than simple “any one signatory” rules. The bank's channel needs to represent combinations accurately.
Shared-service centres add complexity because users may act for multiple group entities. A treasury employee can have permission over the accounts of several subsidiaries if each entity has granted appropriate authority. Access should be account- and entity-specific. Being employed by the parent does not automatically create rights over every subsidiary.
Authority changes need timely maintenance. Staff leave, directors change and powers of attorney expire. Stale entitlements create fraud and operational risk. Banks and clients share responsibility for maintaining current mandates according to agreed procedures.
13. Legal entities inside the payment chain
Payments contain multiple parties, and corporate structures make those distinctions important. At minimum there is an account owner whose funds are debited and a beneficiary whose account is credited. But the initiating party, ultimate debtor, ultimate creditor, on-behalf-of entity and account servicers can differ depending on the payment model.
In a simple payment, Guna Germany GmbH uses its own account to pay Supplier AG. The debtor is Guna Germany. In a shared-service model, a central treasury team may create the payment file, but the debtor remains Guna Germany because its account is debited. The initiating party can be different from the debtor.
In some payment-factory structures, a treasury entity makes payments from its own account on behalf of subsidiaries. The legal and accounting model is different. The bank needs clear onboarding and product support for such arrangements because message party fields, remittance, intercompany accounting and screening may all be affected.
Ultimate debtor and ultimate creditor data can preserve the underlying commercial parties when the immediate account parties are intermediaries. These fields should be used according to message and scheme rules, not as a generic place to store group names. Incorrect party mapping can reduce transparency instead of improving it.
Sanctions and AML screening depend on accurate party data. If a shared-service centre's name is substituted for the actual debtor, the transaction may lose important information. Payment design should preserve legal and economic meaning through channel transformations and internal formats.
Reconciliation also depends on party clarity. A treasury company paying invoices for ten subsidiaries must give accounts payable enough information to identify which entity's obligation was settled. The bank's reporting and remittance handling can materially affect that process.
14. Legal entities in cash pooling and liquidity structures
Cash pooling is one of the clearest examples of why group and legal-entity views must coexist. The economic goal is to optimise liquidity across the group. The legal reality is that balances belong to different entities. Moving or offsetting those balances creates rights and obligations between participants.
In physical pooling, automated sweeps move funds from participant accounts to a concentration account. If the accounts belong to different legal entities, the sweep can create intercompany loans. Documentation should define the relationship, interest and repayment mechanics. Local legal and tax rules can affect participation.
Zero balancing sweeps accounts to zero, while target balancing leaves a defined amount. The mechanics are operational, but ownership determines the accounting. A EUR 5 million sweep from Guna Germany to Guna Treasury is not simply moving money between two “Guna accounts.” It transfers value between separate entities.
Notional pooling offsets balances for interest calculation without physically transferring principal in the same way as physical sweeps. It can still require cross-guarantees or set-off arrangements and is subject to legal and regulatory constraints. The product specialist and legal team determine availability by jurisdiction.
Cross-border pooling adds further complexity: currencies, exchange controls, withholding tax, corporate-benefit rules and local restrictions may apply. A relationship manager should never promise that every subsidiary can join a global pool before specialist review.
Liquidity systems need participant-level data. The concentration account owner, participant account owners, sweep hierarchy, currency, target amounts and credit limits should be explicit. If a subsidiary is sold, it must be removed safely from the structure before ownership transfer takes effect.
15. Borrowers, guarantors, obligors and group credit
Credit relationships often involve more legal entities than the borrower alone. A revolving facility may have several borrowers, parent and subsidiary guarantors, security providers and an agent bank. Each role has legal significance.
Group credit analysis begins with consolidated economics but then asks where debt sits and where cash is generated. A parent holding company may borrow while operating subsidiaries generate cash. Lenders need to understand whether dividends can flow to the parent and whether guarantees provide additional recourse.
A subsidiary loan supported by a parent guarantee creates direct exposure to the subsidiary plus contingent support from the parent according to the legal terms. Credit systems should record the obligors and risk mitigation correctly. Simply assigning the exposure to “Guna Group” hides important legal detail.
Cross-guarantees can connect entities in a cash pool or financing arrangement. Before relying on them, the bank considers corporate benefit, authority, enforceability and local law. Minority shareholders can complicate guarantees because one entity may be asked to support obligations of another group company without receiving equivalent benefit.
Covenants may apply at borrower, guarantor or consolidated group level. Financial reporting requirements can also differ. Operations and relationship managers need to know which entity must deliver which information and when.
When an entity is sold, credit documentation may require mandatory prepayment or guarantee release. Corporate events should therefore trigger credit review before legal ownership changes are treated as mere master-data updates.
16. Tax, regulatory and jurisdictional context
Legal structure is closely connected to tax and regulation, but bankers should be careful about giving tax advice. The bank can explain product mechanics and documentation, while clients obtain their own legal and tax advice where needed. The operating model should know when specialist review is required.
Cross-border interest on intercompany balances can create withholding-tax or transfer-pricing considerations. Cash-pooling participants may need arm's-length interest arrangements. Some jurisdictions restrict upstream loans or financial assistance. These questions can determine whether a proposed structure is feasible.
Entity tax residence may differ from incorporation in complex cases. Banks collect tax information for reporting obligations according to applicable regimes. Relationship data should not assume that registered address alone determines tax status.
Financial institutions add regulatory-entity complexity because branches and subsidiaries can have different licences and supervisory treatment. A banking subsidiary may be separately capitalised, while a foreign bank branch is part of the head-office legal entity. Correspondent banking and credit teams need the correct structure.
Sanctions rules can apply based on ownership and control, not only direct name matches. Accurate ownership hierarchies are therefore operationally relevant to screening and customer-risk assessment. Changes in ownership may alter sanctions risk even if the customer's legal name is unchanged.
17. Designing the legal-entity data model
Bank architecture should treat legal-entity data as foundational master data. Each entity needs a stable internal identifier independent of display name. Names can change; identifiers should preserve history. Registration number, jurisdiction, entity type, status and relationship to parent should be structured attributes.
Group hierarchies should be effective-dated. Ownership changes over time, and systems may need to reconstruct the hierarchy as it existed when a credit decision or transaction occurred. A current-only tree is insufficient for audit and historical analysis.
Relationship types should be explicit. “Branch of” is different from “subsidiary of.” “Guarantees” is different from “owned by.” A data graph can represent multiple relationships, but governance must define which source owns each relationship and how conflicts are resolved.
Legal names should be preserved accurately, including local characters where systems support them. Friendly aliases can help users, but should not overwrite legal names. Payment and screening systems may need both structured legal identity and transliterated forms according to requirements.
Entity status matters. Active, dissolved, merged, sold, in liquidation and dormant have different implications. A dissolved entity should not continue opening new products. A sold entity may remain a customer but move to a different group hierarchy.
Downstream systems should consume entity data rather than maintain isolated copies. CRM, onboarding, credit, accounts, payments and reporting all need related information. Interfaces should carry identifiers so that name differences do not break matching.
18. Corporate events that change legal structure
Mergers, acquisitions, demergers, incorporations, liquidations and reorganisations can change the customer model quickly. A mature bank treats these events as coordinated change programmes.
In an acquisition, the buyer may want immediate access to the target's accounts. The bank cannot grant that simply because ownership changed. Existing mandates remain until properly changed according to legal and contractual requirements. New directors and signatories may need verification.
A legal merger can eliminate one entity and transfer assets and liabilities to another under local law. Accounts, facilities and contracts may need migration or novation. Payment identifiers and statements can be affected. Technology teams need effective dates and cutover plans.
A demerger or spin-off is equally complex. Shared accounts or cash pools may need separation. Credit exposure must be reallocated. Guarantees may need release or replacement. KYC records become independent. Historical transaction access must be handled according to legal rights.
Name changes are simpler but still require coordinated updates. Legal evidence should support the change. Account names, statements, payment reports, customer communications and screening reference data may all need refresh. Stable internal IDs help prevent accidental creation of a duplicate customer.
Liquidation or insolvency can restrict account operation and trigger legal holds. Ordinary corporate authority may be replaced by administrators or insolvency practitioners. Operations needs controlled procedures rather than treating the event as normal mandate maintenance.
19. End-to-end case: Guna Group restructures European treasury
Coverage first maps the intended structure. The parent remains the ultimate listed company. Guna Treasury AB is a wholly owned subsidiary with a treasury mandate. Existing operating companies remain separate legal entities. The acquisition vehicle will temporarily own the target before a later legal reorganisation. This hierarchy is loaded into customer master data with effective dates.
Onboarding performs KYB for Guna Treasury AB even though the parent is already a customer. Verified group ownership information can be reused where policy permits, but the treasury entity still needs its own incorporation documents, directors, tax data, expected activity and authorised representatives. Expected transaction volumes are high because it will run payments for multiple subsidiaries; that profile is documented.
Accounts are opened for Guna Treasury in EUR and SEK. The subsidiaries keep their local operating accounts. A physical cash pool is designed with the treasury entity as concentration-account owner. Legal and tax specialists review which subsidiaries can participate. Intercompany sweep agreements are executed. Credit approves target account overdrafts and intraday limits where needed.
The payment factory uses a central SAP instance. Treasury employees prepare files containing payments for German, French and Spanish subsidiaries. The bank's channel authenticates the corporate user and checks entity-level account entitlements. In the payment data, the debtor reflects the relevant account owner. The central treasury or service centre can appear as initiating party where appropriate. Mapping rules preserve underlying party information into downstream payment processing.
User authority is configured carefully. A treasury preparer can create payments for all participating subsidiaries, but approval requires designated approvers according to each entity's mandate. High-value treasury transfers require an additional approver. The bank does not assume parent employment equals subsidiary authority.
Reporting is designed for both entity and group needs. Each subsidiary receives statements for its own accounts. Group treasury receives consolidated reporting under contractual and mandate permissions. The reporting service preserves legal account ownership while providing a group view.
When the French acquisition occurs, the new target is not simply inserted into the pool. The acquisition SPV is onboarded for financing. Credit records the acquisition loan against the SPV with parent support according to documents. The target companies undergo their own onboarding and account review. Existing bank accounts remain under current authority until migration.
After closing, Guna wants the target's French subsidiary to join the payment factory. Implementation assesses its ERP, accounts and payment types. New mandates grant treasury users authority. The cash-pooling team evaluates whether the entity can join the structure. Only after legal, tax, credit and operational readiness are complete is the entity activated.
Later, Guna merges the acquisition SPV into another holding company. Customer master data records the legal event. Credit and legal teams determine whether the acquisition facility must be novated or repaid. Accounts that are no longer needed are closed under proper authority. Historical records retain the SPV identity so past payments and credit decisions remain traceable.
This case shows why legal structure is not a static onboarding topic. It runs through payments, liquidity, credit, digital access, reporting and corporate events. The same hierarchy must be understood consistently across the bank.
20. Common legal-entity failure modes
Using the brand name as the customer
Staff say “Guna” without specifying which entity. Requirements, incidents and approvals become ambiguous. Every operational action should identify the relevant legal entity and account where necessary.
Assuming a parent can sign for subsidiaries
Ownership does not automatically create account authority. Mandates and legal powers must be evidenced.
Treating a branch as a separate company
This can distort ownership, KYC and credit aggregation. The data model must represent branch relationships correctly.
Applying group pricing to a joint venture automatically
A minority partner may exist and contractual terms may differ. Relationship connection is not itself a pricing mandate.
Cash pooling without entity-level documentation
Automated sweeps can create intercompany exposures. Legal, tax and credit analysis belongs in solution design.
Replacing debtor identity with shared-service-centre identity
This can reduce payment transparency and cause downstream screening or reconciliation issues. Initiating party and debtor should be mapped according to their actual roles.
Stale group hierarchies
Sold subsidiaries remain visible to former parent users or included in exposure reports. Ownership events must trigger entitlements and reporting review.
Duplicate customers after name changes
If matching relies on name rather than stable identifiers, a renamed entity can be onboarded again. Registration numbers and governed customer IDs help prevent this.
Assuming consolidated accounts prove support
Consolidated financial strength does not automatically make every group company legally liable for another's debt. Credit needs explicit obligor analysis.
21. What business analysts, engineers, testers and operations should do with this knowledge
Business analysts should start every corporate requirement by asking which legal entity is acting. “Customer sends payment” is incomplete. Which entity owns the debit account? Which user initiates? Is the user employed by the same entity or a shared-service centre? Is there an on-behalf-of model? Requirements should separate legal party, initiating party, account owner and user authority.
For onboarding journeys, BAs should model entity types because document requirements and relationships differ. A branch cannot be treated identically to a subsidiary. An SPV may need transaction documents. A joint venture may have shared control. The workflow should support variation without embedding uncontrolled manual exceptions.
Engineers should use stable internal entity IDs across APIs and events. Names are attributes, not keys. Group IDs should be separate from legal-entity IDs. Account services should expose the owner entity. Entitlement services should bind users, roles and accounts explicitly. Audit events should record who acted, for which entity and on which account.
Payment-system developers should preserve party semantics. If an ISO 20022 message distinguishes initiating party, debtor and ultimate debtor, internal mappings should not collapse them into one generic “payer” field unless the product genuinely does not need the distinction. Lossy mapping can create problems later in screening and investigations.
Credit-system designers should represent borrower, guarantor, security provider and parent group separately. Group exposure aggregation should be derived from relationships, not achieved by discarding obligor detail. Changes in hierarchy should be effective-dated.
Testers need scenarios that cross entity boundaries. A user authorised for Parent A should be denied access to Subsidiary B unless separately entitled. A shared-service user should be able to prepare for three subsidiaries but not a fourth. A sold subsidiary should disappear from group reporting after the effective date while historical records remain accessible according to policy.
Cash-pooling tests should verify participant ownership, sweep direction, target balances, overdraft behaviour and removal of participants. Corporate-event testing should include name change, merger, sale and liquidation. These are not rare edge cases in long-lived corporate relationships.
Operations teams should have procedures that show legal names and entity identifiers clearly in repair and service tools. A payment incident affecting “Guna” should be narrowed to the exact account and entity before action. Manual repairs should not alter party identity merely to make a transaction pass validation.
Service teams should respect information permissions. A parent-company contact may be commercially important but not entitled to receive a subsidiary's detailed statement. The bank should use contractual and mandate permissions, not relationship seniority, to determine access.
Data teams should run quality checks for impossible or suspicious hierarchy states: entity with two active ultimate parents where the model does not allow it, branch without head office, active account whose owner is closed, subsidiary with missing ownership percentage, or group reporting entitlement after sale. Data-quality monitoring can prevent downstream control failures.
22. Key takeaways
Legal entity structure is one of the most important foundations of corporate banking because it determines who the customer actually is. The bank can and should view a multinational as one commercial relationship, but it must never lose the legal identities inside that relationship. Parents, subsidiaries, branches, joint ventures, SPVs and treasury companies have different meanings and can create different authority, credit, onboarding and transaction outcomes.
The strongest banking models maintain both group and entity views. The group view supports coverage, profitability, exposure aggregation and strategic service. The entity view supports contracts, accounts, mandates, payments, KYC, credit and reporting. Systems connect these views through governed relationships and stable identifiers.
Legal structure is dynamic. Acquisitions, sales, mergers, treasury relocations and reorganisations change who owns what and who may act. Those events should trigger coordinated review across onboarding, mandates, entitlements, cash management, credit and service. A customer hierarchy that is correct only on onboarding day is not sufficient.
For payments professionals, the practical lesson is especially important: the person who presses “submit,” the entity whose account is debited and the group that economically benefits can be different parties. Message and system designs must preserve that meaning. For credit professionals, consolidated strength must be separated from legal recourse. For service teams, relationship importance must be separated from access authority.
When a bank gets legal entity structure right, complex multinational banking becomes manageable. When it gets it wrong, almost every downstream process becomes harder: KYC duplicates, mandates conflict, payments carry weak party data, cash pools create uncertainty, credit exposure is misaggregated and corporate events become risky. Legal-entity clarity is therefore not a legal-team detail. It is core banking architecture.