Bill Amendment
Configure billing services to allow bill amendments

Overview

The consumer sometimes needs additional amounts (Amendments) added to their bill due to reasons external to the system. The addition of amounts happen with respect to the consumer-code of the entity in the product(PT, WS etc..,), any unpaid demand in the system is a candidate for amendments.

Functionality

Amendment mainly works with two types of functionality as follows:
    Amendment
    Demand

Objective

The main objective of the Bill-Amendment module is to create Credit/ Debit Notes against the bills for consumers who need an additional amount to be added to their bill.

Feature List

    Create Amendment
    Search Amendment
    Update Demand
    Update Amendment

API DEFINITION

POSTMAN-COLLECTION

Functionality

Bill Amendment provides a separate flow to enable workflow and validation for the process of adding additional amount into the existing demands which were done through the respective modules only till this point in time. An amendment will be allowed only when the reason arises from out of the system to add or reduce the amount from the existing bill belonging to an entity. The reasons are as listed below -
    1.
    Court case settlement
    2.
    One time waiver
    3.
    Write-offs
    4.
    DCB correction (Old demands in paid status)
    5.
    Remission for Property Tax

Criteria

There are certain prerequisites to create an amendment,
    1.
    Presence of demand in the billing system
    2.
    One of the reasons listed above
    3.
    Valid document proof for the reason
    4.
    No other Amendment already in workflow

PROCEDURE

The process of adding Amendment is as follows
There are two scenarios on how an amendment will be completed which is based on the paid status of the existing demands in the system.
1. When demand is unpaid/partially paid
    1.
    create a demand (Or an existing demand can be used) with demand detail → DD1.
    2.
    Do not pay the bill or make payment partially.
    3.
    Create an amendment for the same consumer-code (with demand detail → DD2).
    4.
    approve the amendment, the response should return an amendment with status CONSUMED.
    5.
    search the demand or fetch bill for the consumer-code, demand/bill should contain demand details of demand and amendment together DD1 and DD2 in the same demand/bill.
2. When demand is completely paid
    1.
    create demand and make complete payment or choose a consumer-code which is fully paid.
    2.
    create amendment (with demand detail → DD1).
    3.
    Approve amendment, the response should be APPROVED this time.
    4.
    create new demand for the consumer -code (with demand detail → DD3), demand response should contain two demand details DD1 and DD2 saved to the demand.
    5.
    Now amendment search will return CONSUMED status after the demand is created.

IMPACT

Does not impact any other functionality other than adding demand details to demands on APPROVAL.
IMPACTED BY:
Existence of demands in the system.

WORKFLOW CONFIG

1
{
2
"RequestInfo": {
3
"apiId": "Rainmaker",
4
"action": "",
5
"did": 1,
6
"key": "",
7
"msgId": "20170310130900|en_IN",
8
"requesterId": "",
9
"ts": 1513579888683,
10
"ver": ".01",
11
"authToken": "{{authToken_amritsar}}"
12
},
13
"BusinessServices": [
14
{
15
"tenantId": "pb",
16
"businessService": "BS.AMENDMENT",
17
"business": "BS",
18
"businessServiceSla": null,
19
"states": [
20
{
21
"tenantId": "pb",
22
"sla": null,
23
"state": null,
24
"applicationStatus": "INWORKFLOW",
25
"docUploadRequired": false,
26
"isStartState": true,
27
"isTerminateState": false,
28
"actions": [
29
{
30
"tenantId": "pb",
31
"action": "OPEN",
32
"nextState": "APPROVALPENDING",
33
"roles": [
34
"EMPLOYEE"
35
]
36
}
37
]
38
},
39
{
40
"tenantId": "pb",
41
"sla": null,
42
"state": "APPROVALPENDING",
43
"applicationStatus": "INWORKFLOW",
44
"docUploadRequired": true,
45
"isStartState": true,
46
"isTerminateState": false,
47
"actions": [
48
{
49
"tenantId": "pb",
50
"action": "APPROVE",
51
"nextState": "APPROVED",
52
"roles": [
53
"EMPLOYEE"
54
]
55
},
56
{
57
"tenantId": "pb",
58
"action": "REJECT",
59
"nextState": "REJECTED",
60
"roles": [
61
"EMPLOYEE"
62
]
63
}
64
]
65
},
66
{
67
"tenantId": "pb",
68
"sla": null,
69
"state": "REJECTED",
70
"applicationStatus": "INACTIVE",
71
"docUploadRequired": false,
72
"isStartState": false,
73
"isTerminateState": true,
74
"actions": null
75
},
76
{
77
"tenantId": "pb",
78
"sla": null,
79
"state": "APPROVED",
80
"applicationStatus": "ACTIVE",
81
"docUploadRequired": false,
82
"isStartState": false,
83
"isTerminateState": true,
84
"actions": null
85
}
86
]
87
}
88
]
89
}
Copied!
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Last modified 5mo ago