Schemas and Outputs

A schema specifies what data is read from a document and how it is named. The output format specifies how it is recorded in a file. These are two independent things — one schema can be outputted in multiple formats.

System and Custom

• System schemas are prepared by us: invoice, receipt, fuel receipt. They cover common documents and are continuously improved. Accounting exports are based on their fields.
• Custom schemas are defined by you when you need fields that are not included in the system schemas. Their output is JSON, XML, YAML, table, or PDF.

How the Schema is Selected

By default, this is done automatically (Automatically Recognize). The model examines the document and selects whether it is an invoice, receipt, or fuel receipt; it reads the type of invoice (credit note, pro forma invoice…) from the document. In the document details, you can see that the type was selected by the model.

The selection can be overridden during upload, or permanently in the folder. If the model makes a mistake, it will offer to process the document again with the correct type — this is free the first time. Changing the type for a document where you selected the type yourself costs the same as uploading.

Next Steps

• System Schemas — what we can read from common documents.
• Custom Schemas — how to define your own fields.
• Export Formats — where you will receive the results.
• ISDOC, UBL, and CII — electronic invoicing standards in detail.