Skip to content

Settings and activity

1 result found

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

    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
    zion wang commented  · 

    A useful duplicate bill review needs separate buckets rather than one generic duplicate warning. I would split the review into true duplicate supplier bill, recurring legitimate bill, draft-not-yet-posted bill, paid historical bill, voided/deleted bill, and sync-created bill from another source. The fields that matter are supplier label, invoice/reference number, normalized reference, amount bucket, bill date, due date, status, payment status, source system, and whether it was previously reviewed. Header-only or fake-row examples are enough to decide which buckets are possible without exposing real supplier or bill data.