How to Raise Recurring Payments Without the Admin Nightmare

Costs go up. Membership fees and regular giving levels often don’t — not because a rise isn’t justified, but because nobody’s keen to be the one who takes it on.

Raising fees is a no-brainer – but doing it can be a head-scratcher.

If your members or donors pay by standing order, cheque, or a Direct Debit mandate set up individually years ago, “raising fees” means something like this: write to everyone individually, ask them to change their payment amount themselves, chase the ones who don’t, manually update your records to match, and spend the next three months fielding “I thought I’d already changed it” emails.

Multiply that by fifty, two hundred, or a thousand people, and you can see why treasurers, membership secretaries, and fundraising volunteers — usually doing this alongside a full-time job — quietly let it slide another year. And another.

For clubs: you’ve made the decision, now cut through the admin.

If your members pay by standing order, an old-style Direct Debit mandate, or anything that requires them to personally change their own payment, “raising fees” means writing to everyone, asking them to update it themselves, chasing stragglers, and manually reconciling who actually did it. That’s the part that makes committees put it off year after year — not reluctance, just dread of the process.

With WPdirectdebit, there’s no process to dread. You select the relevant subscriptions and apply the change across the board — the amount updates on the member’s existing Direct Debit directly through GoCardless. Nothing for the member to do, nothing for you to chase.

For charities: consent first, then apply it precisely

Here the order of operations matters. You need to go to donors and ask permission before increasing a regular gift — which means the actual amendment has to be applied only to the specific donors who’ve said yes, not your entire donor base.

This is where WPdirectdebit’s filtering earns its keep: before applying a bulk change, you can narrow the group down by subscription name, amount, status, or date range. If you’re rolling an increase out to donors in stages as they give permission, you can use a naming convention or the date they confirmed to isolate exactly that group — and leave everyone else untouched. Consent and execution stay properly separated: get permission the way your organisation needs to, then let WPdirectdebit apply it accurately to exactly the people who agreed.

Three ways to make the change

However you arrive at the group you want to adjust, WPdirectdebit gives you three ways to change their payment amount in one action:

• Percentage increase — apply the same proportional rise across a group (useful for an inflation-tracking adjustment)
• Fixed amount — add (or subtract) a set sum from everyone’s payment
• Set to a new value — move everyone in the group to a specific new amount, regardless of what they were paying before

Every change is on the record

Bulk changes are audited — a permanent record of exactly what changed, when, who made the change, and the old and new value for every subscription touched. For a club treasurer reporting back to committee, or a charity accountable to trustees and donors, that’s not a nice-to-have: it’s the difference between “trust me, I updated everyone correctly” and being able to actually show it.

Start early, save pain later

It’s worth being direct about this, because it changes when you should act, not just whether you should. WPdirectdebit, since it is a GoCardless Partner App, can only apply changes to mandates and subscriptions it created itself. A member or donor paying through a mandate set up directly with GoCardless, a different partner app, or any route that didn’t go through WPdirectdebit will still turn up when WPdirectdebit searches your account, but GoCardless itself will refuse the change – the same goes for any partner app.

Every month you delay moving your members or donors onto WPdirectdebit is a month where more of them land in that outside-the-system pile — each one a payment you’ll handle manually forever, or migrate individually later, and a potential landmine in your next bulk update. The earlier everyone’s inside it, the smoother every future change goes, whether that’s next year’s subs rise or your next appeal for a giving increase.

The takeaway

Whether you’re a club that just wants the admin gone, or a charity that needs to ask before it acts, the fix is the same underlying tool used two different ways: bulk changes, precise targeting, and a clear record of what happened. Get your members’ or donors’ payments into a system built for that, and “review giving levels” or “review subs” stops being the thing nobody wants to own.

WPdirectdebit brings GoCardless Direct Debit collection into WordPress — recurring payments, membership fees, donations, and bulk subscription changes, without leaving your site. Start a free 30-day trial.