Vendor detection : Picking up a wrong vendor when it is not in Vendor dataset


I want to get error or notified when an invoice with a vendor that is not in Vendor dataset.

However, when I recognize an invoice having a vendor not in dataset, the program matches up a vendor in dataset. 

I tried changing the Rule setting in Vendor must be found in database in Vendor property and datasets in Document Definition properties. (Please see attached) But the result does not change. 

It seems like the project picks up some digit in the invoice and then matches a zipcode of a vendor in dataset.  So I removed the zipcode from Field links in Rule settings of Vendor must be found in database properties, but the program still do the same. 

My build number is a bit old ( and I heard it does not happen in the newer version. 

But I need to make it possible in the old version. 

Are there any solutions to solve this issue?

The desired result is: 

If invoices whose vendors are not in Vendor dataset are recognized, the Vendor fields should be blank and get error.

It is that simple but I cannot get it. 

Any ideas help. 


Thank you,


Was this article helpful?

0 out of 0 found this helpful



  • Avatar
    Adrian Enders

    It's not that simple. FlexiCapture does not know if it is correct or not. The issue is "fuzzy" matching. You can take the document index fields in the rule and make more of them "Exact", not "Fuzzy". This will start to reduce the number of matches in the database. But you have to do this for more index fields than just zip codes. (And I would put zip code back by the way. That can be important)

    Keep in mind if you don't use fuzzy matching, then the OCR results will need to be perfect all the time. They won't be.

    I would rethink your approach. Your desired rule assumes that OCR is correct all the time. The system will most always "try" and match a vendor, even if that is not the correct vendor. What is the purpose behind this rule?

  • Avatar
    Dheeraj Sah

    Hi All,

    we  are facing the same issue , wrong vendor is detected .same issue like original thread describe.

    any suggestion highly appreciated.






Please sign in to leave a comment.