ABSTRACT

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 service. 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 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 formation into their account every month. User scan then view their electricity
bill and pay before the month end.
 TABLEOFCONTENTS
Abstract i

Table of contents ii
List of figures iii
1. Introduction
1.1 Preamble 1-2
1.2 Problem statement 2
1.3 Proposed solution 2
2. Analysis sand System Requirements
2.1 Existing and Proposed System 3
2.2 Software & Hardware Requirements 3
3. System Design and Modelling
3.1 Preliminary Design
3.1.1Entity- Relationship Diagram 4-6
3.1.2SchemaDiagram 7-8
3.2 Normalization
3.2.1 First normal form(1NF) 9
3.2.2 Second normal form(2NF) 9
3.2.3 Third normal form(3NF) 9
4. Implementation
4.1 Implementation of operations 10
4.2 Implementation of SQL statements 10-11
4.3 Algorithm of pseudo code of implementation 12-15
5. Testing
5.1 Testing process 16
5.2 Testing objectives 16
5.3 Levels of Testing
5.3.1Unit Testing 16-18
5.3.2 Integration testing 18-19
5.3.3 System testing 19-20
6. Discussion and Snapshots
6.1 Tables 21-23
6.2 Snapshots 23-33
7.source code 33-36
Conclusion
LIST OF FIGURES

FIG3.1.1: Schematic diagram of Electricity Billing System 6

FIG3.1.2:ER diagram of Electricity Billing System 8
FIG6.1: Snapshot of List of tables 21
FIG6.2: Snapshot login table description 21
FIG6.3: Snapshot of customer table description 22
FIG6.4Snapshot of tax table description 22
FIG6.5: Snapshot of rent table description 22
FIG6.6: Snapshot of bill table description 22
FIG6.7: Snapshot of meter_info table description 23
FIG6.8: Snapshot of Splash page 23
FIG6.9:Snapshot of Login page 24
FIG6.10: Snapshot of Sign up page 24
FIG6.11: Snapshot of Forgot Password page 25
FIG6.12: Snapshot of Admin home page 25
FIG6.13: Snapshot of New Customer page 26
FIG6.14: Snap shot of Meter Info page 26
FIG6.15: Snap shot of Customer Details page 27
FIG6.16: Snapshot of Tax Details page 27
FIG6.17: Snapshot of Calculate Bill page 28
FIG6.18: Snapshot of Delete Customer page 28
FIG6.19: Snapshot of Customer Homepage 29
FIG6.20: Snapshot of Update Customer Detailspage 29
FIG6.21: Snapshot of View Customer Details page 30
FIG6.22: Snapshot of View Customer Details page 30
FIG6.23: Snapshot of Pay Bill page 31
FIG6.24: Snapshot of Paytm page 31
FIG6.25: Snapshot of Bill Detail spage 32
FIG6.26: Snapshot of Generate Bill page 32
FIG6.27: Snapshot of Deposit Bill page 33
FIG6.28: Snapshot of About page 33
LISTOFTABLES
Table5.1: Negative test case for phone number insertion 17
Table5.2: Positive test case for phone number insertion 17
Table5.3: Negative test case for e mail insertion 17
Table5.4: Positive test case for email insertion 17
Table5.5: Negative test case for customer name insertion 18
Table5.6: Positive testcase for customer name insertion 18
Table5.7: Test case on basis of generation of bill 18
Table5.8:Test case on basis of Deposit Details 19
Table5.9: Test cases for the project iv 19-20
 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 over all 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, its efforts and resources.

1.1 Preamble
We, the owners of our project, respect all customers and make them happy with
our service.
Themainaimofourprojectistosatisfycustomerbysavingtheirtimebypaymentproces
s, maintaining records, and allowing the customer to view his/her records and permitting
them to update their details.
The firm handles all the work manually ,which is very tedious and mismatched.
The objectives of our project areas follows:
❖ To keep the information of Customer.
 ❖ To keep the information of consuming unit energy of current month.
❖ To keep the information of consuming unit energy of previous month.
❖ To calculate the units consume delivery month regularly.
❖ To generate the bills adding penalty and rent.
❖ 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
bill sis to be maintained with ands 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.

