> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/deploy/configure-digit/services-overview/business-services/billing-service/bill-amendment-service-configuration.md).
# Bill Amendment Service Configuration
## **Overview**
The consumer sometimes needs additional amounts (Amendments) added to their bill due to reasons from outside of the system. The addition of amounts happens 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.
## **Pre-requisites**
* Prior knowledge of billing-service in the DIGIT framework.
## **Key Functionalities**
Amendment mainly works with two types of functionality as follows:
* Amendment
* Demand
Bill Amendment provides a separate flow that triggers the workflow for validating the process of adding additional amounts to existing demands. This validation was earlier available only to the respective modules. An amendment is allowed only when there is a need to add or reduce the amount from the existing bill belonging to an entity. The reasons for such cases could be:
1. Court case settlement
2. One time waiver
3. Write-offs
4. DCB correction (old demands in paid status)
5. Property tax remission
**Criteria:**
Below are certain prerequisites to creating an amendment,
1. presence of demand in the billing system
2. any one of the reasons listed above
3. valid document proof for the reason
4. there is no other amendment already in the workflow
**Procedure:**
The process of adding an amendment in specific scenarios is given below.
There are two scenarios on how an amendment is completed 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 a partial payment.
3. Create an amendment for the same consumer code (with demand detail → DD2).
4. Approve the amendment - the response should return an amendment with the status CONSUMED.
5. Search the demand or fetch the bill for the consumer code. The demand/bill should contain demand details of the demand and amendment together with 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.
4. Create new demand for the consumer code (with demand detail → DD3). The demand response should contain two demand details DD1 and DD2 saved to the demand.
5. The amendment search returns 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.
## **Configuration Details**
[Billing Service | Configuration-Details:](/local-governance/deploy/configure-digit/services-overview/business-services/billing-service.md#configuration-details) Refer to billing-service config for MDMS data. The amendment makes use of the same data set.
**WORKFLOW CONFIG:**
```
{
"RequestInfo": {
"apiId": "Rainmaker",
"action": "",
"did": 1,
"key": "",
"msgId": "20170310130900|en_IN",
"requesterId": "",
"ts": 1513579888683,
"ver": ".01",
"authToken": "{{authToken_amritsar}}"
},
"BusinessServices": [
{
"tenantId": "pb",
"businessService": "BS.AMENDMENT",
"business": "BS",
"businessServiceSla": null,
"states": [
{
"tenantId": "pb",
"sla": null,
"state": null,
"applicationStatus": "INWORKFLOW",
"docUploadRequired": false,
"isStartState": true,
"isTerminateState": false,
"actions": [
{
"tenantId": "pb",
"action": "OPEN",
"nextState": "APPROVALPENDING",
"roles": [
"EMPLOYEE"
]
}
]
},
{
"tenantId": "pb",
"sla": null,
"state": "APPROVALPENDING",
"applicationStatus": "INWORKFLOW",
"docUploadRequired": true,
"isStartState": true,
"isTerminateState": false,
"actions": [
{
"tenantId": "pb",
"action": "APPROVE",
"nextState": "APPROVED",
"roles": [
"EMPLOYEE"
]
},
{
"tenantId": "pb",
"action": "REJECT",
"nextState": "REJECTED",
"roles": [
"EMPLOYEE"
]
}
]
},
{
"tenantId": "pb",
"sla": null,
"state": "REJECTED",
"applicationStatus": "INACTIVE",
"docUploadRequired": false,
"isStartState": false,
"isTerminateState": true,
"actions": null
},
{
"tenantId": "pb",
"sla": null,
"state": "APPROVED",
"applicationStatus": "ACTIVE",
"docUploadRequired": false,
"isStartState": false,
"isTerminateState": true,
"actions": null
}
]
}
]
}
```
## Integration **Details**
### Integration Scope
Amendment integration helps organizations add additional value to the demand without any change in the system.
### Integration Benefits
* Easy to create and simple process of updating demands
* Helps ease changes into the system which are not part of normal functionality - Amendment of bills in case of legal requirements.
### Steps to Integration
This is integrated into the billing system by default.
1. The amendment facility can be used in case of a legal issue to add values to existing demands using /amendment/\_create. The parameter /amendment/\_update is used to cancel the created updates or update configured workflows.
### Interaction Diagram
{yet to be added}
## **Doc Links**
**API Definition**
[API SPEC FOR BILL-AMENDMENT](https://raw.githubusercontent.com/egovernments/business-services/master/Docs/billingservice/BillAmendment/v1.0.yml)
**API List**
| Description | Link |
| ----------------------------- | ------------------------------------------------------------- |
| /amendment/\_create, \_update | |
[**](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/local-governance/deploy/configure-digit/services-overview/business-services/billing-service/bill-amendment-service-configuration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.