Skip to content

Settings and activity

1 result found

  1. 574 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi community, We're excited that enhancements to your bank reconciliation experience in Xero are in the process of being rolled out! Some may notice you can now effortlessly search and filter statement lines based on your preferred criteria, giving you ultimate control and efficiency. Plus you’ll be able to view more statement lines on your screen - up to 50 unreconciled statement lines on one page. 🚀
    Worth noting here with the interest in getting a narrower view of statement lines that need reconciling on a given or between certain dates - you’ll find with the more option to the right of Search you’ll be able to set a date range and filter down your view 😁

    If you don't quite  have the new features yet, I can assure you they are coming soon, as we ramp up the release of this to everyone over the next few weeks. I'll…

    An error occurred while saving the comment
    Robin Brinkler commented  · 

    In the past I wrote a Chrome extension which performed basic UI tasks in Xero, such as unticking the "Show GBP Transactions Only" option during reconciliation, where Xero allows you to search for a transaction to match against. Now that AI is able to assist users with writing code, I see an opportunity for Xero to provide the tools to allow users to write their own Xero extensions.

    How I see this working:

    Xero Smart Scripts

    Users are able to enter their own scripts, after accepting responsibility for any changes this might make to their financial records in Xero. Provide an option for a backup / history / time machine backup of your Xero records and if necessary charge extra for the time machine option. This would prevent such user scripts from causing irreperable damage to financial records with no recourse which might happen without this option.

    Xero provides the ability for users to share scripts, once they are vetted by the Xero team, so that other users can make use of them too. If a feature gets a lot of traction and adoption, Xero can consider adding this as a permanent or optional feature in Xero. It would allow the community to contribute to improving Xero in real time. This way the users that need new features can help make the situation better for themselves and others, rather than considering alternatives or suffering through any problems that could be easily remedied in short order by the community.

    Xero allows users to process some data on the client side (user browser side) for the duration of the browser session in order to take pressure off the Xero servers, as it was previously suggested by Xero staff that searching / filtering transactions is computationally expensive for Xero. If a transaction search is beyond the scope of the default download (say 7 days, 30 days, 3 months, or some other transaction limit) then a download can be requested, which will be run when the servers are able to handle the request, much like PayPal's transaction history downloads where they will email the user once the data is ready to download.

    Using machine learning, a chatbot could help users write code, with the chatbot's knowledge of the Xero UI and existing features, it could either help the user write code and test it on sample data (or a copy of real data from the user's accounts in Xero). With the time machine feature, there is less risk of permanent error here. The chatbot could ask the user what they want to achieve, and if this has already been done by another user from the community, it could suggest an existing Xero Smart Script to try out.

    The code required to interact with a UI is often quite simple, filtering options might be more difficult, but if Xero had an API which was only accessible from within Xero in a logged in session, I think quite a lot of problems users bring up could be solved by the community.

    Robin Brinkler supported this idea  ·