Direct debit: collecting payment without chasing it

Direct debit is an arrangement where the customer authorises you to collect from their bank account, and you initiate each collection. For any business billing the same people repeatedly it changes the economics of getting paid: collection stops being a chasing activity and becomes a scheduled one, and the late payment problem largely disappears for customers on it.

What direct debit requires

• A mandate from the payer, authorising collection — set up once and then reusable.
• Advance notice of each collection, with the amount and date, within a stated period before you take it.
• Access to the scheme, either directly or through a provider that sponsors you, which is how most small businesses do it.
• A process for failed collections, since some will fail and the reasons differ: insufficient funds, cancelled mandate, closed account.
• Clear records of the mandate and notifications, because disputes are resolved on whether the payer was properly notified.

How it differs from a card on file

A card expires, gets replaced after fraud, and is declined for reasons unconnected to the customer's intention — card-based recurring billing loses a meaningful share of payments to that alone, which is the involuntary churn nobody budgets for. A bank mandate does not expire. Against that, direct debit settles more slowly, the payer can reverse a collection with relative ease under most schemes, and setup is slower than taking a card. The usual answer for subscription businesses is to offer both and steer longer commitments towards the mandate.

The payer's right to a refund on demand is a feature of most direct debit schemes, not an edge case. Collecting an amount the customer did not expect — a price rise, an extra item, a date change — is the fastest way to trigger it, which is why the advance notification is both a rule and a practical protection.

Running collections cleanly

1. Send the advance notice automatically rather than manually, since the requirement applies to every collection including changed amounts.
2. Give more notice than the minimum where the amount varies, because surprise is what causes reversals.
3. Retry failed collections on a stated schedule rather than immediately, and tell the customer what happened.
4. Cancel mandates promptly when a customer leaves, as collecting after the relationship ends is both a complaint and a reputational cost.
5. Reconcile collections against invoices rather than assuming success, because failures are quiet.
6. Keep the mandate record for as long as the scheme requires after the last collection.

Ettex Invoices tracks which customers are on a mandate, what was notified and when, and which collections succeeded — which is the reconciliation that turns direct debit from a hopeful arrangement into a reliable one. Customers not on a mandate stay in the ordinary ageing, and the contrast between the two groups is usually the strongest argument for moving more of them across.