# Automate account blocking for overdue accounts

**URL:** <https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538>\
**Category:** Ideas & feature requests\
**Created:** [25 June 2024 10:33 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538 "2024-06-25T10:33:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![simon-brown](https://community.breww.com/user_avatar/community.breww.com/simon-brown/32/1035_2.png) [@simon-brown](https://community.breww.com/u/simon-brown)\
**Post date:** [25 June 2024 10:33 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/1 "2024-06-25T10:33:13Z")

</div>

It would be very handy if any overdue accounts could have a block automatically placed on them so that sales staff cannot place even a draft order.  
We offer 14 day terms so it would be great if we could specify that on day 15 the account is blocked until the account is cleared for example.  
As a very busy business running on minimal staffing this would help the back office hugely.

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [3 July 2024 18:08 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/2 "2024-07-03T18:08:33Z")

</div>

Thanks for the suggestion, Simon. Can you confirm that you’re effectively asking for a new option in the below list of “Prevent order creation”?

 ![Screenshot 2024-07-03 at 20.07.39](https://breww-community.fra1.digitaloceanspaces.com/original/2X/8/83efd9e5a162fb11fcbec1fb6c5cbf359a8d06b6.png)

Also, please don’t forget to vote for your own suggestion - every vote counts!

---

<div class="post-metadata">

**Author:** ![simon-brown](https://community.breww.com/user_avatar/community.breww.com/simon-brown/32/1035_2.png) [@simon-brown](https://community.breww.com/u/simon-brown)\
**Post date:** [4 July 2024 07:57 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/3 "2024-07-04T07:57:46Z")

</div>

Hi Luke,  
I’m thinking more along the lines of in “Default Invoice Payment Terms” that there could be an additional section that allows for automated blocking of a customers account if it exceeds the default terms.  
Currently it has to be done on a customer by customer basis by using the Block Order Processing tool in More Actions.

---

<div class="post-metadata">

**Author:** ![darron-anley](https://community.breww.com/letter_avatar_proxy/v4/letter/d/54ee81/32.png) [@darron-anley](https://community.breww.com/u/darron-anley)\
**Post date:** [18 November 2025 11:07 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/5 "2025-11-18T11:07:41Z")

</div>

I thought it would be best to join this thread. Thanks very much for adding a button to the overdue debtors account - this automatically puts anyone who is overdue on stop - which is a great help for us.

However to really help can i suggest some options to tweak it slightly.

Direct Debit Customers - dont show as paid, even though we have the remittance from Go Cardless until the money is in our bank - therefore when we run this routine it will put any direct debit customers on stop.

So if there can be the ability to do a couple of things it would be great - offer the chance to not put customers only x amount of days overdue on stop.

allow the filter list to apply who is on stop - so for instance we could filter out our gold customers that we may not automatically stop - but this gives us lots of other possibilities too.

Thanks

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [25 November 2025 16:27 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/6 "2025-11-25T16:27:02Z")

</div>

Thanks for the comments, @darron-anley, these are useful ideas for how this could be improved.

Regarding this:

> [@darron-anley](#):
>
> Direct Debit Customers - dont show as paid, even though we have the remittance from Go Cardless until the money is in our bank - therefore when we run this routine it will put any direct debit customers on stop.

I’m afraid this isn’t possible. This information will be coming into Breww from your Xero integration and Xero don’t give us this level of detail. We have no way of knowing the difference between a payment showing in your bank account and one that’s not there yet.

(Plus, if this were possible, it would have needed its own feature request to be tracked properly, as it would be lost in comments on this somewhat related thread.)

Having said this, we could solve this by having Breww speak directly to GoCardless, rather than having Xero act as a very vague middleman. Maybe [GoCardless direct debit Integration](https://community.breww.com/t/gocardless-direct-debit-integration/1683) is worth a vote?

---

<div class="post-metadata">

**Author:** ![darron-anley](https://community.breww.com/letter_avatar_proxy/v4/letter/d/54ee81/32.png) [@darron-anley](https://community.breww.com/u/darron-anley)\
**Post date:** [25 November 2025 17:26 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/7 "2025-11-25T17:26:16Z")

</div>

Hi Luke – for me the simplest way to change – assuming it was simple was to make the stop button work on what accounts are not filtered out – this would then allow us & other customers to filter on a tag for Direct Debit for instance – or a gold customer we don’t want to put on stop.

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [25 November 2025 18:34 UTC](https://community.breww.com/t/automate-account-blocking-for-overdue-accounts/4538/8 "2025-11-25T18:34:07Z")

</div>

Ok, that could certainly be looked at. Although somewhat related, that’s not what this feature request thread was requesting, so would you mind creating a new one for your idea? Thank you.
