opencollective
Alert admins when approving an expense if the balance is too low to pay it
User story
As a collective administrator I want to be warned that an approved expense will not be paid if there are not enough funds in the collective, project, or event to pay an expense.
Best solution for this problem
When marking an expese as approved the user should be alerted that there is not enough money in the collective to pay the expense.
Metrics
Reduction in the time between approval and paid expenses
Related issues
https://github.com/opencollective/opencollective/issues/4747
FYI adding this because of a current issue with a collective that has had an approved, unpaid expense for ~15 days.
The way the Platform was conceived, having a low/zero balance should not prevent an Expense to be approved by the Collective admin. It will be paid when there is enough money.
We need @opencollective/design to make sure we put the warning at the right place & with the right styles
Week 3 tasks:
- [ ] Design the placement of the error message
- [ ] Share a loom for feedback
- [ ] Share the production-ready file with the Dev team
Questions:
- Currently, can a host admin tap on the 'pay' button if the collective doesn't have any money, or is it disabled?
- If yes, what is the current behavior that happens after the host admin taps on the pay button? For example, does it go to the 'processing' stage, does it show a toast error, or does go back to the 'approved' state?
- Do we just want to inform the user, or do we also want to allow any actions like 'don't pay now' etc.?
can a host admin tap on the 'pay' button if the collective doesn't have any money
Nope:
Do we just want to inform the user
The important thing here (which is missing from the OP, my bad) is just to set the expectation than an approved expense won't be paid immediately. The expectation should probably be pushed down to the submitter too so maybe I'll create a separate issue for that.
The production-ready Figma files can be found here.
We used the alert banner to inform users and collective admins about the expected behavior.