Compliance Officer Guide

This guide is written for compliance officers, heads of compliance, and money laundering reporting officers who use the Digital Experience Platform (DXP) to screen applicants, clear flagged clients, monitor live transactions, and evidence the decisions they take.

You screen applicants and existing clients, clear the ones the engine flags, monitor live transactions, and keep an audit trail regulators can read. Three surfaces carry most of your work.

The Compliance Engine has two main parts that run against different moments in a client's life.

Both parts surface inside the Compliance Hub and inside the inline review you see on flagged interactions.

1. Open the DXP URL provided by your administrator.
2. Enter your work email, then press Sign In.
3. Enter your password, then press Login.
4. If two factor authentication is on, enter the 6 digit code from your authenticator app.

You can only sign in with a work email that ends in your tenant domain. Once signed in, the left side menu shows Dashboard, Interactions, Clients, Compliance Hub, and Logs. As a compliance officer you will mostly use Interactions, Clients, and Compliance Hub.

When an application is flagged for AML, the Inline Compliance Hub appears inside the expanded row in the compliance Backend Block step. Open the row from your Interactions queue.

1. Open Interactions and expand the flagged row.
2. Read every list searched. A green check means no match on that list. A red triangle means at least one possible match.
3. Open a list that shows a match. The panel reveals the matched record.
4. Read the matched record fields: source name, aliases, source list metadata, country, date of birth where present, and a match score from the AI engine.

The inline screening has two layouts. Toggle between them with the gold tab on the right edge of the panel.

1. Press the gold table tab on the right edge to switch to table view.
2. Use the Filters (Schema, Country) and search to narrow the matches.
3. Sort by any column, for example Score, to work the strongest matches first.
4. Tick the checkbox on each row you want, then apply the action to all selected at once.
5. Press the tab again to return to pill view.

Click a list that has matches (for example UsOfacSdn) to open the matched record. The record shows the possible match with its score, the name, the full alias list, and the country. Page through matches, then choose one action.

Above the lists in the expanded row sits the biometric panel. It gives you context for the adjudication.

Use these together with the list result. A confirmed sanctions match with a high biometric match is a clear stop. A possible match with a poor biometric match is a candidate for additional review.

Workspace is the standalone surface. Use it for ad hoc searches, bulk file based searches, and reportable sessions outside of any incoming interaction.

1. Open Compliance Hub. You land on the Workspace.
2. Set Entity Type to person or business.
3. Type the name in the Search box, then press Enter to turn it into a pill. This commit step is required. Pressing Search without committing the pill returns nothing. Add more pills to screen several names at once, or use the plus by the box.
4. Open Filters and narrow by Lists, Country, Address, Date of Birth, Industry, Document Number, and From / To dates.
5. Set Apply Transliteration To for switching between Arabic and Latin script handling.
6. Set the Compliance Search Focus. The default is AML. Switch it to PEP to surface politically exposed person results.
7. Turn on Show Only Hits to hide green check lists from the result.
8. Turn on Advanced Search for a wider net that uses more name combinations. It is slower.
9. Press the search control to run the session.
10. Press Export Report to download the full session for audit and regulator submission.

Client Clear shows every existing client that the background screening engine has flagged since their last clear. The platform reruns screening on the Run AML Check cadence, configured in Settings, Client Profile, per profile type. The page has tabs at the top for each Client Profile Type, Person, Verified Person, and Verified Business, each with a count badge.

Working a flagged client, step by step

1. Open Client Clear. Pick the tab for the affected profile type.
2. Sort by Last Match, newest first.
3. Open the client. The biometric panel and the Inline Compliance Hub appear inside the profile.
4. Press View More on each match to read the full record.
5. Choose Confirm Match, Confirm and Allow, or Clear Match. Add a note for the audit trail.
6. If confirmed, follow your institution's suspension or enhanced due diligence procedure.

Open Settings, then AML Management. Two tenant level toggles sit at the top, and below them is the Add New List area where you maintain custom lists.

The most important block is the Screening Profile. The profile defines how the engine searches every time you press search in Workspace, Client Clear, or inside an inline review.

1. Pick the Profile Name from the picker, for example Default.
2. Set Apply On to the surfaces this profile drives: Interactions, Client Clear, Workspace.
3. Tune Traditional Matching Algorithms, which carry 40 percent of the score weight. Each algorithm has its own toggle and weight slider, and the enabled sliders must sum to Total Weight 100 percent inside that 40 percent envelope.
4. Leave AI Matching to carry the remaining 60 percent of the score weight.
5. Press Save to commit the profile.

Advanced Features, the sensitivity knobs

Below the algorithm weights sit the Advanced Features. These are the core controls you adjust to balance catching every alias against generating false positives.

RTRA monitors live client transactions after onboarding. Configure it in Settings, RTRA Engine Configuration.

Defining a rule, step by step

1. Set Rule Name and Rule Span in days.
2. If the rule is short lived, turn on Temporary Rule.
3. Build the Rule Structure: pick the Entity, Attribute, Operator, and Value. Add more conditions with the plus icon.
4. Pick the Action that fires when the rule matches.
5. Write the Output Message that the system attaches to the action.
6. Press Add. The new rule appears in the Defined Rules table at the bottom with Status, Type, and Remaining lifespan.

The Risk Based Approach produces an RBA Score per client. Configure it in Settings, Client Profile, per profile type.

1. Turn on the Risk Based Approach toggle for this client profile type.
2. Set the Risk Levels. Low, Medium, and High are the defaults. Add more tiers if your policy needs them.
3. Drag the Thresholds on the 0 to 10 strip to mark the boundary between tiers. Defaults: Low 0 to 3.00, Medium 3.00 to 8.00, High 8.00 to 10.
4. Press Save to commit the bands.

The RBA Score column in Client Clear and the Clients section uses these tiers to color and rank clients.

Where the RBA Score comes from

The bands set the tiers, but the score itself comes from Configure Risk Profile, which opens the Clients Risk Scoring Configuration screen. There you add a card for each data point you want to score, and each card sets a Risk Behaviour.

Open Values Classification Mapping on each card to map every possible value to either a weight, for Contributes, or a target risk level, for Auto Classify. Watch the running Total Weights as you add cards.

1. Press Configure Risk Profile.
2. Press the plus to add a card, expand a flow on the left, then pick the data point.
3. Choose the Risk Behaviour: Contributes to Risk Score or Auto Classify on Value.
4. Open Values Classification Mapping and map each value to a weight or a risk level.
5. Repeat for every risk relevant data point, then Save.

Screening checks these lists. Custom lists you maintain run alongside them.

Every compliance action is captured in two places. The Compliance Hub Audit Hub gives the specialized view filtered by System User and Decision. The platform Logs section gives the complete platform audit by activity type.

Open Logs to review the platform audit trail. Set the audit type to User Activities or System Audit, filter by date, and read Created, Activity Type, User Name, and Message. Press Export for a record.

The DXP supports custom roles built from claims dragged into a role definition. The recommended starting roles for this audience are below. Your administrator can adjust the claims to match your operating model.