Checks pass
ACME's known item, quantity, currency, date, and contract price pass. The authorized path creates one demo draft.
One draft createdPURCHASE ORDER DEMO · SYNTHETIC DATA
From purchase order to checked ERP draft.
This purchase order intake automation demo receives supported order emails and text PDFs, structures their fields, checks them against customer and contract records, and decides whether a demo ERP draft is ready or a person needs to step in.
Extraction is pattern based for supported text PDFs. The downstream system is a demo ERP adapter, and the only write is a draft order. There is no final order submission or production customer ERP connection.
THE ORDER PATH
From incoming PO to a safe next step.
A source document is kept with the case, so a reviewer can compare what was read with what was supplied.
01
Receive the source
Register the email and PDF, including source identity and history.
02
Read the order
Extract customer, PO number, currency, delivery date, and line items from supported formats. Missing or unreadable fields stay visible.
03
Check business records
Resolve the customer, permitted SKUs, contract prices, and prior orders using controlled data.
04
Apply the rules
Check quantities, dates, currency, price, duplicates, missing fields, and ambiguous matches. Each failed check has a reason.
05
Route the case
Ready cases can proceed. Exceptions wait for a reviewer; malformed input stops safely. Corrections trigger all relevant checks again.
06
Create a draft
Only an authorized ready case creates one demo ERP draft. Retries and repeated delivery are guarded against duplicate writes.
FOUR DIFFERENT OUTCOMES
The point is the decision, not one rule.
These are frozen synthetic cases from the project's evaluation set. Price mismatch is also covered; it is one of several reasons to hold an order.
Item not recognized
Customer resolves, but SKU X-999 is unknown. The case goes to human review before any draft.
No draft createdOrder already exists
The customer and PO number match an existing order. Duplicate protection blocks another draft.
No second draftDocument unreadable
An unreadable PDF cannot be trusted as a valid order. Processing stops without inventing the missing data.
No ERP actionWHEN A PERSON STEPS IN
Review changes the evidence, then the system checks again.
A reviewer can inspect the original PDF, extracted fields, business context, rule results, and audit history. A correction makes a new revision; it does not overwrite the original or bypass validation.
Other cases tested
- Unknown customer or ambiguous customer and item matches
- Invalid quantity, date, currency, or missing critical field
- Multiple simultaneous exceptions and price mismatch
- Retry after interruption and duplicate delivery
- Instruction-like text in a document and unauthorized action attempts
What remains bounded
- Supported text-based PDF formats and synthetic evaluation inputs
- Pattern-based extraction, not a live AI document reader
- Draft-only write in a demo ERP adapter
- No final submission and no claimed customer ERP deployment
- Public demo access is not currently offered on this website
Source: frozen V1 evaluation cases, business rules, state machine, and final demo script reviewed 26 September 2026. The repository's final demo gate passed locally; that does not establish a currently available public demo.
LET'S START WITH THE WORK
Show us the workflow you need to control.
Tell us what arrives, what your team checks, and where a wrong action would matter. We will use that to discuss a scoped pilot.
No customer documents are needed for the first conversation.