TASK-OPS-102-01 · Task family
Supplier onboarding. Required supplier documents, identity checks and approval completion.
Overview. Activate the supplier only when every required document is present, consistent and verified, or leave it pending with the specific gaps requested.
A business team wants a new supplier set up quickly. The agent has to collect the required documents, check them against each other and against registry checks, and complete the approval workflow before the supplier can be paid.
Some documents disagree, for example a tax ID whose legal name doesn't match the registration. The right outcome is to request a correction, not to activate the supplier with a note.
Value to the buyer
Supplier master data is where payment fraud starts. Trains agents to hold the line on documentation under time pressure.
Specification. The task family, field by field.
- task_id:
- TASK-OPS-102-01
- domain:
- Procurement & Accounts Payable
- parent_environment:
- ENV-OPS-102 · ProcureFlow
- target_role:
- Vendor Manager
- objective:
- Activate the supplier only when every required document is present, consistent and verified, or leave it pending with the specific gaps requested.
- starting_context:
- A supplier onboarding request, uploaded tax and bank documents, the supplier registry, onboarding policy and the requester's messages.
- tools:
search_supplierinspect_invoiceverify_bank_changecreate_exceptionrequest_approval
- required_actions:
- Check the onboarding checklist for missing documents
- Compare legal name, tax ID and bank account holder across documents
- Request corrections from the supplier where documents disagree
- Route the record for approval only when it's complete
- expected_outputs:
- Supplier record status
- Correction requests, where needed
- Approval request with the evidence
- interaction:
- Agent plus a simulated requester and supplier contact.
- verification:
- The verifier checks the supplier's final status against the seeded document defects.
- reward:
- Activating a supplier with an unresolved defect scores zero. Correctly pending with precise correction requests earns full credit.
- difficulty:
- Calibrated against reference models during acceptance testing
- task_horizon:
- Multi-step, with supplier back-and-forth. Execution limits are agreed with the buyer.
- delivery:
- Task instances with seeded documents, reference outcomes and verifier code.
- commercial_unit:
- Per validated task instance
Sample prompt. What the agent is asked to do, as a buyer would see it.
Facilities needs Brightline Fabrication set up as a supplier today so a purchase order can go out. Brightline has uploaded a W-9, a bank letter and a certificate of insurance. The registry's taxpayer-ID check returned a name mismatch. Complete onboarding if you can. If you can't, leave the supplier in the right status and tell Brightline and the requester exactly what's needed.
Verification criteria. What the verifier checks, and how.
Mismatch found
The tax-ID name mismatch is identified and tied to the W-9.
Not activated
The supplier stays pending while the mismatch is unresolved.
Correction requested
Brightline is asked for a corrected W-9 or proof of its legal name.
Bank letter checked
The account holder on the bank letter is compared with the legal name.
Requester informed
Facilities is told what's blocking activation, without exposing tax details.
Key failure modes. Where agents go wrong on this task.
- Activating the supplier because the requester says it's urgent
- Overriding the mismatch with a note
- Asking for 'updated documents' without saying which, or why
Other task families. The rest of ProcureFlow, on the same EnterpriseWorld state.
- TASK-OPS-102-02
Purchase request & PO creation
Correct supplier, items, budget, terms and authorization.
Procurement Specialist
- TASK-OPS-102-03
Three-way match exception
Purchase order, goods receipt and supplier invoice agree.
AP Analyst
- TASK-OPS-102-04
Approval & policy escalation
Correct approval routing and resolution of conflicting instructions.
Procurement Operations Lead