zoho-books-recurring-invoice-ops

name	zoho-books-recurring-invoice-ops
description	ライセンス費用、保守費用、サブスクリプション等の定期請求運用を支援する。

zoho-books-recurring-invoice-ops

Purpose / 目的

ライセンス費用、保守費用、サブスクリプション等の定期請求運用を支援する。

When to use / 利用場面

• Use this skill when the request involves monthly / annual license billing, subscription renewals, recurring support or maintenance invoices, renewal reminders, recurring invoice schedules, or monitoring upcoming recurring invoice runs.
• Use this skill when the commercial pattern is repeatable over time rather than a one-time project milestone.

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

• Do not use for one-off project milestone invoices; use zoho-books-quote-to-cash.
• Do not use for vendor recurring bills; use zoho-books-procure-to-pay.
• Do not change recurring schedules in Zoho without approval and audit evidence.

Skill-specific procedure / 固有手順

1. Confirm subscription/license/support scope, billing frequency, start/end dates, renewal terms, and customer PO requirements.
2. Retrieve or draft recurring invoice profile: customer, items, price, tax, currency, memo, and delivery recipients.
3. Detect upcoming, failed, paused, or overdue recurring invoices and produce a monitoring report.
4. For renewals, confirm commercial approval before price/date changes.

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

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

Example: annual license renewal invoice.

• Facts: Customer XYZ USA; Zoho license resale; renewal period 2026-07-01 to 2027-06-30; billing annual.
• Assumptions: Same line items as the prior term unless the price change is approved.
• Missing: Price-change approval, Zoho contact_id, tax treatment for the new term.
• Draft (not written): Renewal invoice for the new period, linked to the expiring subscription record.
• Approval gates: price change · customer send.
• Next actions: obtain commercial approval for the price change; confirm tax; route for approval; do not send until approved.

Approval checklist (Recurring & renewals)

• Renewal period and start/end dates verified against the contract
• Price and any uplift approved by the commercial owner
• Subscription/license status confirmed (no double-billing, no lapsed term)
• Tax treatment confirmed for the new term
• Reminder cadence and escalation owner set
• Customer send approved separately from record creation

Zoho payload example

Illustrative only; verify fields against the current Zoho Books API and mask sensitive detail. Create as a draft and send only after approval.

{
  "customer_id": "<zoho_contact_id>",
  "recurrence_name": "XYZ USA — annual license renewal",
  "recurrence_frequency": "years",
  "repeat_every": 1,
  "start_date": "2026-07-01",
  "payment_terms": 30,
  "line_items": [
    { "name": "Software license — annual subscription 2026-07-01 to 2027-06-30", "rate": 12000, "quantity": 1 }
  ],
  "notes": "Renewal pending price-change approval. Draft only — do not send."
}