Legal compliance software that puts every check on the record.

Legal compliance management software records and controls operational checks around client onboarding and matter opening, such as conflict searches, client due diligence, AML or KYC routing, approvals, and audit evidence. It supports a firm's approved process. It does not provide legal advice or replace the judgment of qualified lawyers and compliance officers.

The workflow searches the client, matter, party, relationship, and historical records the firm has approved. It presents possible matches with source evidence to an authorised reviewer, then stores the query, result, decision, reviewer, reason, and time. A name match is not itself a legal conclusion.

It can collect identity and ownership evidence, apply the firm's routing rules, call approved screening providers, track missing documents, block matter opening where policy requires it, and preserve approvals. The firm's compliance team defines the policy and makes escalation and acceptance decisions.

Buy or configure an established product when its checks, jurisdictions, matter model, screening connections, and evidence meet the firm's needs. Consider an integration or focused custom workflow when historical records sit across proprietary systems, the firm's gates are unusual, or compliance must sit inside an existing matter-opening path that the product cannot support cleanly.

Both need visible operating rules. Similar names should enter a reviewer queue with the source records and matching reason. A provider timeout or unavailable source should not silently return a pass; it should preserve the failed request, keep the required gate unresolved, alert the named owner, and support an approved manual route.

The firm defines which events trigger a fresh conflict or due-diligence review, which prior evidence can be reused, and who approves any exception. The system should show the previous decision without treating it as current automatically, then preserve the new evidence and sign-off against the re-opened matter.

Use representative historical and current cases, including similar names, incomplete ownership evidence, high-risk clients, delegated reviewers, unavailable providers, denied access, re-opened matters, and export or retention requests. Acceptance should measure false matches, missed required steps, queue age, evidence completeness, and whether a reviewer can reproduce the decision.

The buyer diagnostic. If the evidence exists but nobody can assemble a report, you have a reporting problem and another scanner will not fix it. Count controls by system of record before counting features. Automation does not decide whether a control passed. A program that buys one expecting testing has bought a routing layer. Scoping, control design, risk acceptance, and the assessor's opinion still require people. The dangerous gap is the check that happened off the record.

A polished demo tells you nothing about how the product behaves in month seven. Feature count correlates with interface complexity and paying for modules nobody opens; the common failure is buying for what was demonstrated rather than what you are required to evidence. The demo test: ask the vendor to show the query behind one control, not the dashboard tile. A tool showing current state but discarding history cannot evidence a 12-month audit window. Demand the audit trail on a record somebody changed.

Renewal pricing is the known risk: fees move when frameworks or headcount grow. The platform is only part of the first-year bill; the independent audit, penetration test, and engineering hours carry the rest. Switching platforms mid-cycle can disturb an in-flight audit, so confirm the timing with your auditor first. On the compliance question: platforms surface gaps, automate evidence, and hand the auditor a structured workspace. They do not make you compliant.

Bring one control, the approved policy, source records, screening providers, matter-system boundary, common exceptions, and the people who investigate and sign off. We first recommend buy, configure, integrate, custom, or wait. If custom work fits, the written scope names the rules, dependencies, acceptance cases, responsibilities, and commercial terms.