Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

What the Order Confirmation Agent does

The step after the purchase order leaves your desk

The Order Confirmation Agent (OC Agent) automates the step that follows sending a purchase order. Once a purchase order (PO) has gone out to a supplier, the supplier returns an order confirmation (OC, in German Auftragsbestaetigung or AB). The agent ingests that confirmation, matches it to the PO, compares every field, decides what is fine and what needs attention, communicates back to the supplier when needed, and writes the confirmed result back into your ERP.

It removes the manual work of reading each confirmation, comparing it line by line against the order, chasing missing confirmations, and keying the result into the ERP. A human stays in the loop for anything that deviates beyond your policy.

Where the agent sits in the process

The agent uses a three stage model for everything that happens after the PO is sent:

  1. OC check (owned by the OC Agent)
  2. Goods receipt (GR)
  3. Invoice (INV)

The OC Agent owns the OC check stage. The goods receipt and invoice stages exist in the model and the Thread Overview can filter by stage, but they sit downstream and are not yet part of the OC workflow.

What a thread is

Every pairing of a purchase order and its confirmation is a thread. A thread holds the comparison, all decisions, the supplier conversation, and the audit trail. The Thread Overview is your work list, and the Thread Detail view is where you review and confirm.

What the agent does end to end

  1. Reads the incoming confirmation from the connected shared mailbox or an SFTP drop.
  2. Extracts the document content into a structured data model.
  3. Matches the confirmation to the correct purchase order.
  4. Compares every header field and every line item field against the order.
  5. Auto confirms whatever matches or falls within your tolerances.
  6. Surfaces real deviations for a human decision.
  7. Drafts and sends supplier emails for rejections, clarifications, and reminders.
  8. Writes the confirmed values back to the ERP and logs what was written.

Language

The Thread Overview and the Thread Detail view are available in English and German. Field labels, statuses, and actions are translated. Supplier names, values, and supplier prose are never translated.