Procedures
Configure at a higher level
Build flows that span every module
Automate everything your team does
When risk goes high, everything that should happen, happens
A customer’s risk score moves to High. One procedure opens a case, posts to the compliance channel in Slack and sets a review property on the customer in your CRM. Nobody has to remember the steps.
After onboarding, the record keeps filling itself
Once a customer is onboarded, a procedure fetches what your own systems already know, accounts, products, ownership, and writes it onto the Bits customer record. When something changes later, it flows back the other way.
An alert the moment a limit is crossed
A transaction comes in. The procedure adds it to the customer’s 30-day volume, checks the total against the limit for their risk level and opens a case with the numbers attached the moment it tips over. Not on the next routine check.
Your systems can start a procedure too
A call from your own platform can kick off a flow in Bits: fetch the data your core system already holds, run it through your rules and write the result back where your team works.
app.bits.bi/procedures/when-risk-goes-high
When risk goes high
v3
Published
Validated with no issues, by Compliance just now
No-code builder. Your compliance team builds, tests and publishes procedures themselves. No tickets, no release queue.
Onboarding
Risk score
Transaction monitoring
Screening
Ongoing due diligence
Case management
Bits provides. The AML modules, the core data model and the connectors to external providers, ready to be used in any flow.
Holm & Partners
High risk
Organisation
Country
Sweden
Segment
yours
Enterprise
Monthly volume limit
yours
€250,000
Review needed
yours
Yes
You configure. Your own data model, rules and thresholds on top of ours, and the flows that run between the modules.
Triggers
Every procedure starts somewhere.
Risk score changes
Application submitted
Case opened or closed
Due diligence review due
Screening status changes
On a schedule
Call from your system
Another procedure finishes
Actions and tools
Then it does the work.
Get any data point
Create or update records
Evaluate a rule
Open a case
Send to Slack or email
Call a webhook
Split and branch
Loop over records
Framework
And it stays reliable.
Runs in parallel
Context passed along
Execution log
Metadata on every run
Statistics
Versioning
Error handling
Test runs
You own the flows. Your compliance team builds and changes procedures in a no-code builder. No vendor requests or engineering tickets needed.
Any data, any system. A procedure can read and write Bits modules, your own data model and external systems in the same run.
Audit-ready by default. Every run is logged with its version, its context and its outcome, so you can show exactly what happened and why.
Nothing goes stale. Changes flow back into the customer record and out to your systems, automatically.
CleverCards
Ray Brash
COO of Clevercards
What is a procedure?
What can start a procedure?
What can a procedure do?
Can a procedure use data outside Bits?
How is this different from the rules inside each module?
Can a procedure wait for something, like a provider check or a customer’s answer?
How do we change a live procedure safely?
Can we see why a decision was made?
What happens when a step fails?
Does it scale?
Do we need developers to build procedures?
See Procedures in action.
