Invoice Glossary

Invoice Processing Glossary: Key Terms Explained

Plain-English definitions of the terms you meet when you extract, match, and process invoices: OCR, line items, 3-way matching, GL coding, e-invoicing, and more. Each definition answers the question in its first sentence, then links to a full guide.

Data Extraction and OCR

Terms for how invoices are read and turned into structured data.

Invoice data extraction

Invoice data extraction is the process of reading an invoice and turning its contents (vendor, invoice number, dates, line items, tax, and totals) into structured data you can use in a spreadsheet, accounting system, or ERP. It can be done by hand, with template-based OCR, or with AI models that understand invoice layouts without setup.

Read the full guide →
Invoice OCR

Invoice OCR (optical character recognition) converts the text on a scanned or PDF invoice into machine-readable characters. Plain OCR only reads text; it does not know which number is the total or the tax, so it is usually combined with templates or AI to map text to invoice fields.

Read the full guide →
Line-item extraction

Line-item extraction captures every row of an invoice's item table (description, quantity, unit price, line total) rather than only header fields like vendor and total. It is the hardest part of invoice OCR because tables vary in layout, wrap across lines, and continue over multiple pages.

Read the full guide →
Template-based OCR

Template-based OCR extracts fields by reading fixed zones that someone has drawn for each supplier's invoice layout. It works well for a few consistent formats, but every new vendor or layout change needs a new or updated template.

How no-template AI extraction differs →
Intelligent document processing (IDP)

Intelligent document processing (IDP) is software that combines OCR, machine learning, and validation rules to classify documents and extract structured data from them. Invoices are the most common IDP use case; large IDP suites add workflow and exception handling on top of extraction.

Read the full guide →
Agentic invoice processing

Agentic invoice processing uses AI agents that take multi-step actions on an invoice, such as extracting data, checking it against records, and routing exceptions, instead of only returning extracted fields. Most small businesses get the bulk of the value from accurate extraction alone.

Read the full guide →
Structured invoice data (JSON, CSV, Excel)

Structured invoice data is invoice information organized into named fields and rows, for example a JSON object, a CSV file, or an Excel sheet with one column per field. Structured output is what lets invoice data flow into accounting software, automations, and AI tools without retyping.

Read the full guide →
Batch processing

Batch processing means extracting data from many invoices in one run and collecting the results in a single, consistent table. It replaces opening and handling invoices one at a time.

Read the full guide →
Invoice digitization

Invoice digitization is converting paper invoices into digital files and then into searchable, structured data. Scanning creates an image; extraction is the step that turns that image into usable fields.

Read the full guide →

Accounts Payable and Matching

Terms from the accounts payable process that extracted invoice data feeds into.

Invoice processing

Invoice processing is the end-to-end handling of a supplier invoice: receiving it, capturing its data, checking it against orders and receipts, approving it, recording it in the books, and paying it. Data capture is one step of that process, and usually the slowest when done by hand.

Read the full guide →
Accounts payable (AP) automation

Accounts payable automation is software that handles some or all of the AP process (invoice capture, matching, approvals, and payments) with less manual work. Full AP suites cover the whole flow; extraction tools automate the data-capture step and hand clean data to the rest.

Read the full guide →
Purchase order (PO)

A purchase order is a document a buyer sends to a supplier to authorize a purchase at agreed items, quantities, and prices. The supplier's invoice is later checked against the PO before payment.

Purchase order vs invoice →
2-way matching

2-way matching compares a supplier invoice with its purchase order to confirm that items, quantities, and prices agree before the invoice is approved for payment.

Read the full guide →
3-way matching

3-way matching compares three documents before paying a supplier: the invoice, the purchase order, and the goods receipt (proof that the items arrived). Payment is approved only when all three agree within set tolerances.

Read the full guide →
Invoice reconciliation

Invoice reconciliation is checking invoices against related records, such as purchase orders, receipts, statements, or payments, to confirm amounts agree and catch errors or duplicates.

Read the full guide →
GL coding

GL coding is assigning each invoice, or each line item on it, to the correct general ledger account (for example office supplies or freight) so the expense is recorded in the right place in the books.

Read the full guide →
Duplicate invoice

A duplicate invoice is the same bill submitted or entered more than once, which can lead to paying a supplier twice. Duplicates are usually caught by comparing invoice number, vendor, amount, and date across records.

Invoice Types and Fields

Terms for the documents themselves and the fields they contain.

Invoice number

An invoice number is a unique identifier the seller assigns to each invoice, usually sequential, so the invoice can be tracked, referenced in payments, and kept from being recorded twice. Most tax authorities require one on every invoice.

Line items

Line items are the individual rows on an invoice that list each product or service billed, typically with a description, quantity, unit price, and line total. Their sum (plus tax, shipping, and discounts) makes up the invoice total.

Read the full guide →
Receipt

A receipt is proof that a payment has already been made, while an invoice is a request for payment that is still due. Receipts typically carry fewer fields, such as merchant, date, items, total, and payment method.

Read the full guide →
Proforma invoice

A proforma invoice is a preliminary bill sent before goods are delivered or work is done, showing the expected items and costs. It is a quote-like document, not a request for payment, and it is not recorded as a sale or an expense.

Credit note

A credit note is a document a seller issues to reduce or cancel the amount of an earlier invoice, for example after a return, a pricing error, or a discount. It is recorded against the original invoice.

Multi-currency invoice

A multi-currency invoice is billed in a currency different from the buyer's reporting currency, so the amount must be converted at an exchange rate (usually the invoice date or payment date rate) when it is recorded.

E-invoicing

E-invoicing is sending invoices as structured data in a standard format (such as UBL, ZUGFeRD, or XRechnung, often over the Peppol network) that the buyer's system can read directly, instead of as PDFs or paper. A PDF emailed as an attachment is a digital invoice, but not an e-invoice in this sense.

Peppol

Peppol is an international network and set of standards for exchanging e-invoices and other procurement documents between businesses and governments. Several countries use it as the backbone of their e-invoicing mandates.

Pricing and Measurement

Terms for comparing what invoice tools cost and how well they perform.

Cost per invoice

Cost per invoice is the total cost of processing one invoice, including labor, software, and error correction. It is the standard way to compare manual processing with automated tools.

Read the full guide →
Per-page vs per-invoice pricing

Per-page pricing charges for every page processed, while per-invoice pricing charges once per invoice regardless of length. For multi-page invoices, per-page and credit-based models can cost several times more than per-invoice plans.

Read the full guide →
Field-level accuracy

Field-level accuracy is the share of individual fields (such as total, date, or a line item's quantity) that a tool extracts correctly across a test set. It is more meaningful than document-level accuracy, which only counts invoices with zero errors.

See the Invoscope accuracy benchmark →

See These Terms in Action on Your Own Invoices

Upload an invoice and get vendor, dates, line items, tax, and totals back as structured data. 10 invoices every month on the free plan, no credit card.