there are a number of flaws with the manual system. Because the entire bill must
be kept and maintained by hand, the process of keeping and maintaining the information
is extremely laborious and time-consuming for the consumer.
It’s a time-consuming and exhausting operation because employees must visit clients’
homes every month to deliver bills and collect money.

1.3 Proposed Solution

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

The proposed system of an electricity billing system aims to overcome the

limitations of the existing system by leveraging modern technologies and
streamlined processes.

Online Self-Service Portals: The proposed system provides online self-service

portals for customers, allowing them to access their consumption data, billing
history, and payment options. Customers can view and download their bills, make
online payments, and monitor their energy usage in real-time. This enhances
customer convenience and engagement.

Automated Billing Generation: The proposed system automates the billing

generation process based on the consumption data received from smart meters. It
generates accurate and detailed bills, incorporating the applicable tariff rates, fees,
and taxes. Bills can be delivered electronically via email or made available for
download through the online portal.

Real-time Notifications and Alerts: The system sends automated notifications

and alerts to customers, keeping them informed about their energy consumption,
upcoming bill due dates, and any unusual usage patterns. This promotes
transparency and helps customers manage their energy usage effectively.

Advanced Analytics and Reporting: The proposed system incorporates

advanced analytics and reporting capabilities. It generates comprehensive reports
on energy consumption trends, revenue analysis, customer behavior, and demand
patterns. These insights assist utility companies in making data-driven decisions,
identifying areas for improvement, and developing targeted energy conservation
initiatives.
 CHAPTER 2

ANALYSIS AND SYSTEM REQUIREMENT

2.1 Existing System

The existing system of an electricity billing system typically involves a
combination of manual and automated processes. While the specific
implementation may vary among customers. 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.

• Meter Reading: In the traditional system, meter readers physically visit

customers' premises to record electricity consumption from analog meters. They
note down the readings and pass them on to the billing department for further
processing.
• Data Entry and Validation: The recorded meter readings are manually
entered into the billing system by operators. The system performs basic data
validation to ensure accuracy and consistency.
• Billing Generation: The system generates bills or invoices, summarizing
the energy consumption, charges, and payment due date. These bills are typically
printed and mailed to customers or made available for download through online
portals.
 • Payment Processing: Customers can make payments through various
channels, such as in-person at payment centers, by mail, or online. Payment details
are manually entered into the system, and the payment status is updated
accordingly.
• Customer Service: The existing system includes customer service
functionalities, such as handling inquiries, complaints, and bill dispute resolutions.
Customer service representatives manually access customer information and
transaction history to address customer queries.
• Meter Maintenance and Replacement: The system tracks meter
maintenance schedules and facilitates meter replacement when necessary. It
maintains records of meter installations, removals, and repairs.
Reporting and Analytics: The billing system generates reports on energy consumption
patterns, revenue analysis, customer segmentation, and other relevant metrics. These reports
aid in decision-making and performance evaluation

2.2 Software & Hardware Requirements

Hardware Requirements:

➢ Hardware Specification :- Processor Intel

➢ Clock Speed: -1.7GHz or more
➢ System Bus: -64bits
➢ RAM: -16GB
➢ HDD: -2TB
➢ Monitor: -LCD Monitor
➢ Keyboard: -Standard keyboard
➢ Mouse: -Compatible mouse
Software Requirements:

➢ Operating System: -Windows11

➢ Software: - Microsoft SQL Server
➢ Front End: - Java core/swings(NetBeans)
➢ Back End: -My SQL
 CHAPTER - 3
SYSTEM DESIGN AND MODELLING

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, there by ensuring a faster application.

3.1.1 Entity-Relationship Diagram

An entity relationship diagram (ERD) shows the relationships of entity sets
stored in a database. An entity in this context is an object, a component of data. An
entity set is a collection of similar entities. These entities can have attributes that
define its properties.
There are two reasons to create a database diagram. You’re either designing a
new schema or you need to document our existing structure.
If you have an existing database you need to document, you create a database
diagram using data directly from your database. You can export your data base
structure as a CSV file (there are some scripts on how to do this here), then have a
program generate the ERD automatically.
An ER diagram is a means of visualizing how the information a system
produces is related. There are five main components of an ERD:
❖ Entities, which are represented by rectangles. An entity is an object or
concept about which you want to store information.
❖ A weak entity is an entity that must defined by a foreign key relationship with
another entity a sit cannot be uniquely identified by its own attributes alone.
 ❖ Actions, which are represented by diamond shapes,show how two entities
