Schedule recurring report digests

Scheduled Reports is a first-class Settings pane — not a placeholder and not a section of Notifications. Standard users are told to ask an Owner or Admin.

Prerequisites

• Sign in as Admin or Owner.
• Timezone already set on Settings → Localisation (frozen onto each schedule when you save).
• Recipients must be live team members. You cannot type an external address.

Create a schedule

1. Open Settings → Scheduled Reports.
2. Press ＋ Add Scheduled Report.
3. Enter a Schedule name.
4. Set Send to Weekly or Monthly, then Every, On, and At.
5. Under Include reports, keep or clear:
   • Aged debt — current, 30-day, 60-day and 60+ balances
   • Collection activity — reminders sent, channels used and replies received
   • Recovery performance — payments recorded and the honest subset paid after a reminder or PayBlah link
   • SMS usage — segments and allowance. Usually empty while SMS is not launched for customer send
6. Under Send to, tick live members.
7. Leave Start this schedule immediately ticked, or clear it.
8. Press Create Schedule.

The card shows Next send in your workspace timezone. Nothing is emailed until an enabled schedule becomes due. Missed reports are never back-sent in a stack.

Edit, pause, resume, archive

1. On an existing card, press Edit schedule, change fields, then Save Changes.
2. Press Pause to stop future sends without deleting the schedule (state becomes Paused).
3. Press Resume to turn it Active again from the next window.
4. Press Archive and confirm. Delivery history stays under Archived Schedules (read-only).

Use Open Reports on the pane header for the live Reports page. One-off report export there is separate from these digests.

Expected result

An Active card lists reports, recipients, next send, and last outcome (Sent, Part sent, Not sent, Skipped, or Never sent). Last Delivery by Recipient shows per-person outcomes, including Email not configured when staff mail cannot go out.

If nothing is emailed

• Pane warning Scheduled Reports needs its database migration — no schedule can be saved until that migration has run.
• Ask an Owner or Admin to manage schedules — you can still open Reports.
• Recipient left the team — that delivery is skipped because membership is checked again immediately before every send.
• SMS usage in the digest does not mean customer texts are launched.

What this will not do

• Schedules do not email arbitrary external addresses that are not live members.
• They do not change chasing or send reminders to customers.
• They do not invent a successful send when the tenant schema is not ready.
• Recovery performance does not claim PayBlah caused every payment — it distinguishes recorded payments from the subset paid after a reminder or PayBlah link.