Recurring payments record an arrangement to give regularly. They are separate from the individual payments received. Saving an arrangement does not authorise a new Direct Debit mandate or prove money has arrived.
Creating one requires relationships:write:fundraisingactivities and access to the associated records. Reading fundraising/payment information requires the corresponding read permission.
Add an arrangement
- Open the contact’s profile and choose Set up recurring payment.
- Enter Amount per instalment and its currency.
- Set Every to an interval of at least 1 and choose Period: Week(s), Month(s), or Year(s). For example, 2 weeks means fortnightly. Days is not an available period.
- Choose the Collection day rule and complete its day values using the table below.
- Optionally set Start date, Payment method and Bank account. The method and account lists use your beehive’s active configuration.
- Choose the Collection provider: who collects the money. See Choose a collection provider below. Leave it empty for an arrangement nobody collects automatically, such as a standing order.
- Optionally turn on Link to an organisation? or Link to a resource? and choose the record.
- Choose Set up recurring payment. You’ll see “Recurring payment set up”, and the arrangement appears in the contact’s activity feed shortly.
Choose a collection rule
| Rule | What to enter |
|---|---|
| Day of month | Day 1–28 |
| Day of month (skip weekends) | Day 1–28; move a weekend collection to the following working day |
| By working day number | Working-day number 1–23 |
| Day of week | Monday through Sunday |
| Annual date | Month 1–12 and day 1–28; offered only when Period is Year(s) |
Changing the rule resets its day inputs. Changing from Year(s) while Annual date is selected switches back to Day of month, so review the day again before submitting.
Choose a collection provider
The Collection provider list has up to two groups:
| Group | What it means | What to do next |
|---|---|---|
| Integrated platforms | A provider connection whose settlements ThirdSectorBee reconciles automatically, such as a Stripe account. A connection is listed only while it’s enabled and its integration is turned on for your beehive | Enter the provider’s Subscription or mandate reference for this supporter. The connection’s payment method and bank account are filled in for you if those fields are still empty; you can change them |
| External — collection run managed via files | A collection system, such as a Bacs bureau, that collects outside ThirdSectorBee | Nothing more on this form. The form reminds you that collections are not reconciled automatically: record each run from the platform’s file |
If the list says “No collection providers configured”, an administrator can add them; see Connect a payment provider for reconciliation.
Linking an integrated platform associates this arrangement with a subscription or mandate that already exists at the provider, so its settlements can be attributed. It doesn’t create or authorise a mandate. The link is saved only when both the connection and the reference are filled in.
If settlements aren’t being attributed, check the connection and reference, then look for exceptions on the Reconciliation page; see Resolve reconciliation exceptions. Don’t create a second arrangement because the first is slow to appear in the activity feed.