Recovery automatically retries failed subscription payments and reminds customers, so you collect more without chasing them manually.
One recovery flow for every failed subscription payment.
When a subscription payment fails, the invoice enters recovery. QuickBill then follows your recovery policy:
It retries on a fixed-day schedule
It emails the customer when an attempt fails
It stops as soon as a payment clears
If it's still unpaid at the end, it applies your end-of-recovery action
Only one policy is active at a time. Open Billing → Dunning to see it.
Your recovery numbers, queue and policy in one place.
| Card | What it shows |
|---|---|
| Failed Payments | How many payments are in recovery, and the amount at risk. |
| Retry Scheduled | Invoices awaiting their next attempt. |
| Recovered (30d) | Payments recovered in the last 30 days, with the recovery rate. |
| Avg Days to Recover | How long recovery took, over the last 30 days. |
The switch on the Your Recovery Policy card turns recovery on or off for all customers. While it is off you see "Failed payments won't be retried automatically and no reminder emails are sent. Invoices stay due for manual follow-up." Click Turn recovery on to switch it back on.
To stop recovery for just one invoice, use Pause on that invoice instead.
Shows the active policy — its retries, payment attempts, recovery window and timezone — and What the customer experiences, day by day. Click Edit in Policy Settings → to change it.
Subscription invoices whose payment failed and are now in recovery.
Search by invoice number or customer, or filter by status.
| Column | What it shows |
|---|---|
| Customer | The customer, with the invoice number. |
| Amount | The amount due. |
| Attempts | Attempts made out of the maximum, e.g. 2 / 3. “Final” marks the last attempt. |
| Last Failure | Why the last attempt failed. “may work later” means a retry can succeed; “needs the customer” means the customer has to act. |
| Next Retry | When the next attempt runs, or the date a paused invoice resumes. |
| Status | See the table below. |
| Actions | What you can do with this invoice. |
| Status | Meaning | Actions |
|---|---|---|
| In Progress | Still retrying. | Retry now, Pause (Stop recovery on the final attempt), View timeline |
| Paused | Retries on hold until a date. | Resume, Stop recovery, View timeline |
| Not recovered | All attempts used up. Shown as “Exhausted” in the status filter. | View timeline |
| Stopped | Recovery was ended by hand. | View timeline |
| Recovered | Paid. | View timeline |
When a subscription payment fails, the invoice shows up here automatically. With nothing in recovery you see "All caught up — no failed payments right now."
Charge the customer's saved payment method right away.
Click Retry now on the invoice
Add a Note (optional) and confirm
Watch the result
If the customer has no saved payment method the retry fails with "The customer has no saved payment method to charge."
Use this when the customer promised to pay by a date.
Click Pause on the invoice
Set the Expected payment date
Add a Note (optional) and confirm
Click Resume on a paused invoice. It rejoins the schedule at its next step.
End recovery for one invoice.
Click Stop recovery on the invoice
Enter a Reason
Confirm
The invoice stays payable and no end-of-recovery accounting action is applied.
Everything that happened to one invoice in recovery.
Click View timeline on any invoice in the queue. You see:
Set it up once, and it runs on its own.
Go to Dunning → Edit in Policy Settings →, or Settings → Dunning & Recovery → Policy Settings. Click Create policy, or Edit on an existing one.
Name the policy
Set the Recovery window (days)
Build the retry schedule
Check What the customer experiences
Choose what happens at the end
Save & Close or Publish
| Day | Attempt | Email if it fails |
|---|---|---|
| Day 1 | First payment attempt | Payment failed |
| Day 2 | Retry 1 | Account at risk |
| Day 3 | Final retry | Final warning |
Retries run on a fixed-day schedule, in your organization timezone. Reset to default brings this schedule back.
The accounting outcome when an invoice is still unpaid.
| Option | What happens |
|---|---|
| Keep the subscription active | Customer keeps access; you chase the invoice separately. (Default) |
| Pause the subscription | Access is suspended; the subscription can be resumed later. |
| Cancel the subscription | Subscription ends and stops billing. |
| Option | What happens |
|---|---|
| Keep due | Invoice stays open as a receivable; follow up manually. (Default) |
| Mark as not paid | Closes the invoice as unpaid; the receivable is written down. |
| Void | Reverses the invoice; revenue is removed. |
The invoice outcome affects your receivables and revenue recognition.
Only one policy is active at a time — that's the one your dashboard follows.
| Status | Meaning | Actions |
|---|---|---|
| Built-in | The built-in default, kept for reference. | View |
| Active | Your dashboard follows this policy. | Edit, View |
| Draft — unpublished | Not live yet. Publish it to switch your customers onto it. | Edit, Publish, Delete, View |
| Archived — previous | Replaced by a newer publish. | Edit, Publish, Delete, View |
Publishing a policy makes it active immediately and moves the previous active one to archived history.
Deleting a draft changes nothing for your customers, because it was never published. Deleting an archived policy removes it from your history permanently — this can't be undone.
What your customer receives during recovery.
| When it's sent | |
|---|---|
| Payment failed | After a failed attempt, if the schedule says so. |
| Account at risk | After a failed attempt, if the schedule says so. |
| Final warning | After a failed attempt, if the schedule says so. |
| Payment received | When any attempt clears and recovery ends. |
Pick No email on failure on a row to skip the email for that attempt. Click Preview on a row to read the full email. Emails use your Portal Branding and fill in the customer name, subscription, invoice number, amount, attempt number, next retry date and your support email.
A read-only record of every recovery action — what happened, to which invoice, and who did it.
Open Dunning → Dunning Logs →. Filter by:
Each entry shows When, What happened, the Invoice / Customer, the Case status, the Change, By (System for automatic actions) and the Reason.
Auto-recovery isn't available in India yet.
Under RBI and NPCI rules, a saved card can't be charged without a registered e-mandate. We're building an NPCI e-mandate–compliant recovery flow. In the meantime, customers still get a secure payment link to settle failed invoices.