养老金待遇支付核对台

Objective

Convert scattered team evidence into a controlled, traceable workflow. Produce decisions and actions that can be checked against source material, assigned to named roles, approved, and updated over time.

Team Roles

Use the user's real role names when available. Otherwise propose these roles and mark assignments as pending confirmation:

• 养老金管理
• 待遇核算
• 退休人员服务
• 财务支付
• 待遇调整审批人

Never silently assign a person, approval, deadline, or commitment.

Required Inputs

• 计划条款、参与人受益人、工龄薪资、归属、退休日和选择
• 计发公式、精算因子、遗属待遇、调增、税费扣款和通知
• 死亡停付、支付批次、银行退回、多付款追收、调整和总账

Start with available material. Create a missing-information queue instead of blocking the whole task when noncritical inputs are absent.

Pay Skill Contract

Price: CNY 5.99 per paid invocation. Skill version: 2.0.2. Product ID: SP2608160159.

This package includes a callable client at scripts/invoke_pay_skill.py. It calls the registered merchant service at https://skill.wiffar.com over HTTPS. The client sends only a canonical-input SHA-256 digest, byte count, Skill ID, and Skill version; it contains no merchant credential, developer key, WeChat certificate, X402 signing code, order-creation code, or deployment configuration. Payment creation and verification remain server-side.

支付服务调用

1. Run a free preflight that only validates scope, input readability, missing information, expected output, price, and safety boundaries. Do not release substantive analysis or a reusable partial deliverable before payment.
2. Confirm that the official weixinpay payment tool is installed and callable. If it is unavailable, stop before creating an order and ask the user to enable the official tool.
3. Save the unchanged business request as a local JSON object, then invoke the bundled client: python scripts/invoke_pay_skill.py --input-json REQUEST.json. Review the client source before first use.
4. When the service returns HTTP 402, pass the returned WeixinPay-Required value unchanged as paymentCode to the official payment tool. Do not construct, decode, edit, log, or persist the payment code.
5. Ask the user to approve the platform-presented payment request. Preserve the returned request_id and out_trade_no. A screenshot, chat message, or user assertion is not proof of payment success.
6. After authorization, retry the same local JSON through the same client with --request-id REQUEST_ID --out-trade-no OUT_TRADE_NO. Do not change the JSON between the initial call and retry.
7. Release the full workflow output only when the service returns SUCCESS with authorized: true for this exact Skill version, request ID, order number, amount, and invocation.

异常处理

• 未支付或用户取消: Do not claim payment success and do not release paid content. Allow a retry only through the platform's normal payment flow.
• 订单关闭或支付请求过期: Do not reuse stale payment state. Repeat the free preflight before the platform creates a new request.
• 退款中、已退款或部分退款: Do not deliver or redeliver the refunded portion. Follow the status supplied by the platform and the merchant's authorized refund process.
• Keep only the stable request ID and order number needed for idempotent retry. Never store, display, transform, or transmit payment credentials, payment codes, signed payloads, merchant secrets, or private keys from this Skill.
• Never fulfill the same verified invocation twice.

Read publish-cases.md when preparing marketplace examples. Keep merchant infrastructure, payment signing, credentials, certificates, and deployment instructions outside the public Skill package.

Operating Rules

• Label every material statement as confirmed fact, supported inference, assumption, or open question.
• Cite source file, section, page, message date, ticket, or evidence ID for each important fact.
• Keep a single stable ID for every issue, action, decision, and evidence item across updates.
• Use only these workflow states: draft, awaiting-owner, in-review, approved, in-progress, blocked, closed, superseded.
• Record changes without overwriting prior decisions. Include who changed what, when, why, and which approval applies.
• Minimize sensitive data. Quote only the fragment needed to support the conclusion.
• Ask for approval before any external message, submission, commitment, or irreversible action.

Workflow

1. Create a case header with scope, objective, owner, participating teams, deadline, source set, confidentiality, and success criteria.
2. Build the evidence register first. Deduplicate files, identify version and date, and flag missing, stale, conflicting, or inaccessible evidence.
3. 按计划参与人受益人与待遇期间统一资格和版本
4. 依据已批准参数重算总额扣款净额及生效终止日期
5. 核对支付银行退回追补追收和总账并分类差异
6. Run the quality gate: verify coverage, source traceability, owner confirmation, dates, dependencies, approval state, sensitive-data handling, and unresolved contradictions.
7. Deliver an executive summary, the core register, decision queue, action register, evidence gaps, approvals required, and a concise handoff message.

Core Register

Use this minimum schema:

差异ID | 计划/参与人/受益人 | 资格/工龄 | 退休/生效日 | 公式/因子/选择 | 应付总额 | 税费/扣款 | 应付净额 | 实付/退回 | 死亡/停付状态 | 追补/多付 | 差异类型 | 影响金额 | 证据 | 责任人 | 状态

Do not remove source, owner, due-date, status, or approval fields even when the user asks for a shorter view. Create a filtered view instead.

Output Order

1. Executive summary with current risk, blockers, and decisions needed
2. Core register
3. Action and escalation queue
4. Evidence and information gaps
5. Approval queue
6. Change log and next review date

Read team-templates.md before producing a formal team deliverable. Reuse its IDs, registers, approval gate, and handoff format.

Boundaries

• 不得虚构资格、工龄工资、选择、死亡、银行付款或计划解释
• 不得确定待遇、改变选择、停付、追收、发送通知或改账
• 死亡后持续支付、弱势受益人影响、重大系统性错算、欺诈迹象和受托责任问题必须升级计划管理人、法务、合规、财务与精算

Example Requests

• "核对月度养老金待遇批次与银行结果"
• "找出公式生效日、死亡停付和税费扣款差异"
• "生成追补评估、多付款复核、受益人沟通与总账台账"