zoho-finance-contract-orchestrator

name	zoho-finance-contract-orchestrator
description	Zoho Books と契約業務を横断し、Quote→契約→受注→請求→入金→完了証明までを統括する。

zoho-finance-contract-orchestrator

Purpose / 目的

Zoho Books と契約業務を横断し、Quote→契約→受注→請求→入金→完了証明までを統括する。

When to use / 利用場面

• Use this skill when the request spans multiple workflows or the correct workflow is ambiguous.
• Use this skill for initial routing, work-packet decomposition, confidence/matched-term review, and deciding which specialized skill should run next.
• Use this skill when classify_request() returns zoho-finance-contract-orchestrator or classify_request_details() shows low confidence / ambiguous candidates.

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

• Do not use for detailed payload construction after workflow routing; delegate to the specialized workflow skill.
• Do not use to approve or execute external sends or Zoho writes; use finance-contract-control-gates first.

Skill-specific procedure / 固有手順

1. Classify the request into one or more workflows using the bundled references/workflow.py implementation or classify_request_details() when available.
2. If multiple workflows are present, split the work into ordered packets: contract → quote/SO → invoice/PO/bill → monitoring.
3. Select the specialized skill and list the control gates required before execution.
4. Return a routing memo with workflow, confidence, matched_terms, missing information, and recommended next skill.

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-books-quote-to-cash
• zoho-contract-lifecycle
• finance-contract-control-gates

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

Example: routing memo for "monthly SOW acceptance and invoice".

• Classification: four workflows tie at one matched term each — recurring (monthly), acceptance (acceptance), contract (sow), quote-to-cash (invoice). Confidence 0.25 with ambiguous candidates → route to the orchestrator, do not force one workflow.
• Work packets (ordered): 1) confirm SOW/acceptance terms (zoho-contract-lifecycle / sow-acceptance-workflow) → 2) acceptance certificate → 3) invoice draft (zoho-books-quote-to-cash or zoho-books-recurring-invoice-ops once the billing type is confirmed) → 4) payment monitoring.
• Missing: whether "monthly" means recurring billing or a monthly milestone; customer and record IDs.
• Approval gates: acceptance sign-off · invoice creation · customer send.
• Next action: ask the requester to confirm the billing type, then dispatch packet 1.

Routing checklist (Orchestrator)

• Classification evidence captured (workflow, confidence, matched terms, ambiguous candidates)
• Mixed requests split into ordered work packets, not forced into one workflow
• Missing information listed per packet
• Control gates listed before any execution
• A specialized skill named for each packet

Classifier output example

Real output shape of classify_request_details("monthly SOW acceptance and invoice") from references/workflow.py:

{
  "workflow": "recurring_invoice",
  "recommended_skill": "zoho-finance-contract-orchestrator",
  "confidence": 0.25,
  "matched_terms": {
    "quote_to_cash": ["invoice"],
    "contract_lifecycle": ["sow"],
    "acceptance": ["acceptance"],
    "recurring_invoice": ["monthly"]
  },
  "ambiguous_candidates": ["quote_to_cash", "contract_lifecycle", "acceptance", "recurring_invoice"]
}