Recognize spaces used as digit-group separators

A space can carry structure

Check the source convention so the extracted amount survives import without manual repair.

Test an invoice with the dates, quantities or amounts you find hardest to copy accurately. ParseMill puts extracted invoice fields beside the source for review and correction before export. Open the downloaded workbook in your usual spreadsheet application and check those values there too.

Check the type of space as well. A regular space, a nonbreaking space and a narrow nonbreaking space can look similar while behaving differently in search, splitting and conversion. Record normalization as a separate operation so the original remains recoverable.

Compare three invented source layouts

The same broad cleanup rule cannot serve all four cases. Deleting spaces from the second row would invent 12345.6. Splitting the first row would destroy a valid grouped number. The final row should remain unresolved rather than being forced into a familiar three-digit pattern.

NIST: SI notation checklist describes grouped digits separated by spaces in SI writing. That establishes a legitimate notation possibility, not proof that every space in extracted text has that role.

Review a candidate grouping rule

1. Inspect the source cell boundaries and heading. Confirm that all digits belong to one field and one observation.
2. Look for a stated numeric convention and unambiguous examples in the same source range. Record the evidence supporting grouping.
3. Retain raw text, then normalize only confirmed grouping characters in a separate field. Keep identifiers and unresolved strings outside the rule.
4. Compare the converted value with the expected fixture and reopen the export. Check that later splitting or import steps do not reintroduce ambiguity.

Unicode: Normalization forms distinguishes character normalization forms. Choose a documented text operation rather than assuming all visually similar spaces are identical or semantically disposable.

Catch bad joins and bad splits

An extraction that joins adjacent columns can create a believable grouped number. Check row identity and neighboring headings before accepting it. Conversely, a parser may split a grouped number at its internal space and shift the unit into the result column. Inspect the entire row when either error appears.

Do not infer a missing digit from the expected grouping size. A damaged scan with 1 23 may be incomplete, incorrectly copied or an intentional code. Keep the uncertainty attached to that record.

Check the outcome against the source

The fixture passes when the first example becomes a reviewed numeric value, the second remains two fields, the identifier retains its space and the unclear string remains on hold. Save the normalization rule with the affected source range.

In the invoice trial, include grouped amounts beside quantities or other numeric columns. Review each complete line beside the PDF and open the Excel output. Compare the checking and correction effort with your current method before committing to a plan.