Accounting information system

Traditionally, accounting is purely based on a manual approach. The experience and skillfulness of an individual accountant are critical in accounting processes. Even using the manual approach can be ineffective and inefficient. Accounting information systems resolve many of the above issues. AISs can support the automation of processing a large amounts of data and produce timely and accurate information.

Early accounting information systems were designed for payroll functions in 1970s. Initially, accounting information systems were developed "in-house" as no packaged solutions were available. Such solutions were expensive to develop and difficult to maintain. Therefore, many accounting practitioners preferred the manual approach rather than computer-based. Today, accounting information systems are more commonly sold as prebuilt software packages from large vendors such as Microsoft, Sage Group, SAP and Oracle where it is configured and customized to match the organization's business processes. Small businesses often use accounting lower costs software packages such as Tally.ERP 9, MYOB and Quickbooks. Large organisations would often choose ERP systems. As the need for connectivity and consolidation between other business systems increased, accounting information systems were merged with larger, more centralized systems enterprise resource planning (ERP). Before, with separate applications to manage different business functions, organizations had to develop complex interfaces for the systems to communicate with each other. In ERP, a system such as an accounting information system is built as a module integrated into a suite of applications that can include manufacturing, supply chain, human resources. These modules are integrated together and are able to access the same data and execute complex business processes. Today, Cloud-based accounting information systems are increasingly popular for both SMEs and large organisations for lower costs. With adoption of accounting information systems, many businesses have removed low skills, transactional, and operational accounting roles.

An AIS typically follows a multitier architecture separating the presentation to the user, application processing and data management in distinct layers. The presentation layer manages how the information is displayed to and viewed by functional users of the system (through mobile devices, web browsers or client application). The entire system is backed by a centralized database that stores all of the data. This can include transactional data generated from the core business processes (purchasing, inventory, accounting) or static, master data that is referenced when processing data (employee and customer account records and configuration settings). As transactions occur, the data is collected from the business events and stored into the system's database where it can be retrieved and processed into information that is useful for making decisions. The application layer retrieves the raw data held in the log database layer, processes it based on the configured business logic and passes it onto the presentation layer to display to the users. For example, consider the accounts payable department when processing an invoice. With an accounting information system, an accounts payable clerk enters the invoice, provided by a vendor, into the system where it is then stored in the database. When goods from the vendor are received, a receipt is created and also entered into the AIS. Before the accounts payable department pays the vendor, the system's application processing tier performs a three-way matching where it automatically matches the amounts on the invoice against the amounts on the receipt and the initial purchase order. Once the match is complete, an email is sent to an accounts payable manager for approval. From here a voucher can be created and the vendor can ultimately be paid.

A big advantage of computer-based accounting information systems is that they automate and streamline reporting, develop advanced modelling and support data mining.[1] Reporting is major tool for organizations to accurately see summarized, timely information used for decision-making and financial reporting. The accounting information system pulls data from the centralized database, processes and transforms it and ultimately generates a summary of that data as information that can now be easily consumed and analyzed by business analysts, managers or other decision makers. These systems must ensure that the reports are timely so that decision-makers are not acting on old, irrelevant information and, rather, able to act quickly and effectively based on report results. Consolidation is one of the hallmarks of reporting as people do not have to look through an enormous number of transactions. For instance, at the end of the month, a financial accountant consolidates all the paid vouchers by running a report on the system. The system's application layer provides a report with the total amount paid to its vendors for that particular month. With large corporations that generate large volumes of transactional data, running reports with even an AIS can take days or even weeks.

After the wave of corporate scandals from large companies such as Tyco International, Enron and WorldCom, major emphasis was put on enforcing public companies to implement strong internal controls into their transaction-based systems. This was made into law with the passage of the Sarbanes–Oxley Act of 2002 which stipulated that companies must generate an internal control report stating who is responsible for an organization's internal control structure and outlines the overall effectiveness of these controls.[2] Since most of these scandals were rooted in the companies' accounting practices, much of the emphasis of Sarbanes Oxley was put on computer-based accounting information systems. Today, AIS vendors tout their governance, risk management, and compliance features to ensure business processes are robust and protected and the organization's assets (including data) are secured.

Many large and SMEs are now adopting cost effective cloud-based accounting information system in recent years. However the majority of existing automated accounting systems use typical databases (DBF, MS SQL, MS ACCESS etc.).[3] In 2020 accounting software used 94% of pollees.[4]

Looking back years ago, most organizations, even larger ones, hire outside consultants, either from the software publisher or consultants who understand the organization and who work to help select and implement the ideal configuration, taking all components into consideration.

The steps to implement an accounting information system are as follows:

Detailed Requirements Analysis

where all individuals involved in the system are interviewed. The current system is thoroughly understood, including problems, and complete documentation of the system—transactions, reports, and questions that need to be answered—are gathered. User needs that are not in the current system are outlined and documented. Users include everyone, from top management to data entry. The requirements analysis not only provides the developer with the specific needs, it also helps users accept the change. Users who have the opportunity to ask questions and provide input are much more confident and receptive of the change, than those who sit back and do not express their concerns.

Systems Design (synthesis)

