Model Run: Supplier documents to spreadsheet
Synthetic model example of converting supplier PDFs and images into XLSX, CSV, a review queue, and draft QBO/Xero CSVs, with measured errors and mandatory operator checks.
Turn multi-format supplier documents into structured spreadsheets, a review queue, and draft accounting exports—designed around explicit error flags and human sign-off before anything touches your ledger.
Note: This page presents a single synthetic model example from our Agent Reliability Lab (measured November 16, 2026 on DeepSeek V4.1 Flash 1017 against reference checks fixed before the run). It is not a client case study or an overall accuracy score.
Who it is for
Teams handling incoming supplier paperwork across mixed formats (PDF, PNG, JPEG) who want structured line-item spreadsheets and draft accounting CSVs prepared for review rather than blind auto-posting.
Input → Output
- Input: 6 supplier document files (PDF, PNG, JPEG), spanning 7 pages in total.
- Output:
- Structured XLSX workbook
- Line-item CSV (
14exported rows) - Operator review queue
- Draft QBO and Xero CSVs
Model Run: Results and Measured Errors
In this November 16 synthetic English evaluation run (DeepSeek V4.1 Flash 1017, reference expectations locked prior to execution):
What matched
- Final line-item rows:
14/14exact matches against fixed checks - Document-level decisions (
review/OK):6/6 - Document flags:
TP 2 / FP 0 / FN 0 - Row flags:
TP 2 / FP 0 / FN 0 - Field values matching fixed checks:
167/175raw page fields;120/126final document fields
Where the run fell short
- Whole-document exact match:
0/6documents matched end-to-end.- Why: The source documents print
"Buyer reference", which the fixed reference maps to thePOfield, whereas the model leftPOempty. Because"Buyer reference"is an ambiguous label, this reflects a mapping ambiguity in this fixed test—not proof that the model misses an explicitly labeled"Purchase order"field.
- Why: The source documents print
- Tax mode on continuation pages: A separate discrepancy occurred on raw
tax_modeon a continuation page.
What the operator checks
Before using any exported spreadsheet or draft accounting CSV, a human operator must:
- Verify extracted document header fields and line items against the source pages.
- Check tax mode handling (
tax_mode), especially across multi-page documents and continuation pages. - Confirm buyer reference / PO field mapping according to internal accounting conventions.
- Decide whether the exported files are ready for downstream use.
Limitations
- No accounting import tested: Actual import into QuickBooks Online or Xero and the correctness of chart-of-accounts mapping were not tested in this run.
- Small synthetic sample: Results come from one synthetic English test set (
6documents,7pages,14rows). They do not establish an overall accuracy percentage, production reliability, or improvement over prior test sets. - Untested edge cases: Current lab coverage does not yet test continuation pages without line items or percentage syntax such as basis points.
Next step
Have supplier document formats you want evaluated under explicit review gates?