ELECTRICITY BILLING SYSTEM

Declaration

To,
The Principal,
Jayawantrao Sawant college of Engineering, Hadapsar,
Pune-28

Respected Sir,
I, Miss. Neha Pandit Indalkar hereby declare that the Mini Project entitled “ Electricity Billing
System ” has been developed and submitted under the guidance of Prof. Anil Gaikwad is my original
work.
The Project work presented here is my own work and has not been duplicated from any
other sources.

Date: / /2023 Yours Sincerely

Place : Pune Neha Pandit Indalkar
 ELECTRICITY BILLING SYSTEM

Acknowledgement

I would take this opportunity to thank Dr. R. D. Knaphade Sir, Principal of JSCOE for their
extended support to me throughout the course.
I would like to thank Prof. Swayam shah sir, HOD, MCA Department for scholarly
disposition, timely guidance, support and cooperation.
I would like to thank [Guide Name] for his/her kind guidance, keen interest, continuous
encouragement and inspiration throughout the project work.
Finally, I am grateful to all the staff members of JSCOE for their cooperation and support.
I also thankful to get constant encouragement, support and guidance from all teaching and
non-teaching staff for their support which helped us in successfully completion of our project work.

Mr. / Miss. Neha Pandit Indalkar

Exam Seat No:-5018
 ELECTRICITY BILLING SYSTEM

SYNOPSIS

Electricity consumers are often faced with the problem of inaccuracy and
delay in monthly billing due to some drawbacks. Thus, it is essential to have an
efficient system for such purposes via electronic platform with consideration to
proximity.

The proposed system automates the conventional process of paying

electricity bill by visiting the Electricity Board which is tiresome and time
consuming. It is also designed to automate the electricity bill calculation and
payment for user convenience. The system is developed with Java swings as the
base programming language which can be used to develop websites, web
applications and web services.

The Microsoft Structured Query Language (SQL) server is also used

for creating back-end database. The system would be having two logins: the
administrative and user login. The administrator can view the user's account
details and can add the customer's information of consuming units of energy
of the current month in their account.

The Admin must feed the system with the electricity usage data into
respective user’s account. The system then calculates the electricity bill for
every user and updates the information into their account every month.
Users can then view their electricity bill and pay before the month end.
 ELECTRICITY BILLING SYSTEM

TABLE OF CONTENTS

CHAPTER CONTENT PAGE NO.

NO.
1. Introduction
1.1 Preamble 1
1.2 Problem Statement 2
2. Analysis and System Requirements
2.1 Existing And Proposed System 2
2.2 Software and Hardware Requirements
3. System Design And Modeling
3.1 Preliminary Design 3
3.1.1 UML Diagram
3.1.2 Schema Diagram

4 Implementation
4.1 Implementation of Operations 11
4.2 Implementation of SQL Statements
4.3 Algorithm or Pseudocode of Implementation
5. Testing
5.1 Testing Process 14
5.2 Testing Objective
5.3 Levels of Testing
5.3.1 Unit Testing
5.3.2 Integration Testing
5.3.2 System Testing
6. Discussion And Snapshots
6.1 Tables 20
6.2 Snapshots
7. Future Scope And Limitations 38
8. Conclusion 39
9. Bibliography 40
 ELECTRICITY BILLING SYSTEM

Chapter 1

INTRODUCTION

Electricity Billing System is a software-based application.

i. This project aims at serving the department of electricity by computerizing
the billing system.
ii. It mainly focuses on the calculation of units consumed during the specified
time and the money to be charged by the electricity offices.
iii. This computerized system will make the overall billing system easy,
accessible, comfortable, and effective for consumers.
To design the billing system more service oriented and simple, the following
features have been implemented in the project. The application has high speed of
performance with accuracy and efficiency.
The software provides facility of data sharing, it does not require any staff as
in the conventional system. Once it is installed on the system only the meter
readings are to be given by the admin where customer can view all details, it has
the provision of security restriction.
The electricity billing software calculates the units consumed by the
customer and makes bills, it requires small storage for installation and
functioning. There is provision for debugging if any problem is encountered in
the system.
The system excludes the need of maintaining paper electricity bill,
administrator does not have to keep a manual track of the users, users can pay
the amount without visiting the office. Thus, it saves human efforts and
resources.

