A loan with nothing behind it
A facility is disbursed and sits in the books like any other. Every field on the loan record is filled in.
Red flag: No item of security is recorded against the facility.
It runs automated audit tests on the bank's own data every night and explains every finding. Auditors decide.
A bank's internal audit team has to test its controls across every loan, deposit, ledger posting and change of staff access. Checking a sample by hand misses things, and banks need to be ready for the Central Bank's 1 January 2027 audit rules. Audit Assure gives the Chief Internal Auditor one command dashboard over the bank's own data. Each night it reads the core systems over read-only connections, masks customer identities, and runs 10 automated audit tests over every record in scope: duplicate identities, loans with no security recorded, postings to closed periods, access raised just before a posting, and more. Hits are grouped into ranked cases, and a branch risk heatmap ranks every branch by open findings, entity risk and pattern hits. Every finding shows the rule that matched, the records behind it and the innocent explanations to check first. An auditor reviews it, can ask questions in a chat that answers from the masked data, and records a decision: fraud case, control weakness, false positive or no issue. Findings are tracked through to the audit committee, and the output is a readiness pack for the Central Bank's rules. It runs on the bank's own Red Hat Linux server, and every scan, approval and decision is kept in a tamper-evident log.
The dashboard shows confirmed frauds this financial year, money prevented and recovered, open findings and the last nightly run. Pattern coverage says how many tests ran and how many could not, so nothing looks clean just because it was skipped. Below it, the branch heatmap ranks every branch by open findings, entity risk and pattern hits.
Alerts by pattern show, for each test, how many alerts were confirmed, are still under review, or turned out to be false positives. A test that raises mostly false positives gets tuned or retired. Underneath, detections are counted day by day over the last 30 days.
Open findings are ranked by severity, then by how unlikely their combination is to be chance. Each one says in plain words why it was flagged, and that it is a lead, not a finding. The auditor records the outcome: open a fraud case, log a control weakness, close it as a false positive with a reason, or mark it no issue.
The evidence page shows the rule that matched, the records it matched, and the known innocent explanations to check before escalating. A side panel says how strong the case is: here, about 4 in 9 subjects with this combination would turn up by chance, so it is a lead worth a look, not a strong anomaly.
The deep dive answers questions from the masked data: what the finding is, why it was raised, and what would make it a false positive. The answer names the pattern, its threshold and the dates behind it, and repeats that the finding is a lead for a person to check.
An auditor describes a new test in plain words, and the assistant drafts it: title, audit assertion, severity, threshold and the evidence columns to show, with every assumption listed so the auditor can remove it. A second person must approve the pattern before it runs.
A facility is disbursed and sits in the books like any other. Every field on the loan record is filled in.
Red flag: No item of security is recorded against the facility.
A staff member's access rights are raised, and a few days later they post a ledger entry. Each step on its own looks routine.
Red flag: The privilege escalation came within days of that same person's own posting.
The period is closed and its results reported. Then a new entry appears in the ledger.
Red flag: The entry was posted after its account's period had closed.
Two customer records with different reference numbers, opened at different branches.
Red flag: Both records carry the same national identity number.
Each night it reads the bank's core systems over read-only accounts against standby copies, plus scheduled HR and directory file exports.
Customer names, identity numbers, addresses and contact details become consistent codes, so the same person keeps the same code. A named person signs off the column classification once; it then runs each night while the data layout stays the same.
Every active pattern runs over every record in scope, with no sampling. The same patterns on the same data give the same results, even a year later.
Hits are grouped into cases and ranked, allowing for patterns that coincide by chance, and branches are scored for the heatmap.
Auditors work the findings queue, check the evidence, ask the assistant, and record a decision: fraud case, control weakness, false positive or no issue.
Findings are tracked through to the audit committee, and the output is a readiness pack for the Central Bank's 1 January 2027 audit rules.
A test missing its input data is shown as untestable or unable to run, with what is missing, never as a clean result.
Every hit is a lead, not a finding. Nothing is closed or escalated without a person deciding.
Patterns are fixed, versioned rules, so a scan re-runs to the same result. The AI assistant explains and drafts; it never picks which records get flagged.
The person who approves a pattern is never the person who drafted it, and the software enforces it.
It has no write access of any kind to the bank's systems.
Scans, approvals, decisions and AI turns go into a hash-chained log, so an edited, backdated or reordered entry shows up when the chain is checked.
The command dashboard, findings queue, Discover, Pattern Library and Data Sources screens, with role checks on each.
Audit tests kept as declarative records in seven detection kinds, such as duplicate groups, missing related records, time proximity and a first-digit (Benford) screen. No SQL inside a pattern.
Replaces identities with consistent keyed codes before analysis. A separate locked store turns a code back into a name for a permitted officer, and every use is logged.
Runs the nightly cycle and queues the scans users ask for. It holds no credential that reaches bank data.
Answers questions about a finding, branch, pattern or feed from masked data, and drafts new patterns, within set limits on rows, time and spend.
A tamper-evident, hash-chained record of every scan, approval, decision and assistant turn.
It reads over read-only accounts against standby copies and never changes a record.
Every hit is a lead for an auditor. Only a person's decision turns it into a confirmed case.
No model sits in the detection path. Patterns are fixed rules that a reviewer approved.
Names, identity numbers, addresses and contact details are masked before analysis, and an egress check sits on every path out.
There is no automatic closure or escalation. A person records every decision.
Every record in scope is tested on every run.
It runs on the bank's own Red Hat Linux server, with PostgreSQL and the application in containers.
Audit Assure runs on-premises on the bank's own Red Hat Linux server, with PostgreSQL and the application in containers. It is four apps written in TypeScript on Node: a Next.js dashboard, a scheduler that runs the nightly cycle, a worker that extracts, masks and scans, and a host for the AI assistant. They talk through the database, and each part runs under its own database role (eight in all), so the part that reads raw data is not the part that scans it. Core systems are read over read-only accounts against standby copies; HR and directory data arrive as scheduled file exports, with nothing installed in those systems. Masking uses consistent keyed tokens (HMAC), so the same person keeps the same code across records. Patterns are declarative records over a common data model, in seven detection kinds, with no SQL inside them. Sign-in is through LDAP (Active Directory) or local accounts with Argon2-hashed passwords, with role checks, and TLS through nginx. The AI assistant reaches a configurable model endpoint behind an egress check and limits on rows, time and spend; it is never part of detection.
Chief Internal Auditors and audit committees at banks. Also the internal auditors who work the findings day to day, and the reviewers who approve new audit tests before they run.
No. It reads over read-only accounts against standby copies and has no write access of any kind to the bank's systems.
The application and its database run on the bank's own server. Before analysis, customer names, identity numbers, addresses and contact details are masked. The AI assistant calls a model endpoint the bank configures, and an egress check scrubs what is sent.
No. Detection is fixed rules that re-run to the same result. The AI explains findings and drafts new patterns; a person approves every pattern and decides every finding.
It is shown as untestable or unable to run, with what is missing, never as a clean pass.
Yes. An auditor describes the test in plain words, the assistant drafts it with its assumptions listed, and a second person approves it before it runs.
Each test's alerts are tracked as confirmed, under review or false positive. Patterns that raise mostly false positives get tuned or retired.
On the bank's own Red Hat Linux server, with PostgreSQL and the application in containers.
Through LDAP (Active Directory) or local accounts with Argon2-hashed passwords. Each person's role decides what they can see and do.
A 30-minute walkthrough with the team that built it.