Invoice line items missing: when the job is billed but not completely

Last updated November 16, 2026 · 6 min read

Short answer

An invoice can be sent, paid, and still wrong — a part line dropped in transcription, a second labor block folded away. The check compares the job's full contents against the invoice's actual lines and lists what fell off, line by line.

The data reality

Where to export: Completed jobs' full contents (parts, labor, fees, equipment) crossed against their invoices' line items; the check lists missing or reduced lines per invoice.

Columns that matter: Invoice # · Job line · Expected amount · Invoiced amount · Difference

Job contents live in the FSM's job record (or the tech's paper ticket); invoice lines live in the accounting export — formats differ, and packages/discounts reshape lines. The check matches at job level with line-level comparison where exports support it, and flags invoices whose totals are short of job totals even when line detail is unavailable.

Why this system leaks

The tech replaces a blower motor and, while in the attic, a worn run capacitor — noted on the job, added to the truck's part count. The office builds the invoice from the ticket's top section: motor, labor. The capacitor line, lower on the ticket and half-erased, never makes the invoice. Payment arrives; the customer is satisfied; the invoice is 'done.' The $63 part is unrecoverable by any check that asks only 'was it invoiced?' — because it was.

Invoice creation is transcription, and transcription drops low-salience lines under time pressure. Every downstream signal — payment received, invoice closed, month reconciled — validates the incomplete document. The failure is invisible at the invoice level and visible only at the line level, where job contents meet invoice contents.

Paid is not the same as complete

Every billing check that stops at 'did an invoice exist and did it get paid' stops one level too shallow. The invoice is a document, and documents drop lines. The comparison that matters is the job's full contents against the document's actual lines — a check only a reconciliation performs.

Where lines drop

Bottom-of-ticket parts, second labor blocks, add-ons noted verbally, fees assumed included, discounts applied to the wrong line. The shapes vary; the mechanism is transcription under time pressure. The check's line-level comparison catches all shapes with one pass, and labels each gap so the invoice can be corrected precisely.

Correcting a paid invoice is routine

A missing line on a paid invoice is fixed with a corrected invoice or a supplementary one — customers accept documented additions far more readily than businesses expect, especially with the job details attached. The awkwardness of the call is small; the annual total of dropped lines is not.

A worked example

Invoice #8814 — blower motor replacement, sent and paid. The job record shows the motor ($412), labor ($180), and a run capacitor ($63) noted and used. The invoice carries the motor and labor; the capacitor line is absent.

Recorded work
$632.00
Invoiced
$458.00
Residual
$174.00

Residual = $174 — the capacitor, its markup, and the tax the line would have carried. Small, real, and multiply this by one dropped line a week across a year for the annual figure. A corrected invoice or credit-note-plus-rebill recovers it cleanly.

What the data cannot show

  • Line detail depends on export richness — where the FSM export lacks line-level job contents, the check falls back to total comparison, catching short invoices but not naming the missing line.
  • Line consolidation by the office (combining parts into one 'materials' line) is billed-and-legitimate — the check compares values, not line counts, so consolidation is not flagged.

Questions shops ask

How do I find invoices with missing line items?

Compare each invoice's lines to its job's full record — parts used, labor logged, fees applied. The check automates this at line level where exports allow, and falls back to invoice-versus-job totals where they do not, listing every short invoice in minutes.

Can I bill a customer for a line that was missing from a paid invoice?

Yes — issue a corrected or supplementary invoice with the job details. Most customers accept documented additions; the work was received. Handle it as a correction with an apology for the oversight, not a new charge.

Doesn't the FSM total catch this?

Job totals catch short invoices only if someone compares them to invoice totals — which no native report does across history. The check runs the comparison over every invoice, every month, so one dropped line a week stops being the cost of doing business.

See a sample report for your export

See a sample report for your export

Related