Supplement E T he Changing Nature of Journals and Ledgers.

Slides:



Advertisements
Similar presentations
Chapter 14 Audit of the Sales and Collection Cycle
Advertisements

Controlled Online Accounting General Ledger and Adjustments.
Accounting Principles, Ninth Edition
Chapter 5 - Tuesday.
CHAPTER 7 ACCOUNTING INFORMATION SYSTEMS
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 43 The data processing cycle consists of four steps:
© Jerry L. Turner 2006 Jerry L Turner The University of Memphis An Efficient Approach to Identification and Documentation of Critical Accounting Application.
Week 1b.
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Subsidiary Ledgers Special Journals
Click to edit Master title style 1 Job Order Cost Systems 17.
Criticisms of the Traditional Accounting System Architecture and a Solution Slides 2.
Chapter 11 THE REVENUE CYCLE. Introduction Revenue cycle: 1. Respond to customer inquiries 2. Develop agreements with customers to provide goods and services.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 85 C HAPTER 1 Accounting Information Systems: An Overview.
Principles of Information Systems, Seventh Edition2 An organization’s TPS must support the routine, day-to- day activities that occur in the normal course.
Collecting and Reporting Accounting Information Design of an effective AIS begins by considering outputs from the system. Outputs of an AIS include: 1.
The Islamic University of Gaza
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Chapter Lead Black Slide © 2001 Business & Information Systems 2/e.
COPYRIGHT © 2007 Thomson South-Western, a part of The Thomson Corporation. Thomson, the Star logo, and South-Western are trademarks used herein under license.
Accounting Information Systems, 1st Edition
1 Auditing Revenue. 2 Auditing Implication Designing of the audit plan and perform the audit Evaluating the results of our audit procedures Understanding.
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA.
Computerized Accounting Information Systems OVERVIEW
Financial and Managerial Accounting
CHAPTER 6 ELECTRONIC DATA PROCESSING SYSTEMS
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 10 Business Operations.
Introduction Business Process Fundamentals
Principles of Information Systems, Sixth Edition Transaction Processing & Enterprise Resource Planning Systems Chapter 9.
Accounting Principles, Ninth Edition
2-1 ©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart Overview of Business Processes Chapter 2.
The Traditional Accounting Information System Architecture
Accounting Principles, Ninth Edition
Copyright © 2007 Pearson Education Canada 1 Chapter 13: Audit of the Sales and Collection Cycle: Tests of Controls.
THE SALES/COLLECTION BUSINESS PROCESS
1 Unit 1 Information for management. 2 Introduction Decision-making is the primary role of the management function. The manager’s decision will depend.
1 California State University, Fullerton Chapter 10 Business Operations.
Copyright © 2007 Pearson Education Canada 1 Chapter 14: Completing the Tests in the Sales and Collection Cycle: Accounts Receivable.
Systems Analysis and Design of a Business Event-Driven System
CHAPTER NINETEEN THE ACCOUNTS RECEIVABLE LEDGER.
Auditing the Revenue Cycle. Learning Objectives After studying this chapter, you should: Understand the operational tasks associated with the revenue.
CHAPTER 2 TYPES OF BUSINESS INFORMATION SYSTEM. INTRODUCTION Information System support business operations by processing data related to business operation.
13-1 Sequential File Processing Chapter Chapter Contents Overview of Sequential File Processing Sequential File Updating - Creating a New Master.
© 2016 Pearson Education, Inc. Appendix C Accounting Information Systems.
13- 1 Chapter 13.  Overview of Sequential File Processing  Sequential File Updating - Creating a New Master File  Validity Checking in Update Procedures.
Click to edit Master title style 1 Lesson Click to edit Master title style 2 Job Order Cost Systems 19.
Appendix E Financial Accounting John J. Wild – Fifth Edition Reporting and Preparing Special Journals McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill.
FINANCIAL MANAGEMENT GUIDE © Marin Management, Inc. 1 A. The Purpose of This Policy The purpose of this policy is to provide those who perform the Company's.
Completing the Tests in the Sales and Collection Cycle:
Chapter 10 Auditing the Revenue Process McGraw-Hill/IrwinCopyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
CHAPTER 11 SALES AND COLLECTION CYCLE: TESTS OF CONTROL AND SUBSTANTIVE TESTS OF TRANSACTIONS.
Audit of the Sales and Collection Cycle. Identify the accounts and the classes of transactions in the sales and collection cycle. Describe the business.
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA
The REA Approach to Business Process Modeling
General Ledger, Financial Reporting and Management Reporting Systems
Problem 9-3, Page 473 Key Control, Control Test Evaluation
Accounting Principles, Ninth Edition
Introduction to Transaction Processing
The Combined Journal Chapter 11.
Using Special Journals & Subsidiary Ledgers
Overview of Transaction Processing and Enterprise Resource Planning Systems Chapter 2.
Accounting Principles, Ninth Edition
ACCOUNTING INFORMATION SYSTEMS Accounting Principles, Eighth Edition
Introduction to FIS 318/618: Financial Systems & Databases
Chapter 22, Part
CHAPTER 6 ELECTRONIC DATA PROCESSING SYSTEMS
Accounting Information Systems and Business Processes - Part I
Accounting Principles, Ninth Edition
Presentation transcript:

