Professional Documents
Culture Documents
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 1 of 136
INTRODUCTION
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 2 of 136
INTRODUCTION
(discussed in Chapter 7)
CONFIDENTIALITY
AVAILABILITY
– Confidentiality
PRIVACY
– Privacy
– Processing integrity
– Availability
SECURITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 3 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 4 of 136
PROCESSING INTEGRITY
• Input Controls
– If the data entered into a system is inaccurate or
incomplete, the output will be, too. (Garbage in
garbage out.)
– Companies must establish control procedures to
ensure that all source documents are authorized,
accurate, complete, properly accounted for, and
entered into the system or sent to their intended
destination in a timely manner.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 5 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 6 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 8 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 9 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 10 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 11 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 12 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 13 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 14 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 15 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 17 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 18 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 19 of 136
PROCESSING INTEGRITY
• Records information about data input or processing
errors (when they occurred, cause, when they were
corrected and resubmitted).
• Additional Batch Processing Data Entry
• Errors should be investigated, corrected, and
Controls resubmitted on a timely basis (usually with the next
batch) and subjected to the same input validation
– In addition to the preceding controls, when
routines.
using
• batch
The log processing, the periodically
should be reviewed following todata
ensure
that all errors
entry controls have been
should corrected and then used to
be incorporated.
prepare an error report, summarizing errors by record
• Sequence check
type, error type, cause, and disposition.
• Error log
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 20 of 136
PROCESSING INTEGRITY
• Summarize key values for a batch of input records.
Commonly used batch totals include:
– Financial totals—sums of fields that contain dollar
• Additional Batch Processing Data Entry
values, such as total sales.
Controls– Hash totals—sums of nonfinancial fields, such as
the sum of all social security numbers of
– In addition to the preceding
employees being paid. controls, when
using batch processing,
– Record count—countthe following
of the number ofdata
records in
a batch.
entry controls should be incorporated.
• These batch totals are calculated and recorded when
• Sequence check
data is entered and used later to verify that all input
• Errorwas
log processed correctly.
• Batch totals
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 21 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 22 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 23 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 24 of 136
PROCESSING INTEGRITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 26 of 136
AVAILABILITY
AVAILABILITY including:
– Hardware and software failures
PRIVACY
SECURITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 27 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 28 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 29 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 30 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 31 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 32 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 34 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 35 of 136
AVAILABILITY
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 36 of 136
CHANGE MANAGEMENT CONTROLS
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 37 of 136
SUMMARY