sow-acceptance-workflow

name	sow-acceptance-workflow
description	システム開発案件の SOW 作成、受注時 50% / 完了時 50% 請求、Acceptance Certificate 発行を支援する。

sow-acceptance-workflow

Purpose / 目的

システム開発案件の SOW 作成、受注時 50% / 完了時 50% 請求、Acceptance Certificate 発行を支援する。

When to use / 利用場面

• Use this skill for software/service SOW preparation, SOW approval routing, acceptance criteria, completion confirmation, Acceptance Certificate drafts, and invoice triggers tied to acceptance.
• Use this skill when the request connects project completion, customer acceptance, and milestone invoice timing.

When not to use / 使用しない場面

• Do not use for generic NDA/MSA lifecycle without SOW or acceptance trigger; use zoho-contract-lifecycle.
• Do not assume 50/50 billing for every customer; confirm in SOW or project intake.
• Do not issue Acceptance Certificate without project owner confirmation.

Skill-specific procedure / 固有手順

1. Draft or review SOW structure: scope, deliverables, assumptions, exclusions, milestones, acceptance criteria, change requests.
2. Map billing triggers to invoice plan, including 50/50 only when confirmed.
3. At completion, prepare Acceptance Certificate with deliverables, completion date, open issues, signer, and invoice trigger.
4. Route SOW/certificate and linked invoice plan through control gates.

Hard rules / 厳守ルール

• This skill is operational support, not legal, tax, accounting, or financial advice. 法務・税務・会計判断は必ず担当者または専門家承認を得る。
• Never send quotes, invoices, purchase orders, bills, RFQs, signature requests, or external emails without explicit human approval.
• Before writing to Zoho Books / Zoho Contracts through MCP or API, produce a draft and a change summary; require approval for create/update/send actions.
• Separate facts, assumptions, missing information, risks, and recommended next actions.
• Minimize personal/confidential data in outputs. Mask bank, tax, payment, and sensitive contract details unless needed for the task.
• Confirm market/entity context: US entity, Japanese parent/subsidiary, currency, tax treatment, payment terms, and approval authority.
• For Zoho product capabilities, API/MCP availability, pricing, and workflow behavior, verify against current official Zoho sources before asserting.

Procedure / 手順

1. Intake — 顧客、案件、契約、見積、請求、ベンダー、金額、通貨、期日、承認者、関連 Zoho レコードを確認する。
2. Classify workflow — Quote-to-Cash / Procure-to-Pay / Contract Lifecycle / Recurring Invoice / Acceptance のどれかに分類する。
3. Retrieve context — Zoho MCP/API、既存テンプレート、過去案件、メール文面、契約テンプレートを参照する。取得できない情報は Missing として列挙する。
4. Draft only — Quote、SO、Invoice、PO、Bill、SOW、NDA、MSA、Acceptance Certificate、RFQ メール等はドラフトを作成し、変更点とリスクを添える。
5. Control gates — 金額、支払条件、税、契約条項、顧客送付、署名依頼、会計計上、外部メールは承認ゲートを通す。
6. Execute after approval — 承認後のみ Zoho やメールへ反映し、レコードID/URL/送信先/日時を監査ログへ残す。
7. Follow-up — 入金・未署名・未承認・期限超過・作業完了請求などの次アクションを提示する。

Inputs / 入力

• Company / customer / vendor name
• Zoho Books organization and record IDs when available
• Deal / project / contract type: Quote, SO, Invoice, PO, Bill, SOW, NDA, MSA, Acceptance Certificate
• Amount, currency, tax treatment, payment terms, billing split, due date
• Approval owner and external recipient
• Templates, clauses, customer/vendor instructions, email thread summary

Outputs / 出力

• Draft artifact or action plan
• Missing information checklist
• Approval checklist
• Risk notes
• Zoho MCP/API action plan with proposed create/update/send operations
• Audit log summary after execution

Quality gates / 品質ゲート

• No external-facing artifact is sent without human approval.
• Draft includes source record IDs or states that IDs are missing.
• Accounting/legal/tax assumptions are separated from facts.
• Customer/vendor-specific terms are not generalized into the reusable template.
• For Example Customer use, apply the company overlay skill after this generic skill.

Related skills / 関連スキル

• zoho-finance-contract-orchestrator

SOW + Acceptance workflow

• SOW draft: scope, deliverables, assumptions, exclusions, milestones, acceptance criteria, change request process.
• Billing: default software development split can be 50% upon order/SOW execution and 50% after work completion/acceptance; confirm case-by-case.
• Acceptance Certificate: include project, deliverables, completion date, open issues, signer, and invoice trigger.

Output format example / 出力フォーマット例

Example: Acceptance Certificate triggering the final 50% invoice.

• Facts: Project "ERP integration phase 1"; PM confirms completion; SOW total USD 40,000; remaining 50% due after acceptance.
• Assumptions: The open issue (minor reporting enhancement) is handled as a disclosed exclusion, not a blocker.
• Missing: Customer signer for the certificate, Zoho contact_id for the final invoice.
• Draft (not sent): Acceptance Certificate with deliverables, completion date, and the open-issue disclosure; final invoice plan USD 20,000 triggered by the signed certificate.
• Approval gates: acceptance sign-off · customer send (certificate and invoice are separate gates).
• Next actions: confirm signer; obtain sign-off; only then issue the final invoice draft for approval.

Approval checklist (Acceptance & milestones)

• Deliverables checked against the SOW scope
• Open issues disclosed and explicitly included or excluded
• Certificate signer and date confirmed
• Invoice trigger = signed Acceptance Certificate (not verbal OK)
• Final amount equals the remaining contracted split
• Certificate send and invoice send approved as separate gates

Output structure example

Illustrative only. The certificate is a document draft; the final invoice uses the same payload shape as zoho-books-quote-to-cash (see that skill's Zoho payload example) with the milestone set to "50% on acceptance".

{
  "acceptance_certificate": {
    "project": "ERP integration phase 1",
    "deliverables": ["<deliverable 1>", "<deliverable 2>"],
    "completion_date": "2026-02-27",
    "open_issues": ["Minor reporting enhancement — excluded, tracked separately"],
    "signer": "<customer signer name / title>",
    "invoice_trigger": "Final 50% (USD 20,000) upon signature"
  },
  "status": "draft — not sent",
  "approval_required": true
}