Klippa - Recognises S for Success
Use Cases and Deployment Scope
We are building our own Invoice processing system and went looking for an OCR API that could quickly identify Invoice numbers, line items, tax, totals, and company names. This internal application will eliminate paper processing of invoices, streamline approvals and increase security around fraud and scams. The application is restricted to invoices and the accounts payable function.
Pros
- Identifies invoice numbers.
- Extracts text from any angle - 45 degrees and upside down.
- Extracts line items from a printed invoice.
Cons
- More flexibility in tailoring the templates to suit individual customers.
- Better documentation around the API; as I recall it was hard to find.
- Commercial follow up. No one has contacted me since my initial purchase.
Likelihood to Recommend
Klippa does well with invoices without graphics and logos. If you can convince your suppliers to remove their branding and submit plain company names it will perform better. One issue that I could not overcome was when a supplier used "SO" (for Sales Order) as the prefix for an invoice. Every time the OCR ran it deciphered this as "S0" S-Zero. I wouldn't downgrade my rating based on that though. My one significant disappointment was I was led to believe that they would tailor the template for us. There was some minor work around our local tax rules but when it got to specific coding for our purchase order numbers the work ceased. To be fair, I may have misunderstood the scope of what changing these templates was included in the agreement. Either way, we could work around it so it wasn't a major flaw.
