Risk assessment and rating
Checklist marks roll up into Control Risk; CBS figures give Business Risk. A Risk Audit Matrix combines them into a rating with its trend, and overrides need a second approver.
On-premise audit management software for Indian banks. It runs on your bank’s own servers, sits between your audit teams and your Core Banking System, and takes concurrent, statutory, risk-based and IS audits from plan to closure on live data.
Risk-based internal audit (RBIA), concurrent, statutory and IS audits · Risk assessment · On-premiseMost bank audits still run on exported spreadsheets and long email threads. This works on the bank’s live data instead, inside the bank, and keeps each finding tied to the record it came from.
Installed on your own servers, one bank per install. Customer and transaction data never leave your infrastructure.
What the auditor marks in the workspace is what the board reads in the report. No re-keying between spreadsheets.
Figures are read from your Core Banking System and keep their lineage back to the record they came from.
Eight roles, each scoped to its level. A finding is a conversation between the audit side and the bank side.
Plans the year, publishes audits, approves ratings and compliance, releases reports and issues closure certificates.
Sets up regions, units, the risk matrix, sampling policy and compliance deadlines.
Manages users and branches, and reads the audit trail.
Reviews submitted audits, approves non-critical compliance and handles incidents for the region.
Completes monthly branch inspections and files compliance.
Leads the audit team on site and submits the audit for review.
Works the checklist, checks sampled accounts, raises findings and attaches evidence.
Replies to findings, submits compliance and rectifies monitoring exceptions.
Risk assessment, planning, fieldwork, compliance and monitoring, all working on the same data.
Checklist marks roll up into Control Risk; CBS figures give Business Risk. A Risk Audit Matrix combines them into a rating with its trend, and overrides need a second approver.
Generate the year’s plan from risk ratings and your frequency policy, schedule around auditor leave and training, and track man-days.
Rules check CBS data between visits. Exceptions are graded, routed to the right level by a distribution matrix, rectified by the branch and accepted by RO or HO.
A dashboard for every role, MIS reports by region, Annexure tables pre-filled from the CBS, and audit documents in PDF and Excel.
Concurrent, statutory, risk-based (RBIA), IS and credit audits, plus your own audit types, on versioned questionnaires with loan accounts sampled by bank policy.
Each finding is a thread between the auditor and the branch, with evidence. Deadlines follow severity, unresolved items carry into the next audit, and closure ends in a certificate.
An optional rule library for cash (CTR), cross-border (CBWTR) and suspicious-pattern (STR) reporting, with a watchlist, alerts, cases and FIU-IND filing.
Monthly branch inspections open on their own. Auditors record spot rectification, income leakage and incidents, and can work offline in an Excel file.
Deploy on your bank’s own servers, inside your infrastructure. One bank per install.
Connect your Core Banking System read-only. Each connection is scoped to the audit that needs it.
Run audits and monitoring rules, track findings to closure and report to the board.
Runs on your servers. No shared tenancy and no vendor access across banks.
Reads accounts, GL and transactions. It never writes to your Core Banking System.
Every request is recorded in a hash chain that can be verified, and published records cannot be edited.
Account references, PAN and other sensitive fields are encrypted with AES-256.
Every PDF and Excel export carries the user, time and checksum, and is logged.
Eight roles across head office, region, field and branch. People see only their own scope.
Sensitive files can be restricted to named people, view-only, with every access logged.
The interface and checklists are available in both languages.
No. It reads from your Core Banking System through a read-only connector and never writes to it. Accounts, GL entries and transactions are pulled per audit, so auditors work on live data while the CBS stays the system of record, and every figure links back to its source record.
On your bank’s own servers. Each bank gets its own install, so customer and transaction data stay inside the bank’s infrastructure and there is no shared tenancy. Your staff sign in to your bank’s own instance, and your administrators manage users, branches and roles.
Concurrent, statutory, risk-based internal audit (RBIA), IS and credit audits, plus audit types your bank defines, such as audits of PACS and other societies. Each audit runs on a versioned questionnaire, and its findings, compliance and closure stay linked to the evidence and data behind them.
Checklist marks roll up into a Control Risk band per area and overall, using bands your bank sets. Business Risk comes from CBS deposit and advance figures. A Risk Audit Matrix combines the two into a risk rating with its trend, which then drives how often each unit is audited in the annual plan.
No. AML monitoring is an optional module. When enabled, it runs CTR, CBWTR and STR rules on CBS transactions, raises alerts for review, groups them into cases and prepares FIU-IND filings. Offsite monitoring of branch exceptions works with or without it.
Each bank's staff sign in to their own on-premise install. Demos are arranged through our sales team.