System Schemas

Prepared schemas for the most common documents. They cannot be modified, but you can use them as a basis for creating your own (Create a copy).

Invoice

The richest schema and also the default. Besides the header and both sides, it includes items, VAT summary by rates, payment details, and document type.

The type is read by the model from the document: invoice, credit note, debit note, proforma invoice, tax document for received payment, simplified tax document. The document is accounted for based on the type — the credit note goes into ISDOC, Pohoda, and Money S3 as a correcting document, into UBL as CreditNote. The type can also be set rigidly in the binder or during upload; if a different model reads it, it will report it as a finding.

Receipt

A receipt from a store, restaurant, or service. It does not have a customer — it typically isn’t present on a receipt — and assumes that payment occurred immediately. It supports VAT rates from the summary, discounts, and payment methods. It goes into Pohoda and Money S3 as a cash or bank document depending on whether the payment was made in cash or by card; into ISDOC as a simplified tax document.

Fuel Receipt

Only for refueling at a gas station. It adds the volume in liters to the receipt fields, the price per liter including and excluding tax, type of fuel, station, and for each item a flag indicating whether it is fuel. The registration number and odometer reading are read only if they are on the document; a regular receipt does not have them — the vehicle is identified by the binder.

Above these fields is an overview of refueling in Overviews.

What is Not Included

Delivery notes, orders, or bank statements do not have a system schema. The delivery note is among the templates of own schemas, so you can obtain data from it as JSON or a table, but it will not go into accounting. We do not recommend processing bank statements — the bank issues it exactly in ABO, GPC, or CAMT, while PDF recognition is an estimate.