Blog · Engineering

AI for judgement. Rules for money.

The design principle behind our order intake agents — and why a model should never decide a price.

When we automated order entry for a large enterprise — taking it from about 60 minutes per order to 6 — one design rule did more for trust than any model choice: AI for judgement, rules for money.

Where models shine

Language and vision models are excellent at messy, judgement-heavy work: reading a 7-page scanned purchase order, recognising that "418,00" is a European decimal, ranking which customer account an email most likely belongs to, and explaining why.

Where they don't belong

Pricing, tax and fee logic must be deterministic and testable. If the same order can produce two different invoices, finance will never trust the system — and they shouldn't. So in our design a model never decides a price; it hands structured data to rules that do.

Each order posts once, and only a real ERP order number counts as success.

And humans approve everything

Every step offers Approve, Correct or Regenerate. There is no unattended mode. That's not a limitation — it's why the operators adopted it.

Want this in your business?

Start with a Data Readiness Assessment.

Talk to us

Keep reading

All insights