Billing Water and Sewerage - ERP and DIGIT

Glossary

  • Demand - A demand is the liability that citizen is responsible to pay

  • Bill - A bill is a representation of demand in a particular format as a physical copy (with due dates, clauses etc)

Citizen user scenarios

  1. Receiving

    1. Correct Bills

    2. Incorrect Bills → Visits ULB to understand and resolve.

      1. A citizen may or may not visit the ULB within the bill due date time frame

  2. Paying Bills

    1. How? → Online/ Offline

    2. When?

      1. Pays before/on due date →

      2. Pays after due date →

      3. Pays with next bill →

      4. Forgets to pay →

        1. Gets a penalty for not paying in time AND an interest incurred on the due amount

Data Structure

 

ERP

DIGIT

 

ERP

DIGIT

Connection : Demand : Bill Relationship

 

 

Demand Schema

 

 

Bill Schema

 

 

What is a MUST have information in a demand?

 

 

What is a MUST have information in a bill?

 

 

Demand Generation

 

ERP

DIGIT

 

ERP

DIGIT

Who generates the demand?

Employee Controlled

  • has to perform demand generation action

System Controlled

How is a demand generated?

Employee generates

  • batch or single demand for

  • a specified billing period

 

When is a demand generated?

Demand is generated in the billing cycle

  • For a service like Water and Sewerage, demand is generated at the end of a billing cycle generally

  • Metered Connection: Demand is generated when meter-reading is entered

  • Non-metered: A defined scheduler auto-generates the demand ??

When can a demand NOT be generated?

 

 

What happens in the system after a demand is generated?

 

 

How do employees use a demand?

 

 

How do citizens use a demand?

N/A

N/A

Bill Generation

 

 

ERP

DIGIT

 

ERP

DIGIT

How do citizens use a bill on-ground?

 

 

How do employees use a bill on-ground?

 

 

How is a bill generated?

 

 

When is a bill generated?

 

  • Meter: Monthly reading

  • Non-Meter:

When can a bill NOT be generated?

A billing cycle cannot be skipped

  • For example: If for Q1 a bill exists and for Q2 a bill does NOT exist, then employee cannot generate the bill for Q3

 

 

What happens in the system after a bill is generated?