1.1 Preamble
We, the owners of our project, respect all customers and make them happy
with our service.
The main aim of our project is to satisfy customer by saving their time by
payment process, maintaining records, and allowing the customer to view his/her
records and permitting them to update their details.

Page 1
 ELECTRICITY BILLING SYSTEM

The firm handles all the work manually, which is very tedious and
mismatched.

The objectives of our project are as follows:

• To keep the information of consuming unit energy of current

month.

• To keep the information of Customer.

• To keep the information of consuming unit energy of previous
month.

• To calculate the units consumed every month regularly. • To save

the time by implementing payment process online.

1.2 Problem Statement

The manual system is suffering from a series of drawbacks. Since whole
of the bills is to be maintained with hands the process of keeping and maintaining
the information is very tedious and lengthy to customer. It is very time
consuming and laborious process because, staff need to be visited the customers
place every month to give the bills and to receive the payments. For this reason,
we have provided features Present system is partially automated (computerized),
existing system is quite laborious as one must enter same information at different
places.

1.3 Proposed Solution

o This project system excludes the need of maintaining paper electricity
bill as all the electricity bill records are managed electronically. o
Administrator doesn't have to keep a manual track of the users. The
system automatically calculates the fine.
o Users don't have to visit to the office for bill payment.
o There is no need of delivery boy for delivery bills to user's place. o
Thus, it saves human efforts and resources.

Page 2
 ELECTRICITY BILLING SYSTEM

CHAPTER 2

ANALYSIS AND SYSTEM

REQUIREMENT

2.1 Existing and Proposed System

The conventional system of electricity billing is not so effective; one staff
must visit each customer’s house to note the meter readings and collect the data.
Then, another staff must compute the consumed units and calculate the money to
be paid. Again, the bills prepared are to be delivered to customers. Finally,
individual customer must go to electricity office to pay their dues.
Hence, the conventional electricity billing system is uneconomical,
requires many staffs to do simple jobs and is a lengthy process overall. In order
to solve this lengthy process of billing, a web based computerized system is
essential. This proposed electricity billing system project overcomes all these
drawbacks with the features. It is beneficial to both consumers and the company
which provides electricity.
With the new system, there is reduction in the number of staffs to be
employed by the company. The working speed and performance of the software
is faster with high performance which saves time. Furthermore, there is very little
chance of miscalculation and being corrupted by the staffs.

2.2 Software & Hardware Requirements

Hardware Requirements:

➢ Processor: - AMD 3020e with Radeon Graphics

➢ Clock Speed: -1.7 GHz or more
➢ System Bus: -64 bits
➢ RAM: -4GB
➢ HDD: -256GB
➢ Monitor: -LCD Monitor
➢ Keyboard: -Standard keyboard
➢ Mouse: -Compatible mouse

Page 3
 ELECTRICITY BILLING SYSTEM

Software Requirements:

➢ Operating System: -Windows 11

➢ Software: -Microsoft SQL Server
➢ Front End: -Java core/swings (NetBeans)
➢ Back End: -My SQL

Page 4
 ELECTRICITY BILLING SYSTEM

CHAPTER 3

SYSTEM DESIGN AND MODELING

3.1 Preliminary Design

System design is an abstract representation of a system component and
their relationship and which describe the aggregated functionally and
performance of the system. It is also the plan or blueprint for how to obtain
answer to the question being asked. The design specifies various type of
approach.
Database design is one of the most important factors to keep in mind if you
are concerned with application performance management. By designing your
database to be efficient in each call it makes and to effectively create rows of data
in the database, you can reduce the amount of CPU needed by the server to
complete your request, thereby ensuring a faster application.

