Settings and activity
4 results found
-
1,168 votes
Hi community, we acknowledge the strong feelings in this idea and why you need a feature to flag bills directly within Xero. We really appreciate all your feedback and the detailed explanations of how this would help streamline your accounts payable.
We are dedicated to providing a solution for this over the longer term, but this will take some time requiring changes that sit beneath the face of bills.
In lieu of a direct feature for this we wanted to highlight some of the options discussed by the community here:
- Add a note to the bill: A detailed note on the bill itself can serve as a clear internal reminder of the dispute.
- Utilise tracking categories: Creating a specific tracking category like "Disputed Bills" can help you filter and report on these items.
- Adjust the due date: Temporarily extending the due date can prevent accidental payment while the dispute is…
An error occurred while saving the comment An error occurred while saving the comment 
Christopher Moore
commented
Julia - yes, you've hit the nail on the head.
Arnis - 👍
An error occurred while saving the comment Christopher Moore
commented
@JimAlexander I agree totally with @ArnisVeisbergs and @WillBroome that, however good your add-in is, this functionality is so fundamental to any competent accounting system that it should be provided within the Xero basic subscription.
Someone elsewhere has pushed their addin (Statey) for getting aged totals in statements - another fundamental feature, and another I'm not prepared to pay money to get. At this rate if we buy all the addins needed to make Xero competent, we'd end up with a bill that'd make a fully fledged Microsoft Dynamics implementation look cheap!!
I don't know what add-in developers get charged by Xero as commission for selling their products, to provide functionality Xero can't be bothered to include?
I'm increasingly believing Xero have changed their model from selling a competent accounting product for a monthly subscrtiption, to selling a basic framework and making money from developers by taking commission for all the other bits Xero doesn't provide. Shameful and an approach that won't wash.
Our year end is coming up in a few months and I'm likely to decamp - I've had enough of the abuse we're being delivered from Xero.
Xero - Xero competence for non-Xero cost!
An error occurred while saving the comment Christopher Moore
commented
This is an absolutely basic and fundamental function implemented in every other accounting system I've ever used or implemented - and that's quite a few across several decades!
I'd say it's as fundamental as deciding whether to record bill/invoice values or not; ie absolutely essential to any accounting workflow.
As others have described, bills received need to be entered onto the system but there must be a process to prevent any that are in dispute being paid, with the ability for accounting staff to see notes describing the problem, what a supplier needs to do to resolve it, and for the invoice to be cleared for payment as and when it's resolved.
While Xero has many neat features, this is one of a number of annoying functions which are absolutely standard accounting requirements and which Xero has somehow missed. The cavalier attitude of Xero staff to this implies a total lack of understanding of real world accounting process within the dev team.
Flash, glitz, fancy UI changes etc are all very well and fun to design and build, but for someone who runs a real business the basics - such as this issue, multiple price lists on sales and the ability to allow a negative stock value are way more important.
I've been using Xero for 18 months and love much of it, but am seriously considering the pain of migrating again SO SOON to something else, just to get the basics working as they should, rather than having to build external systems of my own to cover fundamental shortcomings.
Chris Moore
Christopher Moore
supported this idea
·
-
1,064 votes
Hi everyone, we appreciate the interest surrounding this idea, however we want to be open that we're unable to extend our log-out time past 60 minutes. Xero hold a lot of sensitive information including bank data and we're required to be as secure as online banking.
Any session information running on a web browser can potentially be stolen. If the session does not time out. You then have an infinitely long vulnerability window to session hijacking. Our best option is to keep a tight expiration window on the session cookie, and regenerate them frequently. Even setting a long timeout doesn't help with this - too long a timeout will greatly increase the risk of invasion or potentially jeopardise your personal data and the safety and integrity of the Xero application itself. This is why we maintain control of this.
If we detect there's been no activity on a page (e.g…An error occurred while saving the comment Christopher Moore
commented
My particular problem with this is for Time Logging in Projects. Xero has usually logged out when we want to add a time record, which means they don't get logged as diligently as they should and money gets lost!
I get that there may be regs for auto-timeout on the critical ledger access, and that security is critical, but to enforce the same rules on someone entering a time entry - which needs authorising anyway - means that logging doesn't happen reliably.
How can a vendor that's so deaf and unresponsive still be in business? 1 full year in for us and I'm close to looking for an alternative. So much that's really neat but so many issues that bomb productivity and usefulness to the point of unusability.
Christopher Moore
supported this idea
·
-
615 votes
Thanks for your support on the idea, everyone. We thoroughly appreciate your participation, and letting us know where you'd like to see change across Xero.
Customer statements, is an area of Xero that needs upgrades to it's technology in order to make ideas like this one here possible.
Currently, while we have plans for modernising this space soon we cannot commit to any new developments for Statements until this work has been complete. Once this has been done I'll round back to the idea here when we can reset the objectives.
An error occurred while saving the comment Christopher Moore
commented
Yet another utterly obvious, basic feature I've just discovered is missing from Xero. And I'm not going to accept this model of 'charge users for half a package and get 3rd parties to charge them the rest'. Statey, at £18/month for the only version apparently not emblazoned with Statey branding is an outrage. I'm not going to play - another reason to seek a Xero alternative.
Christopher Moore
supported this idea
·
-
485 votes
An error occurred while saving the comment Christopher Moore
commented
We've just received duplicate invoices from a supplier that need to be placed "In Dispute" until we receive a credit note for one of them. I cannot conceive how anybody could design an accounting system without this most fundamental and straightforward of features.
This would be very simple to do and needs doing by tomorrow. A huge credibility hit against the competence of Xero's designers!
Christopher Moore
supported this idea
·
Hi Sharon,
I agree with Will - this and many other missing functions are so basic that they should have been included as core requirements in the absolute first basic spec before a line of code was written. Xero are charging a rate now that should include them.
I accept that modules such as Projects and Expenses, to which I subscribe and use, are not needed by all and are reasonable functions to provide as chargeable add-ons.
But 'in dispute' flags for bills and invoices - amongst many others - are absolutely fundamental IMHO and should be included for what we pay now.