Document templates

Template-guided extraction, the template library, and customizing fields.

When you create a parser you choose how extraction is guided.

Two ways to start

Pick a document type (recommended when one fits). The parser starts from a template with a proven field schema. Extraction is aligned to that schema, so every document returns the same field keys, ready for column mapping and delivery.
Build from my document. Upload one sample document instead of picking a type. Parsedit reads it once, proposes the fields and tables it found, and you rename, retype or remove them before saving. The parser that comes out works exactly like any other: same review, same destinations.

Either way, the template is a starting point you can keep editing later.

Template library

Parsedit ships templates for common business documents, including:

Finance: invoices, sales invoices, receipts, bank statements, credit card statements, financial statements, remittance advice, payment processor payouts, utility bills.
Operations: purchase orders, delivery notes, shipment documents, work orders, contracts, insurance documents, reports.
People: resumes, job applications, pay stubs, application forms, medical records, academic transcripts.
US tax forms: W-2, W-9, W-8BEN, W-8BEN-E, 1099-NEC, 1099-K, checks.
EU e-invoicing: EN 16931 core invoice, ZUGFeRD, XRechnung, FatturaPA, Facturae, EU VAT invoice.
UAE e-invoicing: PINT-AE (PEPPOL) invoices.

If your document type is not listed, choose Build from my document and let a sample define the fields.

Customizing fields

Templates are starting points, not constraints. In the parser settings you can:

Rename fields to match your spreadsheet columns or accounting categories.
Add fields the template does not cover.
Remove fields you do not need.
Adjust field types, for example dates and numbers, so values are normalized consistently.

Changes apply to future uploads. Existing documents keep the fields they were extracted with, and you can edit any value during review.

Two ways to start

Pick a document type (recommended when one fits). The parser starts from a template with a proven field schema. Extraction is aligned to that schema, so every document returns the same field keys, ready for column mapping and delivery.

Build from my document. Upload one sample document instead of picking a type. Parsedit reads it once, proposes the fields and tables it found, and you rename, retype or remove them before saving. The parser that comes out works exactly like any other: same review, same destinations.

Either way, the template is a starting point you can keep editing later.

Template library

Parsedit ships templates for common business documents, including:

Finance: invoices, sales invoices, receipts, bank statements, credit card statements, financial statements, remittance advice, payment processor payouts, utility bills.

Operations: purchase orders, delivery notes, shipment documents, work orders, contracts, insurance documents, reports.

People: resumes, job applications, pay stubs, application forms, medical records, academic transcripts.

US tax forms: W-2, W-9, W-8BEN, W-8BEN-E, 1099-NEC, 1099-K, checks.

EU e-invoicing: EN 16931 core invoice, ZUGFeRD, XRechnung, FatturaPA, Facturae, EU VAT invoice.

UAE e-invoicing: PINT-AE (PEPPOL) invoices.

If your document type is not listed, choose Build from my document and let a sample define the fields.

Customizing fields

Templates are starting points, not constraints. In the parser settings you can:

Rename fields to match your spreadsheet columns or accounting categories.

Add fields the template does not cover.

Remove fields you do not need.

Adjust field types, for example dates and numbers, so values are normalized consistently.

Changes apply to future uploads. Existing documents keep the fields they were extracted with, and you can edit any value during review.