ProcureOps Task Solver
Overview
Use this skill to turn a task-local memo or packet plus the ProcureOps API into the exact JSON requested by the template.
Procedure
- Read the prompt, the answer template, and every local payload file first.
- Read
environment_access.mdto get the task API base URL and allowed endpoints. - Call
GET /manifestfirst, then fetch only the record collections needed for the packet. - Treat the API as source of truth. Use local payloads for target IDs, dates, aliases, chargeback excerpts, and other task-scoped hints.
- Resolve IDs outward from the memo to programs, suppliers, items, requisitions, contracts, purchase orders, receipts, invoices, approvals, budget snapshots, payments, and vendor-risk events.
- Fill the answer template exactly. Return JSON only.
Shared Rules
- Preserve field names, enum spellings, and required ordering from the template.
- Sort IDs and row arrays exactly as requested.
- Treat set-like lists as deduplicated sets unless the template says otherwise.
- Round USD to cents; keep ratios, percentages, and counts at the template precision.
- Prefer live record IDs over stale aliases or supporting notes. Put non-authoritative clues only in fields meant for support records.
- Copy required fixed values from the template exactly; do not invent new keys.
- When the template includes source-tracking fields, place live API record IDs in authoritative/evidence fields and local payload filenames in support-only fields.
Nomination Readiness Packets
- Find the nominated supplier, requisition, contract basis, package PO(s), receipts, invoice exceptions, approvals, budget headroom, and open supplier risk.
- Classify each line with the strongest blocker present.
- Use
holdornot_readyfor hard blockers such as missing contract, no receipt, late due date, or unresolved risk. - Use
conditional_nominationorat_riskwhen the line is otherwise supportable but still has AP, watch, or exception clearance issues. - Set committee action from the line-level outcomes and overall readiness.
Receiving Closeouts
- Reconcile ordered, received, rejected, and billed quantities.
- Compare PO, contract, and invoice prices and mark the price match explicitly.
- Compute received goods value, unreceived value, invoice totals, and AP hold status.
- Choose batch disposition, supplier action, and exception codes from the live records.
AP Close Reconciliations
- For each target invoice, compare invoice total to scheduled payments through the close date.
- Use opening balance plus invoice total minus scheduled payments for close balance.
- Put released invoices in the payment release queue and held invoices in the payment hold queue.
- Use controlled reason codes only, and keep them sorted when required.
Change-Control Files
- Compare the requested change against the active contract, ceiling, requisition approval trail, budget snapshot, and supplier risk.
- Calculate requested subtotal, tax, total, remaining budget, and blocker count from the live records.
- Release only when contract, budget, approval, and risk checks all pass.
AP Release Files
- Use the chargeback register plus the memo to separate approved from pending chargebacks.
- Release invoices only when the net amount is ready and no hard receipt hold remains.
- Treat missing receipt as a hold.
- Keep supporting alias notes separate from authoritative sources when the template asks for both.
Output
Return a single JSON object only. Do not add prose, markdown, or code fences.