Bug #7776
closedI tested the Expense module, identified several issues, and resolved them related to the backend API, UI, frontend logic, and validations. Issues are as follows:
Tested Date:
02/17/2026
Raised by Tester:
Description
Fixed an issue where Action History data was not populating from the backend.
Resolved the restore alert issue for expenses.
Fixed the payment splitting logic, which was not working correctly.
Disabled the amount field after the first payment is completed.
Corrected the frontend payment logic to properly calculate and display due amount and full amount.
Added proper validation for the Expense Name field during creation, including length limits to prevent invalid or unnecessary data from being stored in the database.
Fixed field mapping issues that occurred while selecting an Expense Type.
Subtasks
Related issues