Skavio Flow: correct an extracted field without a second extraction job
Skavio Flow has demonstrated that an extracted scalar value—a single field value—can be corrected and the results regenerated without starting a second extraction job. For a bookkeeping team, that supports a review-first handoff: check dates, reconcile totals and inspect line items before exporting.
Keep the correction inside the review workflow
Flow turns invoices, orders, scans and text into reviewed structured outputs using custom fields and saved company workflows. Its outputs include XLSX document and line-item worksheets, CSV, JSON, source evidence and review warnings. In Skavio’s October 1, 2026 acceptance check, two synthetic PDF invoices were extracted and exported, and a scalar-field correction regenerated results without a second extraction job. That is a bounded demonstration—not a guarantee of extraction accuracy. The record does not identify the field corrected or establish that every output format was regenerated. For a bookkeeping team, the distinction matters: a correction changes the extracted data used for the handoff. It does not amend the original supplier invoice.
Check dates against the source—and after import
Consider an illustrative supplier invoice showing “03/04/2026.” Before accepting the extracted value, a reviewer needs to establish which date convention the document uses. Compare the value with the source evidence and relevant document context; if the meaning remains unclear, seek confirmation rather than guessing. Also check that an invoice date has not been mistaken for a due date. The date needs another check at the receiving end. Microsoft documents that Excel interprets CSV columns using its current default data-format settings. Its text-import workflow offers more control over that interpretation. After importing a regenerated CSV, inspect the date values again: a correct reviewed value can still be interpreted differently during import.
Reconcile totals without treating every difference as an error
The sum of invoice lines is not necessarily the amount payable. Peppol BIS Billing distinguishes line-net totals, document-level allowances and charges, VAT, paid amounts and rounding. Those distinctions are useful reconciliation references where applicable; they do not imply that Flow implements Peppol validation. In an illustrative invoice with no other adjustments, a €1,000 net total plus €200 VAT produces a €1,200 tax-inclusive total. If €300 has already been paid, the amount due is €900. A reviewer should identify which amount each extracted field represents before correcting a suspected mismatch. Inspect the underlying rows as well:
- Compare descriptions, quantities, unit prices and line amounts with the source.
- Check for omitted rows, duplicated rows or values shifted into the wrong column.
- Review discounts, charges and tax information before expecting line sums to match the final amount due.
- Keep the capability boundary clear: the acceptance record establishes scalar correction and regeneration, not line-item cell editing or adding and deleting rows.
Regenerate, then verify the file you will hand off
After a supported scalar correction, regenerate the results and inspect the export intended for the next person or system. Confirm that the corrected value appears as expected, then revisit related fields. Do not assume that changing one value automatically recalculates totals; the acceptance record does not establish that behavior. Choose the output around the handoff. Flow’s XLSX output includes document and line-item worksheets, while CSV and JSON are also available. If someone later saves an XLSX workbook as CSV in Excel, Microsoft warns that only the current worksheet is saved. One such CSV should not be treated as a substitute for both worksheets. The final check belongs to the exported file—not just the reviewed extraction.