Skip to content

Case detail

The case detail gathers everything the system knows about a process: the data the customer supplied, what the external lookups confirmed or contradicted, the document and selfie images, the risk engine’s decision with its reasons, and the complete event history.

You reach it by clicking a row on the Onboarding screen.

This is a read-only screen: there is no approve or reject action. Recording the decision on a case happens in the analysis desk, which is a separate product. The actions available here are copying the journey link, sending the link to the legal guardian again, downloading documents and, on company cases, writing notes.

The header follows the scroll, keeping the case identification always visible. It carries the button back to the list, the person’s name or the company’s legal name, the first eight characters of the process code, the creation date and time, and the type, status and priority tags.

They appear only when they apply to the case and are the quickest read on the screen.

TagMeaning
PEPPolitically exposed person, according to the external lookup
SanctionsNumber of restriction lists with a match
LawsuitsNumber of court cases found
FaceMatchResult of the comparison between the selfie and the document photo
Doc ExpiredThe document reading showed it is out of date
GuardianStage of the legal guardian’s journey
Risk bandLow, Medium, High or Critical, once a decision exists

The button copies the customer’s journey link. It is not shown when the case is closed, that is, approved, rejected, expired or cancelled, since the link stops being valid. In those cases a new process has to be created.

The Cancel journey button appears in the header while the case has no outcome, that is, on any status other than approved, rejected, expired or cancelled. Before it existed, a process stuck mid-journey could only be closed through an API call.

The dialog names the holder, warns that the journey cannot be resumed and that the holder loses access to the onboarding link, and offers a reason field, optional, which is recorded in the process history. Where there is a linked journey, such as the legal representative of a minor, it is cancelled along with it.

The cancellation frees that customer’s active-session slot on that flow: after it, a new journey can be opened for the same person. If the case was concluded between opening the dialog and confirming, the screen says the journey had already been concluded and refreshes itself, cancelling nothing.

The screen offers two distinct sets of tabs. Individual cases, including minors and legal guardians, use one set. Company cases use another, longer one, laid out as a company dossier. You cannot switch between them: the set follows the type of the case.

TabAnswers the question
Identity and DocumentsWho is the person, what did they submit, and does it match the external sources?
Background CheckWhat did the external lookups return about them?
Ownership StructureWhat do the analysed corporate documents reveal?
Risk AnalysisWhy did the engine decide the way it did?
TimelineWhat happened, when and by whom?

The Ownership Structure tab appears only when the case has at least one analysed corporate document. On most individual cases it is not shown, and the screen offers four tabs.

TabContent
JourneyOpening tab, with the customer’s path through the journey
Identity and DocumentsData and documents of the representative who ran the journey
Ownership StructureOwnership, ultimate beneficial owners, powers and the signature matrix
Risk and ScreeningResult of the risk lookups and restriction lists
Rules and EngineEngine decision, signals and analysis stages
TimelineEvent history
NotesRecord of the team’s observations about the process

A case is treated as a company when the flow is of type KYB or when company data has already been collected. A company journey abandoned before the tax ID step is already shown in that format.

The rest of this chapter describes the individual tabs, which are the ones most often used. The ownership structure and notes sections, specific to companies, are described at the end.

It is the opening tab and the most used. The blocks appear depending on whether the case carries that kind of data.

The biometrics block shows the captured selfie, which enlarges on click, the liveness tag and the facial comparison, with the similarity percentage between the selfie and the document photo.

When one of those checks was not carried out, the screen raises an explicit alert. It is worth telling the two apart: a check that did not happen and a check that failed are different situations, and both call for care in the analysis.

The collected data and cross-check table has nine fixed rows, among them name, tax ID, email, phone, date of birth and address. For each one, the value the customer supplied and the result of matching it against the external source.

Cross-check resultMeaning
ValidatedThe supplied value matches the external source
Partial mismatchThe value is similar but not identical. The similarity percentage is available on hover
MismatchThe value does not match the source
No sourceThere was no lookup for that field. This is not a failure
Validation bypassedThe validation was waived by the system, with the reason available on hover

