Payments - Introduction / Learning brief
Standing orders and scheduled payments
Your notes
In simple terms / 01
What this means in plain language
Explains how standing orders and scheduled credit transfers repeat a fixed payment on the payer's instruction, who controls them, and why they differ from a direct debit, where the payee collects and can vary the amount.
A standing order is a way to make the same payment happen automatically without starting it by hand each time. The payer instructs their own bank to send a fixed amount to the same payee on a regular schedule — for example EUR 500.00 on the first of every month — and the bank repeats that transfer until the payer changes or cancels it. A scheduled payment is the same idea for a future date: the payer sets a transfer to leave on a chosen day, either once or on a repeating pattern. Both are ordinary credit transfers on a timer, which means they are push payments: the payer starts them, sets the amount, and holds the controls. That is the key difference from a direct debit, where the payee collects the money and can vary the amount. With a standing order the payer decides everything; the payee only receives what arrives.
Complete lesson / 02
Understand the full idea, step by step
Every month, on the first, Riya opens her banking app, types the same INR 10,000.00, picks the same payee, and presses Send. Twelve times a year, the identical ritual. There is a way to hand exactly that repetition — and nothing more — to her bank.
The bank repeats the sending, not the deciding
Each run of Riya's instruction is an ordinary credit transfer — a push, exactly like the one she used to send by hand. The only addition is the timer. The amount was decided once, at set-up, and stays in force until Riya changes it; the payee was named once and does not change. The bank automates the act of sending. The decision of how much to send remains entirely, and permanently, Riya's.
Standing order
A standing order is a payer's lasting instruction to their own bank: pay this fixed amount, to this named payee, on this date, at this frequency, until amended or cancelled. A scheduled payment is the single-shot version — a transfer set today to leave on a chosen future date — and it becomes a recurring schedule when set to repeat. Both are push payments on a timer; the money moves as a normal credit transfer each time.
If Arjun raises the rent, does the standing order adjust itself?
No — and nothing else can adjust it either. Arjun cannot reach into Riya's account, and Bank Alfa will not change a payer's instruction on a payee's word. Riya must edit the standing order herself. That rigidity is not a flaw; it is the whole point of the instrument. Nothing ever leaves except exactly what the payer set.
| Standing order | Scheduled one-off | Direct debit | |
|---|---|---|---|
| Who initiates | The payer, via a lasting instruction to their own bank | The payer, in advance | The payee, collecting under a mandate |
| Who sets the amount | The payer — fixed until the payer edits it | The payer — fixed for that one date | The collector, and it may vary each time |
| Repeats? | Yes, on the payer's schedule | No — a single future date | Yes, whenever the collector submits |
| How to stop it | Cancel at your own bank, any time | Cancel before the execution date | Cancel the mandate; scheme refund rights back you up |
COMMON CONFUSION
“A standing order and a direct debit are the same thing — both are just automatic monthly payments.”
They sit on opposite sides of the push–pull divide. A standing order is a push: the payer's bank sends a fixed amount on the payer's instruction, and the payee has no part in it. A direct debit is a pull: the payee collects, and may vary the amount, under a mandate. Who initiates decides who is in charge — and who the protections are built around.
WHAT IF — The run date arrives and Riya's balance will not cover the INR 10,000.00
What happens: Bank Alfa cannot push money Riya does not have. The run fails, or is retried, according to the bank's own policy — a standing order is a bank product, not a scheme instrument, so there is no rulebook queue waiting to rescue it.
How it is handled: Riya is notified and the obligation to Arjun is now hers to settle another way. The calm practitioner's view: a failed standing order run is a signal about the account, not a fault in the instrument — and a standing order left running after an agreement ends will keep paying until cancelled, so a periodic review of one's own instructions is part of using them well.
REMEMBER IT
A standing order is the payer's hand on a timer: same amount, same payee, until the payer says stop. A direct debit is the payee's hand — with the mandate as its leash.
FOR NOW, REMEMBER
- A standing order is a fixed credit transfer the payer's bank repeats to a schedule; a scheduled payment is the one-off version.
- Both are push payments: the payer sets the amount, the date, and the frequency, and only the payer can change them.
- The instrument automates sending, not deciding — a changed obligation means the payer must edit the instruction.
- A direct debit automates the same calendar from the other side: the payee collects and can vary the amount, balanced by refund rights.
TRY IT YOURSELF
Arjun tells Riya the rent rises to INR 11,000.00 from next month. Riya's standing order says INR 10,000.00, and she does nothing. What happens on the first?
Timers and apps are recent. For centuries the payer's instruction travelled as a signed piece of paper — and cheques still clear today, mostly as images. Worth understanding, not least because they refuse to disappear.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A standing order is a fixed credit transfer the payer's bank repeats on a set schedule until the payer changes or cancels it.
- 02
Standing orders and scheduled payments are push payments, so the payer sets the amount, the timing, and the end date.
- 03
A direct debit differs because the payee collects the money and can vary the amount, whereas a standing order pays the same figure every time.
Practical use cases / 04
Where you would use this
A tenant sets up a standing order to pay a fixed monthly rent, keeping full control of the amount and the payment date.
A saver schedules a recurring transfer into a savings account on payday, moving a set sum before it can be spent.
A treasury team uses future-dated scheduled payments to line up supplier settlements for their due dates without releasing the funds early.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional tenant, Lena Fischer, owes EUR 850.00 in rent on the first of each month to a fictional landlord, Oakfield Lettings. Lena sets up a standing order with her bank: send EUR 850.00 to Oakfield Lettings on the 1st, every month, starting in September. Her bank makes the push automatically each month, and the amount never changes unless Lena edits the instruction — if the rent rises to EUR 875.00, she must update the standing order herself, because the landlord cannot. Compare her electricity, which she pays by direct debit: there the supplier collects EUR 61.20 in one month and EUR 48.90 the next as usage falls, varying the amount under the mandate Lena signed. The rent stays in Lena's hands because it is a push she controls; the electricity flexes because it is a pull the supplier controls.
Evidence & review / 07
Evidence & review
Standing orders and scheduled transfers as bank-level products layered on credit-transfer rails; the direct-debit contrast follows SEPA-style scheme design. Product names and retry behaviour vary by bank and country.
What this brief simplifies: A standing order is presented as a single clean instrument; in practice it is a bank product whose failure and retry handling is bank policy, described here generically rather than by any one bank's rules.
Sources for this brief3
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · Each standing-order run executes as an ordinary credit transfer
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · Direct debit contrast: payee-initiated collection under mandate
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.