See what survives the trip from invoice to Excel

Lost zeros, rounded values and missing units all create work for the next reviewer. Keep the source meaning intact, then use a real invoice trial to check whether ParseMill produces the workbook you need with less manual entry.

Inspect the interactive invoice sample, then try your own invoices. Eligible new workspaces get 10 pages for 7 days after email verification, with no card or automatic subscription.

Five small changes that alter the meaning

Source textKeepReview before using it
42.60 MPaResult 42.60; unit MPaDo not silently remove the displayed precision
< 0.0100 %The inequality and all decimal placesA limit is not a measured value of 0.0100
0 mgThe explicit zeroZero and a missing result mean different things
1,234 g/cm3The original comma and unitResolve decimal separator versus thousands separator
00042A text identifier with leading zerosCheck spreadsheet import has not changed it to 42

These values appear in the public synthetic material report. They were chosen to make silent changes visible. The public sample preserves their raw text; it does not decide what the ambiguous density comma means or convert units. Use it to inspect the evidence, then test your invoice values separately in the current invoice workspace.

Keep missing, zero and unsupported separate

If a source cell is blank, do not fill it with zero or a value copied from a neighbouring row. A missing field means no value was extracted. An unsupported field means the parser cannot safely interpret it. Neither state establishes what the true result should be.

For example, a hypothetical blank moisture result should remain missing until checked. This is a decision example, not an additional extracted row in our sample. The actual residue result is an explicit 0, so replacing it with a blank would discard evidence.

Normalize only as a separate, documented step

Keep Result_raw and Unit_raw columns in a downstream working sheet. If a qualified reviewer converts units, record the conversion rule and put the converted value in new columns. Do not overwrite the original reading.

A field labelled MPa cannot be compared with another unit merely because both cells contain numbers. Methods and conditions may also differ. ParseMill does not currently perform automatic unit normalization or technical equivalence checking.

Check the spreadsheet application too

An extraction can preserve 00042 while a later CSV import removes its zeros. Open CSV through your spreadsheet’s import workflow and explicitly choose text for identifiers. Check decimal separators and scientific notation before distributing the file. The XLSX sample provides a second inspectable format; compare both with the source when validating your handoff.

Put it to work with ParseMill

Make one real invoice your buying test

Choose an invoice you would otherwise enter by hand. Upload it, inspect the extracted fields, correct what needs attention and download Excel. Include every checking minute in the comparison. Subscribe if the result and the time saved make sense for your recurring work.

Eligible new workspaces: 10 pages for 7 days after email verification. No card or automatic subscription.

Invoice processing: $49 USD/month · 500 PDF pages · one user. Buy only after you have checked the fit on your own invoices.

Sources and evidence

Public examples are synthetic. Each example and evaluation describes its tested inputs and limitations. This page is authored by ParseMill.