Case study · AI Process Automation

We cut order entry from 60 minutes to 6.

Start a similar project Read the full story

Large enterprise · Manufacturing & distribution

60 → 6minutes per order, reported
~90%of the work handled by AI agents, reported
13 of 13real sample orders read correctly, measured
9intake formats, one reading layer
At a glance
!The challenge

Every purchase order was keyed in by hand — about an hour each, with costly pricing errors.

⚙What we built

Four AI agents read, match, build and validate each order. An operator approves every one.

★The result

Order entry down from 60 minutes to 6, with ~90% of the work handled by agents.

Before60 minper order, keyed by hand
→
After6 minper order, agent-prepared and approved
How it works

From input to outcome

✉Order arrives
⌕Read
⇄Match
▦Build
✓Validate
☺Approve
Illustrative scene: Large enterprise · Manufacturing & distribution
Illustrative scene · Large enterprise · Manufacturing & distribution
The full story

Details for the curious

Open any section for the full detail — figures, design decisions and how it fits your business.

Document AI / OCRMulti-agent orchestrationDeterministic pricing rulesERP integrationHuman-in-the-loop UI
Start a projectPDF
Download the studyPetroleum AI use case studies (PDF)
The challenge

Every order was keyed in by hand. Each one took about an hour of skilled effort before it even reached the queue.

  • Slow: about 60 minutes of skilled effort per order.
  • Lost margin: orders arrived with a net total, while the price breakdown sat in an old quote.
  • Costly errors: a wrong billing entity or fee code came back later as an invoice dispute.
  • Hard to scale: more volume meant more people, and the rules lived in operators' heads.
How it is designed

AI for judgement. Rules for money. Models read any document, rank the right customer account and explain their reasoning. Pricing, tax and fee logic is deterministic and testable, so a model never decides a price.

Humans approve everything. Every step offers Approve, Correct or Regenerate. There is no unattended mode. Each order posts once, and only a real ERP order number counts as success.

How it works

Four agents, eight steps, one approval.

ReadParser reads the inbox and every attachment, scans too
MatchMatcher finds the customer and quote, and asks if unsure
BuildAssembler builds the ERP order and sends the confirmation
ValidateValidator checks fees, nine rule categories and exceptions
ApproveAn operator approves, corrects or regenerates every step
Proven on a hard order

A 7-page, image-only scan worth $86,149.80: 229 units, 7 delivery batches over 13 months, 5 components per unit — handled end to end.

In the orderWhat the agents did
Image-only scan, no textOCR with confidence-based retry, every line read
European numbers such as 418,00Read by convention: 418.00, not 41,800
Net price only, no breakdownMatched to the quote, component sum rebuilt
229 units, 7 delivery datesSplit into 7 lines, one per delivery date
Mandatory items not on the orderGap detected, items added by rule

Measured · 13 of 13 sample orders correct · 154 fields checked against the source.

What it is worth

Illustrative, on your volume. The 60 to 6 minutes is reported; volume and cost are planning assumptions (54 minutes saved per order at $45 an hour).

$243,000a year at 500 orders a month
$486,000a year at 1,000 orders a month
$972,000a year at 2,000 orders a month

Labour only · the larger value is likely faster delivery and fewer disputes.

Where it applies

The same pattern fits any business that receives orders by email, Excel, PDF or portal and prices them against contracts — for example fuel and lubricant suppliers serving fleets, stations and industrial customers, with surcharges, exemptions, credit limits and scheduled multi-site delivery.

More case studies

All case studies

How can we help you?

Let's pick the first workflow to automate — and prove it on your own data.

Book a Data Readiness Assessment Scope it with our assistant