Read the guide

Review amounts, dates and identifiers before exporting a table

Check decimal conventions, negative amounts, blanks and leading zeros so visual values become the data you intend.

The most expensive table errors can be small: a missing minus sign, a decimal interpreted as a thousands separator, or an account code losing its leading zeros. Review data meaning as well as visual similarity.

Choose a few fields that matter to your task and check them systematically. A table that looks tidy is not necessarily ready for arithmetic or import into another system.

Keep three different data types distinct

An amount is a number, an account code is usually an identifier, and a date needs a calendar interpretation. An identifier such as 00125 should not become 125 merely because the spreadsheet decides it looks numeric.

Likewise, a blank amount is not automatically zero. It might mean missing, inapplicable or an empty printed cell. Preserve that distinction until you understand the document's convention.

Check locale and sign conventions

A source can use 1,234.56 or 1.234,56 for the same amount. A lone 1.234 is ambiguous without context. Compare column labels, nearby examples and the source's convention before deciding what it represents.

Parentheses can indicate a negative amount in some statements. A percentage displayed as 12% may be stored as 0.12 with percentage formatting. Check how your target application treats it rather than changing the appearance alone.

Use totals as a cross-check, then inspect rows

If the source provides a meaningful total, compare it with the extracted values using the same scope. Exclude subtotals or carry-forward rows when the document's structure requires that. Matching totals are useful, but two offsetting errors can still cancel.

Tablora understands several number conventions and lets you edit extracted cells. Use the original page beside the preview, check uncertain readings and inspect the XLSX or CSV after export. Extraction does not prove that an original invoice or statement was correct.

  • Compare complete records, including their identifiers.
  • Check dates around month/day ambiguities.
  • Keep a record of material corrections.
  • Test a small import before moving a large dataset.

Questions, answered

Does a matching total prove every row is correct?

No. Offsetting mistakes can preserve a total, and a correct amount can be attached to the wrong record. Check representative complete rows too.

Will CSV preserve leading zeros automatically in Excel?

The CSV can contain the characters, but Excel may infer a numeric type on import. Choose an appropriate text type for identifiers and check the result.

Sources & method

Reviewed:

Keep going in Tablora

Read PDF, photo and camera-scan tables on iPhone without uploading documents · Preview and edit cells free, with uncertain readings marked beside the source · Pro exports XLSX/CSV and merges multi-page tables or multiple tables into a workbook

Get the iPhone app

Keep exploring