Link a verified UK trading name to its registered company without merging histories

Add a trading-name link only after an explicit statement and the company identifier establish the same legal entity. Keep the existing records and their histories intact while you preview the affected opportunities; linking an alias does not require merging every record that happens to use the name.

Define the conflict that needs an alias decision

Start with the two labels creating the problem. One opportunity may be filed under a product-facing trading name while an incoming supplier form names a registered company. Preserve the source statements and both existing record identifiers before making changes. The immediate question is whether the trading label can be linked to that company, not which account should survive a merge. Keeping that question narrow prevents a simple identity clarification from becoming an uncontrolled transfer of commercial histories.

Record what is actually at risk if the labels remain disconnected. Perhaps two team members are preparing the same response, or an opportunity cannot be matched to the entity named on the requested paperwork. That consequence gives the correction a scope. Do not use a routine duplicate score as the final answer, especially where different opportunities or contact restrictions are attached. A high similarity between names may identify a case for review, but it cannot establish who the trading name represents.

GOV.UK explains that a company can trade under a business name different from its registered name. That makes a verified alias relationship possible; it does not mean every matching brand is an alias of the company you found. There may be separate entities, an old operator or an unrelated business with a similar label. Capture a current explicit statement connecting the trading name to the entity and compare the identifier, rather than treating search ranking as identity evidence.

Gather an explicit statement and corroborating entity details

Look for wording that actually names the operator, such as a current business disclosure identifying the company trading under the relevant name. Save the wording, source location and check date. Read it in context: a parent company mentioned in a privacy notice or a distributor named on a contact page may have a different relationship. If the statement does not say what you need it to say, record the limitation instead of rewriting it into a stronger relationship for convenience.

Compare the company identifier and other relevant context against the intended account. GOV.UK provides a route to public company information, including previous names and registered addresses. Those details support an identity check, but the alias statement still needs to connect the actual trading label. Do not infer current ownership of a domain merely because a historic record once named the same company. If the source dates differ materially, retain that mismatch as an unresolved point for the reviewer.

Use a proportionate clarification if the public evidence remains incomplete and you have an appropriate existing communication route. Ask which registered entity operates the named business for the specific enquiry. Do not reveal another account’s correspondence to prove why you are asking. A generic confirmation from an unverified sender should not override contradictory identifiers. The decision records the source and confidence limits of the response, rather than converting any reply into official registration evidence.

Populate an alias decision with a contrasting hold case

The following example is entirely fictional. Account A contains an opportunity labelled Project Cedar under Trading Label T. Account B carries Registered Company R and its separately verified illustrative identifier. A current fictional disclosure explicitly states that Company R trades as Label T, and the identifier agrees with the account evidence. The reviewer records the source statement, entity identifier, alias and affected record keys. The proposed action is a documented alias link, not a merge of Account A into Account B.

The completed fictional decision says that the link helps staff recognise the company behind the label while Project Cedar and its original correspondence remain on Account A. Existing restrictions on either record are reviewed before any operational use and are not reset. The commercial owner checks whether any other opportunities depend on the label. The alias relationship is released only within the scope supported by the statement; it does not claim group-wide ownership or authorise a change to contracting documents.

In the contrasting fictional case, Label T appears on a website but the disclosure names a different entity from Company R. A similar address and logo do not resolve the mismatch. The alias link remains on hold and both account histories stay separate. This is not a failed deduplication effort to be forced through with a lower threshold. It is an unresolved identity question. Neither fictional case is a real customer record, and no observed commercial improvement is claimed from adding the link.

Preview opportunities and restrictions before adding the link

List the opportunities, conversations and account-level rules attached to each affected record. Identify which would merely display an alias and which might be reassigned by the available software operation. Some tools use labels differently, so do not assume a button called link preserves everything. Inspect the documented behaviour or a controlled copy. If the only supported operation combines records and histories, it does not meet this narrow task without a separate reviewed migration decision.

Pay particular attention to open proposals, invoices or documents that name an entity. A display alias must not silently change the party named in a commercial document. Refer such documents to the responsible commercial or legal reviewer where necessary. This guide does not decide who is a contracting party or whether an existing agreement can be amended. It establishes a bounded identity link that helps the team recognise an evidenced trading label while leaving substantive document decisions with the authorised owners.

Check how contact restrictions will be found after the link. Keeping histories separate must not hide a relevant objection from the person considering a new activity. Record the applicable restrictions through your existing approved process without inventing a universal rule for all records. A trading-name clarification does not establish a new contact permission or revive a closed conversation. If the restriction’s scope is unclear, hold the affected activity for review instead of using the alias as a workaround.

Apply a reversible link and verify the actual outcome

Write the proposed change before applying it: the exact alias label, the registered entity reference and the source evidence attached. Keep original record identifiers unchanged. Use the smallest authorised change that represents the relationship in your actual system. If a separate evidence note is the only available safe option, document that limitation rather than claiming a native alias feature. This article does not assert that LDM provides any particular linking interface or automatic identity resolution.

After the change, reopen or export the relevant records. Check that the alias refers to the intended entity, Project Cedar remains attached to its original record in the fictional model and unrelated opportunities have not moved. Compare the histories and restrictions against the saved preview. Record the observed result in the decision note. A screen showing the new trading label is not enough if the operation also combined attachments, reassigned owners or changed a party field without review.

The undo instruction names the added relationship or note, the original record keys and the fields that must remain untouched. Test its behaviour in a controlled copy where appropriate. Removing an alias link should not require deleting the company record or its conversations. If your system cannot reverse the operation at the required scope, stop before applying it and obtain an approved method. Reversibility is a property to verify in the actual workflow, not a benefit to promise from a generic CRM description.

Close the identity question without expanding into a merge project

The completed record contains the explicit source statement, checked entity identifier, alias, affected records, reviewer and observed post-change check. An unresolved record names the precise conflict and the evidence needed to reopen it. Keep source dates visible so that a later change in operator can trigger a new review without rewriting what was known at the time. A past verified link remains historical evidence, not permanent proof of every future use of the trading name.

This task differs from general company deduplication because the desired output is a verified relationship with preserved histories. A routine instruction to merge account duplicates would not answer whether the alias is established, which opportunities were previewed or how the link can be undone without moving them. It also differs from a company-name change: the trading label and registered name may be in concurrent use. That distinction determines what the evidence needs to show and why a date-only rename is insufficient.

Sources, checked 18 October 2026: GOV.UK, Choose a company name, https://www.gov.uk/limited-company-formation/choose-company-name ; Get information about a company, https://www.gov.uk/get-information-about-a-company . Source claims concern trading names and available public company information. The alias workflow and all labelled cases are editorial recommendations or explicitly fictional, with no legal-party determination, software guarantee or actual company relationship asserted.

You can test this in practice with open email infrastructure statistics for domains on check.live-direct-marketing.online.

FAQ