Recognition and extraction are usually sold as one capability and they fail in different ways. Extraction reads fields. Recognition decides what the document is and, critically, which of your existing suppliers sent it. An extraction error costs a correction. A recognition error creates a duplicate supplier record or attaches an invoice to the wrong account, and both take far longer to unpick than they took to create.
Supplier identity is a matching problem
The name printed on an invoice is often not the name in your system: trading names, legal entities, abbreviations and acquisitions all diverge. Good recognition matches on several signals together, such as a tax reference, a bank account and an address, rather than on the printed name alone. Ask how a product handles a supplier whose trading name differs from its registered one.
What a duplicate supplier record costs
Two records for one supplier split the payment history, break duplicate-invoice detection, and produce statements that will never reconcile. They are also easy to create and hard to merge afterwards. This is why supplier creation deserves a control of its own rather than happening automatically whenever recognition fails.
Document type recognition
Before the supplier question comes a simpler one: is this an invoice, a statement, a credit note or a delivery note. Treating a statement as an invoice creates a payment that is not owed; treating a credit note as an invoice reverses the sign of a correction. Both are worse than any field-level error, so confidence handling matters here most of all.
Questions people ask about invoice recognition software
What happens when a supplier is not recognised?
It should go to a person, not create a new supplier automatically. Automatic creation is the fastest way to accumulate duplicate records.
Can it tell an invoice from a statement?
Good products can, most of the time. Test it, because the consequences of getting it wrong are larger than any extraction error.
Does recognition improve over time?
For suppliers you see repeatedly, usually yes, since more history means more signals to match on. Ask what a correction actually teaches the system.