Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
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.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agentic systems · Agentforce, CrewAI, ADK, A2A
- 03Agentic memory · Neo4j, Cognee, IndyKite
- 04Automation and voice · n8n, Retell
- 05Deployment and governance · identity, evals, policy, audit
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 flow
One invoice, pay, hold or review.
Arrives
An invoice reaches AP
A PO number, a line description, maybe a note about a change order.
Before Jev
OCR and rules do the reading
OCR and Claude extract the fields. Rules check the math. Jev reads no amounts.
Jev decides
Pay, hold or review
And which cost centre owns it.
Who acts
Pay moves on. A person takes the holds.
Anything under the line goes to review in the ERP or Salesforce.
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.
Who runs it
Who would run this, and what changes.
Example
Finance controller, Riyadh distributor
Today: Every supplier invoice waits in a shared folder until the controller reads it and decides who signs.
After: Invoices that match the PO move on to pay. Holds and odd lines reach the controller with the reason.
For CFOsExample
AP lead, Dubai facilities management group
Today: Subcontractor invoices mention change orders nobody has approved yet. They get paid anyway, or sit for weeks.
After: An invoice that points to a change order goes to review. OCR still reads the amounts and rules check them.
Facilities managementExample
Finance manager, Dammam manufacturer
Today: Invoices for services and invoices for raw material go to the same approver.
After: Each invoice is routed to the cost centre that owns it. Approvers see only their own.
Manufacturers
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.