A company's name does not tell you which company it is

Two stores have the same brand on their doors. One belongs to a franchisee; another belongs to a different legal entity. A buyer places a purchase order under the brand name and assumes the same supplier contract applies to both. The accounting system has found matching words, not the contracting party.

Brand, storefront, legal entity, operating establishment and beneficial relationship are different objects. The distinction matters when a contract is signed, a payment is settled, or a regulator asks who actually performed an obligation.

The Global Legal Entity Identifier Foundation^{[1]Global Legal Entity Identifier Foundation} describes the LEI as a unique identifier connecting legal entities to reference information. It is an institutional registry for a particular domain of organizational identity, not a universal brand number or proof of every business claim.

A legal name can change without necessarily creating a new entity. A brand may be licensed to many entities. One entity may operate several brands. A merger may change ownership and obligations without making every historical commercial record interchangeable.

Suppose a retailer's historical invoices reference Vendor A, while a new quote is issued under a similar trading name. Automatically mapping both to one vendor could cause payment to the wrong recipient or obscure which terms govern the new purchase.

The system should retain legal entity identifiers when available, source registry, trading names, jurisdiction, relationships, current and historical status, and the actual account or contract to which a purchase belongs.

A public registry record can help verify a legal entity. It does not alone establish that a particular employee, website or automated agent has authority to sign a contract on its behalf.

Entity resolution can use names, addresses, ownership clues and registry numbers to propose matches. An approximate match is still a proposal. High-stakes actions require exact authority and sometimes independent review.

The reverse also matters. Overly strict matching can scatter one enterprise into multiple disconnected records after a harmless spelling change. Maintain provenance and time so a corrected name can coexist with historically accurate invoices.

Aurekai wants independent businesses to share software infrastructure without collapsing their legal boundaries. The correct architecture separates the reusable product system from the particular business account, its branding, contracts, customers and effect permissions.

The real business is not its text label. It is a continuing set of rights, relationships, assets and obligations.