Skip to content

Settings and activity

6 results found

  1. 4 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)

    Like your forward thinking, Johan. 

    As Freya mentioned there is some AI going on in Xero already with the way Xero makes suggestions to help you reconcile your bank account. 

    We recently shared some insights with our customers on our approach to generative AI with Xero and you can read more about this on our blog

    Later this year you'll see Just ask Xero (JAX) be introduced and I'll round back to share once this is available. 

    An error occurred while saving the comment
    Mike Baptiste commented  · 

    I understand it's a beta, but JAX is struggling. Most of the time I ask it something, it just says it can't do it. I'm not asking it difficult questions. Mostly just playing around. What were the last five invoices paid. What was our most profitable product. What clients have the biggest overdue balances. The one time I got an answer (most recent paid invoices) I got random invoices from eight years ago 😂) I realize that AI success depends heavily on prompt engineering. But I hope it starts to get some footing. Im a big AI skeptic - I think it's being massively overhyped. But I see huge potential for it in Xero. So much time saved not having to ***** around with report structure or filters. So don't take this as hating on it - I want to see it succeed. But it's got to come up with answers 😎 And if the beta team has any tips and tricks to get more useful info from it, definitely let us know

  2. 34 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)
    An error occurred while saving the comment
    Mike Baptiste commented  · 

    This is a HUGE issue for us. AOL and Yahoo constantly block our Xero emails (directly impacting our ability to get paid because clients never see the invoice) All our other systems like Hubspot, Zendesk, etc send using our domain and a specified email address (ar@domain.com etc). We just add the appropriate SPF and DKIM CNAME records and it works great. They ALWAYS get emails from Zendesk. But from Xero? Depends who their email is with. I realize it's easy to say this is an issue with AOL/Yahoo because the Xero emails ARE spf/dkim compliant. But they get blocked anyway and it's the only system we have this issue with.

    For people that choose to use Xero to send the email - you should include the bounce error in the notification emails that a Xero email bounced. It's impossible to troubleshoot. It's usually a typo,but we've had a few instances that the email address was 100% correct - but still bounced. We had no idea why.

    Mike Baptiste supported this idea  · 
  3. 267 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 team, as you may have noticed we've made a change to the Invoice Date and Due Date fields that now allows you to type in these fields rather than having to select a date from the calendar drop down. It does still require entering delimiters between day month and year such as a '.' or '/' (we understand there are a few situations when entering US date formats and are continuing to look into this).

    We're working on also adding this functionality to the Payment date, and I'll keep you in the know of when this is made available, here.

    An error occurred while saving the comment
    Mike Baptiste commented  · 

    May have already been mentioned, but thankfully the date field still doesn't require a year. Just type in mm/dd (or dd/mm for countries that do it correctly hahaha) and tab out. It'll set the current year

  4. 230 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)
    An error occurred while saving the comment
    Mike Baptiste commented  · 

    This has been an issue from the first time we switched to Xero. It takes SOOOOO long to print an invoice for counter customers - they look at us like 'what are you doing? I already paid!' It's insane how long it takes.

    PLEASE add a native browser print button that immediately brings up the browser print dialog. Just about every other commerce/finance site does this.

    The best we could do was set the browser to 'Always download PDF' and after downloading a pdf, right click it in the download dropdown and select 'Always Open in (your PDF viewer)' At least this way when we click the Print PDF, it eventually opens in the PDF viewer and we click the print button and then 'OK'. So less clicks, but still a LOT of effort.

    Coupled with the multiple seconds it takes to add a payment and get the paid invoice screen, this just adds to the time needed to get a customer on their way.

    Mike Baptiste supported this idea  · 
  5. 33 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 everyone, we know our customers would like more efficiency and simpler methods when logging in to use Xero. 

    We're pleased to share that our product team have begun work to enable logging into Xero using passkeys. 

    We'll shift to Under review and I'll return to keep you updated of progress in this space. Thanks 

    An error occurred while saving the comment
    Mike Baptiste commented  · 

    So glad to see this. Having to login multiple times a day, plus the login popup doesn't smoothly integrate with password managers (sometimes it fills, sometimes it doesn). Passkeys are life changing when properly setup because reauthenticating can be as simple as a single click. We would be happy to beta test this! As a MSP, we've setup MANY types of FIDO2 authentication methods (Yubikeys, Google Titan, Windows Hello, 1Password Passkey, etc) to help our client deploy them.

    Now add Microsoft and Google SSO.

    Mike Baptiste supported this idea  · 
  6. 397 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 appreciate many businesses have adopted single sign on with providers like Google, Microsoft Azure/Entra, and Okta to easily streamline logins to many applications and manage operational risk. Our team are staying close to votes and feedback of the idea here, and though we can't commit to development at this time, we will be sure to let you know of any progress toward enabling single sign on

    Mike Baptiste supported this idea  · 
    An error occurred while saving the comment
    Mike Baptiste commented  · 

    As the push towards Passkeys kicks into high gear in 2025, Xero is way behind here. Most small businesses have Google Workspace or Microsoft 365. These are some of the most secure authentication methods because they've been pushing their users towards 2FA and now Passkeys. At the very least there should be native Passkey support, but ideally, SSO/SAML support for the like of Google. Microsoft, Okta, and Duo. This is the only 'major' app in our business stack that still relies on direct password authentication. Everything else is Passkeys or Google SSO Auth.