3.1.1 UML Diagram

Class diagram.

Page 5
 ELECTRICITY BILLING SYSTEM

Use Case Diagrams:

Page 6
ELECTRICITY BILLING SYSTEM

Page 7
 ELECTRICITY BILLING SYSTEM

Activity Diagram:

Page 8
 ELECTRICITY BILLING SYSTEM

3.1.2 Schema Diagram

Database schema is described as database connections and constraints. It
contains attributes. Every database has a state instances represent current set of
databases with values. There are different types of keys in a database schema.
A primary key is a table column that can be used to uniquely identify
every row of the table. Any column that has this property, these columns are
called candidate key. A composite primary key is a primary key consisting of
more than one column. A foreign is a column or combination of columns that
contains values that are found in the primary key of some table.
All the attributes of each table are interconnected by foreign key which is
primary key in another column and composite key. Primary key cannot be null.
The fact that many foreign key values repeat simply reflects the fact that its one-
to-many relationship. In one-to-many relationship, the primary key has the one
value and foreign key has many values.
Figure 3.1.2 is a Schema diagram of Electricity Billing System which has
six tables i.e., login, customer, tax, rent, bill, and meter_info where each table
contain attributes some with primary key, foreign key. In the login table there are
6 attributes "meter_no”, "username”, “password”, "user”, "question”, "answer”.
The customer table has 7 attributes "name”, "meter_no"(primary key), "address”,
"city”, "state”, “email”, "phone”. The rent table has 3 attributes
"cost_per_unit"(primary key), " meter_rent”, "service_charge". The tax table has
3 attributes " service_tax”, "swacch_bharat_cess”, "gst”. The bill table has 5
attributes "meter_no"(foreign key that references the primary key of the customer
table meter_no), "month”, "units”,"total_bill”, "status”. The meter_info table has
6 attributes "meter_no"(foreign key that references the primary key of the
customer table meter_no), "meter_location”, "meter_type”, "phase_code”, "
bill_type”, "days ".

Page 9
 ELECTRICITY BILLING SYSTEM

3.1.2 Schema Diagram

Login
Meter No Username Password User Question Answer

Page 10
 ELECTRICITY BILLING SYSTEM

CHAPTER 4
IMPLIMENTATION

4.1 Implementation of operations

❖
Adding Customer: Here admin can add new customer to the customer list
who started using electricity bill system.
❖
Searching Deposit Details: Here admin can search according to meter
number and month to view deposit details.
❖
Viewing Details: Here admin and user can view customer details and about
details.
❖
Adding Tax: Here admin can add tax details.
❖
Updating Customer: Here customer can update his/her details by using
meter_no of the customer.
❖
Delete Customer: Here admin can delete details based on meter number.

4.2 Implementation of SQL statements

Insert statement:
• The INSERT INTO statement is used to insert new records in a table.
• The INSERT INTO syntax would be as follows: INSERT INTO
table_name VALUES (value1, value2, value3, ...).
• The following SQL statement insert's a new record in the “customer” table:
Insert into customer VALUES (“sai”,”12345”,” btm”,” Bangalore”,
“Karnataka”, “sai@[Link]”, “9876543333”).
Update statement:
• The UPDATE syntax would be as follows: UPDATE table_name SET
column_name =value, column_name=value... [WHERE condition].

Page 11
 ELECTRICITY BILLING SYSTEM

The following SQL statement update's a new record in the “customer” table:
UPDATE TABLE customer SET email= su@[Link] WHERE meter_no
=”12345”.
Delete statement:
• The DELETE statement is used to delete existing records in a table.
• The DELETE syntax would be as follows: DELETE FROM table_name
WHERE condition. • The following SQL statement delete's a record in the
“customer” table:
delete from customer where meter_no=12345. Create
statement:

• The syntax would be as follows: CREATETABLE table_name

