Getting low accuracy on two fields after labelling using the tool, Form Recognizer, Custom Label API, please help.

Kuntal, Varun 1 Reputation point
2020-10-07T15:04:51+00:00

I need help with recognition of two particular fields- "credit date" and "credit type". Getting low accuracy (training ~30%) after labelling and even lower on the test set (~10%). The receipts along with the two mentioned fields look like this (highlighted):

30712-1.jpg

30540-2.jpg

I am using Custom Label API after labelling, tagging and training.
I think as these two fields appear at different places relative to other fields due to different number of entries in in different receipts.
Is there anything that I can do to improve these fields accuracy.

Azure Computer Vision
Azure Computer Vision
An Azure artificial intelligence service that analyzes content in images and video.
305 questions
Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
1,333 questions
Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
2,343 questions
{count} votes

1 answer

Sort by: Most helpful
  1. GiftA-MSFT 11,151 Reputation points
    2020-10-09T22:36:43.64+00:00

    Thanks for following up. We recommend that you label each value on the form, for example date_p1, date_p2, date_p3 as the label names for each value. If your forms have tables with varying numbers of rows, label at least one form with the largest possible table. Furthermore, it seems like you're trying to label a single model for different form types. As every hotel invoice has a different structure, we recommend you create a model per hotel vendor with at least 5 sample invoices from that hotel, and then compose those into a single composed model. In some scenarios, table extraction doesn't happen automatically so manual tagging is necessary, however, we plan to support more complex scenarios as the service evolves. Hope this helps!

    0 comments No comments