Compare both start times with the same boundary
Synthetic rule: validity is tested at the session start. P-V has one held session and becomes unusable on 16 Oct at 00:00. The customer requests a move from 15 Oct 18:00 to 16 Oct 09:00. Keep the original booking until an eligible replacement funding source and replacement place are established.
| Option | Start | Funding | Decision |
|---|---|---|---|
| Original B-V | 15 Oct 18:00 | P-V / before expiry | Keep valid |
| Replacement using P-V | 16 Oct 09:00 | P-V / after expiry | Not eligible |
| Replacement using P-V2 | 16 Oct 09:00 | P-V2 / 2 valid sessions | Possible if selected and place exists |
Resolve the new allocation before releasing the old one
- Read original allocation, proposed start and package boundaries.
- Identify an eligible source for the proposed session and record the customer’s choice.
- Complete the move with linked old-release and new-hold entries; then replace reminders.
A rejected move must not consume a second session or remove the original booking.
If P-V2 is selected, what is its available balance after the new hold?
Show the worked answer
One available and one held. P-V’s old held session returns under the move policy and keeps its original expiry; it does not become a P-V2 session.
The move record needs both package IDs, enabling a later cancellation to return the replacement allocation to the correct source.