Skip to main content
A schema lists the fields anyformat looks for in each document. It says two things:
  • Which fields you want: the invoice number, the date, the total.
  • What type of value each field holds: text, a number, a date.
An invoice schema might hold three fields: invoice number as text, issue date as a date, and total amount as a decimal. Give anyformat that schema, and every invoice comes back with those three fields filled in. A schema does not read documents. It describes the result you want. The workflow does the reading. The schema tells it what to aim for. Schema view

​
When you use schemas

You use a schema when:
  • You want consistent output across many documents
  • You care about structure, not just raw text
  • You plan to verify or improve results over time
Most workflows are built around a single schema.

​
What a schema is not

A schema is the what: the list of fields you want back. It is not the how. It does not say how to read the document or where on the page to look. anyformat handles that. You describe only what the finished result looks like.

​
What’s next?

Fields

Define individual pieces of information within a schema

Instructions

Write plain-English guidance for better accuracy