What is a standing instruction?

The difference that matters in a product

A standing instruction is a push. Your bank holds the order, releases a fixed amount on a fixed date, and the recipient has no say. If the amount changes, you must change it. If you cancel, you cancel it at your own bank and it stops.

A mandate is a pull. The biller holds the permission, initiates each collection, and can usually vary the amount within agreed limits. If the amount changes, they change it. If you cancel, you can cancel at your bank, but the biller may still believe the arrangement is live.

For anyone building recurring billing, the consequence is that these are not interchangeable options to expose in a settings screen. A standing instruction cannot handle a variable bill. Usage-based pricing, changing subscription tiers, taxes that shift, or any amount not known at setup time all require a pull. A push arrangement forces the customer to act every time the price changes, which they will not do, and your collection quietly falls short.

Conversely, a push is the more customer-controlled instrument, and for a fixed obligation where the payer wants certainty, it is often what they would choose if asked.

Where the terminology gets slippery

The vocabulary varies by market and it causes real confusion in requirements documents.

In much of Europe, standing order means the push and direct debit means the pull, and the distinction is clean. In India, standing instruction is used for both a bank-held push and for card-based or account-based recurring authorisations, and e-mandate or NACH mandate is used for the pull. In the United States, recurring ACH debits are authorisation-based pulls, while a bill pay instruction from your own bank is a push.

The practical rule: do not reason from the word, reason from the direction. Ask who initiates each collection. That single question resolves every ambiguity about who can change the amount, who can stop it, and where the customer will go when they want it to end.

What breaks in production

Cancellation asymmetry. A customer cancels a mandate at their bank, tells nobody, and your next collection fails with a reason code you must interpret correctly. Retrying it is not a retry, it is a collection against permission that no longer exists.

Amount-change rules. Pull arrangements typically carry advance-notification obligations before the amount changes, and card-based recurring authorisations often carry a maximum amount fixed at setup. Exceed it and the collection fails even though the mandate is live.

Silent expiry. Card-based recurring permissions die with the card. Account-based mandates usually outlive it. A billing system that treats both as the same object will be surprised by exactly one of them.

The customer's mental model. People believe cancelling the service cancels the payment. For a push, they must cancel at the bank. For a pull, cancelling with you should stop it, and if it does not, you have created a complaint rather than a churn event.

Setting your own alarm, against giving someone a key to your bedroom so they can wake you when they think it is time. Both get you up. Only one of them lets you decide what "time" means, and only one of them requires a conversation to stop.

Where you meet it

Every rent payment that goes out on the first regardless of anything. Every utility bill that varies each month and still collects itself. Every subscription you cancelled that kept taking money, which was almost certainly a pull nobody told the biller to release.