EDI order exceptions
Reads failed EDI orders, the catalogue, price lists. Produces fixed orders, customer queries. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.
Narrow questions, each with a check behind it.
Why an order failed; the fix
Proven by code: catalogue, prices. Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.
| Reads | Failed EDI orders, the catalogue, price lists |
| Produces | Fixed orders, customer queries |
| Who signs | A person on your team, with every figure traced to its document and every call on record |
| Process | Payables, receivables and payments |
| Industry | Manufacturing and supply chain |
Every line, decided where it's safest.
An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.
| Ref | Item | Value | Decided by |
|---|---|---|---|
| EDI-901 | Unknown item codeCustomer's old code, mapped · 0.95 | Engine · proven | |
| EDI-902 | Price differs from listContract price applies | Code · corrected | |
| EDI-903 | Ship-to address missingDefault delivery address · 0.92 | Engine · proven | |
| EDI-904 | Quantity 10,000 instead of 100Typo or a real order? | To a person | |
| EDI-905 | Duplicate orderSame PO number sent twice | Code · rejected | |
|
Settled 4
To a person 1
Settled wrong 0
| |||
Your volumes in. Your hours out.
In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.
Start from what's closest.
Payables, receivables and payments in other work
Cash application
Which open invoices a receipt pays; short-pays and deductions
FinanceAP invoice processing with two- and three-way match
Which PO and receipt an invoice is for; price and quantity differences
FinanceDuplicate and erroneous payment check
Whether two payments are the same obligation
More for manufacturing
What buyers ask
What happens when Sumarity isn't sure?
Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.
How are its judgements checked?
Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.
Can we change it to fit how we work?
Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.
Does it read our files as they are?
Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.
Where does our data go?
Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.
How does it get better?
Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.
Start from this workflow. Run it on your data.
A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.