The engine decision block summarises the verdict, the 0 to 1000 score, the risk band, the main signals that weighed in and the reasons. The See full analysis button leads to the Risk Analysis tab.

When there is no verdict yet, the screen states why, and each reason carries its own meaning: the case is still in flight, it was sent to manual analysis without a detailed record, or it predates the detailed analysis record.

The submitted images appear as thumbnails: front, back where there is one, and the guardianship document on minor flows.

Clicking any thumbnail opens the viewer, with zoom from 25% to 400%, 90-degree rotation, download and side-by-side comparison, which puts document and selfie on the same screen. The comparison is available when both images exist and the document is not a PDF file.

The extraction block shows what the system read from the document: name, date of birth, document number and tax ID. Comparing it with the data the customer supplied is where typing discrepancies and elementary fraud attempts surface.

Document analysis offers four indicators.

IndicatorHow to read it
QualityScore from 0 to 100 for the image. “Not assessed” means the analysis assigned no score, either because it did not score or because the call to the document forensics service failed. It does not mean a score of zero
ConfidenceScore from 0 to 100 on authenticity
ExpiredWhether the document is out of date
TamperingNo indication found, or the number and the list of indications found

Below that, an alert describes the outcome of the document forensics. Telling them apart matters for the analysis: “Authenticity not verified” means the analysis did not run or failed for a technical reason, while “Document failed document forensics” means the analysis ran and did not confirm authenticity. The first is absence of information; the second is negative information.

Check these blocks even when the engine approves the case. In the current version, the decision engine does not take the biometrics result or the document analysis into account when computing the score. A case can carry an approval verdict and a low score even though the facial comparison failed or the document was not confirmed by document forensics. Those checks are still run and their results are still shown here, but weighing them is the analyst’s job.

On the right sits the journey timeline, with the counter of completed steps and markers for the current step, the steps that failed and the ones that were skipped. It is where you spot the point at which the customer stopped filling things in.

Block shown on minor cases or cases involving a representative. The title adapts to the side being viewed: Linked minor when looking at the guardian’s case, and Legal Guardian when looking at the minor’s case.

The card shows the progress of the guardian’s journey, the link to the tied case, the engine’s score and a notification block with the channel used, the recipient, the delivery status and how many resends have been consumed.

While the guardian’s journey is not finished, three actions are available: copy the onboarding link, resend by SMS and email, and resend by email only. Resends run immediately, without confirmation. The limit is three resends in total, shared across channels, so using SMS and email draws on the same allowance. Once the limit is reached, the buttons become unavailable.

The location block shows the address supplied and the addresses found in the external lookups, with a tag comparing the address city against the city of the access IP.

The contact trust block shows a confidence score and the verdict per category for tax ID, email and phone.

The device verification block reports where the person connected from: IP country, browser, operating system and, above all, the device signals, among them VPN, proxy, emulator and remote access. Several signals at once are a meaningful indication of an attempt to mask.

When the case carries company data, the screen also shows the business data, separating what came from the registry and what came from the journey, the ownership table with each partner’s name, tax ID, role and stake, and the tax ID registry validation with the company’s official data.

In the ownership table, tags flag the legal representative, politically exposed person status and any identity discrepancy, that is, the same tax ID tied to different names between the registry and the journey.

Shows what the external lookups returned.

The registry data block carries name, tax ID looked up, registry status, date of birth and name similarity. On minor cases, the screen reports that the source does not publish data on minors, which is the expected behaviour and not a fault.

The datasets group the information by family, among them basic data, financial risk, collections, indebtedness, media and exposure, phones, emails, addresses and lawsuits. Each card’s tag sums up the finding.

Where there are court cases, the matching block lists number, court, type, amount and status, highlighting those of a criminal nature.

The diagnostic drawers record the technical details of the calls made, useful when you need to show support that a lookup failed.

When a lookup runs but returns nothing useful, the screen states the cause in plain language, distinguishing an absence of information about the person from an inability to run the lookup at all.

It explains the decision, and is the tab to use when an outcome has to be justified.

