# AbenAudit — internal audit software for banks

> AbenAudit is internal audit management software from Aben Consulting Kft. (Budapest, Hungary). It covers the whole internal-audit path, from the annual audit plan to the closed action. A configurable workflow engine, a versioned document store and a hash-chained ledger run in one system. Own, isolated deployment per customer; sign-in with Microsoft Entra ID.

- Vendor: Aben Consulting Kft., 1037 Budapest, Visszatérő köz 6., Hungary
- Contact: info@aben.ch · +36 70 336 4324
- Product page (English): https://aben.ch/audit/
- Last updated: 2026-11-19

This is a plain-Markdown summary of the public AbenAudit pages on aben.ch. It is the same file for every visitor, human or software. The HTML pages linked below are the reference.

## What it is

Internal audit management software. One system holds the whole audit path:

1. Annual plan — approval, with a quorum if needed; engagements start from it.
2. Engagement — objectives, risks, controls, tests, document requests.
3. Work programme — steps, working papers, evidence sheets.
4. Finding — criterion, condition, cause, effect.
5. Report — from draft to issue, built from the record.
6. Action and monitoring — deadlines, reminders, escalation.

## Who it is for

Internal audit functions in banks, and in groups of companies with several legal entities. It suits teams that want their own approval matrix enforced by the system rather than by email and spreadsheets.

## Key capabilities

- **Annual audit planning.** Approval chain with a quorum if needed. Engagements start from the plan, with demand and capacity side by side on the plan tree.
- **Engagements.** Objectives, risks, controls and tests. Document requests to the auditee, with the evidence tied to the record.
- **Work programme.** Steps, working papers, evidence sheets. Every hand-off is a recorded derivation, with no re-typing.
- **Findings.** Criterion, condition, cause and effect in separate fields. Risk rating on the bank's own scale, traced back to the control.
- **Auditee commenting.** The auditee comments on the finding inside the report; the comment appears in the next report version.
- **Remediation and monitoring.** The original deadline is write-once. An extension needs an approver and a reason. Reminders and escalation run on a working-day calendar.
- **Document store.** Versions with SHA-256 content digests. Check-out lock and check-in as a new version: one working copy at a time.
- **Second-person conclusions.** No draft report without a conclusion; the reviewer is not the preparer. Enforced server-side; cannot be switched off.
- **Engagement report.** Built from the record and the ledger chain: draft, review, committee, issue, management response, closure.
- **Management overview.** Coverage on the bank's own structure, including the areas not yet audited. Dashboards, CSV and Excel export.
- **The team's work.** A task list that names the next step and why work is stuck; who is on what, what is late.
- **Methodology as configuration.** Lifecycles, approval matrix, gates, deadlines, fields and notification wording live in versioned configuration. Changes are made as proposals and need a second approver before they apply; every version is kept.

### Group internal audit (several legal entities)

Roles are given per legal entity, and each entity has its own planning cycle. Findings record which company they concern, and each company can receive a local version of the report. Another entity's record returns the same 404 as a record that does not exist, so not even its existence leaks. Details: https://aben.ch/audit/group-audit/

### List of Potential Findings (LoPF)

Potential findings are tracked as records from the start: raised from a work-programme step, listed per engagement during fieldwork, evaluated, put to the auditee and agreed before reporting. A downloadable LoPF extract is planned. Details, including the link to IIA Standards 14.2 and 14.3: https://aben.ch/audit/list-of-potential-findings/

### IIA Global Internal Audit Standards

AbenAudit records the evidence the Standards ask for in planning, engagement work, findings, reporting and follow-up. A standard-by-standard mapping shows which records AbenAudit keeps, with status (available / partly / planned): https://aben.ch/audit/standards/global-internal-audit-standards/ . Conformance remains the internal audit function's responsibility, and AbenAudit is not certified by The IIA.

## Differentiators

- **Hash-chained ledger.** Every transition, approval, document write and refused access is a ledger entry. The director and the supervisory body can verify the chain from the start and export it as CSV. If an entry is tampered with, the chain stops verifying, the system turns read-only and names the broken entry.
- **Own, isolated deployment.** Not multi-tenant: each customer has its own PostgreSQL database and configuration, and upgrades follow the customer's schedule.
- **Entra ID, no directory rights.** AbenAudit asks only for openid, profile and email. Roles come from the organisation's existing Entra app roles and take effect at the next sign-in, so joiners, movers and leavers are handled in Entra.
- **Segregated legal entities.** Another entity's record returns the same 404 as one that does not exist.
- **Methodology is configuration, not a development request.** Changes go through a proposal and a second approver.
- **Controls that cannot be switched off.** Second-person conclusions and the write-once original remediation deadline are enforced server-side.
- **Acceptance checking.** AbenAudit is checked against Aben's proprietary 59-case end-to-end acceptance suite.

## Status

- The workflow engine, the security spine and the offline demo run today.
- Integrations: Microsoft Entra ID for sign-in today. Oracle and live SharePoint connections are on the roadmap.
- Languages: free text is stored and shown as typed, including Hungarian, Slovak and Croatian accented characters; exports are XLSX and CSV. The interface is in English today. A screen language choice and per-country report and mail templates are planned.
- Screenshots on the product page come from a demo deployment with fictional companies and synthetic data.

## How to evaluate it

1. A demo on a laptop, without touching the bank's systems.
2. The bank's approval matrix configured as a live workflow.
3. A sandbox on the bank's Entra tenant, with three sign-in scopes.
4. A pilot on an anonymised sample, running one engagement in parallel.

Request a demo: info@aben.ch

## Pages on aben.ch

- AbenAudit (English): https://aben.ch/audit/
- Group internal audit: https://aben.ch/audit/group-audit/
- List of Potential Findings (LoPF): https://aben.ch/audit/list-of-potential-findings/
- IIA Global Internal Audit Standards mapping: https://aben.ch/audit/standards/global-internal-audit-standards/
- FAQ: https://aben.ch/audit/faq/
- Magyar: https://aben.ch/hu/belso-ellenorzes-szoftver/ (also https://aben.ch/hu/csoportszintu-belso-ellenorzes/ and https://aben.ch/hu/lehetseges-megallapitasok-listaja/)
- Română: https://aben.ch/ro/software-audit-intern/
- Slovenčina: https://aben.ch/sk/softver-interny-audit/
- Hrvatski: https://aben.ch/hr/softver-interna-revizija/

## Related

- Company brief: https://aben.ch/agents/aben-consulting.md
- SecReg brief: https://aben.ch/agents/secreg.md
- AbenAlpha brief (in development): https://aben.ch/agents/abenalpha.md
- All briefs: https://aben.ch/agents/index.md

## Contact

Aben Consulting Kft. · 1037 Budapest, Visszatérő köz 6. · info@aben.ch · +36 70 336 4324 · https://aben.ch/
