Skip to content

Settings and activity

1 result found

  1. 127 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 wanted to share another update here. The ability to schedule and send a one-off invoice at a date and time that works best is now available to all organisations.

    You can find this feature in the send window by clicking the dropdown arrow next to the Send email button.

    As mentioned in my last update, we understand there’s strong interest in extending this functionality to repeating invoices as well. While this isn’t currently in the pipeline, it’s something our product team will closely consider as they shape the future of repeating invoices in Xero.

    I’ll be sure to share any further updates with you here.

    BlueStone Accounts supported this idea  · 
    An error occurred while saving the comment
    BlueStone Accounts commented  · 

    So let me get this straight.

    Back in 2012, someone asked Xero for the ability to schedule when invoices get sent. Fair enough, reasonable ask. Fourteen years later, in July 2026, Xero finally delivers, for one invoice at a time. Manually. Via a dropdown. If you've got a handful of invoices a month, congratulations, you're sorted. If you run repeating invoices for dozens or hundreds of customers, you're still stuck watching them fire off at 2am UK time because that's apparently just how it is.

    This thread has been open since April 2022 asking for exactly that, scheduled sending for repeating invoices, and on 29 May 2026 Xero's official response was that it's "not currently in the pipeline." So the workaround for repeating invoice customers is, what, manually recreate every single one as a standard invoice each month? That's not a solution, that's just moving the manual labour Xero was supposed to remove.

    I'd genuinely like to understand the reasoning here. Is this a technical limitation, a prioritisation call, or is it just not commercially interesting enough to build? Because from where I'm sitting it looks like the one-off fix was done to close out the oldest, most-voted thread, while the actual repeating invoice problem, the one costing your business customers real time every month, got quietly parked.

    126 votes and counting isn't a fringe request. An honest answer on where this actually sits, and why, would go a long way.