Verify order documents and prepare a fulfilment package

Why use this

1. An operations team preparing an order may have an invoice, purchase order and deposit record that disagree on dates or amounts. Producing a packing list and commission register before resolving those discrepancies can spread one mistake into several downstream documents.

2. A cross-document review packet could identify the authoritative correction and keep every proposed output aligned. The reviewer would confirm order details and commission basis before fulfillment changes or customer correspondence occur.

Why an agent / simpler alternative

Useful judgment

Reconcile related documents and expose conflicting references rather than choosing the most plausible value.

Simpler alternative

Use a standard order export when one authoritative system already holds reconciled data.

Unsuitable when

The correction requires unapproved financial judgment or an unsupported customer commitment.

Proposed inputs

1. Name

   Order document set

   Owner

   Operations owner

   Minimum scope

   Relevant invoice, purchase order and deposit evidence

   Quality check

   Confirm all records concern the same order and customer.

2. Name

   Approved correction and commission rules

   Owner

   Order/finance owner

   Minimum scope

   Explicitly confirmed values, commission basis and fulfillment requirements

   Quality check

   Distinguish owner-approved corrections from agent suggestions.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only documents and separate proposed register, packing list and message drafts.

Compatibility unknowns

1. Unknown: exact runtime, document extraction, accounting tools and Gmail draft access.

External actions requiring approval

1. Updating order records, changing commissions, initiating fulfillment or sending the customer email.

Expected deliverable and review checks

Proposed artifact

Discrepancy log and aligned fulfillment-package previews with a customer-message draft.

Critical checks

1. Corrected values are supported by explicit owner evidence.

2. Packing quantities, deposit treatment and commission calculations use the same approved order basis.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A date conflict is silently resolved from whichever document was read last.

   Why it matters

   Downstream records could preserve an unapproved correction.

   Proposed response

   Keep the conflict open until the responsible owner confirms the date.

2. Signal

   The commission register uses the deposit rather than the approved sales basis.

   Why it matters

   The calculation may misstate compensation.

   Proposed response

   Apply only the supplied rule and flag any missing basis.

Effort and cost — unknown

Setup work

1. Identify authoritative order fields and approved commission rules.

Ongoing review

1. Check consistency across every output before release.

Unknowns

1. Unknown: extraction quality, reconciliation effort and system-write support.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invented order documents contain conflicting dates and a deposit distinct from the stated commission basis.

Acceptance checks

1. The date remains unresolved without owner confirmation.

2. The proposed commission check uses only the approved basis.

Stop conditions

1. A financial correction, fulfillment action or external send lacks approval.

Limits

1. Editorial fulfillment preparation; no shipped order, posted commission or sent email is established.