Systems and records
Revenue customer entity change data: modeling a mid-contract switch
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Revenue training data should keep the account and the legal entity as separate records linked by effective dates, record each entity change as a typed event (name change, merger, assignment or new subsidiary) with the signed evidence, and never overwrite prior invoices or bookings. The change counts as verified only when the contract, finalized billing and CRM agree from the effective date onward.
Value drivers
Revenue customer entity
Key takeaways
- Account and legal entity are separate records; an entity change is a dated event with signed evidence, not a CRM edit.
- Name changes, mergers, assignments and new subsidiaries change different identifiers and need different contract evidence.
- CRM merges and in-place edits erase which entity held the contract on a given date, so capture history before cleanup.
- Finalized invoices that keep the old name are correct history, not errors to fix.
- An entity change is verified only when contract, paid billing and the next contractual act by the new entity agree.
How should revenue training data represent a customer changing legal entity mid-contract?
Represent the account and the legal entity as separate records joined by effective-dated links, and record the change as an event with a type, an effective date and the signed evidence behind it. Never overwrite history: invoices, bookings and activity before the effective date stay attached to the entity that was the customer then.
The task a model should learn is not reading the current account name. It is reconstructing who the contracting party was on a given date, which document made the change, whether the contract allowed it, and whether billing and delivery actually followed. A record that only shows the latest name teaches a model that the new entity signed a contract it never signed.
This matters for any revenue model. Renewal forecasts, churn labels, expansion attribution and collections predictions all depend on whether the counterparty is the same legal person, a successor, or a new customer that happens to share a logo.
Name change, merger or assignment: which event actually happened?
Start by classifying the event, because each type changes different identifiers and needs different contract evidence. The general patterns below are a starting point; counsel and finance confirm the specific facts.
Tax identifiers are a useful cross-check. The IRS says a business generally needs a new EIN when its ownership or structure changes, but not to change its name, address or responsible party. Its internal guidance adds that when one corporation merges into another, the target's EIN is discontinued and the surviving corporation keeps using its existing number.
| Event type | What usually changes | Contract evidence to collect | How the record should show it |
|---|---|---|---|
| Legal name change only | Name on the charter; tax ID usually unchanged | Name change notice or certificate, updated order forms | Same entity record with a dated name history |
| Customer is the surviving entity in a merger | Often nothing for this customer; it absorbs another company | Customer's notice, if the contract requires one | Same entity; note the absorbed entity as a separate record |
| Customer merged into another company | Customer ceases to exist; successor holds its rights and obligations | Merger notice, any consent required by the contract, successor details | Old entity retired with a successor link from the effective date |
| Contract assigned in an asset sale | Counterparty changes by assignment, not by operation of law | Signed assignment or novation, consent if the contract requires it | New entity record; contract link moves on the assignment date |
| Services moved to a new subsidiary | A new legal person, usually with its own tax ID | New order form or assignment signed by the subsidiary | New entity record and a new or assigned contract |
Why the CRM's current account name gives the wrong answer
CRMs are built to show the current state, so the common ways teams record an entity change destroy the history a model needs. Someone edits the account name in place, or merges the old account into the successor's account, and the export shows one customer that always had the new name.
Merges are especially lossy. In HubSpot, merging records by default creates a record with a new record ID (a public beta instead preserves the primary record's ID), keeps the original IDs in a merged IDs property, and keeps the primary record's property values unless the user chooses otherwise. In Salesforce Lightning Experience, up to three accounts can be merged into one principal record. Both behaviors are reasonable for sales teams and both erase which entity held the relationship on a given date unless the history is captured first.
Billing systems often disagree with the CRM, and that disagreement is correct. Stripe's API specification says an invoice's customer name, address and tax IDs track the customer object only until the invoice is finalized, after which they are no longer updated. Finalized invoices keep the old entity's name while the CRM shows the new one, and the training record should preserve both rather than treat one as an error.
The legal entity and contract evidence update packet
The packet is one record per entity change event, linking every system that had to agree. A revenue operations team can copy the fields below into a spreadsheet or a data model as is.
| Field | What it holds | Source system | Check before accepting |
|---|---|---|---|
| event_id and event_type | Stable ID and one of the event types above | Revenue operations | Type is supported by the signed evidence, not by the CRM edit |
| old_entity and new_entity | Legal names, registered jurisdictions, tax ID or LEI where available | Contract, billing, external registries | Identifiers on both sides recorded as of the effective date |
| effective_date | Date the change took legal effect | Merger notice, assignment or name change certificate | Distinct from the date someone edited the CRM |
| contract_ids and clauses | Agreements affected, with assignment and change of control clauses cited | Contract repository | Clause text quoted, not summarized |
| consent_or_notice | Whether consent or notice was required, given and by whom | Contract repository, email or e-signature records | Required but missing consent is flagged, not assumed |
| crm_history | Account IDs before and after, merge events, field changes with dates | CRM field history and merge log | Old IDs preserved; edit date recorded |
| billing_history | Last invoice to old entity, first invoice to new entity, payment status | Billing system | Invoice names checked as finalized, not as currently displayed |
| forecast_and_attribution | How renewal, churn and expansion were attributed across the change | Forecasting tool, revenue reports | No churn plus new logo double count; method stated |
| approvals | Who in finance, legal and sales approved the record update | Approval workflow | Names and dates present for each required approver |
| outcome | Verified, partially verified or unverified, with the reason | Revenue operations | Verified only when contract, billing and CRM agree from the effective date |
Where the signed contract and later events overrule the CRM
The contract itself is the first place a CRM answer fails. Many agreements limit assignment or give the other party rights on a change of control, and the contract review dataset CUAD treats both as standard review questions: anti-assignment asks whether consent or notice is required to assign the contract, and change of control asks whether a merger, stock sale or transfer of substantially all assets triggers termination rights, consent or notice.
If consent was required and never given, the CRM may show the successor as the customer while the contract arguably still runs with the original entity. The packet records the clause, the requirement and the missing step, and leaves the legal conclusion to counsel.
External registries help where they exist. In the LEI system, GLEIF's common data format records a successor entity on a registration that is no longer used, and since format 3.1 a merged entity's registration is generally set to retired rather than to the deprecated merged status. A retired LEI with a successor link is strong evidence of which entity continued, and of when.
Later outcomes can also contradict the CRM. A renewal signed by the original entity months after the CRM was changed, or invoices to the new entity going unpaid because its accounts payable team never set up the vendor, show the change was recorded before it was real.
Worked case (illustrative): a subscription customer merged into its parent in month 14
The case below is invented for illustration. A customer on a 36-month subscription is merged into its parent company in month 14. The CRM administrator merges the customer's account into the parent's existing account the same week.
| Stage | What the records show | Evidence linked | Decision recorded |
|---|---|---|---|
| Starting state | CRM shows one account under the parent's name with 36 months of history | CRM merge log; field history exported before cleanup | Old account ID restored as a separate entity record |
| Event classification | Merger notice names the parent as surviving entity | Merger notice; parent's registration details | Event type: customer merged into another company |
| Contract check | Agreement requires written notice of a change of control within a set period | Change of control clause quoted; notice letter dated after the merger | Notice given late; flagged for counsel, contract treated as continuing |
| Billing check | Months 1 to 14 invoiced to the old entity; month 15 onward to the parent | Finalized invoices; payment records | Old invoices keep the old name; no restatement |
| Forecast and attribution | Revenue report showed churn of the old logo and a new parent deal | Forecast snapshot; renewal pipeline | Corrected to one continuing contract; double count removed |
| Verified outcome | Parent paid months 15 to 18 and renewed in month 36 | Payments; renewal order form signed by the parent | Outcome verified from the effective date |
Counterexample: a rebrand that changed no entity at all
Not every new name is a new entity. If a customer adopts a new trading name while its registered legal name, tax ID and contracts stay the same, the packet records event type none, attaches the evidence that nothing changed legally, and lets the CRM display name change without touching the entity record.
This counterexample belongs in any training set built from these packets. Without it, a model learns that every name change is a successor event, and starts proposing assignments, new contracts and churn labels for customers who simply rebranded.
The mirror case also occurs: the display name stays the same while the legal entity changes, for example when a group moves contracts to a newly formed subsidiary with the same brand. Only the contract, billing and tax ID evidence reveals it, which is why the packet never relies on names alone.
Partial changes need care as well. A customer may move only one product line or region to a new entity while the original entity keeps the rest. The packet then splits the contract scope by effective date, lists which order forms, subscriptions or sites moved, and leaves the remainder linked to the original entity, so that neither side appears to have churned.
Three records that prove the entity change took hold
Three records together prove the outcome: the signed document that made the change effective, the first invoice to the new entity that was finalized and paid, and the next contractual act by the new entity, such as a renewal, an amendment or a notice. If any one is missing, the outcome is partially verified and the packet says which.
Attribution limits belong in the record too. Revenue before the effective date stays with the old entity, and expansion that the parent buys afterward is not evidence that the original customer expanded. State the attribution method so a model trained on the data does not learn a pattern produced by the bookkeeping rather than by customer behavior.
Keep the packet versioned. Entity changes are often recorded twice: once when sales hears about them and again when finance sees the paperwork. Both versions, with dates, show how long the organization took to learn the truth, which is itself a useful signal for revenue operations tooling.
Mask what the packet does not need. Signatory names, personal email addresses and notice contacts can be replaced with stable role tokens, such as old entity signatory or new entity accounts payable contact, which keeps the links intact while removing personal data before the records leave the company.
- Signed change evidence: merger notice, assignment, name change certificate or new order form.
- First finalized and paid invoice addressed to the new entity.
- Next contractual act by the new entity: renewal, amendment or formal notice.
- CRM and billing identifiers that match the contract on and after the effective date.
Entity change histories in licensed revenue records
Revenue records that preserve entity changes with signed evidence, billing history and approvals are scarce, and they teach account and contract models something current snapshots cannot. When a finance or revenue operations team wants to offer such histories to AI developers, SourceX handles the sourcing, rights review, contracting, preparation and delivery around the selected records. No invoice, booking or entity packet leaves the company until it has approved the scope and terms and signed, and a brief assessment that asks for no files tells it whether the history qualifies.
Frequently asked questions
Does a customer's name change mean a new contract is needed?
Usually not on its own. If the legal entity is the same and only its name changed, the contract normally continues and the record needs a dated name history. Counsel confirms the specific case, especially if the contract defines the parties narrowly.
Should merged CRM accounts be unmerged for training data?
Where possible, rebuild the pre-merge accounts from the merge log and field history rather than unmerging in the live CRM. The training record needs separate entity records with effective dates, which can be built in the export without disturbing the sales team's working system.
Why do old invoices still show the former company name?
In many billing systems the customer details on an invoice are fixed when it is finalized. Stripe's API, for example, stops updating an invoice's customer name and address after finalization, so historical invoices correctly keep the name of the entity billed at the time.
How do you tell a merger from an assignment in the records?
Look at the signed paperwork. A merger notice names a surviving entity that takes over by operation of law, while an assignment is a separate agreement transferring the contract, often requiring the other party's consent. The event type in the packet follows the document, not the CRM change.
Can an LEI lookup confirm an entity change?
It can help when both entities have LEIs. GLEIF records a successor entity on a registration that is no longer used, so a retired LEI pointing to a successor is good supporting evidence, though many smaller customers have no LEI at all.
Sources
- The IRS says a new EIN is generally needed when an entity's ownership or structure changes, but not to change the business name, address or responsible party. Source
- IRS internal guidance says that when a corporation merges into another, the target's EIN is discontinued and the surviving corporation continues to use its existing EIN. Source
- HubSpot merges by default create a record with a new record ID (a beta preserves the primary ID), keep original IDs in a merged IDs property, and keep the primary record's property values unless the user chooses otherwise. Source
- Salesforce Lightning Experience lets users merge up to three duplicate accounts into one principal record. Source
- Stripe's OpenAPI specification says an invoice's customer name, address and tax IDs track the customer only until the invoice is finalized. Source
- CUAD's anti-assignment and change of control categories ask whether consent or notice is required on assignment or on a merger, stock sale or asset transfer. Source
- GLEIF's LEI common data format records a successor LEI for a registration no longer in use, and from version 3.1 merged entities are generally set to retired. Source
See if your company qualifies
A short company assessment. No data uploads are needed.