Documentation
Reminder scheduling should feel predictable, inspectable, and tied to the due date.
This guide explains how ChaseNow calculates pre-due checkpoints, due-date reminders, and weekly overdue reminders after the invoice goes late.
Steps
How to handle reminder scheduling in ChaseNow
Start with the due date because the full sequence is anchored to it.
If the initial send happens far enough in advance, ChaseNow keeps the normal pre-due checkpoints.
If the first send happens close to due date, missed checkpoints are skipped and the next valid milestone is used.
After due date, the invoice moves into weekly overdue reminders until resolved.
Milestone logic
Each queued reminder mapped from the due date
Notes
Operational notes
The timeline shown in the UI should match the real backend reminder schedule exactly.
Skipped checkpoints are normal when the invoice enters the system late.
Weekly overdue follow-up should continue until payment, pause, or write-off.
FAQ
What if the invoice is already overdue when I add it?
The first message should reflect that overdue state and the next reminder should continue from the weekly overdue cadence.
What if I send the invoice only one day before due date?
ChaseNow should adapt the first message to that short window and still queue the due-date reminder appropriately.
Related pages
Next step
Use the docs, then put the workflow to work.
The goal of the documentation is not to describe software in the abstract. It is to help you get an invoice into ChaseNow and keep the follow-up moving.