invoice.overdue
When overdue notifications are sent, and how to read the overdue step.
RevKeen sends invoice.overdue when an unpaid invoice passes its due date, and again as it
stays unpaid. Inspect the full schema before
handling the payload.
One notification per overdue step
An overdue invoice is checked regularly, but it produces at most one notification per step. The steps are fixed and are the same for every merchant:
| Step | Sent when the invoice is |
|---|---|
0 | first overdue (on or after its due date) |
1 | 1 day overdue |
7 | 7 days overdue |
14 | 14 days overdue |
30 | 30 days overdue |
An invoice therefore produces at most five invoice.overdue notifications, one per step.
Nothing is sent after step 30. A step can arrive later than its day (for example, while a
payment was being processed), but it is sent only once. The steps do not change when you
edit your own reminder schedule; that schedule controls customer reminders, not webhooks.
Step fields
| Field | Meaning |
|---|---|
overdueStep | The step this notification is for: 0, 1, 7, 14 or 30. |
daysOverdue | The same value as overdueStep. It is the step, not a live count of days. |
Compute the current number of days overdue from the invoice's due date if you need it.
Handling
Treat each (invoice, overdueStep) pair as a single occurrence. A redelivery of the same
notification carries the same event ID, so dedupe on the event ID as described in
receiving webhooks. Reconcile the current invoice state before
acting: the invoice may have been paid after the notification was sent.