Certificate of Status OCR

This article walks you through the building process of an OCR API that extracts data from Certificate of Status using our deep learning engine. It will work for any bank company or bank statement template.

Prerequisites

  1. You’ll need a free account. Sign up and confirm your email to login.
  2. You’ll need at least 20 Certificate of Status images or pdfs to train your OCR.

Define your Certificate of Status use case

First, we’re going to define what fields we want to extract from your Certificate of Status.

Certificate of status key data extraction

  • Entity name: The full name of the entity
  • File Number: The file number of your certificate of status
  • Formation date: The creation date of your entity
  • Type: The type of entity
  • Jurisdiction: The jurisdiction that your entity depends on
  • Status: The status of your entity

That’s it for our use case. Feel free to add any other relevant data to fit your requirements.

Deploy your API

Once you have defined the list of fields you want to extract, head over to the platform and press the ‘Create a new API’ button.

You land now on the setup page. Here is the image you can use to set up the API. For instance, my setup is as follows:

Set up your certificate of status API

Once you’re ready, click on the “next” button. We are going to specify the data types for each of the fields we want our API to extract.

Define your model

To move forward, you have two possibilities:

Upload a json config
Copy the following JSON into a file and upload it on the interface

{
  "problem_type": {
    "classificator": { "features": [], "features_name": [] },
    "selector": {
      "features": [
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "entity_name",
          "public_name": "Entity name",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "is_integer": -1 } },
          "handwritten": false,
          "name": "file_number",
          "public_name": "File Number",
          "semantics": "amount"
        },
        {
          "cfg": { "filter": { "convention": "US" } },
          "handwritten": false,
          "name": "formation_date",
          "public_name": "Formation Date",
          "semantics": "date"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "type",
          "public_name": "Type",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "jurisdiction",
          "public_name": "Jurisdiction",
          "semantics": "word"
        },
        {
          "cfg": { "filter": { "alpha": -1, "numeric": 0 } },
          "handwritten": false,
          "name": "status",
          "public_name": "Status",
          "semantics": "word"
        }
      ],
      "features_name": [
        "entity_name",
        "file_number",
        "formation_date",
        "type",
        "jurisdiction",
        "status"
      ]
    }
  }
}

Or build your data model manually
Using the interface, add up to your data model each field.

In our example, here are the different field configurations we used:

  • Entity name: type String that never contains numeric characters.
  • File Number: type Number without specifications.
  • Formation Date: type Date with US format.
  • Type: type String that never contains numeric characters.
  • Jurisdiction: type String that never contains numeric characters.
  • Status: type String that never contains numeric characters.

Once you’re done setting up your data model, press the Start training your model button at the bottom of the screen.

Ready to train model

Train your Certificate of Status OCR

Train your model

You’re all set!

Now is the time to train your Certificate of Status deep learning model in the Training section of our API.

In a few hours (minutes if you're fast), you’ll get your first model trained and will be able to use your custom OCR API for parsing Certificate of Status in your application.

To get more information about the training phase, please refer to the Getting Started tutorial. If you have any question regarding your use case, feel free to reach out on our chat!

Updated 28 days ago


Certificate of Status OCR


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.