What is line-item detail? Definition, example, and why it matters
Accounts payable and procure-to-pay
Line-item detail is the itemized information on an invoice or payment, such as each product or service, quantity, unit price, tax, and amount, rather than a single total. AP needs it to match each line to the purchase order and receipt, code costs to the right accounts, and catch price or quantity errors a total would hide.
- Level
- Each product or service
- Core fields
- Quantity and unit price
- Supports
- Matching and coding
- Card data
- Level 3
What does line-item detail include?
Each invoice line describes one thing billed, with enough data to match and code it.
- Line number and PO line: Which PO line it bills
- Item: SKU, description, or service
- Quantity and unit of measure: How many, of what unit
- Unit price and extended amount: Price and quantity × price
- Tax and charges: Sales tax, freight, or fees on that line
Structured e-invoices, such as those sent over Peppol, carry lines as data, so they can be matched without re-keying. For commercial card payments, Level 3 data adds line-item detail to the card transaction.
Why does AP need line-item detail?
AP needs line-item detail because errors on different lines can cancel out in the total.
Example: Ravenna Packaging receives invoice INV-6203 on Thursday, October 22, 2026, against PO 3318. The totals match, but two lines don't. All amounts are illustrative.
| Line | PO | Invoice | Difference |
|---|---|---|---|
| 1. Cartons, 200 × $12.50 (PO) vs $12.00 (invoice) | $2,500 | $2,400 | ($100) |
| 2. Brackets, 500 × $3.00 (PO) vs $3.20 (invoice) | 1,500 | 1,600 | 100 |
| 3. Freight | 350 | 350 | 0 |
| Total | $4,350 | $4,350 | $0 |
A header-only match passes. A line-level match holds line 2 for a price variance and flags line 1, which may be a supplier error that gets rebilled later. Ravenna records the invoice as billed and holds line 2, and on Wednesday, October 28, the supplier sends a $100 credit memo that brings the bill to $4,250.
| Date | Account | Debit | Credit |
|---|---|---|---|
| Oct 22, 2026 | Inventory (lines 1 and 2) | 4,000 | |
| Inventory, freight-in (line 3, capitalized) | 350 | ||
| Accounts payable | 4,350 | ||
| Oct 28, 2026 | Accounts payable | 100 | |
| Inventory | 100 | ||
| Total | 4,450 | 4,450 |
What is line-item detail confused with?
Line-item detail is most often confused with header data and with the PO itself.
| Term | What it is | How it differs from line-item detail |
|---|---|---|
| Invoice header | Invoice-level data: supplier, invoice number, date, total, terms | The summary above the lines |
| Purchase order (PO) | Buyer's document authorizing a purchase, stating items, quantities, prices, and terms, sent to the supplier before delivery | Has its own lines that invoice lines match to |
| Invoice matching | Comparing an invoice against supporting documents such as the purchase order and receipt to confirm quantities, prices, and terms before approving payment | Works best at line level |
| Match tolerance | Allowed variance, as a percentage or dollar amount, between invoice and PO or receipt that still passes matching without being flagged as an exception | Usually set per line as well as per invoice |
Quick test: if you can match and code each product or service on the invoice separately, you have line-item detail.
Line-level vs header-level matching
Header-level matching compares only the invoice total with the PO; line-level matching compares each line's item, quantity, and price. Header matching is faster but, as the example shows, lets offsetting errors through.
Line-item detail at month end
Line-level data makes accruals and cost reports in the month-end close more accurate.
- Accruals: Accrue received but uninvoiced lines on partially invoiced POs
- Holds: Review line-level price and quantity holds before the payment run
- Coding: Check lines coded to the right accounts and cost centers
- Tie out: Agree GRNI and AP to the general ledger
Our AP Agent reads invoices from any source, runs two- and three-way matching and duplicate checks, routes each exception to a named owner until it's closed, and posts entries only after your team approves.
Common line-item detail mistakes
The most common line-item detail mistakes throw the lines away.
- Capturing totals only: Errors that offset across lines get paid
- Coding the whole invoice to one account by default: Code each line according to its accounting treatment, including capitalization of applicable freight
- Ignoring unit of measure: Cases vs units can make a match look off by a factor
- Matching freight to goods lines: Match it to its own PO line or tolerance