How should auditors scope systems and feeder applications?
Auditors should scope the systems that initiate, process, record or report information relevant to significant classes of transactions, account balances and disclosures. That usually means considering more than the main accounting system.
Feeder applications can include payroll, revenue, inventory, point-of-sale, banking, billing or consolidation systems. The team should understand how information moves between them, where manual intervention occurs, whether interfaces are automated and which controls support the completeness and accuracy of the transfer.
A practical scoping process starts with the financial reporting flows, not a list of software licences. For each relevant process, ask where the data originates, what transforms it, how it reaches the ledger and what reports the audit or management relies on. This often exposes systems that are easy to miss when the client simply names its “finance system”.
AI can help by connecting process evidence, application inventories and client responses, then highlighting incomplete flows or inconsistent answers. The auditor must still confirm completeness and decide which systems and controls are relevant to the audit.
Platformed capability: Platformed connects process evidence with the applications, interfaces, reports and automated controls it describes. It prepares the first-pass system scope and flags gaps for follow-up; the audit team decides what is relevant.
References: ISA 315 (Revised 2019) · PCAOB AS 2110