The analysis is thoroughly reviewed and a new system is created. The system that surrounds the system is often the most important. What data needs to go into the system and how is this going to be handled? What information needs to come out of the system how is it going to be formatted? If we know what needs to come out, we know what we need to put into the system. The program we select will need to appropriately handle the process. The system is built with control files, sample master records, and the ability to perform processes on a test basis. The system is designed to include appropriate internal controls and to provide management with the information needed to make decisions. It is a goal of an accounting information system to provide information that is relevant, meaningful, reliable, useful, and current. To achieve this, the system is designed so that transactions are entered as they occur (either manually or electronically) and information is immediately available online for management.

Once the system is designed, an RFP is created detailing the requirements and fundamental design. Vendors are asked to respond to the proposal, to provide demonstrations of the product, and to specifically respond to the needs of the organization. Ideally, the vendor will input control files, sample master records, and be able to show how transactions are processed that result in the information that management needs to make decisions. An RFP for the information technology infrastructure follows the selection of the software product because the software product generally has specific requirements for infrastructure. Sometimes, the software and the infrastructure is selected from the same vendor. If not, the organization must ensure that vendors will work together without "pointing fingers" when there is an issue with either the software or the infrastructure.

Documentation

As the system is being designed, it is documented. The documentation includes vendor documentation of the system and, more importantly, the procedures or detailed instructions that help users handle each process specific to the organization. Most documentation and procedures are online and it is helpful if organizations can add to the help instructions provided by the software vendor. Documentation and procedures tend to be an afterthought but is the insurance policy and the tool used during testing and training—before launch. The documentation is tested during the training so that when the system is launched, there is no question that it works and that the users are confident with the change.

Testing

Before launch, all processes are tested from input through output, using the documentation as a tool to ensure that all processes are thoroughly documented and that users can easily follow the procedures: They know it works and that the procedures will be followed consistently. The reports are reviewed and verified, so that there's no garbage in-garbage out. This is done in a test system not yet fully populated with live data. Most organizations launch systems before thorough testing, adding to end-user frustration when processes do not work. The documentation and procedures may be modified during this process. All identified transactions must be tested during this step. All reports and online information must be verified and traced through the audit trail so that management is ensured that transactions will be handled consistently and that the information can be relied upon to make decisions.

Training

Before launch, all users need to be trained, with procedures. This means a trainer using the procedures to show each end user how to handle a procedures. The procedures often need to be updated during training as users describe their unique circumstances and the "design" is modified with this additional information. The end user then performs the procedure with the trainer and the documentation. The end user then performs the procedure with the documentation alone. The end user is then on his or her own with the support, either in person or by phone, of the trainer or other support person. This is before data conversion.

Data Conversion

Tools are developed to convert the data from the current system (which was documented in the requirements analysis) to the new system. The data is mapped from one system to the other and data files are created that will work with the tools that are developed. The conversion is thoroughly tested and verified before final conversion. There's a backup so it can be restarted, if necessary.

Launch

The system is implemented only after all of the above is completed. The entire organization is aware of the launch date. Ideally, the current system is retained and often run in "parallel" until the new system is in full operation and working properly. With the current mass-market software used by thousands of companies and fundamentally proven to work, the "parallel" run that is mandatory with software tailor-made to a company is generally not done. This is only true, however, when the above process is followed, the system is thoroughly documented and tested, and users are trained before launch.

Tools

Online resources are available to assist with strategic planning of accounting information systems. Information systems and financial forms aid in determining the specific needs of each organization, as well as assigning responsibility to principles involved.[5]

Support

The end users and managers have ongoing support available at all times. System upgrades follow a similar process and all users are thoroughly apprised of changes, upgraded in an efficient manner, and trained.

Many organizations chose to limit the time and money spent on the analysis, design, documentation, and training, and move right into software selection and implementation. If a detailed requirements analysis is performed with adequate time being spent on the analysis, the implementation and ongoing support will be minimal. Organizations that skip the steps to ensure the system meets their needs are often left with frustrated end users, costly support, and information that is not current or correct. Worse yet, these organizations build the system three times instead of once.

Accounting Information System is characterize by large amount of different approaches and methodologies Over the past 50 years. Due to the restrictions and weaknesses of previous models each new model evolved. Interestingly After the production of newest technique the newer or recent models of evolution does not eliminate or replace the older or previous technique instantly. However Several Generations and peers of systems exists among different institutions, organizations, groups at the same time and possibly exists with in a single or same institution. Similarly The up-to-date inspector needs to be aware with the functioning features of all AIS approaches that he or she is likely to encounter. currently there are four approaches can be identified which has been evolved during last 50 years.[6]

• Manual Process Model
• Flat File Model
• Database Model System
• REA Model (Resource, Event and Agents)

Many AIS professionals work for consulting firms, large corporations, insurance companies, financial firms, government agencies and public accounting firms, among other types of companies. With technological advancement, traditional accounting practice will shift to accounting information systems practice. Both accounting and information technology professional bodies are working on the new directions of accounting programs and industry practices. System Auditors is one of the top choices in the past two decades, they look at the controls, data processing, data integrity, general operation, maintenance, security and other aspects of all types of information systems used by businesses. Some job titles in this field of work include financial manager, financial examiner and chief financial officer. Other job titles include computer systems analyst, a computer information systems manager or a computer software engineer or programmer specializing in financial software.

There are industry associations offer certificates that related to AIS area include CISA, AIS, CISSP, CIA, AFE, CFE, and CITP.

• Accounting software
• Comparison of accounting software
• List of ERP software packages
• Final accounts