Accounting › Section F · Accounting information systems › Topic F.1
Components of an accounting information system
Every invoice, receipt and payslip has to travel from the moment something happens to a line in the financial statements. An accounting information system is the route it takes, and knowing its parts tells you where errors start and where they can be stopped.
What an accounting information system does
Every business has to capture what happened, turn it into accounting records and report the results. An accounting information system (AIS) is the set of people, procedures, records and technology that does this: it collects data about transactions, records and organises them, summarises them, and produces financial statements and other reports for users inside and outside the business. An AIS can be paper ledgers, software, or a mix of both. Moving from pen and paper to a computer changes how the work is done, not what is done: the same debits, credits, journals and ledgers from earlier sections still sit underneath every screen.
Input, processing, output and storage
An AIS works in three stages, with storage running alongside all of them. Input captures raw data about a transaction, such as the customer, the date, the items and the price. Processing turns that data into accounting records: journalising, posting, and computing totals, taxes and balances. Output presents the result as useful information, such as an invoice, a customer statement, a trial balance or a set of financial statements. Storage keeps data and results so they can be retrieved, checked and reused, for example a customer's address and credit limit. Errors are cheapest to fix at the input stage, before they flow into everything downstream.
Source documents: the evidence for every entry
A source document is the original record showing that a transaction happened and what its terms were. Common ones are sales invoices, supplier bills, till receipts, cheques, bank statements, time cards and purchase orders. One document can play two roles: a form a customer completes to order goods is a purchase order to the customer and a sales order to the seller. An order on its own is not a transaction to journalise, because nothing has been delivered or earned yet; supplying the goods is, and the invoice issued then is its evidence. Prenumbered documents help control the records, because a missing number in the sequence reveals a missing record.
Input devices and input controls
Data enters an AIS through keyboards, barcode scanners, card readers, online forms and electronic feeds from banks. A point-of-sale (POS) system records a sale at the moment the item is scanned and reduces inventory at the same time. Because a computer processes whatever it is given, accountants repeat the old warning "garbage in, garbage out". Input controls catch bad data before it is stored: required fields, format checks (a basic US ZIP code has five digits), range checks (no 300-hour week on a time card), drop-down lists of valid customers, and matching a supplier's bill to an existing order. These are preventive controls: they stop an error instead of finding it later.
Processing: from data to records
Processing is where the accounting happens. The system classifies each transaction, prepares the journal entry, posts it to the general ledger and to the right customer or supplier record, and computes related amounts: sales tax on an invoice, an employee's gross pay from hours worked times the hourly rate, the new inventory balance after a sale. Some systems use batch processing, collecting similar transactions, such as a week's time cards, and processing them together. Others use real-time processing, updating the records as each transaction occurs, as a POS system or an online shop does. Batches suit routine volumes; real-time processing keeps balances current.
Output and storage
Output is information arranged for a decision-maker. Managers use internal reports such as sales by product, an ageing of customer balances or a list of bills due next week. External users such as lenders, investors and tax authorities receive financial statements and tax returns, and US public companies must file audited statements with the Securities and Exchange Commission (SEC). Storage today usually means a database, on the company's own servers or in the cloud. Cloud computing lets staff work from any internet-connected device and leaves software updates to the provider, for a monthly fee. The trade-offs are security risk, since an outside firm holds the data, and dependence on that provider staying online.
Worked example: tracing one credit sale
On 3 March, Brightwater Bike Repair services a cycling club's fleet for $1,850 on credit. Trace the sale through the AIS. 1. Input: the mechanic's job sheet lists parts and labour; the clerk picks the club from the customer list, a preventive control, and the system issues prenumbered invoice 2207. 2. Processing: the system records the entry, debiting Accounts Receivable (Accts Receivable in entries), and adds $1,850 to the club's balance:
3. Storage: the invoice, the entry and the new balance are saved and backed up. 4. Output: the invoice is emailed to the club, and the sale appears in the revenue report, the customer ageing and, at month end, the income statement. Check: debits equal credits, and one input fed several outputs.
Worked example: sorting the parts of a clinic's system
A small dental clinic wants to map its AIS. Classify each item. 1. The receptionist enters the treatment codes for a patient's visit: input. 2. Software looks up each code's fee, totals the charges, splits them between the insurer and the patient, and posts the entry: processing. 3. The patient's account, insurance details and payment history held in the clinic's database: storage. 4. A statement of what the patient owes, and the monthly report of revenue by dentist: output. 5. A rule that rejects a treatment code that does not exist: an input control. Check: items 1 to 4 each fit exactly one stage, because each captures, transforms, keeps or presents data, and item 5 guards the input stage.
From small systems to enterprise systems
Small businesses often run off-the-shelf accounting software. Large organisations group their accounting into subsystems built around business cycles: the revenue cycle (sales, receivables and cash receipts), the expenditure cycle (purchasing, payables and cash payments), payroll, production, and the general ledger and reporting system that pulls them together. An enterprise resource planning (ERP) system integrates these accounting modules with non-accounting functions such as human resources, marketing and the supply chain, so one sale updates revenue, inventory, the warehouse picking list and the reorder plan at once. The more connected the system, the further one input error spreads.
Common mistakes to avoid
First, assuming a computerised system follows different accounting rules: it automates the same double-entry steps. Second, recording a purchase order or sales order as a sale; an order alone creates no receivable and no revenue. Third, mixing up the stages: a bank statement is the bank's output, but for the company it is a source document, an input. Fourth, trusting a report because a computer produced it; if the input was wrong, the output is wrong too. Fifth, forgetting storage: without backups kept off-site or with a second provider, a fire, flood or ransomware attack can wipe out the records.
Key takeaways
An AIS collects, records, summarises and reports accounting data, on paper, by computer or both. It runs in three stages, input, processing and output, with storage throughout. Source documents are the evidence for every entry, and prenumbering exposes gaps. Input controls such as format and range checks stop bad data early. Processing journalises, posts and computes, in batches or in real time. Output serves managers inside the business and lenders, investors and regulators outside it. ERP systems integrate accounting with the rest of the business, and cloud storage trades convenience for security and dependence on a provider.
Flashcards
Flashcard
People, procedures, records and technology that collect, record, summarise and report accounting data
Test your understanding
Question 1 of 5
A customer fills in a form ordering a jacket the shop does not have in stock. Nothing has been paid or delivered. How should the shop's AIS treat the form?
Question 2 of 5
A payroll clerk types 400 hours instead of 40 on a weekly time card, and the system refuses to accept it. What has just worked?
Question 3 of 5
Which pairing of AIS stage and example is correct?
Question 4 of 5
A food truck's POS system records each sale and reduces inventory the moment an item is rung up. This is an example of what?
Question 5 of 5
Which is a genuine disadvantage of keeping a company's accounting data in the cloud?
