Measure the review, not a headline score.

AxLiner evaluates field fidelity, row structure, confidence flags, reviewer effort, and export readiness across a representative batch.

Every result should trace back to its source page.

SourceExtracted draftReview decision
Two finance professionals comparing source documents with a reviewable batch on a laptop

Source, extracted draft, confidence flag, and reviewer action stay connected.

Four checks are more useful than one percentage.

AxLiner treats quality as reviewable field, row, exception, and outcome signals because documents fail in different ways.

01

Field fidelity

Check vendor, dates, tax, totals, and line items against the meaning of the source page.

02

Row integrity

Check that lines, headers, columns, and totals keep their relationship in the workbook.

03

Exception visibility

Keep confidence signals beside the affected field or row so uncertainty is actionable.

04

Review outcome

Track edits, failures, ready items, and published drafts without rebuilding the workbook.

Inspect the path from source page to usable output.

The protocol covers values, workbook structure, review states, and the final handoff—not an isolated OCR transcript.

1

Values

Document fields and line-item cells

The source value is preserved or the exception is surfaced for review.

2

Structure

Headers, row order, columns, totals, and merged areas

The result behaves like a table after export, not a paragraph arranged into cells.

3

Review load

Needs review, edited, ready, and failed states

A reviewer can see where intervention happened and what still blocks the batch.

4

Delivery

Excel, CSV, or reviewed accounting drafts

Only reviewed work moves to download, QuickBooks, or Xero.

Make the benchmark and its limits visible.

Record the sample mix, comparison rule, review decisions, version, and failure cases so another team can understand the result.

Needs reviewReadyEditedFailedPublished

Record with every run

  • The document mix and capture conditions
  • The field, row, and structure comparison rule
  • Which items were flagged, edited, or failed
  • The product and model version used for the run
  • Representative failure cases, not only clean examples

Verify with documents your team already knows.

Keep a representative reference set fixed, review its exceptions, and inspect the delivered workbook or accounting draft.

  1. 01

    Choose a representative set

    Use the scans, phone photos, PDFs, receipts, invoices, statements, and tables your team actually receives.

  2. 02

    Keep a trusted reference

    Record the expected fields, rows, and totals before processing so the comparison is repeatable.

  3. 03

    Upload one batch

    Process the set together. A batch test exposes queue, classification, and review behaviour that a single page cannot.

  4. 04

    Review the exceptions

    Inspect Needs review, Edited, Ready, and Failed items beside their original source pages.

  5. 05

    Check the handoff

    Open the reviewed Excel or CSV output, or inspect the reviewed draft before publishing to QuickBooks or Xero.