Chasing someone who has already paid you is the failure this product is built to avoid. A recorded payment against that customer invoice is a never-gated stop. Two other events are easy to mix up and must not be treated as the same stop:
- Customer pays you — bank / cash you mark, Stripe Checkout on your Stripe account, or accounting sync when that connector is actually connected. PayBlah does not hold those funds.
- You pay PayBlah — Billing / checkout for your subscription. That does not settle a customer invoice and does not stop chasing.
Before you start
- Portal Pay part of it is a promised amount. It is not payment detection.
- Portal I've already paid is a message. Match the bank, then record the money.
- An open stop request is not a payment and does not mute chasing until you Accept.
How a customer payment gets in
- Mark paid → Record payment with amount and date (every plan).
- CSV / XLSX import (every plan) — new rows only. A later file that repeats an existing invoice number is skipped; it does not mark that invoice paid or reduced. Currency is not an import field.
.xlsis rejected. - Tenant Stripe Checkout — when the payments connection is usable, Checkout completion writes a tenant payment (source
payblah_link). - Accounting sync — only while the relevant Xero / QuickBooks / Sage connection is actually connected.
What you should see
- Automated Workflow sends for that invoice stop.
- Last-second send checks are designed to drop anything already paid, credited, or voided.
- The portal receipt can list the row. Attribution stays honest: paid after a reminder is not the same as “PayBlah caused this payment.”
- Your active-invoice count falls as invoices leave the chase set.
If something goes wrong
- They paid you and the invoice is still open — check the bank first, then Record payment (or wait for a tenant Stripe / connected-books update). Do not expect a re-import of the same invoice number to change it.
- They paid PayBlah instead of you — that is a billing invoice. It will not appear on the customer portal receipt.
- They only promised a part amount — open the promise, do not treat it as cash.
Related stops (not payments)
A portal dispute writes a formal dispute and sets the invoice to disputed. An active promise can pause until the date. A portal stop request does not stop chasing until Activity Accept or Decline. Confirm local rules with your own advisor.