Description:
The Pending Settlements stat on the dashboard does not change even after a payment is successfully marked as Settled — not immediately, not after navigation, and not even after a full refresh or app reload. This indicates a deeper issue in how the pending amount is being calculated or updated on the backend.
Observed Behavior:
- User marks a settlement as “Settled”.
- The transaction is marked correctly in the Settlement Plan.
- But the Pending Settlements amount on the dashboard remains the same, even after reload.
- The system continues to count already-settled dues in the pending total.
Expected Behavior:
- Once a settlement is marked as Settled, the amount should be removed from the pending total shown on the dashboard.
- The dashboard should accurately reflect the actual pending dues only.
Possible Causes:
- Backend logic not excluding settled records from pending total.
- Caching or stale data in dashboard endpoint.
- Data structure mismatch (e.g., settlement status not updating where dashboard pulls from).
Suggested Fix:
- Investigate the backend query or aggregation logic used to calculate pending settlements.
- Ensure settlements with
status = "settled" are excluded from the pending total.
- Add a test case to verify that marking as settled immediately affects the pending value.
Impact:
- Shows incorrect financial data to the user.
- Breaks trust in core dashboard insights.
- Can lead to double payments or confusion over what’s actually pending.
Description:
The Pending Settlements stat on the dashboard does not change even after a payment is successfully marked as Settled — not immediately, not after navigation, and not even after a full refresh or app reload. This indicates a deeper issue in how the pending amount is being calculated or updated on the backend.
Observed Behavior:
Expected Behavior:
Possible Causes:
Suggested Fix:
status = "settled"are excluded from the pending total.Impact: