MILabs
Integrations

Invoice chasing automation for GoCardless Direct Debit payments

Connect GoCardless payment events to invoice reminders, with staff approval before any message is sent and a sandbox test first.

Updated 2026-05-19

Invoice chasing automation with GoCardless

For a business that bills by Direct Debit, the gap between a failed payment and a follow-up is where collections tend to slip. GoCardless records the collection side: which mandate was used, when a charge failed and what the bank returned. It does not decide how your team chases the invoice behind that charge or how long to wait before the next message. An invoice chasing workflow fills that gap. It reads payment states through the GoCardless API and webhooks, matches each one to the open invoice in your accounting package, and prepares the next reminder. Your team sets the intervals, approves the wording and decides when an account needs a person. This suits firms whose clients pay on a schedule, such as retainers or instalment fees, and where chasing relies on someone remembering who is due. Start with one payment type, prove the handoff in the sandbox, then widen the scope.

How it works

  1. Read payment records from the GoCardless REST API and select those that have failed or remain unpaid after their due date.

  2. Configure a webhook endpoint so that a payment changing state starts the chasing workflow without a manual export.

  3. Match each unpaid payment to its open invoice in Xero using the customer details and amount, so the reminder quotes the correct invoice number.

  4. Draft a reminder for each account and place it in a review queue, where a team member approves, edits or holds it before anything is sent.

  5. Stop the sequence when a payment clears or a dispute is logged, and write each step to one record per client.

  6. Test the full flow in the GoCardless sandbox before connecting live accounts, then switch to live credentials once staff have checked the output.

good questions, straight answers

Frequently asked questions

How does an invoice chasing automation stay in step with GoCardless?
It stays in step through the GoCardless API and webhooks. When a payment changes state, a webhook tells the workflow, which updates the record for that client. Reminders are drafted from the current payment rather than an old export, so a cleared payment is not chased again. Your team can check any payment in the GoCardless dashboard at any time.
How do I know an invoice chasing automation works with GoCardless?
Check it against a test account before trusting it. Run the workflow in the GoCardless sandbox, where payments can be created without moving real money, and confirm that each event produces the expected entry in your accounting package. A reminder should appear for a missed payment and stop once a payment is marked as paid. Your team reviews a short list of results before the workflow connects to live accounts.
Can I start with a part of an invoice chasing automation on GoCardless?
Yes. Each part works on its own, so a team can begin with the reminder drafts and add the rest later. Reading failed payments and drafting messages for review needs only the GoCardless API connection and access to the invoice list. Webhooks, the accounting match and automatic pausing can follow once the first stage is trusted. Starting small keeps the approval step in place while the rules are tuned.
How does MILabs test an invoice chasing automation against GoCardless?
MILabs tests the build in layers. Each stage is first run against the GoCardless sandbox and a copy of your accounting data, so no live client receives a message during testing. Staff then review drafted reminders for accuracy in tone and amount. Edge cases such as declined, cancelled and disputed invoices are checked one at a time before they are allowed to trigger any automated step.
What does MILabs do after delivering an invoice chasing automation for GoCardless?
After delivery, MILabs documents the workflow, its pause rules and its approval steps, so your team can change an interval or a template without rebuilding the whole thing. Questions about how it behaves can be sent through the enquiry form. When GoCardless or the accounting package changes in a way that affects a reminder, the affected step is retested before the change is relied on.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.