Salesforce MVP Hall of Fame · Certified Partner since 2010
Invoice routing: pay, hold, review
Jev routes the invoice. It does not read the amounts. OCR extracts, rules check the math, a person takes the holds.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agents · Agentforce, CrewAI, ADK, A2A
- 03Memory · Neo4j, Cognee, RAG
- 04Identity · IndyKite, SSO, entitlements
- 05Governance · policy, audit, human override
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
The decision
The decision, drawn.
Choice pay/hold/review + Choice cost centre; extraction stays with LLM/OCR (Jev weakest there)
Jev · Choice
Should this invoice be paid, held, or reviewed, and which cost centre owns it?
- pay
- hold
- review
Vendor matches PO 4471. Line description: 'Q3 managed services, additional hours'. Note: 'see attached change order'.
- pay0.18
- hold0.09
- review0.73
The job
What has to be true.
Act at 0.90 confidence or higher. Below that, a person or a larger model.
The figure
Builder's figure. Not reproduced by us.
TypeSafe eval: invoice processing 61.8 vs 79.1 (routing ok, extraction weak); Huryn 50/50 on tricky invoice docs
aiproplaybook.com/tools/jevDon't let Jev extract amounts or fields; it scored 61.8 vs 79.1 on invoice processing in TypeSafe's eval. It should only route.
The brief
Name the decision your team makes a thousand times a day.
We read the process and write down where Jev fits, where it does not, and where the line sits.