A337 File Design Computerized and Manual Systems 3/27/08.

Slides:



Advertisements
Similar presentations
Unit 6 Journalizing. The Accounting Cycle Analyze Transactions and Source Documents Journalize Entries in the General Journal Post the General Journal.
Advertisements

General Ledger Application Small Business Information System Barry Floyd.
CHAPTER 7 ACCOUNTING INFORMATION SYSTEMS
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Subsidiary Ledgers Special Journals
 Transaction  It is a business event for example a sale of inventory “Hall 2009”
Principles and Learning Objectives
Fundamentals of Information Systems, Second Edition 1 Electronic Commerce and Transaction Processing Systems.
Recording / Financing Fixed Asset Acquisition Human Resources Purchasing Revenue Traditional files approach: separate systems Expenditure Cycles Reporting.
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Electronic Commerce and Transaction Processing Systems
Principles of Information Systems, Seventh Edition2 An organization’s TPS must support the routine, day-to- day activities that occur in the normal course.
Accounting Information Systems: A Business Process Approach Chapter One: Introduction to Accounting Information Systems.
Recordkeeping & Accounting
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Introduction to SAP R/3.
9 C H A P T E R Transaction Processing and Enterprise Resource Planning Systems.
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
MIS 175 Spring 2002 Chapter 9MIS Transaction Processing Systems Manual or automatic – all businesses systematically process transactions Function:
Chapter Lead Black Slide © 2001 Business & Information Systems 2/e.
Financial Accounting (FI)
McGraw-Hill/Irwin Copyright © 2005 by The McGraw-Hill Companies, Inc. All rights reserved. ENTERPRISE INFORMATION SYSTEMS A PATTERN BASED APPROACH Chapter.
TRANSACTION PROCESSING SYSTEM (TPS)
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Supplier/Vendor Management Challenges iSupplier Portal – Closed loop supplier management 1 How can we address critical issues managing your suppliers iSupplier.
Chapter 2 Overview of Transaction Processing and ERP Systems Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 2-1.
A337 File Design Computerized and Manual Systems 4/4/2012.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 10 Business Operations.
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Enterprise Resource Planning Enterprise Resource Planning Systems is a computer system that integrates application programs in accounting, sales, manufacturing,
Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
A337 File Design Computerized and Manual Systems 11/10/2009.
IT Service Delivery And Support Week Eleven – Auditing Application Control IT Auditing and Cyber Security Spring 2014 Instructor: Liang Yao (MBA MS CIA.
Characteristics of ERP Systems. There are some significant differences between ERP and non-ERP systems. These differences are:  In ERP systems, information.
© 2007 by Prentice Hall 1 Introduction to databases.
Enterprise Resource Planning ERP Systems
Is Your Business Ready For The Ultimate Business ERP Solution.
System Descriptions. What we will do today… Today, we will describe the billing and cash receipts systems of a simple company The points to think about.
Chapter 8 Transaction Processing, Electronic Commerce, and Enterprise Resource Planning Systems.
Auditing the Revenue Cycle. Learning Objectives After studying this chapter, you should: Understand the operational tasks associated with the revenue.
Enterprise Resource Planning
7-1 Computerized Accounting Systems Electronic Presentation by Douglas Cloud Pepperdine University Chapter F7.
© 2016 Pearson Education, Inc. Appendix C Accounting Information Systems.
Fundamentals of Information Systems, Third Edition1 An Overview of Transaction Processing Systems Every organization has transaction processing systems.
Chapter 2 Overview of Transaction Processing and ERP Systems Copyright © 2012 Pearson Education 2-1.
A Global fully incorporated Virtual ecommerce Software Solution.
Copyright © 2016 Curt Hill Enterprise Resource Planning Systems ERPs Rule!
Information Systems in Organizations Running the Business: Enterprise Systems (ERP)
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Enterprise Resource Planning ERP Systems
Information Systems in Organizations 3. 1
TRANSACTION PROCESSING SYSTEM (TPS)
TRANSACTION PROCESSING
Computerized AIS October 20
Accounting Information Systems with ERP Applications
Overview of Transaction Processing and ERP Systems
Part I: Purchases and Cash Disbursements Procedures
Using Special Journals & Subsidiary Ledgers
Computerized and Manual Systems
Accounting courses in Chandigarh CBitss Technologies SCO , Level 3,Near Passport office,Sector 34 A, Chandigarh /
Overview of Business Processes
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Module 3 Expenditure Cycle Using SAP Individual Assignment
Overview of Business Processes
Overview of Transaction Processing and ERP Systems
Overview of Transaction Processing and ERP Systems
Enterprise Resource Planning Systems
Presentation transcript:

A337 File Design Computerized and Manual Systems 3/27/08

Topics for next five weeks: Basic discussion of how accounting information systems have evolved from manual to computerized systems Normalization of data - structure of databases - taking the data as “given” Discussion of Microsoft Access and other DBMS systems REA analysis (REAL) another tool for designing the structure of databases - but not taking the data as given.

Topics How do accounting systems work in a manual world –SUA First extension –Same basic structure, but automating the updating process Second extension –Transaction entry from screen documents –ACCPAC, PeachTree, Great Plains Third extension –Integrated accounting/management/finance/marketing software

Let’s look at the SUA

First Extension Automating data entry –Ledgers should not be modified directly (only through data entry) –There should be a “log” of all data entry –Access to data entry should be controlled Example - project 2b

First Extension This extension essentially just took the manual system and put it on computer There were no REAL changes in the structure. The journal/ledger structure might be affected.

Where would we go next?

Second Extension Focus is still on Accounting, but the transaction data that is captured and stored is expanded.

Traditional Accounting System Journals (where data is recorded) What information is recorded?? etcetera

Traditional Accounting System No information can be in the ledgers that was not recorded in the journals –the ledgers are a direct transcription (posting) of the journals The accounting system ONLY contains transaction information (an exchange has occurred)

Traditional Accounting System Each customer, vendor, or other party that we engage in transactions with will probably have a file that details our interactions Once we engage in a transaction, the data is, of course recorded in a journal. Sometimes, even with traditional systems, we maintain additional information - but typically in a different place and there is no necessary reconciliation of the two sources of information. How and where is the data stored

Traditional Accounting System Who has ownership/access to the data With a traditional system, data entry of accounting information is maintained by the bookkeeper or accountant. Sales data is maintained in the sales department Accounts receivable information is maintained in Accounts receivable perhaps. There are varying degrees of DBMS approaches One transaction cycle might involve interaction with all business cells, while others may not.

Event-driven database approach Many events lead up to what ultimately becomes a transaction –Example - sale Receipt of Purchase Order Preparation of Sales Order Header Accepting credit / approving transaction Shipping the goods Preparation of the invoice –Information is added at each event. If we record events we have a more complete tracing of the transaction How are databases different from traditional storage for accounting information?

Event-driven system –Typically all of the document information is included in the database (otherwise why would you have it on the document?) Who, What, When, Where from a document is recorded –Example from the SUA How are databases different from traditional storage for accounting information?

Where Who What When How are databases different from traditional storage for accounting information?

Third Extension Enterprise - Resource - Planning (ERP) systems Sold/provided by large software vendors

ERPs Enterprise Resource Planning software What it is: –Integrative Software Tool that incorporates: Production Accounting Marketing Human Resources Financial Management –Modules Programs on top of a database structure Frequently Oracle databases are used

Providers SAP –they were the leader Oracle –since they were the database leader they already had the infrastructure JDEdwards PeopleSoft –started as a Human Resource Mgt company and then expanded from there. OTHERS...

Approaches In house –Large data requirements and personnel commitment –Better control over features –Faster application Web driven –Lower cost –Security issues?

Advantages of ERPs Coordination and business process improvement –If everyone else in your industry has better business processes than your company, what does that mean to you?….. Better information –You are more aware of how efficiently you are operating.

Disadvantages of ERPs Cost –ERPs (especially In House) are quite expensive to implement. There is also a LONG startup period (two to three years) People –Many people may not buy into it - and it doesn’t work unless everyone (or most everyone) does. –Personnel to run the system are expensive and hard to keep for In House systems It can overwhelm your business

What does it mean to auditors Should be viewed as both an opportunity and a threat to assurance services –Opportunity - consulting and implementation services can provide additional revenues –Threat - data security is a big question mark for ERPs Auditors cannot afford to be behind the technological curve here