Accounting Information Systems (AIS) Overview
Accounting Information Systems (AIS) Overview
Labor
Customers
Materials
Finished Goods
Cash
Cash
Physical
Plant
Finished
Goods
Cash
The Expenditure Cycle
- Business activities begin with the acquisition of materials, property, and labor in
exchange for cash.
physical component – the acquisition of the goods
financial component – the cash disbursement to the supplier
Customer’s
Source Document 1
Order
Data 2
Sales Order
Collection 3
Sales System
Product documents – are result of transaction processing rather than
the triggering mechanism for the process.
Illustration 2-3: A PRODUCT DOCUMENT
Source Document 1
r ’s Data 2
sto me
Cu r Collection Sales Order
e 3
Ord
Customer
Bill
-----------------------
Sales System
-
Remittance
Advice
Product
Document
Turnaround documents – are product documents of one system that
become source documents for another system.
Illustration 2-4: A TURNAROUND DOCUMENT
Source Document 1
r ’s Data 2
sto me
Cu r Collection Sales Order
e 3
Ord
Customer
Bill
-----------------------
Sales System
-
Remittance
Advice
Product
Document
1
Check 2
Cash Receipts System
Remittance
Advice
SPECIAL JOURNALS – are used to record specific classes of transactions
that occur in high volume.
Illustration 2-5: SALES ORDER RECORDED IN SALES JOURNAL
Sales Order
Customer’s Sales Journal
Order
LEDGER – is a book of accounts that reflects the financial effects of the firm’s transactions
after they are posted from the various journals.
1. General Ledger – contains the firm’s account information in the form of highly
summarized control accounts.
2. Subsidiary Ledger – contains the details of the individual accounts that constitute a
particular control account.
Illustration 2-6: SALES JOURNAL
Illustration 2-7: GENERAL JOURNAL
GENERAL LEDGER – summarizes the activity for each of the
organization’s accounts.
Illustration 2:8: FLOW OF INFORMATION FROM THE ECONOMIC EVENT TO THE GENERAL LEDGER
Post er
l Ledg
era
Gen
r to
dge
r y Le
s idia
le Sub
n ci
Accounts eco
l y R
Receivable ical
iod
Subsidiary Per
Ledger
Illustration 2-8: GENERAL LEDGER
GENERAL LEDGER – summarizes the activity for each of the
organization’s accounts.
Illustration 2:8: FLOW OF INFORMATION FROM THE ECONOMIC EVENT TO THE GENERAL LEDGER
Post er
l Ledg
era
Gen
r to
dge
r y Le
s idia
le Sub
n ci
Accounts eco
l y R
Receivable ical
iod
Subsidiary Per
Ledger
The Audit Trail
Illustration 2-9: RELATIONSHIP BETWEEN THE SUBSIDIARY LEDGER AND THE GENERAL LEDGER
COMPUTER-BASED SYSTEMS
Types of File
Master File - generally contains account data (ex. general ledger and
subsidiary ledger)
Transaction File – is a temporary file of transaction records used to
change or update data in a master file
Reference File – stores data that are used as standards for processing
transactions
Archive File - contains records of past transactions that are retained
for future reference
The Digital Audit Trail
Illustration 2-10: ACCOUNTING RECORDS IN A COMPUTER-BASED SYSTEM
Documentation Techniques
Data Flow Diagrams (DFD)
- Uses symbols to represent the entities, processes, data flows, and
data stores that pertain to a system.
Illustration 2-11: DATA FLOW DIAGRAM SYMBOL SET
Symbol Description
1 Assigned 1
Company
Salesperson
Car
1 Places M
Customer Sales Order
M Supply M
Vendor Inventory
Illustration 2-13: DATA MODEL
1 Assigned 1
Company
Salesperson
Car
1 Places M
Data Model
- Is the blueprint for what ultimately will become the physical database.
Relationship between ER Diagrams and Data Flow Diagrams
DFDs and ER diagrams are different aspects of the same system, but they are related
and can be reconciled. A DFD model of system processes, and the ER diagram models
the data used in or affected by the system. The two diagrams are related through
data; each data store in the DFD represents a corresponding data entity in the ER
diagram.
SYSTEMS FLOWCHARTS
- Is the graphical representation of the physical relationships among key
elements of a system.
Rules to be observed:
1. The flowchart should be labeled to clearly identify the system that it
represents.
2. The correct symbols should be used to represent the various entities in the
system.
3. All symbols on the flowchart should be labeled.
4. Lines should have arrowheads to clearly show the process flow and sequence
of events.
5. If complex processes need additional explanation for clarity, a text description
should be included on the flowchart or in an attached document referenced
by the flowchart.
Illustration 2-14: SYMBOL SET FOR REPRESENTING MANUAL PROCEDURES
On-page connector
Manual operation
Off-page connector
Computer process
(program run) Process flow
Real-time (online)
Direct access storage connection
device (disk pack)
Steps:
1. The program retrieves a single record from the unedited transaction file
and stores it in memory.
2. The first logical test is to see the program has reached the end-of-file
(EOF) condition for the transaction files. Most file structures use a special
record or market to indicate an EOF condition. When EOF is reached, the
edit program will terminate and the next program in the system (in this
case, the update program) will be executed. As long as there is a record in
the unedited transaction file, the result of the EOF test will be “no” and
process control is passed to the next logical step in the edit program.
3. Processing involves a series of test to identify certain clerical
and logical errors. Each test, represented by a decision
symbol, evaluates the presence or absence of a condition. For
example, an edit test could be to detect the presence of
alphabetic data in a field that should contain only numeric
data.
4. Error-free records are sent to the edited transaction file.
5. Records containing errors are sent to the error file.
6. The program loops back to Step 1, and the process is repeated
until the EOF condition is reached.
Illustration 2-18: PROGRAM FLOWCHART SYMBOLS
Input/output operation
(read and write records)
Decision
Flow of logical process
Illustration 2-19: PROGRAM FLOWCHART FOR EDIT PROGRAM
Illustration 2-20: SYSTEM FLOWCHART
Record Layout Diagrams
- are used to reveal the internal structure of the records that
constitute a file or database table.
Illustration 2-21: RECORD LAYOUT DIAGRAM FOR CUSTOMER FILE
Customer File
Key
Backup Backup
Transaction Master Program Master
Update
Program
Recovery
Program
Illustration 2-25: BATCH PROCESSING WITH REAL-TIME DATA COLLECTION
Illustration 2-26: REAL-TIME PROCESSING OF SALES ORDERS
End of LESSON 2