Triage incoming EDI documents with AI
Dozens of documents sit in Diadoc, some unsigned simply because nobody got to them. The agent checks each one against the order in 1C.
Medium · 15 min · once a week
What you get
a breakdown in the reply · once a week
Incoming this week: 34 documents Safe to post 26 Waiting for your signature 5 Disagree with the order 3: Supplier A, UPD no. 88 — price 4% above the order Romashka LLC, certificate no. 12 — quantity 100 instead of 90 Supplier B, UPD no. 51 — no matching order in 1C at all Don't sign these three until the supplier replies.
A sample on made-up data — your numbers will be your own.
Who it fits
- Dozens of incoming documents a week, some left unsigned in EDI simply because nobody got to them.
- A supplier keeps sending price and quantity that differ from the order — catch it before signing.
When it won't work
Purchase orders aren't created in 1C — there's nothing to compare against, you just get a register.
How the agent does it
Set the tolerances
Name the period and the price or quantity deviation at which a difference becomes significant. Otherwise the list drowns in penny rounding gaps.
Run the triage
The agent reads the Diadoc inbox, parses details and line items and matches each document against the order and contract in 1C, keeping its EDI status.
Check the links
Signing can't be undone, so first look at where the agent linked a document to an order by eye: on amount or date, with no matching number.
What you set
You'll need Diadoc and 1C. From you: the period to process and the price and quantity deviation below which a difference isn't worth showing.
What you'll need
Starter prompt
Copy the prompt or open it straight in a chat with the agent.
Process the incoming documents from Diadoc for [period] and match them against the orders and contracts in 1C. For each document: type, supplier, number, date, amount, EDI status, the order or contract found. Sort into groups: full match, price differs, quantity or item differs, details don't match the record, no order found, document not posted in 1C. Treat a discrepancy as significant from [deviation] — flag anything smaller but don't escalate it. Don't match items by similarity of the name: if the SKU or code doesn't match, write "not matched" instead of picking the nearest item. Output a table of documents indicating where each figure came from, and a separate list of documents awaiting signature for longer than [deadline].
Open in chatReview the processing. List: — documents linked to an order by amount or date, without a matching number; — items where the product was matched by name rather than by SKU; — within-tolerance discrepancies that repeat with the same supplier month after month; — adjustment and corrected documents: did you link them to the original or count them as separate; — documents with no order: are they really absent from 1C or were you looking in the wrong period. Mark what can be posted without questions and what must not be signed until the supplier responds.
A second prompt — the agent uses it to review its own work and show what's left for you.