(column1datatype, column2datatype, column3 datatype, column datatype,
PRIMARY KEY (one or more columns)).
➢
The following SQL statement creates a table “customer” table:
create table customer (name varchar (30), meter_no varchar (20)
primary key, address varchar (50), city varchar (20), state varchar
(30), email varchar (30), phone varchar (30));
➢
The following SQL statement creates a table “login” table: create
table login (meter_no varchar (30), username varchar (30), password
varchar (30), user varchar (30), question varchar (40), answer
varchar (30));
➢
The following SQL statement creates a table “tax” table: create table
tax (cost_per_unit int (20) primary key, meter_rent int
(20), service_charge int (20), service_tax int (20),
swacch_bharat_cess int (20), gst int (20));
➢
The following SQL statement creates a table “bill” table: create
table bill (meter_no varchar (20), foreign key(meter_no) references
customer(meter_no) on delete cascade, month varchar (20), units
int (20), total_bill int (20), status varchar (40));
➢ The following SQL statement creates a table “meter_info” table: create

table meter_info (meter_no varchar (30), foreign

key(meter_no) references customer(meter_no) on delete cascade,
meter_location varchar (10), meter_type varchar (15), phase_code int
Page 12
 ELECTRICITY BILLING SYSTEM

(5), bill_type varchar (10), days int (5));

Page 13
 ELECTRICITY BILLING SYSTEM

CHAPTER 5
TESTING
This chapter gives the outline of all the testing methods that are carried out
to get a bug free application.

5.1 Testing process

Testing is an integral part of software development. Testing process, in a
way certifies, whether the product, that is developed, compiles with the standards,
that it was designed to. Testing process involves building of test cases, against
which, the product has to be tested. In some cases, test cases are done based on
the system requirements specified for the product/software, which is to be
developed.

5.2 Testing objectives

The main objectives of testing process are as follows:
• Testing is a process of executing a program with the intent of finding an error.
• A good test case is one that has high probability of finding an as yet undiscovered
error.
• A successful test is one that uncovers an as yet undiscovered error.

5.3 Levels of Testing

Different levels of testing are used in the testing process; each level of
testing aims to test different aspects of the system. The basic levels are unit
testing, integration testing, system testing and acceptance testing.

5.3.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of
software design the module. The software built, is a collection of individual
modules. In this kind of testing exact flow of control for each module was
verified. With detailed design consideration used as a guide, important
control paths are tested to uncover errors within the boundary of the
module.

Page 14
 ELECTRICITY BILLING SYSTEM

Table 5.1: Negative test case for phone number insertion

Expected Error Resolved

Function Name Input Output

Phone Length of Consume

Input phone number is phone ()
number 98977 invalid numb er
is
not equal to
10

Table 5.2: Positive test case for phone number insertion

Input Expected Error Resolved

Function
Output

Name
Input 989777 Expected
Phone 8988 Output is _ _
Number Seen

Table 5.3: Negative test case for email insertion

Function
Name Input Expected Error Resolved
Output

Page 15
 ELECTRICITY BILLING SYSTEM

Email is not Consume

Input email Sai1.i n Email is invalid in ()
a format
given

Table 5.4: Positive test case for email insertion

Function Input Expected Error Resolved

Name Output
Input _ _
email aki123@[Link] Expected
output is seen

Table 5.5: Negative test case for customer name insertion

Function Input Expected Error Resolved

Name Output
Input Sana123 Name is Numbers are Consume ()
customer invalid being taken as
input for
name name

Table 5.6: Positive test case for customer name insertion

Function Input Expected Error Resolved

Name Output
Input Gowthu Expected
customer output is seen _ _
name

Page 16
 ELECTRICITY BILLING SYSTEM

5.3.2 Integration Testing

The second level of testing is called integration testing. In this, many
class-tested modules are combined into subsystems, which are then tested.
The goal here is to see if all the modules can be integrated properly. We
have been identified and debugged.

Table 5.7: Test case on basis of generation of bill

Function Input Expected Error Resolved

