Skip to content
Veyact LabsContact
Menu

RUNRAIL DOCUMENTATION · RELEASE QUALIFICATION

From a batch to reviewed rows.

Qualified local profile

The current local path supports bounded invoice and receipt PDFs with explicit source evidence and review. Wider scan support remains gated by the published extraction benchmark.

One invoice or receipt per file. EUR or USD without conversion. Positive two-decimal totals up to 999,999,999.99. Up to 25 files, 20 MiB each and 100 MiB per batch.

Still outside the qualified profile

Handwriting, encryption, active content, multi-invoice bundles, bank statements, payslips, IDs, medical documents, and tax filing remain unsupported. A file outside the profile is rejected with the reason named, not processed halfway.

Review workflow

  1. Create a routine and choose the destination columns and date rules.
  2. Add supported documents and inspect the quote before extraction.
  3. Review source-linked fields, possible duplicates, and ambiguous values.
  4. Inspect the exact selected rows and approve a fresh export.
  5. Save the result and reuse the routine for the next batch.

A batch, end to end

You drop in twelve supplier invoices for March. Before anything is read, the quote shows twelve pages against your allowance. Extraction proposes supplier, date, and total for each row, with the source page beside every value.

Three rows need you. One date reads 03/04/2026 and your routine has no day-first rule yet, so you pick 3 April and the choice is recorded as your correction. One invoice number matches a February entry — flagged as a possible duplicate, not deleted, because revised invoices share numbers more often than you would think. One total differs from its subtotal plus tax, so the row waits until you check the printed page.

You approve nine rows, then the remaining three after review. The export is a new CSV with exactly those twelve rows. Your spreadsheet, your originals, and the February batch are untouched, and next month the same routine starts from your saved columns and date rule instead of a blank setup.

Recovery and limits

State uses append-only checksummed snapshots. An interrupted extraction does not silently restart; an uncertain write is read back under its original identity. Expired or changed output needs fresh approval rather than reusing a stale one.

Sources and detailed history remain available until removed by the owner. Public installer availability follows the Windows lifecycle qualification.