Direct debits (SEPA and others) in Business Central

For subscription businesses, utilities, fitness clubs, and any other operation that wants predictable cash collection without chasing customer payments, direct debit is the canonical mechanism. The customer authorises the seller (once, via a signed mandate) to withdraw amounts from their bank account on a published schedule. Business Central supports the workflow end-to-end with SEPA Direct Debit built in for the European market and configurable formats for other jurisdictions.

The model.

• Mandate — a customer's authorisation, identified uniquely. SEPA mandates use a Unique Mandate Reference (UMR) and capture date of signature, type (one-off vs recurring), and parameters.
• Direct Debit Collection — a batch of customer ledger entries (open invoices) to be collected on a specific date.
• Direct Debit Collection Entries — the individual line items inside a collection, one per invoice or per customer.
• Bank Export File — the structured XML the customer's bank can process — for SEPA, the pain.008 schema.

Mandate management. Each direct-debit customer needs an active mandate. The mandate is set up:

• The customer signs an authorisation (paper, e-signature, or portal-based digital consent).
• The user creates a SEPA Direct Debit Mandate on the customer card with the UMR, signature date, status (Active, Closed, Cancelled), and parameters (recurring vs one-off, FRST vs RCUR vs FNAL schemes for first / recurring / final).
• The mandate ties to a specific customer bank account.

Collection runs. The Create Direct Debit Collection routine:

1. Filters open customer ledger entries by criteria (customers with active mandates, due dates within range, payment method = Direct Debit).
2. Proposes a collection batch.
3. The user reviews and adjusts — exclude customers in dispute, defer specific entries, change amounts.
4. The user Exports the collection as a bank file (SEPA pain.008).
5. The bank file is uploaded to the bank for processing.

Posting the collection. When the bank confirms successful collection (typically 2–5 business days for SEPA), the user posts the collection in BC, which:

• Applies the collected amounts to the customer ledger entries.
• Reduces outstanding AR.
• Posts the corresponding bank account ledger entry (or accrues to a direct debit suspense account pending final settlement).

R-transactions (return transactions). Banks return failed direct debits — customer disputed, account closed, insufficient funds, mandate not recognised. SEPA defines R-transactions with reason codes. BC's direct debit handling reverses returned collections, sets the ledger entries back to open, optionally raises an alert for collections follow-up, and may charge an R-transaction fee back to the customer.

Other jurisdictions.

• UK — Bacs Direct Debit Instruction (DDI). Different scheme than SEPA; requires Bacs-approved bureau or own SUN. BC supports through partner ISVs.
• US — ACH debits (NACHA format). Pull-payment ACH similar to direct debit.
• Nordics — country-specific schemes (Autogiro in Sweden, Direkte Debet in Norway, etc.). Local ISV connectors handle the formats.
• Australia — Direct Debit Request (DDR), bank-specific.

Lifecycle and notifications. Mature direct debit programmes notify customers in advance of collection (some jurisdictions require it — SEPA Core mandates 14-day notification by default). Power Automate flows can send pre-notice emails based on the proposed collection batch.

Compliance.

• SEPA scheme rulebook — mandate format, advance notice, R-transaction handling, recovery rights.
• Country-specific consumer-protection rules — recovery windows, dispute procedures, regulatory notifications.
• GDPR for mandate storage — store mandates with appropriate retention and protection.

Operational reality. Direct debit is high-leverage for the right business: collections cost a fraction of invoice-chase. But mandate hygiene matters — invalid mandates cause R-transactions, which damage bank relationships and customer trust. Manage actively.