📦 Mova Po Approval — Mova工具

技能文档

Contract Skill — A ready-to-use MOVA HITL workflow. Requires the openclaw-mova plugin.

# MOVA Purchase Order Approval

Submit a purchase order to MOVA for automated risk analysis and a human decision gate — with a tamper-proof audit trail of every procurement decision.

什么 做

• Risk analysis — AI checks vendor registry, budget utilisation, authority level, 和 detects split-PO fraud patterns
• Risk snapshot — scores PO (0.0–1.0) 和 surfaces anomaly flags
• Human decision gate — procurement manager chooses: approve / hold / reject / escalate
• Audit receipt — every decision signed, timestamped, 和 stored 在...中 immutable compact journal

Requirements

插件: MOVA OpenClaw 插件 必须 installed 在...中 OpenClaw workspace.

ERP connector — 否 additional credentials 必填: Vendor registry, budget data, and authority matrix are fetched server-side by the MOVA runtime. The agent does not need separate ERP credentials.

Data flows:

• PO ID + approver ID → api.mova-lab.eu (MOVA platform, EU-hosted)
• ERP data (vendor/budget/authority) → fetched 由 MOVA runtime server-side, 读取-仅, 不 stored
• Audit journal → MOVA R2 storage, signed
• 否 data sent 到 第三个 parties beyond 上面

Quick 开始

Say "review PO-2026-004 with approver EMP-1042":

https://raw.githubusercontent.com/mova-compact/mova-bridge/main/test_po_PO-2026-004.png

The agent submits it to MOVA, shows the AI risk analysis with findings and anomaly flags, then asks for your procurement decision.

Demo

Step 1 — Task submitted 带有 PO document !Step 1

Step 2 — AI risk analysis: risk score 0.78, findings, escalate recommended !Step 2

Step 3 — Audit receipt + compact journal !Step 3

为什么 contract execution matters

• Split-PO fraud detection — policy enforces escalation 当...时 相同 vendor submits multiple POs 在...内 72h 到 bypass approval thresholds
• Authority enforcement — approver's authority level validated against authority matrix; inadequate authority always routes 到 escalation
• Immutable audit trail — compact journal records every 事件 带有 cryptographic proof
• EU AI Act / DORA 就绪 — procurement decisions high-risk financial actions requiring human oversight 和 满 explainability

什么 用户 receives

当...时 到 trigger

Activate when the user:

• Mentions PO 数字 (e.g. "PO-2026-001")
• Asks 到 approve, review, 或 check purchase order
• Says "procurement approval", "PO review", "check PO"

之前 starting, confirm: "Submit PO [PO-ID] 对于 MOVA risk analysis?"

Step 1 — Submit PO

Call tool mova_hitl_start_po with:

• po_id: PO 数字 (e.g. PO-2026-001)
• approver_employee_id: HR employee ID (e.g. EMP-1042)

Step 2 — Show analysis 和 decision options

If status = "waiting_human" — show risk summary and ask to choose:

• approve — Approve PO
• hold — Hold 对于 review
• reject — Reject PO
• escalate — Escalate 到 director/board

Show recommended option if present (mark ← RECOMMENDED).

Call tool mova_hitl_decide with:

• contract_id: 从 响应 上面 (不 PO 数字)
• 选项: chosen decision
• reason: human reasoning

Step 3 — Show audit receipt

Call tool mova_hitl_audit with contract_id. Call tool mova_hitl_audit_compact with contract_id for the full signed event chain.

Connect real ERP systems

By default MOVA uses a sandbox mock. To route procurement checks against your live ERP, call mova_list_connectors with keyword: "erp".

Relevant connectors:

Rules

• NEVER 使 HTTP requests manually
• NEVER invent 或 simulate results — 如果 tool call fails, show exact 错误
• 使用 MOVA 插件 tools directly — 做 不 使用 exec 或 shell
• CONTRACT_ID comes 从 mova_hitl_start_po 响应, 不 从 PO 数字