Skip to content
← Share and support customer ideas for Xero

Settings and activity

1 result found

  1. Bills - Option to customise or turn off "Duplicate Bill" review messages

    109 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    62 comments  ·  Purchase orders, bills & inventory » Bills  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Accepted  ·  AdminKelly Munro (Community Manager, Xero) responded

    Thanks for your feedback and letting us know how we could improve the way duplicates alerts work for you here.

    While we don't have any immediate changes planned for this, our team will consider improvements to this model overtime.

    For the time being we'll continue to keep our eyes on the support for this in community, here. I'll share if there is any news.

    An error occurred while saving the comment
    Ali Moss commented  · 

    Same symptom as MICHELLE RAE's September 10th comment: one paid bill, displayed alone as a "group," marked Previously kept, returning after every Keep all.

    Like her situations and unlike many of these others, however, for me it's a single bill that keeps coming up as duplicate. It only shows one bill (rather than two dupes), is not for a recurring charge, and doesn't match the amount of any other bills from that vendor.

    I have ruled out three things on my flagged bill, in case it narrows the search:

    1. Reference number. Four bills from another supplier had blank references.
    Filling all of them in changed nothing.

    2. The flagged bill's own reference. Changed it. The bill still flags.

    3. Payment reconciliation. Un-reconciled and re-reconciled the payment. No change.

    So detection is keyed to neither the reference field nor the payment's reconciliation state, and Keep all does not persist for a single-bill group. Whatever record marks a group as reviewed is either not being written, or not being read on the next detection pass.

    Please fix the persistence, or let us turn the alert off. As it stands it trains everyone to dismiss the banner unread, which costs exactly the duplicate it was built to catch.

    Ali Moss supported this idea  ·