1. Added fields Occupancy type Trade relationship.

2. Challan feature for TL application with pending payment status.

3. Ad Hoc / penalty / Rebate reasons customization.

4. “Modify & Renew” & “One-Click Renewal” Buttons to apply for Renewal along with the Disclaimer added, details in the shared document and following Jira ticket:- ​https://digit-discuss.atlassian.net/browse/UKI-465.

Customized Fields

1. Thana (Police Station): Police boundary is a separate type of hierarchy to be defined in the system. Value to be selected from police boundary type defined in the system. 

2. Road Type: Value to be selected from the master defined for road type. Unit rates are defined based on three masters road type is one of them.

3. Year Of Construction: Year of construction is captured to calculate the age of the building unit. Depreciation is given on Annual Value.

4. Inner Dimensions Known [Yes/ No](enabled Only if the property is residential): In case inner dimensions are known, it is used to calculate carpet area.

5. Rooms Area( enabled Only if inner dimensions are available): Total area of all the rooms in a building unit.

6. Balcony, Corridor, Kitchen, Store Room Area( enabled Only if inner dimensions are available): Total area of Balcony, Corridor, Kitchen, and Store Room

7. Garage Area( enabled Only if inner dimensions are available): Area occupied by Garage in house

8. Bathroom & Staircase Area ( enabled Only if inner dimensions are available): Bathroom and Staircase area

9. Covered Area/ Plinth Area ( enabled Only if inner dimensions are not available, or property is non-residential): Total plinth area/covered area of building unit, It will be read-only in case inner dimensions are known and usage is residential

Other customizations

1. View demand, collection and balance (DCB Section to be added to assessment detail)

2. Consolidated demand bill and collection

3. Counter search and pay property tax

1. Added Citizen and Employee copy in Receipt.

1. Localization support for user manuals upload and view(need to check if we have done it or not)

2. Localization support for SMS.

1. Capital Value system Implementation.

2. Assessment/Reassessment.

3. Apportioning Logic in case of Partial payment

4. Advance Collection

5. Generation and customization of Demand bill in Property tax. (To issues Demand notices to the citizen few state/ULB level customization is required, as well as the need to customized the way these manual bills are generated, information regarding when the notices served to the citizen etc. needs to be captured as per the state/ULB requirement.)

6. Recalculation of tax with its all its intermediate calculation on the revision of unit rates

7. Registration Department Integration API for PT for new property creation/mutation

8. UI for all masters/ rates screens (Add, Edit, View) with an audit trail for rates changes/ maintaining history

9. Notices: assessment, mutation, recoveries, tax exemption, miscellaneous etc. 

10. Subdivision, amalgamation, vacancy remission, court cases, write off (This feature may need for other revenue modules too)

11. GIS integration - QC of surveyed data, two-way integration with the GIS system to perform the actions seamlessly

12. DCB screen :

We would be requiring a DCB breakup after we search for a property as shown in the attached image at the red highlighted area. 

The breakup could be a similar one as done for A.P with a drop-down arrow.

We need the breakup for the demand, collection and rebate year wise as it displayed in the image attached for A.P.

We need the below-mentioned columns for which the respected Tax head codes are to be considered:

• Interest    -PT_TIME_INTEREST

• Rebate    -PT_TIME_REBATE. PT_PROMOTIONAL_REBATE

• Tax    -PT_TAX -SWATCHATHA_TAX -PT_LATE_ASSESSMENT_PENALTY

1.  Verification of Trade License according to Property id/UID.

2. Data migration and Data entry (Add/Edit) with rollout dashboard for review and monitoring.

3. Report: Trade license new/renew/quick renewal /renewal with the edit. Application and collection reports

4. Required Upload document configurable with application type whereas trade type may have additional required documents configuration, it is implemented in ukd, but missing in product, need to verify once.

5. Trade License Application created date shall be shown in the view screen and in the downloaded application form. (​https://digit-discuss.atlassian.net/browse/RDS-11 )

1. NN Rishikesh raised a requirement for some additional fields on the MCS receipt. these are;

   1. Payer's Father name

   2. Payer's Mohalla name

   3. Payer's Address

   4. Payer's account number

   5. Comments at the time of applying the MCS

2.  Challan features similar to trade licenses for universal collection.

1.  User Login Report for Citizen as well as Employee: For Tracking User Adoption, following Report required from the UKD. 

This will greatly help us to understand citizen/employee engagement/adoption of the application.

1. All Dropdown across modules should be in sorted order (​https://digit-discuss.atlassian.net/browse/RDS-10 )

2.  Search and pay feature for the anonymous user for TL. PT and MCS.

3. Single sign-in screen for employee and citizen

4. Rollout dashboards with all combinations and aggregation needed for review and monitoring 

5.  Integration with finance for demand and collection - Support required to configure the integration between PT and finance. Similar integration required for all other revenue modules.

6. Add/Edit mobile number with proper authentication and verification with the owner’s details.

7. ULB/City Name for which application belongs shall be shown in the "My Applications" screen in citizen login.(​https://digit-discuss.atlassian.net/browse/RDS-12 )

8. Fallback mechanism - the system should automatically pick the values in case the ULB level configuration is missing.

9. Localised SMS defaulted for State/ULB, or based on user selection.