Troubleshooting

A payment was not detected

If the customer paid but reminders continued, either PayBlah has not seen the payment yet or it was recorded against the wrong invoice.

3 of 9 in Troubleshooting

Plan: Payment links / portal detection on Growth+. Sync-based detection on every plan when accounting is connected.
Dashboard overview used to verify collected and open balances
Showcase book · Harbour Print & Signage (sample data) · light theme

Chasing is designed to stop when a payment is recorded — by hand, through a payment link, or from an accounting sync.

Quick checks

  1. Open the invoice. Is the balance actually zero in PayBlah?
  2. If they paid in your accounts package, confirm the connection's last successful sync. Trigger or wait for the next poll; re-connect if expired.
  3. If they paid by bank transfer outside both systems, record the payment on the invoice so the ladder stops.
  4. If they used a payment link, confirm the link/provider is live on your plan (portal & links are Growth+).
  5. Check Activity for a payment-recorded event or webhook if you integrate that way.

After you record it

Reminders for that invoice should stop. If a message was already queued for the same day, confirm in Activity that nothing further is scheduled.

Prevent the next miss

  • Keep accounting connected and watch sync-failed notifications.
  • Train the team to record offline payments the day they hit the bank.

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