Real-World Example
Jane changes an installment payment date. The portal updates the internal schedule immediately and then updates Google or Microsoft Calendar when live sync is enabled. The same process keeps external events aligned when an automatic payment action moves, skips, deletes, or completes a scheduled installment. When an automatic skip moves an unpaid installment to the end of a plan, its reminder follows the new payment date at noon Eastern, with a 30-minute duration, Free availability, and a reminder 15 minutes before. Existing Google and Outlook reminders are updated; a missing reminder is created. Retrying the skip or calendar update keeps one reminder for that installment in each connected calendar. The sync runs after the saved schedule commits and respects each provider’s live-sync setting.Visual Flow
How It Should Work
- It should create, update, delete, or change amounts on external events when live sync is enabled.
- It should sync changes made by the consumer and changes made automatically, including an auto-skipped installment moved to the end of a plan.
- It should update external events only after the portal schedule has been saved.
- It should keep the internal schedule as the source of truth. Held payments remain visible in the portal, while their upcoming external calendar events are removed until restart.
- It should retry provider cleanup without forgetting which events still need removal, and restore eligible events once the plan resumes.
- It should handle Google and Microsoft sync without blocking the consumer page.
How It Should Not Work
- It should not let a calendar job change payment truth by itself.
- It should not fail the main payment action only because an external calendar provider is unavailable.
- It should not update events for consumers who disabled live sync.
- It should not create duplicate events for installments already synced.

