Help Center> Optical Character Recognition> Service Overview> Function Description> Auto Classification OCR
View PDF

Auto Classification OCR

Function Description

Auto Classification OCR recognizes and detects multiple cards and receipts in the same image at a time, and returns the category and structured data of each card and receipt.

Application Scenarios

Auto Classification OCR is applicable to multiple scenarios such as identity authentication and financial reimbursement. It is easy to use and effectively improves data entry efficiency.

Scenario 1: Recognition of cards and receipts

Scenario 2: Recognition of receipts of the same type

Scenario 3: Recognition of different types of receipts

Category

  • Cards

    Currently, the following card types are supported: ID card (including the front side and the back side), driving license (including the primary and secondary pages), vehicle license (including the primary and secondary pages), passport, bank card, and transportation license.

  • Receipts

    Currently, the following receipt types are supported: value-added tax (VAT) invoice (including special invoice, general invoice, and electronic invoice), unified invoice for motor vehicle sales, taxi invoice, train invoice, quota invoice, vehicle toll invoice, and flight itinerary invoice.

Advantages

  • Super API

    Auto Classification OCR recognizes a single image of various cards and receipts, and classifies and recognizes any combination of cards and receipts.

  • Simplified calling

    One API can be directly called to recognize various cards, certificates, and tickets. The image type does not need to be determined during calling, and there is no need to call different APIs for each type of data, which simplifies integration and use.

  • Price preference

    The calls of multiple service types can be calculated in a centralized manner. The service will cheaper no matter whether a service package is subscribed or the tiered charging is used.

    For price details, go to OCR Price Calculator.

  • Easier management

    You do not need to predict the number of API calls for each API separately and then purchase packages of different sizes. Taking invoice reimbursement as an example, it is difficult to estimate the number of each type of invoices separately, but it is easier to estimate the total number of invoices based on historical situations.

Parent topic: Function Description