AIS Midterm Notes
AIS Midterm Notes
customers
System An Information System Framework
Management Reporting System ➢ Are facts which may or may not be processed
and have no direct effect on user.
➢ Provides the internal financial information
needed to manage a business. Information
Two General Groups of End Users ➢ Causes the user to take an action that he or
she could not or would not have taken.
1. External ➢ Defined simply as processed data.
➢ Includes creditors, stockholders, potential ➢ Determined by the effect it has on users not
investors, regulatory agencies, tax by its physical form.
authorities, suppliers, customers.
2. Internal Data Collection
➢ Includes managements, operations
personnel. ➢ First operational stage in the information
system
➢ Objective : To ensure that event data
entering the system are valid, complete and
free from material errors.
➢ Most important stage in the system.
INTRODUCTION TO TRANSACTION
PROCESSING
Transaction Cycles
Files ➢ Three transaction cycles process most
➢ A complete set of record of an identical of the firm's economic activity:
class. (1) incurs expenditures in
exchange for resources
Data Base Management Tasks (expenditure cycle),
(2) provides value added through authorizes the payment, disburses the funds
its products or services to the vendor, and records the transaction by
(conversion cycle), and reducing the cash and accounts payable
(3) receives revenue from outside accounts.
sources (revenue cycle).
Payroll system
Relationship Between Transaction Cycles ➢ collects labor usage data for each employee,
computes the payroll, and disburses
paychecks to the employees.
➢ Conceptually, payroll is a special case
purchases and cash disbursements system
➢ Because of accounting complexities
associated with payroll, most firms have a
separate system for payroll processing
REGISTER
SUBSIDIARY LEDGERS
AUDIT TRAIL
2. TRANSACTION FILE
3. REFERENCE FILE.
4. ARCHIVE FILE
➢ Some transactions may prove to be in error ➢ The old saying that a picture is worth a
or invalid for such reasons as incorrect thousand words is very applicable when it
account numbers, insufficient quantities on comes to documenting systems.
hand, or customer credit problems. In this
example, the system determines the available ➢ A written description of a system can be
credit for each customer from the credit file wordy and difficult to follow. Experience has
before processing the sale. shown that a visual image can convey vital
system information more effectively and
➢ Any records that are rejected for credit efficiently than words.
problems are transferred to the error file. The
remaining good records are used to update ➢ Accountants use system documentation
the master files. routinely, as both systems designers and
auditors, The ability to document systems in
➢ Only these transactions are added to the graphic form is thus an important skill for
archive file that serves as the sales journal. accountants to master.
By copying the valid transactions to the
journal, the original transaction file is not ➢ Five basic docu mentation techniques are
needed for audit trail purposes. introduced in this section: data flow
diagrams, entity relationship diagrams, sys
➢ This file can now be erased (scratched) in tem flowcharts, program flowcharts, and
preparation for the next batch of sales orders. record layout diagrams.
➢ Figure 2-12 presents the symbol set most ➢ Systems analysts use DFDs extensively to
commonly used. DFDs are used to represent represent the logical elements of the system.
systems at different levels of detail from very
general to highly detailed. ➢ This technique does not, however, depict the
physical system. In other words, DFDs show
➢ In Chapter 14, we will study the construction what logical tasks are being done, but not
of multilevel DFDs. At this point, a single- how they are done or who (or what) is
level DFD is sufficient to demonstrate its use performing them.
as a documentation tool. We see an example
of this in Figure 2-13. Entity Relationship Diagrams
➢ Entities in a DFD are external objects at the ➢ An entity relationship (ER) diagram is a
boundary of the system being modeled. They documentation technique used to represent
represent sources of and destinations for data. the relationship between entities.
Entities may be other interacting systems or
functions, or they may be external to the ➢ Entities are physical resources (automobiles,
organization. cash, or inventory), events (ordering
inventory, receiving cash, shipping goods),
➢ Entities should always be labeled as nouns on and agents (salesperson, customer, or vendor)
a DFD, such as customer or supplier. Data about which the organization wishes to
stores represent the accounting records used capture data.
in each process, and labeled arrows represent
the data flows between processes, data stores, ➢ One common use for ER diagrams is to
and entities. model an organization's database,
➢ The degree of the relationship, called ➢ A DFD is a model of system processes, and
cardinality, is the numeric mapping between the ER diagram models the data used in or
entity instances. affected by.
➢ The flowcharting examples in the following 6. The shipping department receives Copy 2 and the
sections illustrate techniques for representing goods from the warehouse, attaches Copy 2 as a
both manual and computer-based accounting packing slip, and ships the goods to the customer.
processes. Finally, the clerk files Copies 3 and 4 in the shipping
department.
➢ We begin by documenting manual
procedures. We will add computer elements ➢ Based on these facts, the auditor can create a
to the system later. flowchart of this partial system.
4. When the sales clerk receives credit approval, he ➢ Remember that a flowchart reflects the
or she files Copy I and the customer order in the physical system, which is represented as
department. The clerk sends Copy 2 to the warehouse vertical columns of events and actions
and Copies 3 and 4 to the shipping department. separated by lines of demarcation.
5. The warehouse clerk picks the products from the ➢ Generally, each of these areas of activity is a
shelves, records the transfer in the hard-copy stock separate column with a heading.
➢ From the written system facts, we see that 2. The clerk sends Copy I of the sales order to the
there are four distinct areas of activity: sales credit department for approval. The other three
department, credit department, warehouse, copies and the original customer order are filed
and shipping department. temporarily, pending credit approval
➢ The first step in preparing the flowchart is to 3. The credit department clerk validates the
lay out these areas of activity and label each customer's order against hard-copy credit records
of them. This step is illustrated in Figure 2- kept in the credit department. The clerk signs Copy I
16. to signify approval and returns it to the sales clerk
TRANSCRIBE THE WRITTEN FACTS INTO ➢ Two new symbols are introduced in this
VISUAL FORMAT. figure. First, the upside-down triangle
symbol represents the temporary file
➢ At this point we are ready to start visually mentioned in Fact 2.
representing the system facts.
➢ This is a physical file of paper documents
➢ The symbols used for this purpose will be such as a drawer in a filing cabinet or desk.
selected from the set presented in Figure 2-
17, We begin with the first stated fact: ➢ Such files are typically arranged according to
a specified order. To signify the filing sys tem
1. A clerk in the sales department receives a hard- used, the file symbol will usually contain an
copy customer order by mail and manually prepares "N" for numeric (invoice number), "C" for
four hard copies of a sales order. chronologi cal (date), or "A" for alphabetic
order (customer name). Secondly, the
Figure 2-18 illustrates how this fact could be parallelogram shape represents the credit
represented. The customer is the source of the order, records mentioned in Fact 3.
but is not part of the system. The oval object is
typically used to convey a data source or destination ➢ This symbol is used to depict many types of
that is separate from the system being flowcharted. hand-copy accounting records, such as
The document symbol entering the sales department journals, subsidiary ledgers, general ledgers,
signifies the hard-copy customer order and is labeled and shipping logs.
accordingly.
➢ Having laid these foundations, let's now
➢ The bucket-shaped symbol represents a complete the flowchart by depicting the
manual process. In this case, the clerk in the remaining facts.
sales department prepares four copies of the
sales order. Notice that the clerk's task, not 4. When the sales clerk receives credit approval, he
the clerk, is depicted. or she files Copy I and the customer order in the
department. The clerk sends Copy 2 to the warehouse
➢ The arrows between the objects show the and Copies 3 and 4 to the shipping department.
direction of flow and the sequence of events.
5. The warehouse clerk picks the products from the
➢ By transcribing each fact in this way, we shelves, records the transfer in the hard-copy stock
systematically construct a flowchart. See records, and sends the products and Copy 2 to the
how the second and third facts restated below shipping department.
add to the flowchart in Figure 2-19.
6. The shipping department receives Copy 2 and the
goods from the warehouse, attaches Copy 2 as a
packing slip, and ships the goods to the customer.
Finally, the clerk files Copies 3 and 4 in the ship ping ➢ Typically, a system flowchart shows only the
department. The completed flowchart is presented in flow of documents, not physical assets.
Figure 2-20. Notice the circular symbol labeled "A."
This is an on-page connector used to replace flow ➢ Finally, for visual clarity, system flowcharts
lines that otherwise would cause excessive clutter on show the processing of a single transaction
the page. only.
In this instance, the connector replaces the lines that ➢ You should keep in mind, however, that
signify the movement of Copies 3 and 4 from the transactions usually pass through manual
sales department to the shipping department. procedures in batches (groups).
Lines should be used whenever possible to promote ➢ Before exploring documentation techniques
clarity. Restricted use of connectors, however, can further, we need to examine some important
improve the readability of the flowchart. issues related to batch processing.
Batch Processing
➢ Notice also that the physical products or ➢ The first is that economies are derived by
goods mentioned in Facts 4 and 5 are not making transaction batches large as
shown on the flow chart. possible. The average transaction cost is
thus reduced when the processing fixed
➢ The document (Copy 2) that accompanies cost associated with the batch is allocated
and controls the goods, however, is shown. across a large number of transactions.
➢ The second implication is that finding an 2. A computer program edits the transactions, checks
error in a very large batch may prove the customers' credit by referencing a credit history
difficult. When a batch is small, error file, and produces a transaction file of sales orders.
identification is much easier.
3. The sales order transaction file is then processed
➢ In designing a batch system, the by an update program that posts the transactions to
accountant should seek a bal ance corresponding records in AR and inventory files.
between the economic advantage of large
batches and the troubleshooting 4. Finally, the update program produces three hard
advantage of small batches. copies of the sales order. Copy I is sent to the
warehouse, and Coples 2 and 3 are sent to the
➢ There is no magic number for the size of shipping department.
a batch. This decision is based on a
number of opera tional, business, and 5. On receipt of Copy 1, the warehouse clerk picks
economic factors. the products from the shelves. Using Copy I and the
warehouse personal computer (PC), the clerk records
➢ Among these are the volume of the inventory transfer in the digital stock records that
transactions, the competitiveness of the are kept on the PC. Next, the clerk sends the physical
industry, the normal frequency of errors, inventory and Copy I to the shipping department.
the financial implications of an
undetected error, and the costs of 6. The shipping department receives Copy I and the
processing. goods from the warehouse. The clerk reconciles the
goods with Copies 1, 2, and 3 and attaches Copy I as
➢ Depending on these factors, a system a packing slip. Next, the clerk ships the goods (with
might be designed to process many small Copy I attached) to the customer. Finally, the clerk
batches throughout the day or an entire records the shipment in the hard copy shipping log
day's activity as a single batch. and files Copies 2 and 3 in the shipping department.
6. The program loops back to Step 1, and the ➢ are used to reveal the internal structure of the
process is repeated until the EOF records that constitute a file or database table.
condition is reached.
➢ usually shows the name, data type, and length
of each attribute (or field) in the record.
COMPUTER-BASED ACCOUNTING
SYSTEMS
➢ The amount of lag depends on the frequency ➢ On the other hand, as much as 50 percent of
of batch processing. the total programming costs for real-time
systems are incurred in designing the user
➢ Time lags can range from minutes to weeks. interfaces.
➢ Payroll processing is an example of a typical ➢ Finally, real-time systems require dedicated
batch system. The economic events the processing capacity.
application of employee labor-occur
continuously throughout the pay period. At ➢ Real-time systems must deal with
the end of the period, the paychecks for all transactions as they occur.
employees are prepared together as a batch.
➢ Some types of systems must be available 24
hours a day whether they are being used or
not.
➢ Real-time systems process transactions
individually at the moment the event occurs. ➢ The computer capacity dedicated to such
systems cannot be used for other purposes.
➢ Because records are not grouped into batches,
there are no time lags between occurrence ➢ Thus, implementing a real-time system may
and recording. require either the purchase of a dedicated
computer or an investment in additional
➢ An example of real-time processing is an computer capacity.
airline reservations system, which processes
requests for services from one traveler at a ➢ In contrast, batch systems use computer
time while he or she waits. capacity only when the program is being run.
When the batch job completes processing, the
Resources freed capacity can be reallocated to other
applications.
➢ Generally, batch systems demand fewer
organizational resources (such as
programming costs, computer time, and user
training) than real-time systems.
➢ The primary key for AR is ACCOUNT ➢ Figure 2-29 shows this technique.
NUMBER.
➢ The transaction file is later processed in batch ➢ The answer is to achieve operational
mode to achieve operational efficiency. efficiency.
Key steps in the process are: Each customer sale affects the following six
accounting records:
• The sales department clerk captures customer
sales data pertaining to the item(s) being • Customer account receivable (Subsidiary-
purchased and the customer's account. unique)
• The system then checks the customer's credit • Inventory item (Subsidiary-almost unique)
limit from data in the customer record
(account receivable subsidiary file) and • Inventory control (GL-common)
updates his or her account balance to reflect
the amount of the sale. • Account receivable control (GL-common)
➢ Each user accesses only his or her unique ➢ Real-time systems process the entire
record. transaction as it occurs.
➢ General rule, therefore, master file records ➢ Is well suited to systems that process lower
that are unique to a transaction such as transaction volumes and those that do not
customer accounts and individual inventory share common records.
records can be updated in real time without
causing operational delays. ➢ For example, a sales order processed by the
system in Figure 2-32 can be captured, filled,
➢ Updating the records in the general ledger is and shipped the same day. Such a system has
a different matter. many poten tial benefits, including improved
productivity, reduced inventory, increased
➢ All general ledger accounts previously listed inventory turnover, decreased lags in
need to be updated by every sales transaction. customer billing, and enhanced customer
satisfaction. Because transaction information
is transmit ted electronically, physical source
documents can be eliminated or greatly
REAL-TIME PROCESSING reduced.
➢ Real-time systems process the entire Data Coding Schemes
transaction as it occurs.
➢ Within the context of transaction processing,
➢ A system has many potential benefits, data coding involves creating simple numeric
including improved productivity, reduced or alpha betic codes to represent complex
inventory, increased inventory turnover, economic phenomena that facilitate efficient
decreased lags in customer billing, and data processing.
enhanced customer satisfaction.
➢ To emphasize the importance of data codes,
➢ Because transaction information is we first consider a hypothetical system that
transmitted electronically, physical source does not use them.
documents can be eliminated or greatly
reduced. A SYSTEM WITHOUT CODES
3. Each of these size and material subclasses 1. Sales staff. Properly identifying the items
come in three different threads: fine, sold requires the transcription of large
standard, and coarse. amounts of detail onto source documents.
Apart from the time and effort involved, this
tends to promote clerical errors and incorrect
shipments.