Name Output
Negative 12334(meter_no) Details seen Output not Consume ()
searching of January(month) but not seen
total_bill total_bill
Positive 12334(meter_no) Must display
searching of January(month) full generated
total_bill bill with _ _
total_bill

Table 5.8: Test case on basis of deposit details

Function Input Expected Error Resolved

Name Output
Negative 12334(meter_no) Details not Output not Consume ()
searching of January(month) seen seen
depositedetails

Positive 12334(meter_no) Must display

searching of January(month) depositedetails _ _
total_bill

Page 17
 ELECTRICITY BILLING SYSTEM

5.3.3 System testing

Here the entire application is tested. The reference document for

this process is the requirement document, and the goal is to see IF the
application meets its requirements. Each module and component of
ethereal was thoroughly tested to remove bugs through a system testing
strategy. Test cases were generated for all possible input sequences and
the output was verified for its correctness.

Table 5.9: Test cases for the project

Steps Action Expected output

Step1 The screen appears when A page with different
choice the users run the menu’s appears.
program.
1. If admin login [Link] panel opens and
2. If customer login [Link] panel opens
Step 2 The screen appears when A window for adding
the admin logs in and new customer, inserting
selects any one of the tax, calculate bill, view
menus from the click of deposit details etc.
the mouse.
Selection 1 ❖New Customer
❖Customer
Details

❖Deposit Details
❖Calculate Bill
❖Tax Details
❖Delete Customer
❖New Admin

Page 18
 ELECTRICITY BILLING SYSTEM

Step 2.1 The screen appears when A window for generating

the customer login and bill, update customer
selects any one of the details, view details,
menus from the click of generating bill
the mouse
Selection 2 ❖Update Details
❖View Details

Selection 2a ❖Generate Bill

Selection 2b ❖Pay Bill
❖Bill Details

Page 19
 ELECTRICITY BILLING SYSTEM

CHAPTER 6
DISCUSSION AND SNAPSHOTS
6.1 TABLES:
The given below table is a snapshot of backend view of the localhost and
the structures of the tables present in Electricity Billing System. The tables present
are login, customer, tax, bill, meter_info.

FIG 6.1:List of tables

Login Table:

FIG 6.2:login table description

Customer Table:

FIG 6.3: customer table description

Tax Table:

Page 20
 ELECTRICITY BILLING SYSTEM

FIG 6.4: tax table description Rent

Table:

FIG 6.5: rent table description Bill

Table:

FIG 6.6: bill table description

Meter_Info Table:

FIG 6.7: meter_info table description

Page 21
 ELECTRICITY BILLING SYSTEM

6.2 SNAPSHOTS:

Login Screen

Here Customer and Admin can login to their respective accounts. The
dropdown menu allows to choose whether to login as an admin or as a
customer.

Sign Up Screen

Here New customers will signup to access their accounts.

Page 22
 ELECTRICITY BILLING SYSTEM

User have to enter username, name, password, choose security question

and answer to that question.

Every user must enter their unique Meter Number to complete their
signup process.

Forgot Password Screen

Here customers as well as admins can retrieve their passwords in case they
fail to remember.

Customers and admins have to fill the required details and answer the
security question chosen by them to retrieve their password.

Page 23
ELECTRICITY BILLING SYSTEM

Admin’s Home Screen

Page 24
 ELECTRICITY BILLING SYSTEM

New Customer Screen

Here admin registers new users.

Admin enters Customer’s Name, Address, City, State, Email and Phone
Number.

Meter Info Screen

Here Admin selects the location and type of meter installed at the customers end.

Admin also selects the phase code and Bill type i.e. Residential or Commercial/
Industrial.

Page 25
 ELECTRICITY BILLING SYSTEM

Add New Admin Screen

Here existing admins can add new admins to access the stored data.

New admins have to enter username, name, password, choose security

question and answer to that question.

Admin can be added only by existing admins via Admin module only.

Page 26
 ELECTRICITY BILLING SYSTEM

Customer Details Screen

