Counterparty clearance

Clearance is the record that a counterparty has been through customer due diligence: who verified them, on what date, against which documents, and when that verification runs out.

A counterparty has one clearance, not one per role. The verdict means “verified to the depth this counterparty’s roles require”.

You work with it on the Clearance panel of the counterparty screen.

What the verdict means

Verdict What it means What you do next
Not started Nobody has verified this counterparty yet A compliance officer verifies them
Pending A role they gained needs evidence not yet seen Verify or refuse it
Verified Due diligence is complete and in date Nothing, until it expires
Refused A compliance officer turned it down Gather better evidence, then verify again
Expired The re-verification date has passed Verify again
stateDiagram-v2
    [*] --> NotStarted: Clearance opened
    NotStarted --> Verified: Verify
    Pending --> Verified: Verify
    Pending --> Refused: Refuse
    Verified --> Pending: A new role needs more evidence
    Verified --> Expired: Re-verification date reached
    Refused --> Verified: Verify
    Expired --> Verified: Verify

Freezing is separate from all of this. See Freezing a counterparty.

Getting a counterparty cleared

A clearance opens when the counterparty is registered, if your rules cover its type. From that day, due diligence is owed, and the counterparty appears on Outstanding due diligence under Compliance until someone verifies it.

  1. Open the counterparty and select Clearance in the Compliance group.
  2. The checklist lists each document your rules require for this counterparty’s type and roles, and whether a recorded document meets it.
  3. On an outstanding row, select Record document. The dialog offers only the document types that meet that requirement. An identity document names the customer’s identification, so the number is never typed twice.
  4. Attach a scan to a recorded document if you have one: a PDF, JPEG or PNG, at most 10 MB. One scan per document.
  5. Recording documents moves the clearance to Pending. It does not clear the customer. When nothing is outstanding, the panel says Ready to verify.
  6. A compliance officer selects Verify on the panel and chooses a Risk band. Verify relies on the most recent document that meets each requirement. Refuse, Freeze and Unfreeze sit on the Clearance tab’s header. Before a clearance opens, Freeze greys out and says “Clearance isn’t open yet. Try again shortly, or start Verify.” Registration opens the clearance a moment after it finishes. If a regime starts to cover the type later, only Verify opens it.

Verify greys out while anything is outstanding. The dialog says what, for example “Proof of address is outstanding”. A document’s age is measured on the day it is recorded. With a 90-day limit, a municipal account dated 1 May and recorded on 26 September is 148 days old and does not count; one dated 28 June, 90 days old, does. A bill recorded fresh does not go stale while the sign-off waits.

A mistaken document is withdrawn with a reason, never deleted — it stays in the list, struck through. Withdrawing a document the last verification relied on sends the clearance back to Pending.

If someone records or withdraws a document while a Verify waits for a second pair of eyes, the waiting Verify goes stale and applies nothing. Verify again against the current documents.

Seeing the checklist does not show the scans. A scan of an identity document is special personal information, so opening one needs its own permission.

Some rows are declarations, not documents. Tax residency is one: the checklist ticks it once the compliance officer declares a residency on the counterparty’s Tax residency panel. Registration no longer asks for it.

If the counterparty’s type has no clearance rules configured, the panel says so and there is nothing to verify — clearance does not apply to them.

Verifying, refusing, freezing and unfreezing are all eligible for countersign, so a second pair of eyes can be required on any of them. Recording, withdrawing and scanning a document decide nothing, so they apply at once. A verdict staged from the counterparty page joins the counterparty’s change set and takes effect when that set is granted.

A draft counterparty that is discarded takes its clearance with it: the clearance becomes Discarded and leaves the outstanding list, but its documents and scans stay, read-only.

What clearance blocks

Account activation. An account activates only when every owning party is verified. On a joint account that means each holder: due diligence is per legal person, and the refusal names the holder who is not cleared.

The gate fails closed. If a clearance is missing while clearance rules apply to that counterparty type, activation is refused rather than allowed through.

Clearance does not block anything else. An already-active account keeps running, whatever the verdict.

Freezing a counterparty

A freeze stops outbound money and nothing else. Use it for a screening hit or a direction from the regulator.

While frozen Still runs
New outbound payment instructions are refused Collections in
Statements and documents out
Internal postings and interest

Inflows deliberately continue. An investigation must not tip off its subject by visibly stopping their money coming in.

A freeze leaves the verdict alone: a Verified counterparty stays Verified while frozen, and unfreezing restores exactly what was there before. Freezing and unfreezing are both deliberate human acts — nothing freezes a counterparty automatically.

Freezing is not suspension. Suspending a counterparty refuses every operation; freezing refuses outbound money only.

Expiry

Each verification carries a re-verification date, set from the risk band recorded at the time. At end of day, any clearance that has reached its date becomes Expired, and a follow-up task is raised against the counterparty.

