An accounting information system (AIS) combines people, procedures, data, and technology to collect, process, store, and report transaction information. Accounting information systems encompass the entire accounting process, including manual approvals, supporting documents, application controls, and reports used for decisions.
Its functions follow the transaction information.
- Collection captures source documents, such as customer orders, receiving reports, supplier invoices, employee time records, and bank notices.
- Processing validates data, applies business rules, calculates amounts, updates records, and routes exceptions for resolution.
- Storage preserves master records, transaction histories, supporting documents, and evidence connecting individual transactions with ledger postings.
- Reporting delivers invoices, account balances, exception reports, management information, and financial reports to the appropriate recipients.
Enterprise resource planning (ERP) integrates accounting with operational functions, such as purchasing, production, inventory management, and human resources. An ERP commonly uses shared data and coordinated workflows; its accounting functions form part of the AIS.
A standalone AIS may receive information from separate operational applications through interfaces. ERP integration reduces duplicate entry and inconsistent reference data, but incorrect mappings, unauthorized changes, failed transfers, and timing...
Common mistakes
- Order treated as earned revenue. Order approval establishes permission to proceed; fulfillment evidence and sales terms determine the relevant accounting event.
- Report selected by familiarity. Aged payables addresses recorded obligations; open purchase orders addresses outstanding orders.
- Automation granted combined powers. Invoice-entry credentials should not also permit vendor-bank changes and payment release merely because a bot performs the work.
Bottom line
- An AIS collects, processes, stores, and reports accounting information; ERP integrates accounting with operational functions.
- Shared data reduces duplicate handling without eliminating source-data controls, interface reconciliation, or subsidiary-to-ledger reconciliation.
- Transaction documents distinguish ordering, approval, fulfillment or receipt, billing, and settlement; their sequence determines the control effect.
- COSO applies to blockchain reporting risks through oversight, risk assessment, control activities, communication, and monitoring.
Exam shortcut
Identify the process stage first. Orders point to purchasing or sales; receipts establish delivery evidence; invoices support billing or payables; bank records support collections or disbursements. For a proposed improvement, locate the cause before choosing the tool. Stable repetition suggests automation; fragmented mappings suggest a system change. For a walkthrough discrepancy, compare requirement, documented sequence, and actual timestamps. Separate an outdated document from an unsuitable process or a missed action.
The full lesson (about 7,543 words, 50 min read) adds 2 worked examples, all 6 common mistakes, a self-check, free in the app.
Learning objectives
- I.A2
Browse all free CPA ISC lessons or jump into free CPA ISC practice questions.