Disputes

How disputes stop chasing

While a dispute is open, automated chasing on that invoice is designed to stay off. Closing the dispute is what turns the ladder back on — and only when the outcome says the customer was wrong or the debt is otherwise still due.

4 of 4 in Disputes

Plan: All plans. Never-gated safety behaviour.
Disputes list stating chasing is stopped on the disputed invoice
Showcase book · Harbour Print & Signage (sample data) · light theme

While disputed

  • Activity shows Chasing stopped on the open dispute card.
  • Sequence enrolment should not keep sending ladder steps for that invoice.
  • You can still message carefully from staff tools — do not use ad-hoc sends to recreate the ladder while a dispute is unresolved.

What else stops chasing

For context, automation also stops or pauses on payment, active promises, manual pause, kill switch / sending halt, and similar safety gates. Dispute is the stop for “we disagree on the bill.”

When chasing may resume

  • Outcome Debtor was wrong — ladder may continue from an appropriate step.
  • Outcome Debtor was right — keep automation off; fix or cancel the invoice.
  • Outcome Settled — keep automation off; complete settlement recording.

Firm and Final still need humans

If chasing resumes and later steps are Firm or Final, those messages still wait in Activity → Approvals when approval is enabled (default on). A dispute resolution never bypasses that human gate.

Because this lifecycle is product-changing, if an invoice looks disputed but still has a next send scheduled, pause it manually and tell Support — do not assume the UI is ahead of the engine or vice versa.

Related guides

Raise a dispute Resolve or close a dispute When a payment is detected How the escalation ladder works Approve Firm and Final messages

PayBlah is accounts-receivable automation software. You remain the creditor. Confirm local rules with your own advisor for your territory (US, UK, Ireland, or Australia).

All knowledge base articles Start free trial