Reconcile business identity details before verification review
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A business portfolio contains an abbreviated company name, the website shows a trading brand, and a supporting record still carries the previous address. Staff start changing fields to make them match, but nobody has established which version is authoritative. That turns a verification mismatch into a record-management problem.
Before proceeding with a requested business verification review, classify each difference, identify the owner of the underlying record, and document the correction or explanation. Presentation differences may need only a recorded comparison; conflicting entities, unexplained addresses, and outdated records need resolution by the responsible owner. Do not make every surface match whichever version is easiest to edit.
The worksheet below provides a practical way to make that decision. It is an internal operating aid, not a list of documents Meta accepts or a guarantee of verification. Check the current official requirements presented in your verification flow before choosing evidence or submitting information.
1. Establish which business and which review you are preparing
Start with a short scope statement: which business entity is being represented, which workspace or business portfolio is involved, and what verification request is actually being made. Otherwise, staff can accidentally combine records belonging to a parent company, a subsidiary, and a customer-facing brand.
Keep business identity reconciliation separate from other onboarding work. Reviewing a business identity is not the same task as reviewing a messaging template or preparing a campaign. Completing one task does not establish the status of another.
Assign an onboarding coordinator to capture the current request and its requirements. That person should record:
- The business entity intended for the submission.
- The workspace or portfolio under review, using an internal reference rather than sharing account access.
- The fields and evidence requested by the current verification flow.
- Any specific mismatch or clarification already reported.
- When the requirements were last checked and who checked them.
Do not turn a colleague's previous submission into a universal document checklist. The operational question is whether your current information satisfies the current request, not whether it resembles an old onboarding folder.
2. Separate presentation differences from identity conflicts
A difference is a candidate for harmless presentation variation when it preserves the same underlying meaning. A conflict exists when the versions could refer to different entities, locations, or relationships—or when the team cannot explain the difference with reliable records.
Presentation differences: compare before editing
Capitalization, spacing, punctuation, and some address abbreviations can leave the underlying identity unchanged. For example, in a hypothetical comparison, “Harbor Lantern Services Limited” and “HARBOR LANTERN SERVICES LIMITED” differ only in letter case.
Record both the original value and the comparison value. Normalizing text for internal comparison should not silently rewrite the original record or imply that an external reviewer will accept the variation. If the current flow asks for a particular form of a name or address, follow that instruction.
Context differences: explain the relationship
A brand name and a legal entity name may both be accurate while serving different purposes. Likewise, a customer-facing location and a registered address may differ. These are not automatically mistakes, but they are not automatically interchangeable either.
The reviewer must establish the relationship and determine which value belongs in the requested field. A familiar logo or matching email domain is not enough to settle an unexplained entity relationship.
Identity conflicts: pause the affected submission
Different company names without an established relationship, different address units, or records from before and after a move require investigation. Treat an unexplained discrepancy as unresolved rather than dismissing it as cosmetic.
The useful test is: Can the responsible record owner explain why these versions differ and identify which one is current for this purpose? If not, the onboarding team does not yet have a reliable basis for choosing a value.
3. Assign authority by detail, not by convenience
There is no single source that should automatically override every other source. Authority depends on the detail being reconciled.
- Entity name: Ask the person responsible for maintaining the business's formal entity records to identify the current authoritative record.
- Address: Establish what type of address the field requests, then ask the owner of that address record to confirm the current value.
- Website: Ask the website owner to confirm the intended domain and the business information published there. Ask the entity-record owner to confirm any entity relationship described on the site.
- Workspace entry: The workspace administrator can correct the submitted field, but should not independently decide an unresolved entity fact.
- Supporting material: The record owner should establish whether it is current; the onboarding coordinator should check whether it meets the current request.
Internal authority and evidence acceptability are different questions. A record may be the best internal reference for a fact without being an accepted submission item. Conversely, a requested document may be outdated and need replacement before use.
Give each discrepancy one accountable reviewer. Other people can contribute, but a shared instruction to “check the details” makes it difficult to tell who must resolve the issue.
4. Filled hypothetical identity-reconciliation worksheet
Fictional worked example: Every business name, address, domain, role assignment, and status below is hypothetical. These entries illustrate a recommended workflow, not accepted evidence types or an actual verification outcome.
Submission scope: Harbor Lantern Services Limited is the intended business entity. Harbor Lantern is its customer-facing brand. The onboarding coordinator has captured the current verification request separately; this worksheet tracks consistency, not evidence eligibility.
Entry A — Business entity name
- Relevant detail: Full entity name for the requested business-name field.
- Authoritative source: Current entity record maintained by the corporate administration owner.
- Conflicting versions: Entity record: “Harbor Lantern Services Limited.” Workspace: “Harbor Lantern Service Ltd.” Website heading: “Harbor Lantern.”
- Responsible reviewer: Corporate administration owner; workspace administrator implements the confirmed correction.
- Assessment: The missing final “s” in “Services” is a substantive transcription error. The brand heading is a separate context issue.
- Resolution status: Workspace name corrected and independently rechecked. Brand relationship tracked in Entry C.
Entry B — Business address
- Relevant detail: Address requested in the current verification flow.
- Authoritative source: Current address record maintained by the business-records owner, after confirming the requested address type.
- Conflicting versions: Current record: “Unit 6, 18 Beacon Road, Marlow Bay, MB4 2QT.” Workspace: “Unit 6, 18 Beacon Rd, Marlow Bay, MB4 2QT.” Older supporting record: “Unit 2, 18 Beacon Road, Marlow Bay, MB4 2QT.”
- Responsible reviewer: Business-records owner.
- Assessment: “Road” versus “Rd” is a presentation difference in this comparison. Unit 2 versus Unit 6 is an unresolved address conflict.
- Resolution status: Open. Owner confirms a move occurred but has not yet supplied a current replacement record meeting the request. Older record excluded from the proposed submission set.
Entry C — Website business identification
- Relevant detail: Business represented on the website.
- Authoritative source: Entity relationship confirmed by corporate administration; published content maintained by the website owner.
- Conflicting versions: Site heading uses “Harbor Lantern.” Contact page identifies “Harbor Lantern Trading,” a retired wording that the owner cannot substantiate as current.
- Responsible reviewer: Corporate administration owner confirms wording; website owner publishes it.
- Assessment: Brand use is distinguishable from the incorrect entity wording on the contact page.
- Resolution status: Contact page corrected to identify the confirmed entity behind the brand. Independent reviewer checked the published page.
Entry D — Website URL
- Relevant detail: Intended public website.
- Authoritative source: Domain inventory maintained by the website owner.
- Conflicting versions: Workspace stores “harborlantern.example”; internal onboarding notes store “https://harborlantern.example/”.
- Responsible reviewer: Website owner.
- Assessment: Both identify the same intended host in this hypothetical example. The owner checks the actual destination rather than inferring equivalence from text alone.
- Resolution status: Resolved for internal consistency. Coordinator will use the format requested by the current flow.
Entry E — Supporting-record currency
- Relevant detail: Whether proposed supporting material reflects the current business details.
- Authoritative source: Record inventory maintained by the business-records owner, assessed against the current verification request.
- Conflicting versions: Shared onboarding folder contains the older Unit 2 record; the workspace already shows Unit 6.
- Responsible reviewer: Business-records owner, with the onboarding coordinator checking submission suitability.
- Assessment: The folder's presence does not establish that the record is current or suitable.
- Resolution status: Open and linked to Entry B. Submission remains paused pending replacement and review.
Worksheet decision: Do not submit this proposed set yet. The name and website corrections are complete, but the address evidence remains unresolved. Completed rows do not cancel an open identity conflict.
5. Correct the source, then update dependent records
Use a deliberate correction order. First establish the fact with its owner. Next correct any owner-controlled source that is wrong or outdated. Then update dependent onboarding fields and public content where appropriate. Finally, compare the resulting values again.
This order prevents a common failure: changing the workspace to match stale evidence because that is faster than obtaining a current record. It also prevents the reverse problem—editing a website to support an entity claim nobody has confirmed.
Preserve a compact change trail containing the old value, confirmed value, reason, owner authorization, and recheck result. Keep sensitive evidence in an appropriately restricted location; the worksheet can point to it without reproducing the entire document.
There is a trade-off between speed and certainty. Cosmetic changes may be quick, while replacing an outdated source can take longer. Work on independent rows in parallel, but do not convert an unresolved conflict into “resolved” simply to keep onboarding moving.
6. Use a clear proceed-or-pause decision
Before proceeding, have someone other than the person who made the edits compare the proposed submission with the worksheet. This is a recommended internal check, not a stated Meta requirement.
A practical readiness decision asks whether:
- The intended entity is unambiguous.
- Each requested detail has a confirmed value and a responsible source owner.
- Presentation differences have been documented without obscuring meaningful differences.
- Brand, entity, and address relationships are explained where relevant.
- No unresolved conflict remains in the proposed submission.
- The supporting material has been checked against the current official request.
Record the decision as “ready for submission,” “paused for correction,” or “needs clarification.” Avoid a vague “done” status: it does not distinguish internal preparation from an external review outcome.
If the current flow is unclear about which information is required, seek clarification through the available official support route rather than guessing or changing the business identity to fit a perceived requirement.
7. Recover from a mismatch without starting over blindly
If a review reports a mismatch, retain the submitted snapshot and reopen the relevant worksheet entries. Record the feedback separately from the team's interpretation of it. A message about inconsistent details does not, by itself, establish which underlying record is wrong.
Check for changes since submission: a website edit, an address update, a different attachment, or an unauthorized workspace correction may explain why the current view no longer matches the submitted set. Avoid repeatedly resubmitting the same unresolved combination.
Where possible, change one confirmed issue at a time and record its effect. If an owner cannot establish the relationship between two entities, escalate internally to the person responsible for those records. Do not create a new explanation solely to fill the gap.
8. Make the next action measurable
At the next onboarding handoff, create one reconciliation entry for every relevant detail requested in the current flow. Assign an owner and status before making corrections.
Track three measures: unresolved identity conflicts, corrections awaiting owner confirmation, and completed corrections awaiting independent recheck. These show what is preventing readiness more clearly than a general onboarding completion percentage.
In the hypothetical worksheet, the immediate action belongs to the business-records owner: resolve the current-address record and return it for a suitability check. The coordinator can then recheck Entries B and E and record a new proceed-or-pause decision. That is a concrete handoff—not another request for everyone to make the details match.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications