The report that sits in a shared inbox
Your regular giving runs through a direct debit bureau or a processor such as GoCardless. Every collection run produces a report: payments collected, payments failed, instructions cancelled. The report arrives in a shared inbox as an attachment or a notification email. On a good month, someone opens it, works out which supporters are affected and makes a note. On most months, it waits.
Three months later, during a data review, it becomes clear that a monthly supporter of eight years stopped in the spring. The reason code says the account was closed, which probably means they changed bank and forgot to set up the gift again. Nobody asked. By now, the chance of a friendly reminder working has mostly gone.
Why lapses go unnoticed
The information exists. It just never reaches a person as something to do.
- Failure and cancellation reports come from the bureau or processor, not from your CRM, so they sit outside the supporter record.
- Reason codes are cryptic, and different reasons need very different responses.
- Nobody is named as the owner of regular giving follow-up.
- A failed payment and a deliberate cancellation look the same in a monthly total.
- Supporters who switch banks assume the charity will sort it out.
The gap is between the payment system and the people who look after supporters. A reason code in a CSV is not a task.
What quiet lapses cost
Regular gifts are the most predictable income a small charity has, and it is easy to lose them through inattention rather than choice. A supporter whose payment failed because of a bank switch often would have happily carried on if asked promptly.
Those who genuinely chose to stop deserve a thank-you for what they gave, and that courtesy is the thing that makes them likely to return later. Silence treats both groups badly. Your income forecasts are also wrong for months, because the figures show commitments that are no longer real.
How we build the lapse feed
- We connect to your processor or bureau's notifications or reports, for example through the GoCardless API or the bureau's daily file.
- Each failure or cancellation is matched to the supporter in your CRM and recorded on their record with the date and reason.
- Reason codes are translated into plain categories your team agrees: insufficient funds, account closed, cancelled by supporter, instruction expired, and so on.
- Each category triggers the follow-up you choose: a retry where your processor allows, a friendly email, a phone task, or a thank-you letter.
- Supporters with long or high-value giving histories are flagged for a personal call rather than an automated message.
- A regular giving view shows active, failed, lapsed and recovered supporters, so trends are visible month by month.
| Reason category | Likely meaning | Suggested response |
|---|---|---|
| Insufficient funds | Temporary shortfall | Retry if permitted, no message on first failure |
| Account closed or transferred | Supporter changed bank | Friendly email or call with a link to restart |
| Cancelled by supporter | A choice | Thank-you letter, no pressure |
| Repeated failures | Circumstances changed | Personal contact, offer to pause or reduce |
Your team decides the responses and the wording. The system makes sure every lapse is seen and has a next step.
A normal month afterwards
Collection day passes and by the next morning the regular giving officer has a short list: two payments to retry, three supporters who probably switched banks, one cancellation to thank. The long-standing supporter who changed bank gets a warm email within days, with a simple way to set up the gift again.
Finance sees the committed regular income as it really is. Trustees get a regular giving report that shows movement, not just a total.
Signs you are losing regular givers quietly
- Bureau or processor reports are opened late or not at all.
- You discover lapsed givers during data reviews, months after the fact.
- Cancellations get no acknowledgement.
- Nobody owns regular giving follow-up.
- Forecasts include regular gifts that stopped some time ago.