Customer due diligence that works in practice

Make every customer decision explainable.

Legalbricks.io automatically keeps company information and screening current, then prepares the purpose description, risk classification and documentation trail. When the customer's risk picture changes, the case follows your rules—and your team controls the result.

Customer-specific purpose proposalsExplainable risk classificationOngoing register and list checks

Customer due diligence

Grøn Energi Partner A/S

Low risk

3 of 4 found without asking the customer

  • Company & ownersBusiness registry
  • Sanctions & PEP screeningNo match
  • Owner identityReused evidence
  • Source of fundsAsked the customer
Prepared for approvalwith the reasoning attached
Complete evidence trailfrom invitation to offboarding
Built for
  • Auditors
  • Bookkeepers & accounting firms
  • Leasing
  • Law firms
  • Fintech & payment businesses

The operational gap

The policy may exist. The customer file can still fall short.

Across professions, the recurring challenge is not another policy document. It is applying the policy consistently to each customer and keeping the reasoning ready to show.

01

The purpose is too generic.

A copied sentence does not explain why this particular customer wants the relationship or how it is expected to be used.

02

The risk class has no clear path.

Low, medium or high is selected, but the file does not show which facts and parameters produced the result.

03

The data goes stale.

Without ongoing maintenance, changes in company information or sanctions and PEP exposure may wait until the next manual review.

04

Advice stops at the policy.

The business still has to turn written requirements into customer questions, approvals, renewals and evidence.

From invitation to evidence

Legalbricks.io prepares the work. You control the rules.

  1. Collect

    Legalbricks.io retrieves known company information, and the customer receives a KYC invitation for the information that still needs to be collected.

  2. Prepare

    The system prepares a customer-specific purpose proposal, risk classification and supporting reasoning.

  3. Approve

    The case follows your configured route—automatic where the rules allow it, human where judgement is required.

  4. Maintain

    Company information is updated automatically and screening continues against current sanctions and PEP lists. A changed risk picture triggers your configured process; planned renewals remain a separate periodic review.

One obligation, different working days

Designed around the people who actually handle the customer.

The customer-facing adviser often owns the daily case. In a small firm that may also be the owner; in a larger organisation, central AML or compliance roles set the framework and handle escalations.

Auditors

Give the practising auditor a prepared customer file while partners or the AML-responsible person retain control of the rules and escalations.

Bookkeepers & accounting firms

Standardise purpose descriptions, risk classifications and renewals across advisers without making every employee an AML specialist.

Leasing businesses

Keep customer assessments, evidence and planned follow-up connected across an active portfolio.

Law firms

Apply a consistent, documented customer process while the responsible lawyer remains in control of the individual assessment.

Fintech & payment businesses

Start with CDD and connect customer work with transaction monitoring, compliance management and payment flows as needed.

Why CDD is different

Prepared for approval—not another blank workflow.

Legalbricks.io does the data collection, ongoing maintenance and structured preparation that consumes the case handler's time. Company information and screening stay current between planned reviews, while the result remains reviewable, editable and fully traceable.

Customer-specific output

A purpose description and risk classification for this customer.

The proposal is generated from the individual customer's maintained information. The case handler can review, correct and approve it, with the underlying data and reasoning kept alongside the result.

  • Not a static template repeated across the whole customer book.
  • The customer data stays current through register updates and ongoing screening.
  • The history stays together from invitation through renewals and offboarding.

Customer due diligence

Grøn Energi Partner A/S

Low risk

3 of 4 found without asking the customer

  • Company & ownersBusiness registry
  • Sanctions & PEP screeningNo match
  • Owner identityReused evidence
  • Source of fundsAsked the customer

Approval effort follows risk

Automate the routine case without losing the evidence.

Approval routing is configured by the business. A common setup lets qualifying low-risk customers pass automatically, sends medium risk to one case handler and high risk to a case handler plus the MLRO.

  • Your rules decide the route at onboarding, detected changes and planned renewal.
  • People handle the judgement where the risk class requires it.
  • Automatic still means documented with the full collected basis retained.

Approval rules

Risk determines the approval path

Configurable
  • 0Low riskApproved automatically when the rules are met0 people
  • 1Medium riskCase handler reviews and approves1 person
  • 2High riskCase handler and MLRO approve2 people

Example setup—each business adapts its own rules

A newer requirement, already part of the model

Make proliferation-financing risk operational.

Businesses covered by AML rules must now address the risk that their services are misused for proliferation financing. Adding that requirement to a working customer-risk model is complex. Legalbricks.io includes structured PF support as a standard part of the complete CDD risk model—not as a paid add-on.

  • Standard for CDD customers with access to the complete risk model and its components.
  • Applied in the customer process instead of left as another paragraph in a policy.
  • Transparent and configurable without replacing your business's own legal responsibility.

The outcome

From a policy on paper to a process in operation.

Policy without execution

  • Generic purpose text
  • Risk level without a clear rationale
  • Manual chasing and renewal reminders
  • Rules interpreted differently by each employee
  • Evidence assembled when someone asks

CDD in Legalbricks.io

  • Customer-specific purpose proposal
  • Explainable risk classification
  • Ongoing register, sanctions and PEP checks plus planned renewals
  • Configured rules applied when risk changes
  • A documentation trail built as the work happens

Control without black boxes

Automation you can account for.

Prepared and explainable

Every prepared result stays connected to the customer facts, parameters and evidence behind it.

Configured responsibility

Your setup defines when the system can approve and when a case handler or MLRO must act.

Continuously maintained, fully documented

Register data and screening stay current, while changes, renewals, approvals and offboarding remain part of one customer record.

CDD pricing

One progressive price. The necessary functionality included.

Pay per active customer from the moment the KYC invitation is sent until offboarding. No separate seat, sanctions-screening or API-access surcharge for the CDD functionality you need.

See the full price ladder

See Legalbricks.io with your own customer process in mind.

We will tailor the CDD walkthrough to your profession, portfolio and approval model.