Here Admins can see the details of all registered customers. Admin can

print these details in pdf format if the wish.

Page 27
 ELECTRICITY BILLING SYSTEM

Deposit Details Screen

Here Admin can check the status whether customers have paid their
bills or not.

His list can be sorted according to individual user’s meter number or

according to month.

Admin can print these details in pdf format if the wish.

Page 28
 ELECTRICITY BILLING SYSTEM

Calculate Bill Screen

Here admin calculate the bill of users by selecting appropriate meter

number, units consumed and month.

Page 29
 ELECTRICITY BILLING SYSTEM

Delete Customer Screen

Here admin can delete any existing customer by choosing appropriate

meter number.

Page 30
 ELECTRICITY BILLING SYSTEM

Customer’s Home Screen

Customer lands on this page after successful login.

Page 31
 ELECTRICITY BILLING SYSTEM

View Customer Info Screen

Here customer can see their entered information such as their name, meter
number, address, city , state, email id and phone number.

Page 32
 ELECTRICITY BILLING SYSTEM

Update Customer Info Screen

Here customer can update their entered information if any correction is

needed such as their address, city, state, email id and phone number.

Bill Details Screen for Customers

Here every customer can check the status of their bills, whether they have
paid the bills or not.

Page 33
 ELECTRICITY BILLING SYSTEM

Pay Bill Screen

Here customers pay their bills by selecting appropriate month.

Page 34
 ELECTRICITY BILLING SYSTEM

Paytm Gateway Screen

Customers can pay via Paytm gateway.

Customers can pay via net banking, wallet, Debit or credit cards.

Page 35
 ELECTRICITY BILLING SYSTEM

Generate/ Show Bill Screen

Here customer can generate / see their bill in a proper breakdown of entire
amount.

Page 36
 ELECTRICITY BILLING SYSTEM

Calculator Screen

When user clicks on calculator option under utilities section, its launches
the calculator.

This feature is available to both Admins and Customers.

Page 37
 ELECTRICITY BILLING SYSTEM

CHAPTER 7
FUTURE SCOPE AND LIMITATIONS

SOFTWARE SCOPE:

• Extensibility: This software is extendable in ways that its original developers may not
expect. The following principles enhances extensibility like hide data structure, avoid
traversing multiple
Links or methods avoid case statements on object type and distinguish public and private operations.

• Reusability: Reusability is possible as and when require in this application. We can update
it next version. Reusable software reduces design, coding and testing cost by amortizing
effort Over several designs. Reducing the amount of code also simplifies understanding,
which increases the likelihood that the code is correct. We follow up both types of
reusability: Sharing of newly written code within a project and reuse of previously written
code on new projects.
• Understand ability: A method is understandable if someone other than the creator of the
method can understand the code (as well as the creator after a time lapse). We use the
method, which small and coherent helps to accomplish this.
• Cost-effectiveness: Its cost is under the budget and make within given time period. It is
desirable to aim for a system with a minimum cost subject to the condition that it must
satisfy the entire requirement.
Scope of this document is to put down the requirements, clearly identifying the information needed
by the user, the source of the information and outputs expected from the system.

LIMITATIONS:

This application cannot be accessed remotely.

• This application requires knowledgeable person to use this application.
• This application does not have journals.

Page 38
 ELECTRICITY BILLING SYSTEM

CHAPTER 8
CONCLUSION

After all the hard work is done for electricity bill management system is
here. It is a software which helps the user to work with the billing cycles, paying
bills, managing different DETAILS under which are working etc.

This software reduces the amount of manual data entry and gives greater
efficiency. The User Interface of it is very friendly and can be easily used by
anyone.

It also decreases the amount of time taken to write details and other
modules.

Page 39
 ELECTRICITY BILLING SYSTEM

CHAPTER 9
BIBLIOGRAPHY

REFERENCES

Websites
➢ [Link]
➢ [Link]
➢ [Link]
➢ [Link]
➢ [Link]

Page 40