Help reviewers make decisions without chasing documents.

Match the Salesforce application to its linked Persona inquiry and expected applicant; load the relevant Microsoft SharePoint policy version.

1. 1.1Open an application from the team’s Standard onboarding review queue in Salesforce (ex: KY-2048). Read Persona_Inquiry_ID__c and confirm that the linked inquiry’s applicant reference matches the application.
2. 1.2Check the application’s product, legal entity, and review owner. Select the corresponding effective onboarding checklist in Microsoft SharePoint and retain its version and effective date.
3. 1.3Compare the applicant references across the application, inquiry, and linked LSEG World-Check One case. Route a mismatched reference to the assigned onboarding specialist before copying any screening result.
4. 1.4Create a checklist keyed to the application ID with evidence links and review status. Store document references in Salesforce rather than copies of identity documents.

Read Persona verification outcomes and required evidence. Request missing documents through the secure flow rather than email attachments.

1. 2.1Read each Persona verification result and the inquiry status separately. An inquiry marked completed means the collection flow finished; it does not replace an approved review decision.
2. 2.2Compare the collected documents with the selected checklist, including document type, applicant name, address, and validity requirements. Mark each missing or expired item explicitly (ex: proof of address missing).
3. 2.3For missing evidence, prepare the appropriate configured follow-up inquiry and link it to the existing case. Show the assigned specialist the request before sending the secure Persona link.
4. 2.4After approval, send the link once and record the follow-up inquiry ID and sent time. Keep each outstanding evidence check incomplete until the returned documents have been reviewed against the checklist.

Read LSEG World-Check One results, capture source references and secondary identifiers, and preserve unresolved matches for review.

1. 3.1Open the linked LSEG World-Check One case and retain the screening time, World-Check IDs, and result statuses. Check the configured screening group before interpreting any unresolved match.
2. 3.2Compare Name, Date(s) of Birth, Nationality, and Country Location with verified evidence. Show discrepancies side by side (ex: different birth years) and mark missing secondary identifiers as unavailable.
3. 3.3Include the group’s secondary-identifier and auto-resolution settings in the review context. Do not treat a birth-year difference as an automatic dismissal when the result remains unresolved.
4. 3.4Link each comparison to its source record and prepare unresolved hits for the assigned reviewer. Preserve the original results and any contradictory evidence with the proposed explanation.

Attach evidence references and a completeness checklist to the Persona case. Make missing information and contradictions explicit.

1. 4.1Attach the inquiry links, selected checklist version, and World-Check results to the linked Persona case. Use the team’s packet sections Identity, Address evidence, Screening, and Decision needed.
2. 4.2Set each checklist item from the current evidence rather than copying a prior case’s status. Put the exact missing document or unresolved comparison beside each incomplete item.
3. 4.3After the onboarding specialist authorizes routing, assign the case through the configured compliance-review queue and record the owner and time. Keep secure follow-ups linked to this case rather than opening an independent review.
4. 4.4When new evidence arrives, refresh the corresponding packet section and retain the request history. Leave any screening decision with the assigned reviewer even if every document is now present.

An authorized compliance reviewer evaluates the packet and records the acceptance or escalation decision and rationale.

1. 5.1Have the authorized reviewer check returned evidence against the selected checklist and inspect unresolved World-Check comparisons. Their review must address each missing identifier and discrepancy identified in the packet.
2. 5.2Read the recorded screening disposition, reason, and source comparison. For a result resolved as a different individual, require the supporting rationale before treating that hit as resolved.
3. 5.3Check the Persona decision record for the reviewer’s identity, decision, and timestamp. A message saying the review is done is a prompt to check the record, not a substitute for it.
4. 5.4If the decision is missing, the source links have changed, or a new hit is unresolved, return the case to its reviewer with that specific gap and keep onboarding pending.

Read the recorded Persona decision before updating Salesforce. Keep onboarding pending if any required decision or evidence is absent.

1. 6.1Re-read the Persona case, linked follow-ups, and LSEG World-Check One dispositions together. Synchronize only when the evidence and authorized decision refer to the same application and meet the selected checklist.
2. 6.2Update the team’s Salesforce fields Onboarding_Status__c, Review_Decision_At__c, and Persona_Case_ID__c with the recorded decision and source reference. Do not trigger account activation from this workflow.
3. 6.3Re-open the Salesforce application and compare its saved status, decision time, and reviewer link with the source decision. Leave a synchronization exception if Salesforce rejects any required field.
4. 6.4Retain the original application time, evidence-request time, response time, and decision time. These distinguish time spent waiting on the applicant from time spent preparing the review.