Supplement E T he Changing Nature of Journals and Ledgers

Where are my Debits and Credits To assess whether an alternative system architecture is viable to meet the needs of information customers, it is important to focus not on whether the alternative emulates the traditional mode of processing and data storage, but whether it is able to accomplish the desired objective of the traditional architecture and much more. Accounting wants to report several things: customer owe more money; sales revenue has increased; expenses associated with generating revenue have increased and the organization has less inventory. The events-driven architecture provides an alternative for achieving more efficiency and less data duplication rather than automating traditional manual processes. Separate general ledger system, similar to the statement information is reported. GAAP does not specify the methods for data collection, storage or processing.

EXHIBIT E-1 Event-driven architectures defined by actual business An Event-driven system will document comprehensive, Multidimensional data describing each event and control both business and information risk throughout the Business process. traditional AIS tends to control and collect data at the point of revenue recognition and the collection of payment. The limited data collected in journals are then reprocessed and duplicated in subsidiary and general ledgers. Details data about the business events are outside the accounting system. Event 1: Marketing Sales call Event 2: Take customer order Event 3: Marketing Sales call Event 4: Ship the Goods Event 5: Collect Payment

How Data Can Be Stored and Derived in an Events Architecture In the events-driven architecture, control and information processing is accomplished by creating a logical view of the physical data, which usually corresponds to accessing the event and corresponding resource, agent, and location data-so once again the REAL acronym guides the logic of the process.

Where are My Journals and Ledgers Journals and ledgers events architecture? became logical output views rather than physical files. Subsidiary ledger and general ledger account balances are also summaries of event data. Report summarizing the account receivable subsidiary ledger is required, formatting the output to list the same information by customer is easily accomplished. Income statement figures measure activity over a period of time, you would total the sales data recorded in the sales Event tables between a specified beginning and ending date. The events architecture maintains detail data for relevant organization activities and the outputs and other reports are generated from the detail data.

Other Differences In The Events Architecture Implications of changing to an alternative architecture such as an event-driven design. A primary benefit of an events-driven architecture is the simplicity of data storage and processing.

Open file Opehis tory n file Tran saction file Update files Edit and Store data Input data Event source data May print Multiple Source document Open file Summary data May print Multiple Subsid iary ledger General ledger Excepti on reporti ng Documents, file etc May print Multiple Event source data Input data Control events Edit and Record data General reports as needed Use stored data to generate reports source document, or ad hoc queries Subsid iary ledger Exception reporting Access resource, Agent and locations tables needed to control and edit Record events Data in appropriate Event tables EXHIBIT E-2 The processing Steps to Produce the View

An events-driven architecture requires only one process: Step one in both environments is similar. The critical difference between the two environments is the elimination of the intermediate processing steps of the traditional architecture. Step two replaced by reporting information processes in the events architecture. The two architectures also create different versions of the audit trail. Audit trail in an environment. Because the related events, resources agents and locations are incorporated into the REAL model, the auditor can click on any sale, and the system can use the data table links to retrieve the corresponding shipment and/or order information for each selected sale. The events system allows additional flexibility not possible in a traditional architecture.

An events-driven system also provides the flexibility to compare cash basis versus accrual-basis accounting using the same data. This architecture enables accountants to change their focus from clerical tasks to more value added, real time control and decision support. The events structure provides increased opportunities for accountants to perform analyses that support decision that impact the bottom line.