COMPANY RECORD DECISION WORKSHEET — ANIVO
Updated: 6 October 2026
Guide: https://anivoapp.com/guides/companies-with-same-domain/

Manual review aid. No upload, scoring engine or Anivo import format.
Examples below are fictional. Registry labels are not valid registry numbers.
Use actual evidence addresses and check dates when reviewing your own records.

BLANK REVIEW

Review reference:
Reviewer and decision date:
Record A ID and source system:
Record B ID and source system:
Record unit (legal entity / operating location / brand / buying relationship):
Shared field and raw values:
Normalized values and transformations, if any:
Identity evidence (issuing registry, jurisdiction, identifier, scope, status):
Source addresses and date checked:
Conflicting facts or historical differences:
Verified relationship, if any, and its source:
Other records connected to this pair:
Decision (merge / link / keep separate / review):
Reason and unresolved checks:
Person responsible for the next check:
Source IDs and fields to preserve:
Proposed field changes and selected values:
Where contacts, notes, tasks and conversation history will belong:
Export/restore scope checked in the actual CRM:
Outreach decision (separate from the data decision):

THREE-RECORD COUNTEREXAMPLE

Unit: legal entity.
A — Arda Packaging Global; DEMO-REG-DE-A; arda.example; SWITCHBOARD-A.
B — Arda Packaging Türkiye; DEMO-REG-TR-B; arda.example; SERVICE-LINE-X.
C — Mavi Distribution; DEMO-REG-TR-C; mavi.example; SERVICE-LINE-X.

Supplied fictional facts:
- A and B are distinct legal entities with a verified group relationship.
- B and C are independent entities using one outsourced telephone service.

Simplistic candidate rule: same domain OR same phone.
A–B is flagged by domain. B–C is flagged by phone.
All three become connected; a single-identity interpretation also implies A–C.
That interpretation is unsupported. Shared fields are not identity assertions.

A–B review:
Shared field: arda.example.
Identity conflict: distinct fictional registry identities in different jurisdictions.
Relationship evidence: the verified group relationship is supplied in this example.
Decision: LINK, retaining A and B as distinct legal-entity records.
Preserve: both IDs; each entity's contacts, notes and activity history.
Next check: which entity coordinates the particular buying discussion?

B–C review:
Shared field: SERVICE-LINE-X.
Identity evidence: distinct fictional registry identities; entities are independent.
Decision: KEEP SEPARATE. Document the shared service; do not invent ownership.
Preserve: both IDs and each entity's conversations.

A–C review:
Evidence: only a connection through B under a candidate-matching rule.
Decision: KEEP SEPARATE under the supplied facts.
No identity claim follows from this path.

WHEN MERGING IS APPROPRIATE — SEPARATE FICTIONAL EXAMPLE

D and E are two imports of the same current, verified legal entity.
Both records are scoped to that legal entity, not to distinct operating sites.
The same issuing registry, jurisdiction and identity are confirmed.
An abbreviated name explains the name difference. Other conflicts are resolved.
Decision: MERGE after recording retained IDs, selected values and activity mapping.
Do not silently move a site's separate contacts into the wrong relationship.

WHEN REVIEW IS THE RIGHT DECISION — SEPARATE FICTIONAL EXAMPLE

F and G have similar names and a shared phone in an old directory.
Entity identities and the role of the phone have not been verified.
Decision: REVIEW. Keep the originals and record the missing current identity check.
Pause an outreach or merge action that depends on the unresolved identity.

REMINDERS

- Define the record unit first.
- Compare identifiers within their issuing scheme and scope.
- Retain raw values and sources; repeated copies may share one origin.
- Inspect the whole connected group, including conflicting pairs.
- Holding repeated outreach does not require merging company records.
- This proposal is not a scientifically validated score or a sales-results claim.

Research and official source links are listed in the guide.