Hi everyone, thank you for continuing to share how important it is to clearly identify bills that need attention before they’re paid. We understand the impact this has on teams managing bills and avoiding payments being made before a query is resolved.
While a user control flagging mechanism is not directly in the pipeline yet, we want you to know that your feedback and the volume of support here is getting to the right places.
Our product teams are continuing to consider this wider workflow (not just adding a standalone flag) as they plan and shape our direction for bills.
We’re working towards making it easier to manage payments out of your business, with clearer ways to understand which bills need action as part of a more connected bills and payments experience.
The new bills approval flow which we’re currently developing is an example of this - once available admins will be able to set rules based on factors of bills such as; amount, supplier, account code or who submitted the bill. You’ll then be able to automatically route bills through selected approvers in sequential or parallel steps. While we know this isn’t a direct solution for this idea, this’d provide you with controls to set rules for common flows in which bills need flagging for approval from specific users in your organisation.
We appreciate the detail and persistence you’ve brought to this conversation. As soon as there's more progress surrounding this I'll make sure to share another update here.
Hi everyone, thank you for continuing to share how important it is to clearly identify bills that need attention before they’re paid. We understand the impact this has on teams managing bills and avoiding payments being made before a query is resolved.
While a user control flagging mechanism is not directly in the pipeline yet, we want you to know that your feedback and the volume of support here is getting to the right places.
Our product teams are continuing to consider this wider workflow (not just adding a standalone flag) as they plan and shape our direction for bills.
We’re working towards making it easier to manage payments out of your business, with clearer ways to understand which bills need action as part of a more connected bills and payments experience.
The new bills approval flow which we’re currently developing is an example of this - once available admins…
We recently paid an invoice that was in dispute by mistake, which forced us to find a workaround. Here are the methods we considered:
Keeping bills in draft or awaiting approval, but this prevents the amounts from showing in reports.
Using the planned date field, only completing it if the bill isn't under query.
Adding a comment in the reference field.
Currently, we use both the planned date and reference field methods, as relying solely on the planned date isn't robust enough. However, this approach requires editing the invoice to change the reference each time a condition is met, which is cumbersome and doesn't prevent the invoice from being paid.
I'm not a computer expert, but it seems a simple tick box to mark a bill as "not to be paid" along with a warning banner would suffice. This feature should be a high priority, given the interest from users, as evidenced by the votes on this post (and potentially others on the same topic, splitting the vote). The additional time wasted on workarounds by thousands of users for something seemingly straightforward is baffling.
For comparison, I found that in Sage, you can simply click "dispute" and select a reason. Voila.
If anyone else has other workarounds, please share them with the group as It looks like we'll need to find our own solution to this issue!!
Debbie Jones
supported this idea
·
We recently paid an invoice that was in dispute by mistake, which forced us to find a workaround. Here are the methods we considered:
Keeping bills in draft or awaiting approval, but this prevents the amounts from showing in reports.
Using the planned date field, only completing it if the bill isn't under query.
Adding a comment in the reference field.
Currently, we use both the planned date and reference field methods, as relying solely on the planned date isn't robust enough. However, this approach requires editing the invoice to change the reference each time a condition is met, which is cumbersome and doesn't prevent the invoice from being paid.
I'm not a computer expert, but it seems a simple tick box to mark a bill as "not to be paid" along with a warning banner would suffice. This feature should be a high priority, given the interest from users, as evidenced by the votes on this post (and potentially others on the same topic, splitting the vote). The additional time wasted on workarounds by thousands of users for something seemingly straightforward is baffling.
For comparison, I found that in Sage, you can simply click "dispute" and select a reason. Voila.
If anyone else has other workarounds, please share them with the group as It looks like we'll need to find our own solution to this issue!!