Identify a missing invoice amount instead of filling in zero

Where the extra work starts

If the workbook quietly fills the gap with zero, the reviewer may never see the problem. Keep the missing value visible and resolve it against the invoice.

Upload a representative supplier invoice, inspect its extracted fields and line items beside the PDF, then download Excel. Put the awkward invoice in your trial too: the useful result is less total work after corrections.

Do not infer an amount from quantity and price and label it as extracted. A calculated value may be useful in a separate reviewer-approved check, but the raw source field must remain identifiable.

A practical way to get it right

Inspect the source cell at sufficient magnification and compare its row and column boundaries. Determine whether the amount is blank, unreadable, displaced or present elsewhere. Record the source location and the reason the value remains unresolved.

Keep raw value, field state and review note separate. Use an empty raw amount for a genuinely blank source cell and an explicit state such as “missing in source.” Preserve an actual printed 0.00 as text with its own source evidence. Do not use the same empty state for a parser omission when the source contains a value.

Before exporting, check how the receiving spreadsheet handles blanks and text. Avoid formulas or import transformations that replace all missing values with zero. If a calculation is needed, perform it in a separate column with its assumptions and reviewer decision.

Microsoft: Import or export text and CSV files explains that CSV opening applies default interpretation. Test the actual import route so blank fields and text values are not silently transformed.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

The three rows require different handling. C22 is not repaired by copying C21's zero, while C23 can be corrected because the source provides the value. Copy the source, raw and state fields into a test fixture. Retain the original extraction for C23 so the reviewer can see what was changed and why.

Catch the cases that create rework

A faint value, white text or cropped page can look blank. Inspect the approved original before declaring the source empty. If the amount is unreadable, label it unreadable rather than missing and request a clearer source through the established route.

A matching document total does not justify filling a blank by subtraction. Such a calculation introduces an interpretation that belongs in a separate review, not in raw transcription.

Microsoft: Apply data validation to cells supports lists of permitted states. Use distinct states for missing source, unreadable source and extraction correction rather than one vague exception label.

Decide whether the change is worth keeping

After export and re-import, compare the zero and blank cases again. Confirm that the review-state column survived and that no formula silently converted missing values to zeros. The accepted register should allow a new reviewer to distinguish source absence, extraction failure and explicit zero without reconstructing the whole history.