Compliance software: what still needs a person?

Start with the decision you need to make

Software can collect information, apply configured checks and organize work. Your business still needs to decide who handles exceptions, approves changes and explains the result. A founder comparing a platform with a compliance service is often comparing different parts of the operating model.

Write down the problem before evaluating a product. Is information missing? Are reviewers overwhelmed? Is no one authorized to resolve an exception? A tool may address one part of the problem while the other parts still require people and clear procedures.

Separate the tool, the process and the owner

The tool produces information and supports a workflow. The process explains how the team uses it. The owner makes or escalates decisions within an agreed authority. Ask a vendor to show how an exception moves through the product, then ask your team who will perform each step.

• Who maintains the configuration and approves changes?
• Who reviews exceptions and checks the quality of the work?
• What records can the business retrieve and explain?
• What happens when the system is unavailable or a case exceeds the procedure?
• How will the process change as volumes or products change?

Evaluate the whole operating cost

A subscription price is only one part of the cost. Consider integration, internal review time, vendor management, training, exception handling and the effort required to maintain the process. Compare proposals using the same workload assumptions and clarify what happens when usage increases.

A cheaper tool can be appropriate if your team has the capacity and knowledge to run the process. A more automated tool can still leave important judgment calls unresolved. Ask for a demonstration using a non-sensitive example of a difficult workflow, not only the cleanest case.

Where fractional support can help

Fractional AML and KYC support can provide defined operating capacity and guidance around the systems already in place. Scope may include customer-review workflows, exception coordination, policy maintenance or management reporting. It should explain which tasks are performed, which decisions remain internal and how issues are escalated.

For example, a team may have enough screening technology but lack a consistent route for resolving exceptions. The initial improvement may be clearer decision ownership and procedures, followed by additional review capacity. This is a workflow example, not a reported client outcome.

Make a decision your team can operate

Before committing, agree who owns the process, what evidence will be retained and how performance and quality will be reviewed. Define the handover if you change providers. The aim is a workable combination of systems, people and responsibility that fits the business today and can adapt as it grows.

The FFIEC’s bank examination manual distinguishes written policies from the practices needed to implement them. That bank-specific guidance is useful context, not a statement that every technology startup has identical legal obligations.

Continue reading