Every supplier formats invoices differently. The invoice number might sit top right on one and bottom left on another, the tax ID might be labelled GSTIN, VAT no. or not labelled at all, and line items might wrap across two pages. Template-based tools need a new template for each layout. This guide shows a layout-independent way to extract invoice data.
What to extract from an invoice
Most teams need some version of this:
| Field | Type | Notes |
|---|---|---|
| Supplier name | text | |
| Invoice number | text | keep as text: leading zeros matter |
| Invoice date | date | |
| Due date | date | |
| Tax ID | text | GST, VAT or similar |
| Currency | choice | e.g. USD, INR, EUR |
| Subtotal | number | |
| Tax | number | |
| Total | number | |
| Line items | table | description, quantity, unit price, amount |
Why templates break and schemas don’t
A template says “the total is at these coordinates”. A schema says “find the total”. HussleBook’s vision-language model (VLM) reads each page as an image, finds the field wherever it is, and returns it in the type you asked for. One schema covers invoices from every supplier, including scanned and photographed ones.
Step by step
- Upload a few invoices from different suppliers. HussleBook proposes a schema from what they have in common.
- Adjust the fields. Add any field the proposal missed, set types, and write short instructions where you need a rule, such as “total including tax”.
- Test on a sample and compare each value with the invoice. Re-test after every change.
- Upload the batch. Drag in a folder of PDFs or images. Each document shows its own progress.
- Review. Values the model is unsure about are flagged as needing review. Every value links to the page it came from, so checking takes seconds.
- Export JSON (line items stay nested under each invoice) or an Excel workbook (a summary sheet plus a line-items sheet).
Tips for cleaner invoice data
- Keep invoice numbers as text, not numbers, so
000123stays000123. - Use a choice field for currency so values come back consistent.
- Check totals against line items after export: a quick sum in your spreadsheet catches the rare misread.
- Run invoices and receipts as separate workflows. They have different fields, and a focused schema is more accurate than a combined one.
Common questions
Does it work with handwritten or stamped invoices?
The model reads stamps, handwriting and layout as part of the page image. Faint or partly hidden values may be flagged for review, so check those against the source.
Can I process invoices in Indian GST format?
Yes. Add a GST number field. The schema is yours, so any regional field can be included.
Is my data used to train models?
See the privacy policy for how documents are processed and which providers are involved.
Start with schema extraction or compare plans.
Try HussleBook free with 150 credits (≈ 60–75 pages).