Set Up Billing Fields and Line Items for Invoices
Configure invoice fields in the dashboard — define billing fields, run a test batch, and export structured data without writing code.
Ready to set this up? Sign up for PerfectParser and get 20 free credits — no credit card required.
What this guide helps you do
This guide shows how to configure an invoice parser in PerfectParser, choose billing fields, run a test batch, and export structured results. After you upload a sample, field detection runs automatically. Compare the Schema tab with the recommended fields below and add or rename anything that does not match your layout.
Why invoices are hard to parse
Invoices look simple on the surface, but vendor layouts vary widely — some put the invoice number in the header, others bury it near payment instructions. Tax lines may appear as a single VAT total or as per-line tax columns, and multi-page invoices often repeat headers while line items continue on page two. Currency symbols and decimal separators differ by region, so a parser configured on US-format invoices may misread European totals unless field types and descriptions are explicit. Getting the line_items table right is usually the hardest part: quantity, unit price, and line total must stay aligned row by row, and subtotal or tax fields must not be stored as plain text when you need them for reconciliation.
Recommended Fields
We suggest configuring the following schema fields for your Invoice Parser to capture all essential billing data. You can add, edit, or remove these fields at any time in the schema editor.
| Field Name | Type | Description |
|---|---|---|
invoice_number | Text | The unique invoice reference or identifier (e.g., INV-2026-001). |
vendor_name | Text | The name of the supplier or business billing you. |
vendor_tax_id | Text | The supplier's tax registration or VAT number (e.g., EU123456789). |
issue_date | Text | The date the invoice was generated by the supplier. |
due_date | Text | The payment deadline or due date. |
subtotal | Number | The net amount before taxes, discounts, or shipping. |
tax_amount | Number | The total tax or VAT amount billed. |
total_amount | Number | The final gross amount due. |
currency | Text | The billing currency code (e.g., USD, EUR, GBP). |
line_items | Table | Table containing description, quantity, unit_price, and total_amount for each row. |
Set up this parser in the dashboard
Create a parser
Go to Parsers → New Parser in the dashboard. Give it a name like "Invoice Parser". You can set the parser name while detection runs.
Upload a sample document
Drag and drop a representative invoice (PDF, PNG, or JPEG). Use a real file from one of your suppliers — the AI uses it to learn where fields appear on that layout. Field detection and sample extraction start automatically.
Review detected fields
Field detection and sample extraction start as soon as the upload finishes. Open the Schema tab and compare detected fields with the Recommended Fields table above. Rename, remove, or add fields, and edit each field's instructions. Check sample values on the Results tab.
Review and save your schema
Check that each detected field matches the correct type (Text, Number, or Table). Confirm subtotal, tax_amount, and total_amount are Number, not Text. Edit any field names or descriptions, then click Save parser. You can edit fields later on the parser Fields tab.
Run a test batch
Open Run Extraction, choose how your files are organised, upload a small test set of invoices, and click Start batch extraction. Review the run on the Results tab and export to CSV or Excel.
Common mistakes
- Storing
subtotal,tax_amount, ortotal_amountas Text instead of Number, which breaks totals in exports and downstream systems. - Skipping the
line_itemstable and capturing only header totals — you lose item-level detail needed for PO matching or GL coding. - Using a credit note or pro-forma as the sample document when your production files are standard tax invoices with different field placement.
- Mapping
currencyfrom a symbol alone (e.g. "$") without checking whether the vendor bills in USD, CAD, or another dollar-denominated currency.
Next steps
Test your first extraction free — sign up for PerfectParser, no credit card needed.
FAQs
Do I need a sample invoice to set up this parser?
Yes. Upload one representative invoice from a key supplier during setup. The AI uses it to learn where fields like invoice number, vendor name, and line items appear on that layout. You can refine the schema on the Schema tab after detection finishes.
What if detection misses a field I need?
Open the Schema tab and add the field from the Recommended Fields table, or rename a detected field to match your labels (for example, 'Bill Ref' instead of 'Invoice Number'). Add the line items table manually if detection did not include it.
How many credits does setup and a test extraction use?
Parser setup itself is free. Each page processed during a test batch costs 1 credit. A typical single-page invoice uses 1 credit; a three-page invoice uses 3. Your account includes 20 free credits to run initial tests.
Looking for product features and use cases?