Skip to content
Bahman Shadmehr Independent AI Systems & Automation Engineer

Interactive synthetic demo

Invoice extraction,
with uncertainty visible.

Load a synthetic invoice or provide a plain-text sample. See extraction, schema validation, arithmetic and exception routing as separate stages.

Load the sample Browse design studies
01Source document
Synthetic only
02Processing trace
Waiting
Normalisepending
Extractpending
Schemapending
Arithmeticpending
Routepending
03Structured result
— 
{
  "status": "waiting_for_input"
}
Decision Not processed

Load the synthetic source to begin.

Production version

The real pipeline has more controls.

  • File type, malware and size checks
  • Native text or OCR with quality signal
  • Provider/model regression evaluation
  • Vendor and purchase-order lookup
  • Duplicate invoice detection
  • ERP draft and finance approval

AI boundary

Extraction is not authority.

The model proposes invoice fields. JSON schema, arithmetic, known records and policy decide whether the draft can progress. Payment approval always remains separate.

Read the extraction architecture

Have real document volume?

Evaluate on representative, permissioned samples.

A clean demo is not evidence. Measure field accuracy, hallucinations, abstention, latency, cost and review time.

See AI Data Processing