Expert Guide
A complete walkthrough — Business Process Audit
Reading this guide locally — In St Thomas Mount, on the Guindy-Alandur corridor that passes through St Thomas Mount.
What is a business process audit and how does it differ from internal and operational audit
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.
Process audit versus operational audit versus internal audit
Operational audit is the broader genus — an examination of operational efficiency and effectiveness across functions, often without a structured benchmark framework. Internal audit (in the IIA and ICAI sense) is a continuous independent assurance function reporting to the audit committee, covering financial, operational and compliance dimensions over a multi-year plan. Process audit is a hybrid: it borrows the structured-framework discipline of internal audit and the operational-efficiency orientation of operational audit, but focuses on one or two process families in a single engagement. The Companies Act 2013 Section 138 mandates internal audit for prescribed companies (those crossing turnover and borrowings thresholds under Rule 13 of the Companies (Accounts) Rules 2014), and Section 143(3)(i) requires the statutory auditor to report on the adequacy of Internal Financial Controls over Financial Reporting (IFC-FR) — a process-audit lens is the natural sub-tool used by both internal and statutory auditors to discharge these mandates.
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.
ICAI Standards on Internal Audit (SIA 110 to SIA 740)
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.
Structure and effective date
The ICAI Standards on Internal Audit (SIAs) were initially issued as a recommendatory framework; the Council of ICAI in 2018 announced their elevation to mandatory status for internal-audit engagements conducted by Chartered Accountants, with effective dates rolled out through 2024. The current structure groups SIAs into four series: SIA 100 series (general principles), SIA 200 series (planning), SIA 300 series (performing), SIA 400 series (reporting and follow-up), with key standards including SIA 110 (framework governing internal audits), SIA 230 (objectives of internal audit), SIA 310 (planning the internal audit), SIA 320 (internal-audit evidence), SIA 330 (internal-audit documentation), SIA 360 (communication with management), SIA 390 (monitoring and reporting of prior-engagement issues) and SIA 740 (reporting results to the auditee). A process audit conducted by a Chartered Accountant follows the SIA discipline end-to-end.
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.
Engagement deliverables, timeline and audit-defence positioning
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.
Continuous improvement and the multi-cycle engagement model
A single process-family audit at ₹18,000 is the entry point; the typical SME engagement matures into a multi-cycle annual programme covering the five major process families (revenue-to-cash, procure-to-pay, hire-to-retire, record-to-report, IT general controls) on a rolling basis, with quarterly SIA 390 follow-up reviews on prior recommendations. Over a 24-month horizon, the SME develops a documented internal-control library, a tested process-map repository in BPMN 2.0, a measured closure-rate KPI for prior recommendations, and a Section 143(3)(i) IFC defence file. The ISO 9001 clause 9.2 internal audit requirement and the ISO 27001:2022 clause 9.2 internal audit requirement are also satisfied by this rolling programme; the SME is effectively running an Integrated Management System internal-audit programme without explicit certification, and can pursue formal certification later when commercially warranted.
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.
The COSO 2013 framework — five components and seventeen principles
Component 3 — Control Activities (Principles 10 to 12)
Control Activities — Principle 10 (selects and develops control activities), Principle 11 (selects and develops general control activities over technology), Principle 12 (deploys through policies and procedures) — is where process audit findings are most concrete. Control activities are categorised as preventive (e.g. segregation of duties, authorisation matrices) versus detective (e.g. reconciliations, exception reports), and as manual versus automated. The COSO 2013 Principle 11 explicitly carved out technology general controls (access management, change management, computer operations) as a distinct domain, reflecting the post-SOX experience that ITGCs are a foundational layer for application-level controls. ITIL v4 (service value system, change enablement, incident management) and ISO 27001:2022 Annex A controls provide the operational vocabulary at the ITGC layer; process audit cross-references these to COSO Principle 11.
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.
What St Thomas Mount clients usually ask next: For St Thomas Mount engagements specifically — for St Thomas Mount IT-services firms managing export-LUT cycles alongside payroll and TDS.