Skip to main content

​
Real-World Example

Jane has an active installment plan. She opens Schedule Plan to see upcoming dates, make an extra payment, change an eligible payment date, request a settlement date, or place the plan on hold when the rules allow it.

​
Visual Flow

​
How It Should Work

  • It should show upcoming and historical schedule transactions for the selected account.
  • It should allow only supported plan actions for the current state.
  • It should update calendar events when dates, amounts, holds, skips, or cancellations affect the schedule.
  • It should keep payment history consistent with manual and background payments.

​
How It Should Not Work

  • It should not let a consumer change past successful transactions.
  • It should not allow hold, skip, or date changes when the plan rules block them.
  • It should not update the UI without updating the underlying schedule transactions.

​
Developer Notes

  • Schedule Plan is the operational page for active installment plans.
  • Manual schedule changes often dispatch calendar jobs so external calendars stay in sync.
  • app/Livewire/Consumer/SchedulePlan.php
  • app/Livewire/Consumer/SchedulePlan/ChangeDate.php
  • app/Livewire/Consumer/SchedulePlan/RequestSettlementDate.php
  • app/Services/Consumer/SchedulePlanPaymentService.php
  • app/Jobs/UpdateCalendarEvents.php
Last modified on May 25, 2026