Load context
On first use: Read ../../CLAUDE.md to obtain scenario-level configuration (escalation thresholds/anomaly definitions).
/dispute-identification — Reimbursement anomaly identification
Examples
→ Example: The user says "There is a dispute over a supplier invoice, the amount does not match the contract, help me handle it," and the system should invoke this skill to perform invoice dispute identification and classification.
→ Example: The user says "Help us analyze what invoice disputes there have been recently, whether they are price issues or quality issues," and the system should invoke this skill to analyze invoice dispute patterns and frequency.
→ Example: The user says "A supplier has sent three payment reminder letters, saying we have not been handling the dispute," and the system should invoke this skill to assess the credit risk of dispute handling delays.
Relationship with other Skills
Preceding Skill: Usually after other atomic Skills are executed, perform a secondary risk scan on the comprehensive results.
Not:
- Replacing invoice verification (invoice-verification)
- Replacing standard checks (policy-compliance-check)
- Replacing triple match (triple-match-automation)
Is:
- Cross-node pattern identification (employee historical behavior/cross-dimensional anomalies)
- Risk level reassessment (raising risk level based on pattern identification)
- Escalation decision triggering (complex anomalies beyond the judgment capability of a single node)
Anomaly pattern identification
Pattern 1: Identification of high-frequency anomaly employees
Identification logic:
统计维度：同一员工，同一自然月内
计数项：
- 发票异常次数
- 标准超标次数
- 三单差异次数
- 被驳回次数
触发阈值：
- 任一单项 ≥ 2 次
- 或异常总次数 ≥ 3 次
→ 🔴 升级至财务专员
→ 记录为"高频异常关注对象"
Pattern 2: Identification of amount threshold circumvention
Identification logic:
识别特征：
- 报销金额紧贴审批权限边界（如 4999 元 / 9999 元）
- 同一供应商的连续报销金额均在某一审批权限以下
- 同一费用类型（如"办公用品"）反复小额报销
触发阈值：
- 同一员工同一供应商 30 天内 ≥ 3 笔，金额均在 5000 元以下
- 或金额分布呈现明显的"分档聚集"特征（如 4900-4999 区间异常集中）
→ ⚠️ 标记"疑似分拆报销"
→ 要求提供完整采购记录
→ 如无法证明拆分合理性 → 升级至财务经理
Pattern 3: Supplier concentration risk
Identification logic:
统计维度：同一供应商，所有员工报销汇总
计数项：
- 30 天内对该供应商的报销笔数
- 30 天内对该供应商的报销总额
- 该供应商的发票异常记录
触发阈值：
- 30 天内报销笔数 ≥ 5 笔
- 且总金额 ≥ [填空：如 20 万元]
- 或发票异常 ≥ 1 次
→ 🔴 升级至财务专员
→ 核查该供应商是否在白名单内
→ 必要时触发供应商重新资质审查
Pattern 4: Time concentration anomaly
Identification logic:
识别特征：
- 同一员工在报销截止日前 3 天内集中提交大量报销
- 季末/年最后 1-2 个工作日集中提交（可能是突击花钱）
- 跨年后 5 个工作日内集中提交上年费用（跨期报销高峰）
触发阈值：
- 截止日前 3 天内提交笔数 ≥ 5 笔
- 或单日提交金额 ≥ [填空：如 10 万元]
→ ⚠️ 标注"集中报销，核查真实性"
→ 必要时要求抽查原始凭证
Pattern 5: Related-party relationship anomaly
Identification logic:
识别特征：
- 报销员工为供应商的关联方（查询[GOV]供应商股东穿透）
- 审批人与报销人存在上下级/亲属关系
- 报销金额与员工职级明显不匹配（普通员工报销高管级标准）
触发阈值：
- 任一关联关系被识别
→ 🔴 直接升级至财务经理
→ 不自行判断，记录为高风险案例
Pattern 6: Cross-period anomaly pattern
Identification logic:
识别特征：
- 连续 3 个月以上在月末最后 5 天提交报销
- 费用发生时间与报销提交时间间隔规律性超 60 天
- 每年固定时间（如 12 月）集中报销大量上一年度费用
触发阈值：
- 规律性月末集中提交 ≥ 3 次
- 或规律性跨期 ≥ 60 天 ≥ 3 次
→ ⚠️ 标注"跨期规律异常"
→ 要求说明情况
→ 如无合理解释 → 🔴 升级财务专员
Risk level reassessment
When any of the above patterns is triggered,reassess the risk level：
Initial risk level (output by other Skills)
| Initial conclusion | Initial risk |
|---|---|
| All atomic Skills pass | Low |
| Some Skills have ⚠️ warnings | Medium |
| Any Skill has ❌ rejection | High |
| Any Skill has 🔴 escalation | High |
Risk escalation after pattern triggering
| Triggered pattern | Risk escalation |
|---|---|
| High frequency anomaly (≥3 items/month) | Medium → High |
| Amount threshold circumvention | Low → Medium |
| Supplier concentration | Medium → High |
| Time concentration (rush reimbursement) | Medium → High |
| Related-party relationship anomaly | Medium → High (directly highest) |
| Cross-period pattern anomaly | Low → Medium |
Output template
═══════════════════════════════════════
报销异常识别报告
═══════════════════════════════════════
报销单号：[OA 单号]
申请人：[姓名]
本次报销金额：[X,XXX.XX] 元
异常模式扫描时间：[YYYY-MM-DD HH:MM]
═══════════════════════════════════════
【模式扫描结果】
高频异常员工：[⚠️ 触发 / ✅ 未触发]
→ 本月异常次数：[X] 次
→ 详情：[列举具体异常项]
金额临界规避：[⚠️ 疑似 / ✅ 未触发]
→ 临界点：[X 元] 权限：[Y 元]
→ 详情：[如触发，说明金额分布特征]
供应商集中：[⚠️ 触发 / ✅ 未触发]
→ 供应商：[名称]
→ 30 天内笔数：[X] 总额：[Y 元]
时间集中异常：[⚠️ 触发 / ✅ 未触发]
→ 提交时间：[距截止日 X 天 / 季末最后 X 天]
→ 详情：[描述时间集中特征]
关联关系异常：[🔴 高风险 / ✅ 未触发]
→ 关联类型：[员工↔供应商 / 审批人↔报销人]
→ 详情：[如触发，说明关联内容]
跨期规律异常：[⚠️ 触发 / ✅ 未触发]
→ 跨期次数：[X] 次
→ 平均间隔：[X] 天
═══════════════════════════════════════
【风险等级重评估】
初始风险：[低 / 中 / 高]
模式触发后：[低 / 中 / 高 / 🔴 最高]
调整原因：[如调整，说明触发模式]
═══════════════════════════════════════
最终结论：[✅ 无需升级 / ⚠️ 建议关注 / 🔴 须升级]
═══════════════════════════════════════
[无需升级：] → 返回原审核结论
[建议关注：]
→ 关注事项：[触发模式详情]
→ 建议操作：[是否通知财务经理 / 是否记录备查]
[须升级：]
→ 升级原因：[触发的高风险模式]
→ 接收人：[财务专员 / 财务经理]
→ 升级说明：[描述异常情况供接收人判断]
═══════════════════════════════════════
Escalation trigger conditions
The following situations directly trigger escalation and do not enter risk reassessment:
- Related-party relationship anomaly triggered (supplier is related to employee/approver)
- High-frequency anomaly + any other pattern triggered simultaneously
- Supplier concentration + that supplier has historical invoice anomaly records
- Suspected deliberate splitting of reimbursements (to circumvent approval authority)
Finance Skills — dispute-identification atomic skill