06 / CUSTOMER PO → MASTER CHECK → HUMAN GATE

From the PO.
Against the master.
Ready to review.

Keep extracted fields beside the source. Compare them with master data, hold the conflicts and let your team approve each line before export.

Try the PO review
WL / PURCHASE-ORDER-REVIEWILLUSTRATED WORKFLOW
CUSTOMER POOrder 0917
Part: Widget 042
Quantity: 12
Source: line 1 ↗
MASTER DATACheck the match.
Code: PART-042
Unit: each

Part code needs a human check

Held: unconfirmed part code

A customer purchase-order PDF supplies the order fields and source lines. The illustration uses sample data.

The field and its source.
Always together.

The browser working model accepts supported purchase-order PDFs and includes examples of a normal order, conflicts, a change order and a wrong file.

Source lines remain beside editable order fields. Master-data checks and holds are visible. Only approved orders enter the SAP-ready CSV record; this demo does not post to SAP.

Multiple orders stay in the inbox, with edits and decisions retained while switching between them. Browser state resets on reload.

Different work.
Same review principle.

Invoice matching ↗Proposal preparation ↗Shared knowledge ↗

Let the machine prepare.
Let the team decide.

Try the samples and follow one order from its source to a reviewed export.

Try the PO review