Skip to navigation

Extract fields

View as Markdown

Extract pulls the fields you name out of a document and returns them as structured JSON. Examples include an invoice number, a PAN, a statement period, or every row of a transaction table. Each value comes with a confidence score, and you can see where on the page it came from.

You describe the fields in a schema. You can write it yourself, start from one of 40+ templates, or have AI draft it from your documents.

Step 1: Add your document

Click Extract under Products in the sidebar. Drag and drop your files, click Upload documents, or pick a demo document (GSTR-3B.pdf or Bank statement.pdf) under Try a demo doc.

Extract page with an upload area on the left that accepts PDF, JPEG, PNG, TIFF, or ZIP, up to 10 files or 30 pages in total, and a Schema panel on the right with Form and JSON toggles, Templates, Generate using AI, an empty field row, Add field, and an optional Instructions box.
The Extract playground: documents on the left, schema on the right.

Accepted formats: PDF, JPEG, PNG, TIFF, ZIP. Each run takes up to 10 files or 30 pages in total. For more, use the Extract API.

A demo document comes with a matching schema. If you’ve already built a schema, the app asks before replacing it.

Step 2: Build the schema

The Schema panel lists the fields to extract. Each field has three parts:

  • Field name. What the field is called in the output, for example Invoice number.
  • Type. string, number, integer, boolean, date, enum, or array of objects.
  • Description (optional). A hint about where or how to find the value, for example The invoice number, near the top.

You can fill the schema in three ways:

Click Templates to open Extraction templates. Search by document or field name, then click a template to load its fields. Everything stays editable.

Extraction templates dialog with a search box, a Saved configurations list, and a Start from scratch button.
Extraction templates: your saved configurations first, then ready-made schemas by industry.

The dialog lists your Saved configurations first, then templates grouped by workflow:

GroupTemplates
Loan and insurance underwritingBank statement, Salary slip, Form 16, ITR acknowledgement, PAN card, Aadhaar, Credit bureau report, Property valuation report, Land deed
Accounts payableVendor invoice, GST return (GSTR-3B), Purchase order, Goods receipt note, Delivery challan, Credit / debit note, Cancelled cheque, TDS declaration
Purchase order lifecyclePurchase requisition, Vendor quotation, Order acknowledgement, Packing list
Claims processingClaim form, Medical bill, Discharge summary, Surveyor / repair estimate, FIR / incident report, Death certificate
Trade financeLetter of credit, Bill of lading, Commercial invoice, Certificate of origin, Bill of exchange, Inspection certificate
Cheques processingCheque (CTS image), Deposit / pay-in slip, Dishonour / return memo
More templatesInsurance claim form, Credit card statement, KYC document, Resume screener, Invoice screener, Background verification, Court appeal, GST registration form, Historic land deed

Click Start from scratch to close the dialog with an empty schema.

Lists, tables, and fixed values

  • Tables and repeating items. Use the array of objects type for anything that repeats, such as transactions, line items, or family members. Click + Add column inside the field to define what each row contains.
  • Fixed sets of values. Use enum and list the allowed values (for example debit and credit). The output will always be one of them.
Extract page with a credit card statement on the left and the Schema panel on the right listing fields such as Account holder, Account number, IFSC, Statement period, Bank name, Branch name, Customer ID, Opening balance, and Closing balance, each with a type dropdown.
The Bank statement template loaded into the schema, ready to run on the demo document.

Instructions

Use the optional Instructions box for anything that applies to the whole document, for example Amounts are in INR. Return dates as DD/MM/YYYY.

Step 3: Run the extraction

Click Run extract on N documents. The credits the run will use are shown under the button. While it runs, the Output tab shows progress, for example Processing · 2 of 3 pages done. Large documents can take a few minutes. You can leave the page and reopen the run from History.

Step 4: Review the results

When the run is Done, the Output tab lists every field with its value. Switch between Results and JSON at the top right, or go back to Setup to change the schema and Run again.

Extract results for a credit card statement: the source document on the left with boxes around extracted values; on the right, the Output tab lists fields such as Account number, Statement period, Bank name, Opening balance, and Closing balance with 100% confidence badges, and Not found on the document for missing fields.
Extract results: every value has a confidence score, and boxes on the source show where it came from.
  • Confidence. A percentage badge on every value. Low scores flag what to check first.
  • Source location. Extracted values are boxed on the source document, so you can check each value against the page.
  • Not found. Fields that aren’t in the document show Not found on the document instead of a guessed value.
  • Tables. Array fields render as a table, with a row count such as 20 rows · spans pages. A dashed line marks where a table continues onto the next page.
  • Editable. All values are editable. Click any value to correct it before you download.

Step 5: Download or reuse

  • Download saves the result as a JSON file. It includes the extracted values (result), a confidence score and source location for every field (annotations), and page counts (usage).
  • Save config saves the schema and instructions under a name so you can reuse them. See Save and reuse Configs.
  • View API code gives you cURL, Python, or JavaScript that runs this exact schema through the Extract API.

Improve accuracy

“Total” is vague. “Numeric total at the bottom of the invoice, after taxes, in INR” is not. The description is the main hint the model uses to find a field.

Use number for amounts and date for dates, so you get values you can compute with. Use enum when only a few values are valid, and array of objects for anything that repeats.

Amounts like ₹ 1,24,500 can come back with symbols and separators. Add “Return amounts as plain numbers without currency symbols or commas” to Instructions.

If one PDF holds several different documents, Split it first and run a matching schema on each part.

Blurry or skewed scans hurt accuracy more than any schema change. Rescan at 300 DPI and straighten the page before uploading if you can.