Keep $400 expected
Record a partial payment. The remaining $400 stays in the forecast.
Making financial changes clear before users commit
I designed income and expense scenarios for a live personal finance product, helping users understand how incoming money changes their plan.
PROJECT BRIEF
Problem. Expected income could be mistaken for available money.
My contribution. Designed allocation and payment-review flows alongside a Lead Designer.
Delivery. Forecast changes are visible before confirmation, with received funds kept separate.
01 / MONEY FLOWS
For a live finance planner, I designed allocation views that separate expected income from confirmed balances. Flow widths show proportions; labels give exact amounts. Allocating an expense to an account does not mark it as paid.
02 / PARTIAL INCOME
A payment alone cannot tell the product whether more money is due. I added a review step: when $800 arrives against $1,200 expected, the user decides whether the remaining $400 is still coming.
A partial payment keeps $400 outstanding; a final payment removes it from the forecast. Only $800 enters the balance. The review shows the consequence before confirmation: in this example, final payment reduces planned income to $3,800 and projected money left from $850 to $450.
CONTRIBUTION
Working part-time alongside a Lead Designer, I designed income and expense flows, detail views and supporting states within the live product. My focus was making planned versus received income, partial versus final payments and allocated versus paid expenses explicit.
The amounts shown illustrate the rules, not product performance.