Mandates and Auto-Debit for SaaS and software companies
Track customer payment permissions and recurring debit outcomes.
Does this function belong in your operation?
Use when recurring customer charges are collected through supported payment mandates.
A customer authorises recurring collection through a supported provider.
Customers who pay by a recurring bank debit have their mandate, limit and status held on the account. A failed pull is retried and flagged. Finance sees which mandates are about to expire before a renewal goes through.
Bring the records the workflow depends on.
- Customer mandate details
- Billing schedule
- Provider response and cancellation rules
Outputs to check
- Provider-confirmed mandate register
- Debit attempt and result history
- Failed-collection and settlement list
Follow the mandates and auto-debit workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Mandates depend on an authorised bank or payment-provider process and cannot be created by an internal record alone. Subscription billing supplies eligible amounts; receipts and reconciliation confirm collection. A submitted debit, successful provider response and settled funds are separate states.
Systems and records it connects with
- Subscription billing: Recurring plans, billing periods and account changes.
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Payment gateways and direct debit: Authorised recurring charges and provider-confirmed outcomes.
- WhatsApp and SMS: Permitted message content and channel delivery responses.
Configure, test and introduce the workflow.
- We review your gateway or bank and the kinds of mandate it supports. You provide your account details for set-up. You get a short note on what is possible.
- Plans, due dates and limits per charge are set out. The owner approves them. Wording of customer notices is agreed. Test mandates and debits are run in the gateway’s test mode. Accounts checks that results post against invoices.
- A few willing customers are invited to sign up. The team watches notices, debits and failures. Remaining customers are invited in stages. The register is reviewed with the accounts team at regular meetings.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Debits require an active valid mandate.
- Retries follow the agreed rule.
- Collections reconcile with provider settlements.
How the business operates.
Your product ships code, and the business runs on accounts. Each customer is on a plan, has a renewal date, pays through a gateway and writes to support, and those facts live in different tools.
The records that hold the operation together.
- Account and subscription register. Hold every subscriber with its owner, workspace, plan, seat count, add-ons, billing cycle, start date and renewal date. Billing and success work from the same list.
- Plans, add-ons and pricing rules. Define plans, seat tiers, usage allowances, annual discounts and add-ons once. Proration and the way annual plans count toward monthly revenue are agreed during set-up.
- Trial and onboarding tracker. List trial signups with seats invited, features used and the sales or success person assigned. A follow-up falls due before the trial ends, not after.
- Invoices and recurring billing. Raise an invoice for each cycle from the subscription record, with tax settings per country. Upgrades and seat changes mid-cycle produce the adjusted line on the next invoice.
Operational bottlenecks to check
Revenue numbers do not match
The gateway, the invoice list and the sheet each show a different monthly total. Nobody trusts the report.
Failed payments go unchased
A card expires, the retry fails, and the account is live for weeks without paying. Collections stay manual.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Signup and trial
A visitor registers, and an account is created with the trial plan and its end date. Sales sees which signups used the product and who has been contacted.
2. Conversion
A trial turns into a paid subscription with a plan, seat count, add-ons and billing cycle. Enterprise buyers get a contract with a negotiated price on the same record.
3. Billing and collection
Invoices are raised for each cycle. Payments arrive from the gateway, failures are retried on a schedule, and unpaid accounts are listed for a person to follow up.
4. Support and success
Requests are logged against the account and tagged as a question, a defect or a feature ask. Customer success reads usage and open tickets before every review call.
5. Renewal or change
Upcoming renewals are listed ahead of the date. Upgrades, downgrades and pauses change the plan and the invoice together, with the effective date recorded.
6. Cancellation and learning
A cancellation records its reason, the last day of access and any refund. Reasons are totalled by plan and by period for the product team.
Industry reports to connect with
- Monthly recurring revenue by plan: new, expansion, contraction, cancelled
- Logo churn and seat churn, with cancellation reasons totalled
- Trials started, converted and lapsed, by source and by owner
- Failed payments open, by retry stage and age
Questions before implementation.
When should saas and software companies consider mandates and auto-debit?
Use when recurring customer charges are collected through supported payment mandates. A customer authorises recurring collection through a supported provider.
What should we bring to the requirements discussion?
Bring anonymised examples of Customer mandate details; Billing schedule; Provider response and cancellation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Track customer payment permissions and recurring debit outcomes. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Customer authorisation, provider support and current payment rules determine whether a debit can be made.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Debits require an active valid mandate. Use this check when reviewing the first working version.
Related functions for saas and software companies.
Discuss mandates and auto-debit for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements