Getting Started
Choosing Document Type
When you create a parser, you select a document type. This sets the default fields and tells the AI what kind of document to expect.
Invoice
Vendor invoices and contractor bills. Includes default fields for vendor name, invoice number, date, due date, amounts, and line items.
Use for any bill you receive from a supplier or contractor.
Receipt
Point-of-sale receipts and expense receipts. Includes default fields for merchant, date, items purchased, subtotal, tax, total, and payment method.
Use for employee expense receipts or retail purchase records.
Purchase Order
POs from suppliers or buyers. Includes default fields for PO number, vendor, issue date, delivery date, line items, and total.
Use when processing incoming purchase orders from customers or outgoing POs to suppliers.
Bank Statement
Monthly bank or credit card statements. Includes default fields for account number, period, opening balance, closing balance, and transaction table.
Use for bank reconciliation workflows or transaction categorisation.
Custom
Start with a blank schema. No default fields — you define everything from scratch.
Use for document types not covered above: contracts, delivery notes, medical records, etc.
Not sure which to pick?
When in doubt, choose the closest built-in type rather than Custom. You can always add or remove fields later. The built-in types come with sensible defaults that cover the majority of use cases.
Was this helpful?