Keep a bill separate from its payments
On November 10, I added partial-payment tracking for expense bills in RentFlow. An invoice and the payments against it describe related but different events. Recording the whole bill should not make a later instalment disappear, and choosing an expected payment date should not make an unpaid balance look settled.
The expense form gained an explicit option to track an expense as an unpaid bill. Once selected, the user can add dated payment records, see the amount recorded as paid and inspect the remaining balance. The invoice stays in its own month, while the cash view uses the recorded payment dates. This gives the same expense a clear relationship to both its invoice record and the movement of money, without duplicating the original bill for each instalment.
The expected date remains a separate choice. It can be left unknown or set to a specific date, allowing the outstanding balance to appear as a forecast without marking it paid. The calculations preserve that distinction: actual recorded payments contribute to cash paid, while a remaining amount with no known date stays an item needing attention. The interface explains this difference beside the payment fields, where it affects how the entry is completed.
The change also keeps the feature bounded. Tracked payments belong to one expense per invoice, rather than being combined with recurring or split-month entries. The form rejects recorded totals above the expense amount. Existing ordinary expense behaviour is retained for entries that do not opt into bill tracking. Regression cases cover saving a partially paid bill and carrying its dated payments into the cash-flow summary.
Reflection
RentFlow needs to distinguish what an expense represents from when it is paid. Explicit payment records make that distinction visible. They improve the meaning of the software's figures without turning an expected date into evidence that a payment happened.