AbenAudit / Frequently asked questions
AbenAudit · FAQ
Frequently asked questions
Deployment, sign-in, group audits, standards, languages, and how to evaluate AbenAudit.
What is AbenAudit?
AbenAudit is internal audit management software from Aben Consulting Kft., Budapest. It covers the whole internal audit path, from the annual plan through engagements, work programmes, findings and reports to the closed action. A configurable workflow engine, a versioned document store and a hash-chained ledger run in one system.
Who is it 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. See group audits.
Is it SaaS or multi-tenant?
AbenAudit is not multi-tenant. Each customer gets its own isolated deployment, with its own PostgreSQL database and configuration, and upgrades follow the customer's schedule.
How do users sign in?
Through Microsoft Entra ID. AbenAudit asks only for openid, profile and email; it needs no directory rights. 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.
Can it handle several legal entities?
Yes. 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 records return the same answer as a record that does not exist. See group audits.
Can we change the workflow and approval matrix ourselves?
Yes. The methodology is configuration, not code: lifecycles, approval chains, gates, deadlines, fields and notification wording. Changes are made as proposals and need a second approver before they apply, and every version is kept.
How do we know records were not changed afterwards?
Every transition, approval, document write and refused access is an entry in a hash-chained ledger. 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 and the system names the broken entry. Documents are versioned with SHA-256 content digests.
Does AbenAudit support the IIA Global Internal Audit Standards?
AbenAudit records the evidence the Standards ask for in planning, engagement work, findings, reporting and follow-up. Conformance remains the internal audit function's responsibility, and AbenAudit is not certified by The IIA. See the standard-by-standard mapping.
Does it keep a List of Potential Findings?
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. See LoPF.
Which languages does it support?
Free text is stored and shown as typed, including Hungarian, Slovak and Croatian accented characters, and exports are XLSX and CSV. The interface is in English today. A screen language choice and per-country report and mail templates are planned.
What does it integrate with?
Microsoft Entra ID for sign-in today. Oracle and live SharePoint connections are on the roadmap.
How can we evaluate it?
In four steps: a demo on a laptop, without touching your systems; your approval matrix configured as a live workflow; a sandbox on your Entra tenant; and a pilot on an anonymised sample, running one engagement in parallel. Request a demo.
Feature status per the AbenAudit user manual, verified November 2026.
AbenAudit
See it
running.
A demo on a laptop, without touching your systems. Demo deployment, fictional companies, synthetic data.