Check extraction and business approval separately

Invoice data validation starts by comparing the extracted record with the source. Is the invoice number correct? Did the total retain its decimal mark? Are all pages present? Those checks establish whether the data represents the document. They do not establish whether the invoice is authorized for payment or belongs in a particular account.

Parzable returns fields selected through your schema. Treat them as proposed data for review. Use your own purchase-order matching, supplier verification, approval, and accounting processes after extraction. The checklist here focuses on data quality and is not a claim that Parzable automates those controls.

Keep the original document and a working review sheet available. A filename alone is not enough to resolve a disputed value if you cannot reopen the corresponding invoice.

Review the record in a repeatable order

  1. Document: confirm supplier, customer, invoice identity, and complete page set.
  2. Identifiers: compare invoice and purchase-order numbers character by character, preserving prefixes and zeros.
  3. Dates: distinguish invoice date from due date and hold ambiguous formats for review.
  4. Currency and amounts: preserve currency and check decimal and thousands separators.
  5. Completeness: inspect missing values, N/A, omitted rows, and unexpected duplicates.
  6. Reconciliation: compare the printed summary with the relevant printed line amounts, discounts, and charges.
  7. Destination: confirm column mapping and keep unresolved records out of the final import.

Download the review checklist and record pass, hold, or not applicable for each check. These statuses belong to your review process; they are not automatic Parzable approvals.

A worked reconciliation with a deliberate error

Fictional invoice: items total 200.00, a printed discount is 10.00, a delivery charge is 5.00, tax is 39.00, and the printed invoice total is 234.00.

200.00 - 10.00 + 5.00 + 39.00 = 234.00

If extraction returns 243.00 as the total, the difference is 9.00. Hold the record and compare it with the source. Do not overwrite the source total with a calculated value just to force agreement. The cause could be a reading error, a missing charge, or a problem on the invoice itself.

This arithmetic is an illustrative data check, not a tax calculation rule. Real documents can use different discount, rounding, or tax presentations. Use the amounts and labels actually printed, and refer unresolved accounting treatment to the person responsible for your books.

Look for duplicates without discarding evidence

Compare supplier plus invoice number as a first duplicate candidate key. Add date, currency, and amount as supporting evidence. A repeated filename is not sufficient, and the same invoice number can be used by different suppliers.

A candidate duplicate should be reviewed against its source and import history. A corrected invoice, credit note, or legitimate resend can require different handling. Keep the reason for your decision in the review sheet.

Finish by recording what changed, who reviewed it, and where it was imported. If a value remains uncertain, mark it as held instead of turning uncertainty into a plausible-looking number. Extraction is useful when it reduces typing while preserving a clear path back to evidence.

Put the workflow to work

Try your own invoice in Parzable

Create an account, define a schema, and test a small sample. Review extracted values before using them. See current plans and page allowances.

Try Parzable