ACCOUNT INFORMATION SYSTEM ABSTRACT

The project Accounts Information System is designed using Microsoft Visual Studio.Net 2003 as front end and Microsoft SQL Server 2000 as backend which works in .Net framework version 1.1. The coding language used is VB .Net. The accounting functions of management information systems as a context; this system develops an interdisciplinary approach to data reliability assessment. Our work builds on the Customer, Supplier, Employees and their Payment details, where reliability assessment has been a topic of study for a number of years. While formal probabilistic approaches have been developed in this literature, they are rarely used in practice. The research reported in this paper attempts to strike a balance between the informal, heuristic-based approaches used by auditors and formal, probabilistic reliability assessment methods. The infrastructure of a corporate enterprise information system is concerned with acquiring, transferring, converting, and selling economic resources such as cash, inventory, and supplies. Accounting systems with individual computerized modules, such as: payroll, accounts payable and receivable, job costing, order entry, and general ledgers, have traditionally tracked such data, and accounting system designers usually have had a preemptive call on the basic schemes used to type economic data. This is because of a need to meet either statutory reporting requirements for governmental agencies, or private reporting requirements for creditors and shareholders. If accountants use these preemptive privileges to force traditional account coding onto the organization database as its fundamental classification architecture (that is, to require early bookkeeper filtering of transaction data), then many dysfunctional effects arise. The purpose of this system has to maintain the customer, supplier, employees, and their salary details .This process has been handle through admin only.

EXISTING SYSTEM The present practice involved in the organization contains many drawbacks which is so called bottlenecks of the system. In order to retrieve a particular record many enquiries must be made only through manual involvement and also it takes more time to complete that process. The detail of the customer, employee and supplier services takes longer time to maintain for a long time. At present, they are maintained manually using complain slip, fault slip, notebooks and registers. Those records are saved for many years, which get damaged after sometime.

DRAWBACKS OF THE EXISTING SYSTEM

In the existing practice of recording the customers, employee and supplier details in a paper or register in a manual manner leads to a lot of drawbacks. They are Reports have to be produced manually. Maintaining all information of all customers, employee and supplier payment/receipt details consume a lot of time and space. Maintaining a unique Emp ID for each record is very difficult. Since data has to be maintained as hardcopies, it becomes bulky. Searching and updating for a particular record is very difficult in manual processing. Data redundancy occurs frequently which results in confusion. Paper in the register may get damaged which results in the loss of the particular records. In the manual process mistakes may occur, which are made carelessly. It may create unnecessary problems and confusions later.

PROPOSED SYSTEM
The aim and the benefit for developing the system aroused mainly to overcome the shortcoming of the previous system and to improve upon the system. The main aim of the ACCOUNT INFORMATION SYSTEM is to ensure user friendly and more interactive software to the user.

ACCOUNT INFORMATION SYSTEM brings an easy interesting working environment, more clarity in presenting apt information to the required user. It gives faster access and retrieval of information from the database. The present system gives more security assurance to the database. There is no chance of missing a record. And it is almost nil to errors. It consumes minimum time to work on it. Any type of queries can be resolved using the software. It is very easy to maintain customer, employee and supplier records with the present online system. Comparative analysis is aimed easily using this software. This makes the feedback to be effective to the users.

BENEFITS 1. We can easily maintain all the customer, supplier, employee details 2. Report generation is easier. 3. The Admin can view all the details of customer, supplier and their reports can be viewed. 4. Customer can register the details easily in time consumptions. 5. Monitor the status of the entire at any time and the verification of reports generated by the admin. 6. Less time consuming.

SYSTEM CONFIGURATION
HARDWARE CONFIGURATION The hardware used for the development of the project is:
A Server PC with 3.0 GHz processor Windows 2000/2003 Server

 2 GB of RAM MS-SQL Server 2005 PC with a minimum of 512 MB RAM

SOFTWARE CONFIGURATION The software used for the development of the project is:
Microsoft .NET Framework 2.0 (Runtime Environment) Visual Studio 2008 (Development Tool) VB.NET (Coding) Enterprise Library 3.1(Development Tool) SQL Server (Database) SQL Server Reporting Services Windows XP/2000

MODULE DESCRIPTION The modules involved in this project are customer, supplier, employees, payment, receipt, salary, parties report, payroll report, transaction report and logout.

This project consists of following modules: Admin Customer Supplier Employee Payment details Receipt details Salary details

Reports

ADMIN: Admin login allows entering the admin username and password. CUSTOMER DETAILS: This module allows the new customer to register their details such as username, address, phone no, email id. SUPPLIER DETAILS: This module allows the supplier to register their details such as their name, address, phone no, and email id, website urls. EMPLOYEE DETAILS: This module allows the new employee to register their details. Employee name, Employee id, address, phone no, email id. PAYMENT DETAILS: The payment details saves the type of payment allotted to supplier, employee. It allows the admin to select which mode of payment, such as cash, cheque and demand draft. Here, default type is set to Payment. RECEIPT DETAILS:

The receipt details saves type of payment allotted to supplier and employee. It allows the admin to select which mode of payment, such as cash, cheque and demand draft. Here, default type is set to Receipt. SALARY DETAILS: This module shows the salary details of employee and supplier. REPORTS: This report module consists of sub modules: Parties report Transaction report Payroll report

Parties report: It displays the reports of the parties in the data grid. This report is generated according to admin selection such as payment, receipt, both, cheque, payment only, receipt only, all cheques. Transaction report: This report is generated according to admin selection such as payment, receipt, both, cheque, payment only, receipt only, all cheques. Payroll report: This report is generated according to EMP id, for month/year .the details are viewed in the data grid format.

4 DATA FLOW DIAGRAM

Level 0:

User name Admin login Password Admin

Level 1:

Customer id Customer name Address Phone no Fax Email id

Customer details

Customer

Level 2:

Supplier id

Supplier name Address Phone no Fax Email id

Supplier details

Supplier

Level 3:

Employee id

Employee name Address Phone no Fax Email id

Employee details

Employees