Manual direct debit work quietly drains a finance team. Chasing failed collections, re-keying mandate changes from a bank file into a spreadsheet, matching incoming payments to invoices by hand, explaining to a customer why they were debited twice. None of it grows the business, and most off-the-shelf software only moves the problem rather than removing it, because you end up shaping your collections process around the tool.
ByteGears builds custom direct debit automation tools for UK businesses. Rather than another subscription platform, we build a system that fits how your team already collects payments and meets the rules you actually operate under. We are a London-based development shop, and tailored automation for small and mid-sized companies is most of what we do.
Where off-the-shelf direct debit tools fall short
The mainstream platforms are good at what they do. The friction shows up at the edges, and for a lot of UK businesses the edges are where the real work happens:
- Per-transaction pricing keeps climbing. A percentage plus a fixed fee per collection is easy to live with at low volume. At a few thousand collections a month it becomes a permanent running cost that grows every time you do.
- Approval flows are too simple. Most tools assume one person presses go. Multi-entity organisations often need operations, finance and compliance to sign off before a file is submitted, and that logic has to live in workarounds.
- Variable amounts are awkward. Usage-based billing, tiered pricing with rebates and revenue-share arrangements rarely fit a platform built around fixed monthly amounts.
- Integration stops at the standard connectors. If you run a legacy billing system, in-house credit checking or custom metering, you are back to CSV exports and manual reconciliation.
- Exception handling is generic. Failed payments, ARUDD returns and chargebacks get logged, but the recovery workflow has to match how your team chases money, not a vendor’s default.
- Vendor lock-in is real. Proprietary data formats and baked-in integrations make switching expensive, and your mandate history is hard to take with you.
The usual result is a stack of workarounds: spreadsheets alongside the platform, manual reconciliation, and a finance team that spends more time on collections admin than it should.
To be fair, off-the-shelf is the right call for plenty of businesses. If you collect under 100 payments a month on a simple membership or subscription model, with one scheme and no unusual approval or compliance needs, a platform like GoCardless will serve you well and a custom build would be hard to justify. We will tell you if that is your situation.
When a custom build is worth it
Bespoke direct debit software earns its place when the standard tools force compromises you keep paying for:
- High transaction volume, where per-transaction fees have become a serious annual cost
- Multi-party or conditional approval before a collection is submitted
- Variable or formula-driven amounts tied to usage, metering or contract terms
- Deep integration with a legacy or proprietary backend, without an expensive ERP migration
- Sector compliance that goes beyond general Bacs and GDPR, such as FCA-regulated collections or healthcare consent rules
- A clear preference to own the workflow, the data and the mandate history outright
What we do differently
We are a small team, and we build direct debit systems around the business in front of us.
Built around your collection process
We shape the software around how you handle mandates, schedules and exceptions, rather than asking your team to relearn their job around a platform.
Sensible about Bacs accreditation
Only Bacs Approved Solution Suppliers and approved bureaus can submit files directly to Bacs, and accreditation is a long, audited process. For most clients we build the system that runs your collections workflow and connect it to a Bacs provider or bureau for submission. You get software shaped to your business without taking on accreditation. If a direct Bacstel-IP connection is genuinely warranted, we will scope it honestly.
Pay once, own it
No recurring SaaS fees that scale with your collection volume. You own the software, and the running cost is fixed rather than tied to how much you process.
Connects to what you already run
It talks to your accounting software, CRM and billing systems, so payment status, reconciliation and customer records stay in step without re-keying.
UK compliance from the start
Built with the Direct Debit Guarantee, ARUDD and ADDACS handling, audit trails and UK GDPR obligations in mind from day one, not bolted on later.
Grows with you
Add schemes, approval steps or integrations as the business changes, without re-platforming.
Support from people you can reach
Our London team handles the rollout and stays available afterwards.
Features we typically build
Not every project needs all of these. A first version usually covers mandates, scheduling, batch files, exceptions and reporting; the rest follows once that is live.
Mandate management
Create, store, sign and cancel mandates, whether they originate online, on paper or by phone. Status tracking, scheme references and signed-form storage for audit.
Payment scheduling
Recurring collections by week, month, quarter or year, plus one-offs, driven by your rules and each customer’s agreement. Pause, resume and bulk changes to amounts or dates.
Batch file handling
Generate and validate Bacs or SEPA submission files, with checks on amounts, sort codes and mandate validity before anything goes out.
Exception handling and retries
Import ARUDD and return files automatically, surface failed collections, and apply retry logic that matches your recovery process. Roughly 3% of collections fail in a typical book, most for insufficient funds, and a sensible retry policy recovers a good share of those rather than writing them off.
Reconciliation
Match incoming payments to invoices and customer accounts using your reference logic, and flag the unmatched items instead of leaving them for a month-end spreadsheet.
Dashboard and reporting
Live view of collection performance, success rates, failure reasons and cash flow, with reports built for how your finance, support and management teams actually read them.
Customer portal
Customers update their own bank details, view payment history and manage their schedule, which cuts inbound queries and keeps mandate data current.
Notifications
Alerts for failed payments, upcoming collections, mandate cancellations and chargebacks, routed to the people who need to act.
User management and audit trail
Per-person and per-department access controls, plus a complete log of every mandate and payment action for regulatory inspection.
System integration
Connectors for the platforms UK businesses actually run, Xero, QuickBooks and Sage for accounting, CRM for customer status, and bespoke links to legacy or in-house systems.
How a project runs
Discovery and planning (2 to 3 weeks)
We walk through your current collections process, mandate handling and failure workflow, find where it costs you time, and pin down requirements and integration scope.
Build (8 to 12 weeks)
Our UK team builds the system with current frameworks and security practices, starting with the core collections workflow and exception handling.
Testing and migration (2 to 4 weeks)
We test the end-to-end flow hard, then handle mandate migration carefully: export, validation, deduplication and a parallel run before cutover. We avoid switching during month-end or a tax quarter.
Training and support (ongoing)
We train your finance, operations and support teams, and stay on for support and later changes.
What it costs
Custom development costs more upfront than a subscription. Over a few years it usually works out better, and the case is strongest at volume:
- A fixed build cost instead of per-transaction fees that grow with every collection you add
- You own and control the system and your mandate history, with no vendor lock-in
- The collections admin time you save tends to offset the cost
- No expensive re-platforming as the business grows or adds a scheme
Where it lands depends on scope. A focused single-scheme system is a smaller project than a multi-scheme build covering Bacs and SEPA with custom approval logic. Rather than quote a brittle number, the first consultation is free and gives you a real figure against your actual volume and requirements.
Where this gets used
Custom direct debit automation fits a range of UK sectors, usually where the collection workflow is more particular than a standard platform expects:
- SaaS and subscriptions: recurring billing with lower failure rates than card, and retry logic tuned to your churn risk
- Utilities and energy: variable collections where the amount changes with usage but the schedule stays fixed
- Membership and fitness: monthly fees with self-service pause and cancel, and a central view of member status
- Charities and fundraising: low-cost recurring donations, Gift Aid tracking and donor agreement records
- Healthcare and clinics: patient payment plans and membership fees, with consent handling integrated into patient systems
- Insurance and financial services: premium collection with FCA-compliant mandate management and automated recovery of lapsed payments
- Property management: rent and service charge collection across portfolios
- B2B and invoice settlement: retainer and invoice collection from many clients, with accounting integration that logs payments automatically
- Councils and public sector: auditable collection with quarterly amendments and a complete audit trail
- Franchises and multi-site: collection across locations under one platform, with routing to the correct entity
Common Questions About Custom Direct Debit Automation Tools
Do we need to be Bacs accredited to use a custom system?
Not necessarily. Only Bacs Approved Solution Suppliers and Bacs-approved bureaus can submit files directly to Bacs, and getting accredited is a long process. For most businesses we build a system that handles mandates, schedules, retries, reconciliation and reporting, then connects to a Bacs provider or bureau for the actual submission. You get a system shaped around your workflow without taking on accreditation yourself. If you genuinely need a direct Bacstel-IP connection, we can scope that, but it changes the timeline significantly.
How does a custom build compare to per-transaction SaaS fees?
Most direct debit platforms charge a percentage plus a fixed fee per collection. That works fine at low volume. Once you are processing thousands of collections a month, those fees become a meaningful running cost with nothing to show for it at the end. A custom build is a larger upfront cost, but it is fixed, you own it, and it does not scale with your transaction count. The crossover point depends on your volume and average ticket size. We will work through the real numbers with you before you commit to anything.
What's the typical development timeline?
A focused first version covering mandates, scheduling, batch files, exception handling and basic reporting is usually 8 to 12 weeks. A fuller single-scheme system with retry logic, a customer portal and deeper integrations runs 12 to 16 weeks. Multi-scheme builds covering Bacs and SEPA take longer. We agree the scope in discovery so the timeline is realistic, not optimistic.
Can you integrate with our accounting and CRM systems?
Yes. The common ones are Xero, QuickBooks and Sage for reconciliation, and HubSpot or Salesforce for keeping customer payment status current. We also build connectors for legacy billing systems, in-house credit checking and proprietary metering, which is often the reason off-the-shelf tools do not fit. Integration scope is assessed during discovery so there are no surprises.
How do you handle the Direct Debit Guarantee, ARUDD and GDPR?
The Direct Debit Guarantee is built in: customers must be able to claim a full refund for a payment taken in error, and your system needs to surface and process that cleanly. We handle ARUDD and ADDACS files so unpaid debits and mandate changes flow back into the system automatically rather than landing in someone's inbox. On GDPR, bank details are personal data, so we cover consent records, retention rules, a full audit trail and erasure. We do not provide legal advice, but we build to the obligations your sector carries.
What happens to our existing mandates if we move to a new system?
Mandate migration is the part most projects underestimate. Legacy data tends to carry duplicates, invalid sort codes and missing fields, and a bad import shows up as failed collections on the first run. We treat it as a proper workstream: export, validation, deduplication, customer notification where required, and usually a parallel run against your existing process before full cutover. We avoid switching during month-end or a tax quarter.