Compliance teams are asked the same questions every month: how many cases did we handle, what kinds, who worked them, and is the backlog growing? Usually the answer comes from an export, a spreadsheet, and an afternoon of pivot tables, and by the time it reaches the board it is already out of date.
Insights is the reporting layer of the Bits dashboard: a page of charts built from the cases, applications, entities, and risk scores already in your workspace. It is not a business intelligence tool you connect and configure. The numbers are the operational counts a compliance lead needs for a Monday stand-up or a quarterly board pack, computed from the same records your analysts work in every day, so what you present is what the team actually did.
Some practical examples. An MLRO preparing the annual report needs case volumes by type per month. A team lead wants to know whether the sanctions backlog is shrinking now that two analysts joined. The owner of a new market wants to see applications stuck in review before customers start complaining. All three are a date range and a filter away.
Six charts, one page
Cases over time: case volume by period, with the case statuses you choose to include.
Cases by type: application reviews, possible PEP matches, adverse media, and sanctions matches, with screening and non-screening variants grouped together.
Cases by assignee: who is carrying the load, including cases with no assignee.
Applications by status: onboarding applications filtered by market and workflow.
Risk score distribution: how your customers spread across the score range.
Entity growth: how your customer base grows over the period.
A date range applies to the page and covers up to 24 months at a time. Each chart has its own filters where they make sense: case status and assignee on the case charts, market and workflow on applications.
What it is for
Capacity planning, board reporting, and sanity checks. If adverse media cases doubled last quarter, you see it before the quarterly review. If one analyst holds most open cases, you can rebalance. If a new market drives a spike in applications stuck in review, the workflow filter shows which one.
Operational numbers straight from the system of record, not from a spreadsheet someone rebuilt on Friday.
Why this matters for compliance
Supervisors expect firms to show that their compliance function is proportionate and working. Having the numbers on hand, from the same platform that holds the cases and customers, makes that conversation with auditors shorter and more credible.
Want to see it in action? Reach out to learn how Bits Technology can streamline your compliance operations.
File goAML SAR and STR reports without leaving Bits
Create suspicious activity and suspicious transaction reports for Sweden and Finland in the Bits dashboard, prefilled from your entities and exported as goAML XML.
Transaction monitoring cases that explain themselves
Every transaction monitoring case in Bits shows the transaction, both parties, and exactly which rules fired, with a one-click plain-text summary for your case notes.
Custom properties: model your own data in Bits
Define your own fields on individuals, organizations, and transactions in Bits, with typed values, translated labels, and use in filters and procedure conditions.

