Chasing

What stops chasing

Chasing stops or pauses when an invoice is paid, disputed, promised, paused, stopped, or the debtor is marked Never chase.

8 of 11 in Chasing

Plan: Available on every plan including trial (Starter).
Activity disputes and stop requests that halt chasing
Showcase book · Harbour Print & Signage (sample data) · light theme

Safety is part of the product model: automated messaging should not keep going after the relationship state changes.

Automatic stops and pauses

  • Paid — full payment recorded or synced; no further chase steps on that invoice.
  • Reply — customer replies; messaging auto-pauses so a human can continue the thread from Activity.
  • Dispute — dispute raised; chasing stopped until you close it (debtor right → stays off; debtor wrong → may resume).
  • Stop request — customer asks to stop; handle under Stop Requests and keep automation off as required.

Manual stops

  • Never chase on the debtor — no reminders to that company.
  • Promise to pay — pauses while the promise is active.
  • Pause on the invoice — Resume when you want the ladder to continue.
  • Settlement / write-off — closes the balance you agreed.

Verify a stop

  1. Open the invoice — status should show promised, disputed, paused, paid, or not chasing as appropriate.
  2. Check Dashboard On Hold or Needs You counts.
  3. Confirm Activity queues are clear or worked.
  4. Ensure Next action on the list no longer schedules unwanted sends.

What this does not do

  • Stops inside PayBlah do not always reverse a message already in flight at the exact send second — work Approvals early for Firm/Final.
  • They do not delete Sent Log history.
  • They do not make PayBlah a collections law firm; they only control your automation.

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).