Question
I selected a specific day of the month (e.g. the 1st) for my recurring payment, but when I chose Direct Debit, I was charged immediately. Why didn’t it wait until the selected date?
Short Answer
This is expected behaviour for Direct Debit payments and is not a system error.
With Direct Debit (bank account payments), the first payment is processed immediately when a donor sign up. The selected “Day of Month” applies to future recurring payments only.
Why
When setting up a recurring Direct Debit, there are two separate steps:
- Mandate / authority creation (permission to debit the bank account)
- Ongoing scheduled debits
Because bank debits (e.g. BECS in Australia) involve bank file processing, clearing timeframes, and validation periods, most gateways treat the first transaction as:
The initial payment + confirmation of the debit authority
For example:
- You sign up on 16 February
- You select 1st of each month as your payment day
What happens:
- 16 Feb → Initial payment is processed
- 1 Mar → First scheduled monthly debit occurs
The Day of Month setting controls future payments — not the initial one.
This approach ensures:
- The payment authority is validated immediately
- The organisation begins collecting right away
- There are no long gaps before the first payment
🔵 Why Credit Cards May Behave Differently
Credit card payments operate differently because they:
- Authorise in real time
- Don’t require bank file batching
- Don’t have the same clearing and return windows as Direct Debit
Depending on configuration, credit card recurring payments may:
- Start immediately and recur monthly from that date
- Or wait until the selected future date
Direct Debit rails, however, are less flexible due to banking processes.