share information in the database.
❖ In some cases, entities can be self linked .For example, employees can
supervise other employees.
❖ Attributes, which are represented by ovals. A key attribute is the unique,
distinguishing characteristic of the entity.
❖ A multi valued attribute can have more than one value. For example, an
employee entity can have multiple skill values.
❖ A derived attribute is based on another attribute. For example, an
employee's monthly salary is based on the employee's annual salary.
❖ Connecting lines, solid lines that connect attributes to show the
relationships of entities in the diagram.
Figure 3.1.1 describes the ER diagram of Electricity Billing System. It has
5entities namely login, customer, tax , bill, and meter info. The entities have
attributes which are primary and foreign and attributes. The primary attributes are
underlined.
3.1.2 Schematic 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 for
eign 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 has3 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".
3.1.2 Schematic

Diagram Login
meter_no Username password user question Answer

customer

Name meter_no Address City state Email phone

rent

cost_per_unit meter_rent service_rent

tax

service_tax swacch_bharat_cess gst

bill

meter_no Month units total_bill Status

meter
__inf_info
meter_no meter_location meter_type phase_code bill_type Days

FIG3.1.2:Schema diagramofElectricityBillingSystem
3.NORMALIZATION

Let’s discuss about anomalies first then we will discuss normal forms with examples.
Anomalies in java dbms There are three types of anomalies that occur when the data base
is not normalized. These are–Insertion, update and deletion anomaly.

