Invoice audit trail with Jev
Pixels never go to System One. An OCR or vendor extractor turns the PDF into strings; Jev then asks whether that text packet looks like a duplicate, a PO mismatch, or a complete AP file. Code posts to the ERP. Jev does not key invoices.
This unofficial page is the audit trail slice of the invoice AP decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to invoice AP decisions audit trail. Primary search language: Invoice Jev audit trail. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): OCR extracts; Jev judges already-extracted text (duplicate/vendor/PO language). Amounts and dates stay in code — not a clone of invoice-OCR IA or a rival AP-recipe page.
Invoice use-case context
An audit trail for invoice AP decisions is a decision trace: replayable inputs, typed answers, floors, and the action the AP router took. It is not a chat log and not a clone of a SIEM product page.
Hub: Use cases. Compare, when the other tool is the real job: invoice OCR.
Audit Trail inputs
Persist the filtered payload (the contract), not whatever arrived at the edge:
{
"invoice": { "id": "INV-1044", "vendor_name": "Northwind Paper LLC", "memo": "Q3 copier paper — matches PO 88." },
"po": { "id": "PO-88", "vendor_name": "Northwind Paper" },
"extract": { "amount_cents": 128500, "invoice_date": "2026-03-12" },
"policy": { "duplicate": "Same vendor + same amount_cents within 14 days is a duplicate suspect." }
}Redact secrets before the object hits cold storage.
Decision signals and actions
Minimum fields:
- invoice.id + po.id
- resolved
model - answers + full probabilities
- code amount compare result
- ERP post id or hold reason
Also store usage.input_tokens (vendor meter) and the full probabilities map — argmax-only logs cannot explain a close same_vendor.
Do not treat a Noul of 0.5 as a “medium” invoice AP decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
If you cannot explain posting an invoice to the ERP from the trace, you are not ready to auto-act. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For invoice AP decisions, treat post_to_erp as the high bar (posting an invoice to the ERP). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Traces are the eval warehouse. Replay against route_match / hold / duplicate gold from AP clerks, plus same-vendor gold after criteria or alias changes. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream action as a decision trace.
May I log raw secrets? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Invoice pack? Start with Invoice human handoff and Invoice evaluation. Cluster hub: Use cases.
Can we skip OCR and send the PDF? No. Official models page: no image input. Extract first. See Jev vs invoice OCR.
Should Jev decide if $1,285.00 matches the PO? No. Compare cents in code. Jev judges leftover language (vendor strings, memos).
What this page does not claim
- Not an OCR, ERP, or AP product.
- No invented extraction F1 or cycle-time lifts.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.