A controller asks why the AR aging report and the GL receivables balance differ by $140,000 at month-end. The AR clerk insists every invoice was posted; the GL accountant insists every batch closed. Both are right inside their own module. The difference is the integration touchpoint, and that is the entire reason ERP and accounting information systems exist.
HIGH-FREQUENCY: An enterprise resource planning (ERP) system is an integrated software platform that supports core business processes (accounting, supply chain, manufacturing, HR, procurement, sales) on a shared database. The defining feature is integration: a sales order entered in the order management module automatically updates inventory, posts a journal entry to the GL, opens a customer receivable, and triggers a fulfillment task. No re-keying, no reconciling between modules.
The benefits the exam tests:
- Single source of truth. One customer master, one vendor master, one chart of accounts. Reports tie because the underlying data is shared.
- Process integration. Cross-functional workflows (order-to-cash, procure-to-pay) execute without manual handoffs.
Common mistakes
- Treating ERP and AIS as synonyms. An AIS is a function set: collect, process, store, report financial transactions. An ERP is an integrated platform that includes an AIS plus operational modules. Every ERP contains an AIS; not every AIS is an ERP. The exam will offer answer choices that conflate the two.
- Listing modules without knowing what each one owns. "AR handles inventory" or "Treasury runs payroll" are wrong. Each module has a defined scope. The exam tests scope by giving a transaction and asking which module is responsible; wrong-module answers are designed to look plausible.
- Confusing master data with transactional data. The customer master is a reference record; the customer's invoices are transactional. Changing a customer's terms (master) is a controlled change; entering today's invoices (transactional) is high-volume operational activity. Controls differ accordingly: segregation of duties around master data changes is a frequent exam topic.
Bottom line
- An accounting information system (AIS) collects, processes, stores, and reports transactions and supports double-entry bookkeeping
- An ERP is a single integrated platform that runs an AIS plus operations (inventory, HR, procurement, sales) on one database, the single source of truth; every ERP contains an AIS but not every AIS is an ERP
- ERP modules map to transaction cycles: revenue, expenditure, production, payroll/HR, financing, investing
- Master data (customers, vendors, items, COA) is permanent reference data; transactional data (invoices, POs, journal entries) is high-volume activity that flows against it
Exam shortcut
When a question describes a transaction and asks "which module," map the noun to the module: invoice from a vendor → AP; invoice to a customer → AR; PO → Procurement; depreciation → Fixed Assets; pay run → Payroll; bank reconciliation → Treasury. When a question asks about an implementation risk, the most-tested answer is heavy customization. It surfaces as cost overruns, missed go-live dates, or upgrade-blocking technical debt.
The full lesson (about 6,186 words, 41 min read) adds 9 worked examples, all 5 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.