The Revenue Cycle:PC-Based Accounting Systems

By -

PC-Based Accounting Systems

The software market offers hundreds of PC-based accounting systems. In contrast to mainframe and client-server systems that are frequently custom-designed to meet the specific user requirements, PC applications tend to be general-purpose systems that serve a wide range of needs. This strategy allows software vendors to mass-produce low-cost and error-free standard products. Not surprisingly, PC accounting systems are popular with smaller firms, which use them to automate and replace manual sys- tems and thus become more efficient and competitive. PC systems have also made inroads with larger companies that have decentralized operations.

Most PC systems are modular in design. Typical business modules include sales order processing and accounts receivable, purchases and accounts payable, cash receipts, cash disbursements, general ledger and financial reporting, inventory control, and payroll. Their modular design provides users with some degree of flexibility in tailoring systems to their specific needs. Many vendors target their products to the unique needs of specific industries, such as health care, transportation, and food services. By doing so, these firms forgo the advantages of flexibility to achieve a market niche. The modular design technique is illustrated in Figure 4-21.

The central control program provides the user interface to the system. From this control point, the user makes menu selections to invoke application modules as needed. By selecting the sales module, for instance, the user can enter customer orders in real time. At the end of the day, in batch mode, the user can enter cash receipts, purchases, and payroll transactions.

Commercial systems usually have fully integrated modules. This means that data transfers between modules occur automatically. For example, an integrated system will ensure that all transactions captured by the various modules have been balanced and posted to subsidiary and general ledger accounts before the general ledger module produces the financial reports.

image

Segregation of Duties

PC systems tend to have inadequate segregation of duties. A single employee may be responsible for entering all transaction data, including sales orders, cash receipts, invoices, and disbursements. In a manual system, this degree of authority would be similar to assigning accounts receivable, accounts payable, cash receipts, and cash disbursements responsibilities to the same person. The exposure is compounded when the individual is also responsible for programming or tailoring the application he or she runs.

Often little can be done in small companies to avoid such conflicts of duties. Controlling the PC environment requires a high degree of supervision, adequate management reports (such as detailed listings of all transactions), and frequent independent verification. For example, the supervisor should reconcile daily transaction details with the affected subsidiary and control accounts.

Access Control

PC systems generally provide inadequate control over access to data files. Although some applications achieve modest security through password control to files, accessing data files directly via the operating system can often circumvent this control. Solutions for dealing with the problem include data encryption, disk locks, and physical security devices.

Accounting Records

Data losses that threaten accounting records and audit trails plague the PC environment. Computer disk failure is the primary cause of data loss. When this happens, recovery of data stored on the disk may be impossible. Formal procedures for creating backup copies of data files and programs can reduce this threat considerably. In the mainframe environment, backup is provided automatically. Backup of PC data files relies on a conscious action by the users, who too often fail to appreciate its importance.

Comments

Post a Comment

Popular posts from this blog

The Conversion Cycle:The Traditional Manufacturing Environment

By -
Image
The Traditional Manufacturing Environment The conversion cycle consists of both physical and information activities related to manufacturing products for sale. The context-level data flow diagram (DFD) in Figure 7-1 illustrates the central role of the conversion cycle and its interactions with other business cycles. Production is triggered by customer orders from the revenue cycle and/or by sales forecasts from marketing. These inputs are used to set a production target and prepare a production plan, which drives production activities. Purchase requisitions for the raw materials needed to meet production objectives are sent to the purchases procedures (expenditure cycle), which prepares purchase orders for vendors. Labor used in production is transmitted to the payroll system (expenditure cycle) for payroll processing. Manufacturing costs associated with intermediate work-in-process and finished goods (FG) are sent to the general ledger (GL) and financial reporting system. Dependin
Read more

The Revenue Cycle:Manual Systems

By -
Image
Manual Systems The purpose of this section is to support the system concepts presented in the previous section with models depicting people, organizational units, and physical documents and files. This section should help you envision the segregation of duties and independent verifications, which are essential to effective internal control regardless of the technology in place. In addition, we highlight inefficiencies intrinsic to manual systems, which gave rise to modern systems using improved technologies. SALES ORDER PROCESSING The system flowchart in Figure 4-12 shows the procedures and the documents typical to a manual sales order system. In manual systems, maintaining physical files of source documents is critical to the audit trail. As we walk through the flowchart, notice that in each department, after completion of the assigned task, one or more documents are filed as evidence that the task was completed. Sales Department The sales process begins with a customer cont
Read more

HIPO (hierarchy plus input-process-output)

By -
Image
HIPO (hierarchy plus input-process-output) 64.1 Purpose The HIPO (Hierarchy plus Input-Process-Output) technique is a tool for planning and/or documenting a computer program. A HIPO model consists of a hierarchy chart that graphically represents the program’s control structure and a set of IPO (Input-Process-Output) charts that describe the inputs to, the outputs from, and the functions (or processes) performed by each module on the hierarchy chart. 64.2 Strengths, weaknesses, and limitations Using the HIPO technique, designers can evaluate and refine a program’s design, and correct flaws prior to implementation. Given the graphic nature of HIPO, users and managers can easily follow a program’s structure. The hierarchy chart serves as a useful planning and visualization document for managing the program development process. The IPO charts define for the programmer each module’s inputs, outputs, and algorithms. In theory, HIPO provides valuable long-term documentation. However
Read more