Expert Guide
A complete walkthrough — Business Process Audit
Reading this guide locally — Across Chepauk, in the government and education sector hub micro-market of Chepauk.
What is a business process audit and how does it differ from internal and operational audit
When does an SME need a process audit
An SME typically commissions a process audit at one of five trigger points: (a) onboarding a new ERP or core system, where the migration is a natural moment to redesign and document processes; (b) preparing for external funding (PE, debt, IPO) where investors expect documented internal controls; (c) after a fraud or material misstatement incident, where the board demands a root-cause and remediation review; (d) ahead of a statutory audit where the auditor has flagged IFC inadequacies in the prior year; (e) on a periodic-improvement basis aligned with ISO 9001:2015 clause 9.2 internal audit and clause 10.2 continual improvement. The OECD Principles of Corporate Governance (2023 revision) treat documented internal-control systems as a board-responsibility item; a process audit is the operational expression of that responsibility at the SME scale.
Comparative framework — process audit, financial audit and forensic audit
Process audit, statutory financial audit and forensic audit differ in objective, evidence standard and reporting outcome. Statutory financial audit under Section 143 Companies Act and the ICAI SA framework opines on the true-and-fair view of financial statements; evidence is gathered to reasonable assurance under SA 200. Forensic audit is investigative, triggered by suspected fraud, with evidence gathered to legal-evidentiary standards under the Indian Evidence Act and is reportable to law enforcement or under SEBI / SFIO frameworks. Process audit sits between the two — it provides reasonable assurance on control design and operating effectiveness, with findings reported to management or the audit committee, and is recurring rather than incident-driven. The OECD International Standards on Auditing convergence work has progressively aligned ICAI SAs with ISA pronouncements, and SA 315 (revised 2021) brings the risk-assessment vocabulary close to the COSO 2013 framework that process audit applies.
Definitional anchor under the IIA Standards and ICAI SIA framework
A business process audit is a structured, evidence-based examination of one or more end-to-end business processes (revenue-to-cash, procure-to-pay, hire-to-retire, record-to-report, plant-and-asset, IT general controls) against a benchmark control framework — most commonly the COSO 2013 Internal Control Integrated Framework (5 components and 17 principles) and SA 315 risk-of-material-misstatement assessment used by statutory auditors. The Institute of Internal Auditors (IIA) International Professional Practices Framework defines internal auditing as an independent, objective assurance and consulting activity designed to add value and improve operations; a process audit is a tactical sub-set focused on individual process families rather than the enterprise-wide annual internal-audit plan. ICAI Standards on Internal Audit (SIA 110 to SIA 740) — mandatory from 1 April 2024 — codify the engagement framework: SIA 310 (planning), SIA 320 (evidence), SIA 330 (documentation), SIA 360 (communication), SIA 390 (monitoring) and SIA 740 (reporting). A process audit follows the same SIA discipline but with a narrower scope and faster cycle than the full annual internal audit.
ICAI Standards on Internal Audit (SIA 110 to SIA 740)
Planning under SIA 310 and risk-based scope
SIA 310 (planning the internal audit) requires the internal auditor to develop an audit plan that addresses the timing, scope and resources required, reflecting a risk-based approach. For a process audit, the planning phase produces three artefacts: (a) the engagement letter under SIA 110 that defines scope, period, deliverables, fee and timeline; (b) the risk-based audit programme that maps process steps to control objectives and to COSO components or ISO clauses; (c) the entity-level understanding document that captures the business, the industry, the regulatory environment and the IT landscape. SA 315 (revised 2021) introduces the risk-of-material-misstatement vocabulary that SIA 310 has aligned to; both standards now emphasise inherent-risk-factor-based assessment rather than the older risk-of-misstatement language.
Evidence under SIA 320 and documentation under SIA 330
SIA 320 (internal-audit evidence) establishes the principle that the internal auditor should obtain sufficient and appropriate evidence to support findings and conclusions. Evidence categories — physical inspection, observation, inquiry and confirmation, recalculation and reperformance, analytical procedures — broadly mirror SA 500 categories used in statutory audit. SIA 330 (internal-audit documentation) requires that working papers be sufficient to enable an experienced internal auditor with no previous connection to the audit to understand the work performed, the evidence obtained and the conclusions reached. Process-audit working papers typically include: BPMN process maps (as-is and to-be), walkthrough memoranda, segregation-of-duties matrices, control-test logs, exception reports, interview notes, and the management-response register. The SIA 330 standard also addresses retention — typically seven years, aligned to the Companies Act records-retention horizon.
Reporting under SIA 740 and follow-up under SIA 390
SIA 740 (reporting results to the auditee) requires that the internal-audit report communicate findings, recommendations and management responses in a structured manner. The typical report structure: executive summary, scope and methodology, summary of findings by risk-rating (high, medium, low), detailed findings each with observation-cause-effect-recommendation-management-response-target-date, and appendices (process maps, working papers index). SIA 390 (monitoring and reporting of prior-engagement issues) requires the internal auditor to follow up on prior recommendations to verify implementation; this transforms the process audit from a point-in-time deliverable to a continuous-improvement engagement. The audit committee typically reviews the SIA 390 follow-up report quarterly and tracks closure rate as a KPI.
Engagement deliverables, timeline and audit-defence positioning
Standard deliverables in a process audit engagement
A FilingPro business-process-audit engagement at ₹18,000 one-time fee for a single process family delivers: (a) the engagement letter under SIA 110 with scope, methodology, period and timeline; (b) the as-is BPMN 2.0 process map for the audited process family, with swimlane-level role clarity; (c) the COSO 2013 17-principles assessment matrix, identifying which principles are designed-effectively, designed-but-not-operating, or designed-deficient; (d) the segregation-of-duties matrix at process-step level; (e) the findings register with observation-cause-effect-recommendation entries, risk-rated high/medium/low; (f) the to-be BPMN 2.0 process map with the recommended redesign; (g) the management-response register with target-dates; (h) the executive summary for board / audit-committee presentation. The full engagement cycle is typically 4 to 6 weeks for a single process family.
Cycle timeline by phase
Week 1 (planning under SIA 310): kickoff meeting, engagement-letter finalisation, document-request list issuance, entity-level understanding through interviews with key process owners (typically 6-8 hours of process-owner time). Week 2 (process mapping and risk assessment): walkthrough sessions for each major process step, as-is BPMN 2.0 map drafting, preliminary risk-and-control-matrix population. Week 3 (testing under SIA 320): control walkthroughs, sample-based reperformance for key controls, ITGC testing where applicable (access management, change management). Week 4 (analysis and to-be design): finding consolidation, root-cause analysis, to-be process redesign. Weeks 5-6 (reporting and management response under SIA 740): draft report issuance, management response collection, final report finalisation, board / audit-committee presentation. Follow-up under SIA 390 happens at quarterly cadence post-engagement.
Audit-defence positioning of process-audit deliverables
The process-audit deliverables serve a dual purpose — operational improvement (the primary objective) and audit-defence (a derivative benefit). At the statutory-audit stage under SA 315, the SA 315 revised standard requires the statutory auditor to understand the entity's risk-assessment process and control activities. Where a documented process audit exists, the statutory auditor's understanding-the-entity work is materially accelerated, and the IFC opinion under Section 143(3)(i) is supported by contemporaneous third-party documentation. At a GST audit under Section 65 CGST, the process-audit working papers are persuasive evidence that the registered person maintains adequate internal controls, supporting the burden of proof on turnover, ITC and refund assertions. At an income-tax assessment, the process-audit file supports the genuineness-of-transactions assertion under Sections 68 to 69D.
The COSO 2013 framework — five components and seventeen principles
Components 4 and 5 — Information and Communication, Monitoring (Principles 13 to 17)
Information and Communication — Principle 13 (uses relevant information), Principle 14 (communicates internally), Principle 15 (communicates externally) — addresses the information-system layer that underpins all controls. Monitoring — Principle 16 (conducts ongoing and separate evaluations), Principle 17 (evaluates and communicates deficiencies) — addresses the feedback loop. Process audit tests Component 4 through dashboard-design review (Are management dashboards capturing the right KPIs? Are exception reports timely?), and tests Component 5 through internal-audit charter review, deficiency-tracking-register inspection, and the Section 143(3)(i) statutory auditor's IFC opinion read-back. The Section 143(12) materiality threshold for fraud reporting and the Auditor's Report under SA 700 / 705 / 706 are downstream consequences of weak Component 5 monitoring.
From COSO 1992 to COSO 2013 — evolution of the framework
The Committee of Sponsoring Organizations of the Treadway Commission (COSO) was formed in 1985 in the United States and issued the original Internal Control Integrated Framework in 1992, identifying five components: Control Environment, Risk Assessment, Control Activities, Information and Communication, and Monitoring. The 2013 update preserved the five components but explicitly codified 17 underlying principles to provide a more testable, evidence-anchored framework. The 2013 update was a direct response to the post-SOX 2002 (USA) implementation experience, which had revealed that companies needed greater specificity to assess whether internal control over financial reporting was effective. The Indian framework — IFC under Section 143(3)(i) Companies Act 2013 — was designed in 2014 with explicit reference to COSO 2013, and the ICAI Guidance Note on Audit of Internal Financial Controls over Financial Reporting (2015) maps each of the 17 COSO principles to the Indian context.
Component 1 — Control Environment (Principles 1 to 5)
The Control Environment component is the foundation — Principle 1 (commitment to integrity and ethical values), Principle 2 (board oversight independence), Principle 3 (management establishes structures, reporting lines and authorities), Principle 4 (commitment to attract, develop and retain competent individuals), and Principle 5 (holds individuals accountable for internal control responsibilities). In a process audit, the Control Environment is typically tested through a tone-at-the-top survey, board / audit-committee minutes review, code-of-conduct dissemination evidence, and HR competency framework. The Indian IFC framework picks up these principles via Schedule IV (Code for Independent Directors) and the SEBI Listing Obligations and Disclosure Requirements Regulations 2015 for listed entities; non-listed SMEs typically have an attenuated control environment, and the process audit's recommendations focus on closing this gap.
What Chepauk clients usually ask next: On the ground in Chepauk, for Chepauk businesses balancing growth ambitions with tight statutory compliance.