The engine decision block shows the verdict, the score out of 1000 and the visual ruler that places the case against the two configured thresholds. Those thresholds are set in the Risk Matrix.

The list of triggered signals shows the alerts the case set off, ordered by how many points each contributed. Added up, they explain the score.

The execution stages block details each step of the analysis, with its score and its time. Expanding a stage reveals the subfactors that fired inside it.

The risk band shown on this screen uses the same cuts as the Onboarding screen, different from those applied on the Dashboard. When comparing screens, use the numeric score.

What the engine does not assess. As noted on the Identity and Documents tab, the score does not incorporate the biometrics result or the document analysis. When justifying an outcome from this tab, bear in mind that a favourable engine verdict is not approval of those two checks, which have to be reviewed separately.

Shows the complete history, event by event, with text search and filters by category: Journey, Audit, Engine and System. Search and category work together.

The table shows date and time, type, event, detail and severity, with icons highlighting warning and critical events. Manual decision events let you open the decision detail, with the status and the note the analyst recorded. Thirty events are shown per page.

The right-hand column carries the journey summary, with the total number of events and the count per category, the history of status changes with author, date and reason, and the resolution block, shown when an operator closed the case, with the outcome, the reason, the author and the handling time.

Shows what was extracted from the corporate documents submitted, such as the articles of association and their amendments. When more than one document has been analysed, a selector at the top switches between them.

SectionContent
CompanyLegal name, tax ID, registry number, document type, date and revision
OwnershipPartners extracted from the document, with type, stake and beneficial owner flag
Ultimate Beneficial OwnersIndividuals with a relevant stake, classified as identified, unidentified or requiring investigation
Powers and SignatoriesWhich powers each person holds and in what form
Signature MatrixWho may sign each type of transaction and in what manner
CompletenessWhich information was found in the document and which is missing

Stakes held by companies appear separately, flagged with the note that the ownership chain has to be opened to identify the individual at the end of it.

When no corporate document has been analysed, the tab reports that condition and shows none of the other sections.

Available on company cases. It lets the team record observations about the process, which stay visible to the panel’s other users.

To record one, write the text in the new note field and confirm. The note then appears in the history, with author and date.

Notes are an internal follow-up record. They do not change the case status, do not call in the analysis desk and are not seen by the customer.

Understand why a case went to manual analysis. Risk Analysis tab, triggered signals block. The signals at the top are the ones that weighed most.

Check whether the person in the selfie is the one on the document. Identity and Documents tab, click the front thumbnail and use the side-by-side comparison.

Find out where the customer stopped. Identity and Documents tab, right-hand column, looking for the step marked as current.

Help a legal guardian who did not get the link. Legal guardian block, checking channel, delivery status and remaining resends.

Gather evidence to justify a decision. Timeline tab, Audit filter, together with the resolution block.

What does “No source” mean in the cross-check? That there was no external lookup for that field. It is neither a mismatch nor a failure.

What is the difference between “Authenticity not verified” and “Document failed”? In the first case the analysis did not run; in the second it ran and did not confirm the document.

Does “Quality: Not assessed” mean a quality of zero? No. It means the analysis assigned no score, usually because it never got to process the image.

A minor appears with no registry data. Is that an error? No. The official source does not publish data on minors, and the screen says so.

The case has no image of the back of the document. The back is only requested for certain document types. For the rest, its absence is the expected behaviour.

How does the decision work on a minor’s case? Minor and guardian are two linked processes with a single analysis. When the guardian finishes the journey, the system brings together the information from both and produces one result, applied to the minor’s case and mirrored on the guardian’s.

The minor’s case sat still after they finished the journey. That is the expected behaviour. The case stays in Awaiting Guardian and the analysis happens when the legal guardian finishes their part.

The legal guardian did not get the notice about the result. The decision notice goes to the holder of the process. The guardian receives the link to run their own journey.

I opened two cases and the tabs are different. That is the expected behaviour. Company cases use their own set of tabs, laid out as a company dossier, distinct from the one used on individual cases.

The Ownership Structure tab does not appear on an individual case. It is only shown when at least one corporate document has been analysed for that case.

Version 18, updated on