How to trigger an overdue invoice quickly

How to trigger an overdue invoice quickly

To test overdue invoice handling without waiting through a real billing cycle, set the net payment term to 0 days in your QA organization's settings (or directly on a test customer). Issue a test invoice — because the payment due date equals the invoice date, the invoice will be flagged as overdue the same day, within approximately one hour.

Lago checks for overdue invoices every hour (at :25 past each hour). Once the clock job runs, any finalized invoice whose payment due date is in the past and has not been paid will be marked as payment_overdue: true. This fires the invoice.payment_overdue webhook and triggers any associated dunning campaign logic.

What to check if invoices are not going overdue

• Confirm the net payment term is set to 0 days (check both the organization settings and any customer-level overrides, since the customer-level setting takes precedence).

• Confirm the invoice is finalized and in a non-succeeded payment status — draft invoices and invoices with a succeeded payment status are excluded.

• Wait for the next :25 clock tick. Lago doesn't mark invoices overdue in real time — it runs the check once per hour.

• Invoices with a lost payment dispute are also excluded from the overdue flow.

This article reflects guidance drawn from customer case resolutions. It is not officially supported documentation and may not apply to all situations.