Set the period at the top of Reports, then read two panels: COLLECTION ACTIVITY (what left) and PAYMENT TREND (what was recorded vs what can be attributed). A scheduled digest calls the second pair Recovery performance. Same honesty rule either way.
Before you start
- Sign in and open Reports.
- Pick This month, 3 months, 6 months, or 12 months. These two panels follow that pill.
- Only overdue payments count: the paid date must be after the invoice due date. On-time settlement never enters these headlines.
- Totals use the home currency from Settings → Localisation.
Read Collection Activity
- Find the panel eyebrow COLLECTION ACTIVITY. The heading is the period label (for example this month so far).
- Read Reminders sent and the line “across N customer(s).”
- Read the email vs text split.
- Read Replies received and open Open activity to review them.
- Use the comparison hint (“+N vs …”) as context only — it is a count delta, not a success score.
What “Reminders sent” includes
A reminder counts only when all of these are true:
- It is an outbound reminder (not a reply, not an internal note).
- Its status is sent, delivered, or bounced — the message left toward the carrier or mailbox.
- It has a real sent time inside the selected period.
Held, queued, awaiting approval, and failed drafts do not count. Firm and Final wording still needs a person in Activity before it can send; those waiting items appear under NEEDS ATTENTION → Reminders awaiting approval, not here.
A bounced reminder still counts as sent, because it left. Texts count only when a text reminder actually left. Settings can say SMS is not available; a zero text count is then expected, not a fault.
Read Payment Trend
- Find PAYMENT TREND / Recorded Payments vs. Attributed Recovery.
- Read the two totals: recorded and after reminders / link. They match the KPI tiles Payments recorded and Paid after reminders for the same period.
- Read the monthly columns. This month still draws six columns for context; the totals above the chart stay month-to-date.
- Use the days-to-pay row under the chart as a habit hint for attributed overdue payments. A dash means no attributed overdue payment in that month.
How attribution is decided
Two different questions sit on this page. Keep them separate.
- Payments recorded — every overdue payment in the period, whatever recorded it: accounting sync, mark paid, a provider webhook, or a PayBlah link. Attribution none stays in this number.
- Paid after reminders — only the attributed subset:
- PayBlah payment link — hard attribution. The customer paid through your PayBlah link. This is the only source PayBlah can prove.
- 14-day window — the money landed within 14 days of a reminder on that invoice that was sent or delivered. The 14-day window is fixed. You cannot widen it.
If there was no PayBlah link and no sent or delivered reminder in that window, the payment stays recorded and stays out of the attributed headline. PayBlah does not hold the funds on a payment link; the link is only an attribution source.
A scheduled digest states the same rule in one sentence: the second figure is attribution, not a claim that PayBlah caused the payment. Confirm how you describe these numbers with your own advisor. This article is not legal advice.
Do not collapse both figures into the word collected. The live labels are Payments recorded and Paid after reminders (or “after reminders / link” on the chart). A sidebar tip may say “Collected after reminders” for the narrower amount only.
Needs Attention and Top Customers
Those panels sit on the same page and ignore the period pill. They are not part of Collection Activity or the attributed recovery total. Needs Attention is four live queues. Top Customers lists who is holding open money (up to eight on screen; the CSV has the full list).
What you should see
Reminders sent never includes drafts waiting for approval. Paid after reminders is less than or equal to Payments recorded. If you explain the attributed figure, you can name the rule (PayBlah link, or 14 days after a sent or delivered reminder) without claiming PayBlah caused the payment.
If something looks wrong
- Activity looks empty while the approval queue is full — those messages have not left, so they must not count as sent.
- Recorded is larger than attributed — expected for mark-paid, sync, and unchased invoices.
- A same-day on-time payment is missing — overdue-only. Paid-on must be after due-on.
- Mixed currencies look short — only the home currency is in the headline.
- The page CSV has no activity or recovery rows — expected. That file is summary + aging + customers only. Use the screen or a scheduled Recovery performance digest for the honest pair.
What this does not do
- It does not prove causation.
- It does not send, approve, or threaten. You remain the creditor.
- It does not score staff on “collections.”