ARCA MonitorDocumentation
Profiles
ARCA MONITOR / USER GUIDE

Profiles

Work with identities, due diligence, screening, and the review history of your workspace’s profiles.

Workspace members using ProfilesReviewed · 2026-10-07

Profiles is the working record for the people and organizations your workspace knows. A profile brings together identity, business roles, due diligence, risk, activity, and evidence. One identity can have several business roles; those roles are different from the permissions of the workspace member reviewing it.

Open the application

Confirm the organization in the workspace selector, then choose Profiles from the application selector. Use Profiles → View all for the general list. Start a search or apply a filter to load results; the initial prompt is not a statement that your workspace has no profiles.

The navigation also provides Agents / Branches, Correspondents, Financial Entities, Duplicates, Homonyms, Metrics, and Reports. Actions and detail sections depend on permissions, workspace settings, and the record’s state.

Choose a workflow

TaskGuide
Locate a person or organization and select recordsFind profiles
Register a person, company, or regulated entityCreate a profile
Work with operational counterparties or import their registerPre-registration
Understand identity, activity, network, and historyReview a profile
Resolve due diligence requirements and evidenceKYC and documents
Examine screening coverage and adjudicate a matchScreening
Interpret risk and follow authorized review actionsRisk and review decisions
Correct a field through the required approval processGoverned changes
Decide whether records belong to the same identityDuplicates and homonyms
Analyze your portfolio and prepare outputsMetrics and reports

A practical review sequence

FROM IDENTITY TO FOLLOW-UP

FROM IDENTITY TO FOLLOW-UP

Scroll to follow the full flow. Press Esc to close.

Find the correct profile, verify identity, inspect KYC and screening, review risk and activity, and document the next action. Follow any required approval through to its result.

Keep the outcomes distinct

An active profile is not necessarily KYC-approved. A verified document does not resolve every screening match. A low model score does not replace a reviewer’s rationale. A submitted proposal does not mean its change is applied.

Check the specific status and timestamp of each area. When a record has been merged into another, follow the surviving profile for current work and use the older record as history. A profile review does not authorize an individual transaction payment; that workflow belongs to Transactions.

On this page