Editing Accounting information system (section)

==An example of architecture==
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 (supply chain)|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.