Where the extra work starts
Check its label and context before using it so a discount, return or credit is not flattened into an ordinary purchase row.
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.
This check concerns faithful transcription. Whether a line represents a credit, reversal, adjustment or another accounting treatment remains a decision for the responsible professional using the full document context.
A practical way to get it right
Inspect quantity, price and amount separately for signs, parentheses and nearby labels. Record the document type as stated and retain the source reference. A negative quantity with a positive price is a different printed pattern from a negative amount alone; preserve what is actually present.
Compare raw extracted strings with the visible source before calculating. If the source uses a trailing minus or parentheses, record that notation and verify the receiving application's interpretation separately. Do not standardize the notation in the raw column without keeping the original.
Create a small export test containing positive, negative and zero values. Re-import through the intended spreadsheet route and inspect both stored values and display. If numeric conversion is required, keep a separate converted column and document the conversion rule.
Microsoft: Text Import Wizard includes an option for trailing minus signs. Use it only in a deliberate conversion test, retaining the original source string alongside the numeric result.
What this looks like on a real task
Synthetic example. The people, references and figures below are invented to demonstrate the method.
| Source notation | Raw register value | Review requirement |
|---|---|---|
| -24.00 | -24.00 | Confirm minus retained |
| 24.00- | 24.00- | Interpret trailing sign only in separate conversion |
| (24.00) | (24.00) | Confirm source convention with reviewer |
| 0.00 | 0.00 | Retain explicit zero |
The examples show different printed notations, not a claim that they are interchangeable in every document. Copy the raw-string comparison and add source page and field location. A receiving spreadsheet may interpret the strings differently, which is why a visual display check alone is insufficient.
Catch the cases that create rework
A short dash can be confused with a minus, a separator or an empty-value marker. Check its position and the source's surrounding convention. If the PDF text layer omits the sign, correct only from visible source evidence and record the reason; do not infer a sign from a total.
Do not apply a blanket absolute-value transformation to make an export easier to sum. That removes a distinction the reviewer may need.
OpenPeppol: Invoice line syntax distinguishes quantity, price details and line amount. Review their signs independently rather than assuming the document title determines all field signs.
Decide whether the change is worth keeping
The accepted output should preserve every sign and notation exactly in raw fields, with any conversion and unresolved meaning visible separately. Compare totals only under a documented, appropriate calculation rule. Keep signed cases in regression examples whenever import settings or export formats change, since a formatting change can alter what the next user sees.
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 editorial notes
- Microsoft: Text Import WizardChecked 2026-10-25
- OpenPeppol: Invoice line syntaxChecked 2026-10-25
Written by ParseMill. Worked examples are illustrative process examples, not customer results. Software availability can vary by subscription and region; check the linked documentation for your account. Review decisions and approvals remain with your team.