Microsoft Support — Keeping leading zeros and large numbers

Skavio Flow turns invoices, orders and scans into structured data, with source evidence, review warnings and XLSX exports. For bookkeeping and procurement teams, the useful finish line is not simply recognized text: it is document fields and line items that someone has checked before the spreadsheet moves downstream.

Define the spreadsheet before extracting the documents

Start with the information your team needs, rather than every detail printed on a supplier document. Flow supports custom extraction fields and saved company workflows, so recurring work can use a reusable field definition. In an illustrative workflow, invoices and orders could have separate field sets. An invoice number and an order reference serve different purposes; neither should become an ambiguous column called “number.” The following are suggested custom fields, not built-in templates.

Invoice fields: supplier name, invoice number, invoice date, currency, net amount, tax and total.
Order fields: supplier name, order reference, order date, product code, description, quantity and unit price.

Extract text—but keep the source in the workflow

Flow reads embedded PDF text locally and uses OCR for scans. Structured extraction then uses the configured OpenAI model to turn that text into the requested fields. The workflow is therefore not local-only. Verified outputs include source evidence and review warnings alongside structured results. These belong in the working process, not just the final archive: they give the reviewer material to check when an extracted value needs scrutiny. OCR and structured extraction do not remove the need to compare important values with the original document.

Review the values that change the business meaning

A readable result can still contain the wrong date, amount or quantity. Review should concentrate on fields that affect how the document is interpreted and used. Microsoft’s Excel Data from Picture instructions likewise require reviewing results and making corrections before insertion—a useful reminder that extraction and acceptance are separate steps. Flow’s October 1, 2026 internal acceptance check extracted and exported two synthetic PDF invoices. Correcting a scalar value regenerated the results without a second job. That verifies a specific correction path; it is not a customer case study, an accuracy benchmark or evidence that every line-item editing scenario has been tested.

Check dates and references against the source, including whether a date is the issue date or due date.
Compare currency, net amount, tax and total with the document; do not assume automatic reconciliation.
Inspect line-item descriptions, quantities and unit prices. Resolve uncertain entries against the source before using them downstream.

Export document and line-item data for Excel

Flow’s verified XLSX output includes document and line-item worksheets; CSV and JSON are also available. Keeping document-level information distinct from line-item data gives the reviewer two different checks: whether the invoice or order is correctly identified, and whether its individual entries are usable. Check identifiers in Excel as well. Microsoft documents that Excel can remove leading zeros and has only 15 significant digits of numeric precision. Treat invoice references and product codes as text where appropriate, especially when importing CSV. Do not assume Flow guarantees identifier preservation; check the exported result. For a collection of supplier documents, distinguish extraction from consolidation. This example does not assume web batch upload or a single workbook containing every invoice and order. If your handoff requires those capabilities, confirm them before committing to the workflow.

Size the trial by document count as well as pages

Flow costs 100 company credits per page, with a minimum of 200 credits per document, including OCR and export. A one-page document therefore costs 200 credits, not 100. The company trial provides 1,000 credits without a card—enough for five one-page documents at the stated minimum if all trial credits are used for Flow extraction. Choose a small representative set, such as a text-based supplier PDF and a scanned order, then inspect the fields, source evidence and exported worksheets before expanding the workflow. Company credits are separate from existing personal web plans, and paid credits never expire.

Extraction produces structured data. Human review determines whether it is ready for the next step.

Sources

Supplied Skavio commercial knowledge — October 1–2, 2026 — Authoritative supplied source for Flow’s custom fields, saved company workflows, processing stages, outputs, synthetic acceptance check, company-credit rates and trial. The URL is the product destination, not independent web verification.
Microsoft Support — Insert data from picture — Excel’s image-to-table workflow includes reviewing results and making corrections before insertion. This provides context for human review, not evidence of Skavio performance.
Microsoft Support — Keeping leading zeros and large numbers — Documents Excel’s automatic conversions, 15-digit numeric precision and the use of text to preserve identifiers.

Try Skavio Flow: review your supplier documents and export XLSX