3.1.3 Firstnormalform(1NF)
As per the rule of first normal form,
✓ All rows must be unique (no duplicate rows).
✓ Each cell must only contain a single value (not a list).
✓ Each value should be non-divisible (can't be split down further).

Customer

name meter_no address city state email phone

3.1.4 Second normal form(2NF)

As per the rule of second normal form,
✓ Data base must be in First Normal Form.
✓ Non partial dependency -All non-prime attributes should be fully
functionally dependent on the candidate key.
3.1.5 Third normal form(3NF)
As per the rule of third normal form,
✓ Data base must be in First and Second Normal Form.
✓ Non transitive dependency-All fields must only be determinable by the
primary/ composite key, not by other keys.
 CHAPTER 4
IMPLEMENTATION
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.

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
customerVALUES(“sai”,”12345”,”btm”,”Bangalore”,“Karnataka”,“sai@gmail
.com”,“9876543333”).
Update statement:
• An SQL UPDATE statement changes the data of one or more records in a
table. Either all the rows can be updated, or a subset may be chosen using a
condition.
• The UPDATE syntax would follows: UPDATE table_name SET column_name
=value, column_ name =value ...[WHERE condition].
• The following SQL statement update's a new record in the “customer” table:
UPDATE TABLE customer SET [email protected]_no
=”12345”.
 4.3Algorithm or pseudo code of implementation
Explanation of Algorithm or pseudo code of system:
✓ Start system
✓ Enter login name and password
✓ On clicking the login button
✓ Connect to database
✓ Query data base to know whether user credentials are correct
✓ If not, deny access and return login page with an error message
✓ If correct, check if credentials for administrator
✓ If yes, allow login
✓ Set admin session, re-direct administrate or to admin login page
✓ If no, allow login set user session
✓ Re-direct user to user home page
Algorithm or pseudo code of admin:
Login:
▪ This program will allow the admin to enter the username and password.
▪ If the entered credentials are correct, then the login will be successful other
wise need to be signup.
▪ If admin forgets password, it can be retrieved by giving username and
answer for security question.
▪ Aftersuccessfullogintheadminwillberedirectedtoadminportalpagewherehe/s
hecandofollowing activities.
New Customer:
▪ This program will allow the admin to enter the customer details and
automatically generates unique meter number.
▪ If customer name, address, city, state, email and phone number is
entered, insert the values into customer
else print error
while next=true
enter the meter_info details
else print meter_info error
Submit the details of customer that has been entered by clicking on to next
button.
▪ If we need to cancel the particulars that has been entered click on to cancel
option

.
 ▪ If we need to submit the particulars that has be entered click on to submit
option.
Customer Details:
▪ This program will allow the admin to view customer details.
▪ Ifweneedtoprinttheparticularsthathasbeenviewedclickontoprintoption.

Deposit Details:
▪ Thisprogramwillallowtheadmintoviewbilldetails.Ifweneedtosorttheparticular
sbasedonmeter_no and month.
▪ Ifweneedtosearchtheparticularsthathasbeenviewedclickontosearchoption.
▪ Ifweneedtoprinttheparticularsthathasbeenviewedclickontoprintoption.

Tax Details:
▪ This program will allow the admin to add tax details.
insert the values into tax
Else print error
Submit the details of tax that has been entered by clicking on to submit button.
▪ Ifweneedtocanceltheparticularsthathasbeenenteredclickontocanceloption.

Calculate Bill:
▪ This program will allow the admin to calculate total_bill when units
consumed are inserted where meter_no and month is selected.
Insert the values into
bills print error
Submit the details of tax that has been entered by clicking on to submit
button.
▪ If we need to cancel the particulars that has been entered click on to
cancel option.

Delete Bill:
▪ This Program will allow the admin to delete the customer info when meter_
no is selected.
▪ If we need to delete the particulars that has been saved click on to delete
option.
▪ If we need to cancel the particulars that has been entered click on to back
option.
About:
▪ This program will allow the admin to view details of the project in short.
▪ If we need to exit the particulars that has been viewed click on to exit option.

Algorithm or pseudo code of Customer:

Login:
▪ This program will allow the customer to enter the username and password. If
the entered credentials are correct, then the login will be successful other
wise need to be sign up with the meter_ no which is given by admin.
▪ If customer forgets password, it can be retrieved by giving username and
answer for security question. After successful login the customer will
beredirectedtocustomerportalpagewherehe/shecandofollowingactivities.
UpdateInfo1:
▪ This program will allow the customer to update the customer details If
customer address, city, state, email and phone number is updated,
Update the values into
customer else print error
update the details of customer that has been updated by clicking
on to update button.
▪ If we need to cancel the particulars that as been updated, click on to back
option.

View Info:
▪ This program will allow the customer to view his/her own details.
▪ Ifweneedtogobackfromtheparticularsthathasbeenviewedclickontoback
option.

Pay Bill:
▪ This program will allow the customer to view bill details and redirects to pay
▪ The bill where status will be updated.
▪ Ifweneedtocanceltheparticularsthathasbeenviewedclickontobackoption.
▪ If we need to pay the bill amount that has been viewed click on to pay option.

Bill Details:
▪ This program will allow the customer to view bill details.
▪ Ifweneedtoprinttheparticularsthathasbeenviewedclickontoprintoption.
Generate Bill:
▪ This program will allow the customer to generate bill when meter_ no and
month is selected.
▪ Generate the details by clicking on generate bill button.

About:
▪ This program will allow the customer to view details of the project in short.
▪ If we need to exit the particular that has been viewed click on to exit option.

NOTE: Utility
(notepad,browser,calculator),queryandlogoutisgiventobothcustomerandadminportals.
 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 away
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 areas follows:
• Testingisaprocessofexecutingaprogramwiththeintentoffindinganerror.
• A good test case is one that has high probability of finding an as yet
undiscovered error.
• A successful test is one that uncovers discovered error.

5.3 Levels of Testing

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

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.
 Table5.1: Negative test case for phone number insertion
Function Input Expected Error Resolved
Name Output
Input phone 98977 Phone Length of Consume()
number number is phone
invalid number is
not equal to
10
Input phone 98977agv Phone Alphabets
number number is are being
invalid taken as _
input for
phone
number

Table5.2: Positive test case for phone number insertion

Function Input Expected Error Resolved

Name Output
Input phone 9897778988 Expected
number output is _ _
seen

Table5.3: Negative test case for email insertion

Function Input Expected Error Resolved
Name Output
Input email Sai1.in Email is Email is not in Consume()
invalid a format given

Table5.4: Positive test case for email insertion

Function Input Expected Error Resolved

Name Output
Input email [email protected] Expected
m output is seen _ _
 Table5.5: Negative test case for customer name insertion
Function Input Expected Error Resolved
Name Output
Input roshi123 Name is Numbers are Consume()
customer invalid being taken as
name input for name

Table5.6: Positive test case for customer name insertion

Function Input Expected Error Resolved

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

5.3.1 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.Thegoalhereistoseeifallthemodulescanbeintegratedproperly.Wehavebe
en identified and debugged.
Table5.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
 Table5.8: Test case on basis of deposited details

Function Input Expected Error Resolved

Name Output
Negative 12334(meter_no) Details not Output not Consume()
searching of January(month) seen seen
deposited
details
Positive 12334(meter_no) Must display
searching of January(month) deposited _ _
total _ bill details

5.3.2 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.
Table5.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 1.Admin panel opens
2.If customer login and
2.Customerpanelopens
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
menu from the click of deposit details etc
the mouse.
 Selection1 ❖ New Customer
❖ Customer Details
❖ Deposit Details
❖ Calculate Bill
❖ Tax Details
❖ Delete Customer

Step2.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
Selection2 ❖ Update Details
❖ View Details
Selection2a ❖ Generate Bill
Selection2b ❖ Pay Bill
❖ Bill Details
 CHAPTER 6
DISCUSSION AND SNAPSHOTS
6.1 TABLES:
The given below table is a snapshot of backend view of the local host and the
structures of the tables present in Electricity Billing System. The tables present are
login, customer, tax, bill, meter _ info.
✓ Theloginisusedtostorethedetailsoflogin’sadminandcustomerwithmeter_no.
✓ The customer is used to store details of customer.
✓ There axis used to store tax values.
✓ There used to store rent values.
✓ The bill is used to store details of bill of meter.
The meter_info is used to store information of meter placed

FIG6.1:List of tables
LoginTable:

FIG6.2:login table description

CustomerTable:

FIG6.3:customer table description

Tax Table:

FIG6.4:tax table description

RentTable:

FIG6.5:rent table description

BillTable:

FIG6.6:bill table description

Meter_InfoTable:

FIG6.7:meter_info table description

6.2 SNAPSHOTS:

FIG6.8:Splash page of Electricity Billing System

 FIG6.9:Login page

FIG6.10: Sign up page

FIG6.11:Forgot Password page

FIG6.12:Adminhomepage
FIG6.13:Newcustomer page

FIG6.14:MeterInfopage
FIG6.15:CustomerDetailspage

FIG6.16:TaxDetailspage
 FIG6.17:CalculateBill page

FIG6.18:DeleteCustomerpage
 FIG6.19:CustomerHomepage

FIG6.20:Updatecustomerdetailspage
FIG6.21:ViewCustomerDetailspage

FIG6.22:Querypage
FIG6.23:PayBillpage

FIG6.24:Paytmpage
 FIG6.25:BillDetailspage

FIG6.26:GenerateBillpage
FIG6.27:DepositDetailspage

FIG6.28:Aboutpage
 CONCLUSION
In conclusion, the electricity billing system plays a crucial role in utility
companies by accurately measuring and charging customers for their energy
consumption. It is a complex system that involves various components and
processes, ranging from meter reading to billing generation and customer
management. Advancements in technology have led to the development of modern
electricity billing systems that leverage smart meters, automated data processing,
online self-service portals, and advanced analytics. These systems offer numerous
benefits, including improved accuracy, efficiency, and customer satisfaction .By
integrating smart meters, utility companies can capture real- time consumption
data, eliminating the need for manual meter reading and ensuring accurate billing
based on actual usage. Automation of data processing reduces errors and streamlines
billing calculations, resulting in more accurate bills and efficient operations.

Online self-service portals empower customers with real-time access to their

consumption data, billing history, and payment options. This convenience
improves customer satisfaction and engagement while promoting transparency and
enabling customers to make informed decisions about their energy usage .The use
of advanced analytics in the electricity billing system enables utility companies to
gain valuable insights into energy consumption patterns, revenue analysis, and
customer behaviour. These insights drive data-driven decision-making, assist in load
forecasting, and facilitate the development of targeted energy conservation
initiatives.
REFERENCES
Book Reference
Database Management Systems 3rd Edition by Raghu
Ramakrishnan(TEXTBOOK).
Websites
➢ http://www.github.com
➢ https://www.youtube.com/watch?v=iWitVuW2D1o&t=4s
➢ www.stackoverflow.com
➢ www.google.com
➢ http://www.javatpoint.com/