Expiry blocks new account activation. It does not stop money on existing accounts — a missed re-verification date must not kill a customer’s debit orders overnight. If money must stop, freeze the counterparty.

An identity document can also run out before the clearance does. If the passport or ID a verification relied on stops being current, the end-of-day run raises a follow-up task, Refresh identity document, once. The verdict stays Verified and money keeps moving. Record a current identity document and verify again.

Worked example

Alex opens a savings account with Woodgrove Bank. Woodgrove re-verifies High-risk customers every 365 days and Low-risk customers every 1,095 days.

  1. Alex’s clearance is Not started.
  2. On 1 March 2026 a compliance officer verifies it at the High risk band, recording an identity document and a proof of address.
  3. The verdict is Verified and the clearance expires on 1 March 2027 — 365 days from the verification date.
  4. Alex’s account activates. A second account for Alex and Sam jointly stays blocked until Sam is verified too.
  5. On 1 March 2027 the end-of-day run marks the clearance Expired and raises a re-verification task. Alex’s existing accounts carry on unaffected; a new one cannot be activated until the clearance is verified again.

What your organisation configures

You work with all of it under Settings, in the Compliance section. It carries six screens, and they read in the order you set them up:

Screen What it holds
Compliance Regime The regime your organisation operates under
Evidence Document Types What a customer can hand over
Evidence Requirements What the regime needs to see, and which documents meet it
Clearance Requirements Which requirements each counterparty type must meet
Re-verification Cadences How long a verification stays in date, per risk band
Reportable Thresholds The cash movements that must be reported

Set the regime up first. The requirement and threshold screens each ask which regime a rule belongs to, and a rule naming one your organisation has not set up is refused.

Everything below is a setting. Onboarding under a different set of rules is configuration rather than a release.

Saving and publishing your changes

A change is not live when you select Save. It joins your draft of the compliance settings, and a second person approves it.

  1. Make your change on any of the six screens and select Save.
  2. Repeat on the other screens until the draft holds everything you need.
  3. Select Publish to send the whole draft for approval as one change.
  4. A colleague with approval rights reviews the draft and approves it.

The approver sees each changed row by its key, so they know which regime or rule moved.

If a change would break the rules below, Save refuses it. The message names the row and what to fix. If a change depends on what is live, Publish refuses it instead. A new rule naming a switched-off regime is one example.

The regime your organisation operates under

Your organisation names the anti-money-laundering regime it operates under, and every clearance rule and reporting threshold hangs off it. The name appears on the Clearance panel, so a compliance officer can see which rules a verdict was reached under.

You can change its description, and you can switch it off. You cannot rename it — clearances and threshold reports already filed record the regime they were raised under, and renaming it would leave those records naming something that no longer exists.

Switching the regime off turns the whole clearance requirement off with it: no counterparty type demands clearance, and no account activation is gated. Switch it back on and every rule you configured is still there.

One regime at a time. Your organisation operates under a single regime, and adding a second is refused. Choosing between regimes — which customer falls under which — is not yet something you can configure, so allowing two would silently apply the wrong rules to somebody.

Document types and evidence requirements

A document type is something a customer can hand over: an ID, a passport, a municipal account, a bank statement. An identity document type names the identification it proves.

An evidence requirement is what the regime needs to see — proof of address, say — and lists the document types that meet it. Each accepted document can carry a maximum age, because a bank statement proves an address only if it is recent. A requirement also says whether a periodic review may rely again on the documents the last verification accepted (reuse), or needs one recorded since (refresh).

A document type a requirement accepts cannot be removed, and neither can a requirement a clearance rule names.

Which counterparty types need clearance, and what they must produce

You add a rule per counterparty type, naming the evidence requirements that type must meet and any data they must declare. A type with no rule has no clearance and no activation gate.

You can add a second rule for the same type in a particular role — an investor, say — and it adds to the type’s requirements rather than replacing them. The two are separate rules: removing the role’s rule leaves the type’s rule alone.

The re-verification cadence per risk band

How long a Low, Standard or High verification stays in date. Cadence is set per risk band and applies whatever the regime, so these rules do not name one.

Reportable movement thresholds

You configure the cash movements that must be reported, as one or more threshold rules. Each rule carries a name, the transaction types it adds up, an amount, and the period it adds them up over.

The name is how you tell two rules apart, so give each one something readable:

Name Adds up Reports over Daily total
cash Deposits A day 24,999.99
eft Withdrawals A day 100,000.00

At end of day, any counterparty whose movements of the named types reach the amount gets a report raised against them, and the report records which rule produced it.

You pick the transaction types from the ones your organisation has declared, so a rule cannot name a movement type that does not exist — a rule that named one would simply never fire.

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.