Load context
On first use: Read ../../CLAUDE.md to obtain scenario-level configuration (data source status/escalation threshold).
/triple-match-automation — Three-way match automation
Examples
→ Example: The user says "The procurement invoice has arrived, help me do a three-way match and see whether it is consistent with the PO and goods receipt." The system should invoke this skill to perform three-way match verification.
→ Example: The user says "The three-way match found a discrepancy, help me determine whether to accept it or whether re-verification is needed." The system should invoke this skill to evaluate handling recommendations for the three-way match discrepancy.
→ Example: The user says "The supplier says their shipping record is consistent with our goods receipt, so why is there still a discrepancy?" The system should invoke this skill to investigate the cause of cross-system data discrepancies.
Definition of the three documents
| Document | Description | Source |
|---|---|---|
| Contract/Order (PO) | Procurement agreement or purchase order | OA contract approval record or ERP purchase order |
| Goods Receipt (GR) | Proof of receipt confirmed by the warehouse or requesting department | OA goods receipt confirmation record or warehouse receipt |
| Invoice | VAT invoice issued by the supplier | Attachment submitted by the employee |
Match check logic
First layer: Amount matching
Core formula:
差异率 = |发票金额 - 合同金额| / 合同金额
| Difference rate | Conclusion | Action |
|---|---|---|
| ≤ [fill in: 2%] | Reasonable error range | ✅ Pass |
| 2% - 5% | Minor difference | ⚠️ Flag, require the employee to explain the reason |
| > 5% | Significant difference | ❌ Reject, require verification and resubmission |
| Amounts exactly the same | Perfect match | ✅ Pass |
Note: Difference judgment is based on the contract amount, not the invoice amount.
Second layer: Date logic
Check items:
检查1:合同签订日期 ≤ 发票开具日期
→ 发票日期早于合同日期 → ❌ 逻辑矛盾,驳回
检查2:收货日期 ≥ 合同签订日期
→ 收货日期早于合同签订 → ❌ 逻辑矛盾,驳回
检查3:发票日期 ≥ 收货日期
→ 发票日期早于收货日期 → ⚠️ 要求说明(如在途物资/跨月结算可接受)
检查4:出差天数与住宿天数逻辑(差旅类)
→ 住宿天数 = 出差天数 - 1(到达当天不住宿)
→ 超出此逻辑 → ⚠️ 要求说明
Third layer: Entity consistency
Check items:
检查1:合同签约方 = 发票开具方
→ 不一致 → ⚠️ 要求提供代理授权书或分包协议
检查2:合同签约方 = 付款收款方
→ 不一致 → ⚠️ 要求说明(如第三方收款须提供授权)
检查3:发票购买方 = 公司全称
→ 须与公司营业执照名称一致
→ 不一致(如开给子公司/母公司)→ ⚠️ 确认内部调拨或要求重开
Special rules by procurement type
Office supplies/consumables (small amount, <5000 yuan)
处理逻辑:
- 通常无正式合同 → 审核重点转为"发票与采购申请一致性"
- 要求附采购申请截图或部门负责人确认
- 差异率阈值放宽至 10%(因无正式合同,误差空间大)
Equipment/assets (≥5000 yuan, must go through fixed assets)
处理逻辑:
- 必须有合同 + 收货确认 + 发票三单
- 发票品名须体现设备规格型号(与合同一致)
- 三单不一致 → ❌ 驳回,不予报销
- 三单一致 → 自动创建固定资产卡片号,写入审核报告
Services (consulting/IT/marketing services)
处理逻辑:
- 合同服务内容须与发票品名一致
- 服务周期须与合同约定一致(如年度服务 vs 月度服务)
- 部分服务完成后开具发票 → 审核里程碑节点与合同节点是否匹配
Exception handling paths
Minor amount difference (2%-5%)
处理:
1. 标注异常,生成说明模板
2. 提示申请人填写"差异原因说明"(系统内置模板)
3. 直属上级加签确认后 → ✅ 可通过
4. 如上级拒绝 → ❌ 驳回,要求重新换开发票
Supplier entity inconsistency
处理:
1. 查询[ERP]供应商主数据,确认是否为同一主体(曾用名/集团关联)
2. 如为集团内部调拨 → ⚠️ 要求提供集团内部调拨授权证明
3. 如为代理/分包 → 要求提供代理协议或分包授权
4. 无法提供 → ❌ 驳回,不予报销
Suspected split invoicing (circumventing approval)
识别特征:
- 同一合同项下,发票分多张开具(拆单)
- 拆分后每张金额均低于审批权限阈值(如低于 5000 元)
- 开票日期集中在同一周内
处理:
→ ❌ 驳回
→ 标注"疑似拆单"
→ 升级至财务经理核查
→ 如确认为故意拆单,记录诚信档案
Output template
═══════════════════════════════════════
三单匹配报告
═══════════════════════════════════════
供应商:[名称]
合同编号:[编号]
合同金额:[X,XXX.XX] 元
发票金额:[X,XXX.XX] 元
差异金额:[X,XXX.XX] 元
差异率:[X.X]%
【匹配结论】
金额匹配:[✅ 一致 / ⚠️ 轻微差异 / ❌ 显著差异]
日期逻辑:[✅ 正常 / ⚠️ 存疑 / ❌ 矛盾]
主体一致:[✅ 一致 / ⚠️ 主体存疑 / ❌ 不一致]
综合结论:[✅ 通过 / ⚠️ 需补正 / ❌ 驳回 / 🔴 升级]
═══════════════════════════════════════
[如通过:] → 流转至下一审核节点
[如需补正:]
→ 补正事项:[具体说明]
→ 补正方式:[补充说明 / 提供授权 / 换开发票]
[如驳回:]
→ 驳回原因:[金额差异超阈值 / 日期矛盾 / 主体不一致 / 疑似拆单]
→ 处理建议:[换开 / 提供证明材料]
[如升级:]
→ 升级原因:[疑似拆单 / 金额重大差异 / 供应商主体存疑]
→ 接收人:[财务专员 / 财务经理]
═══════════════════════════════════════
Escalation trigger conditions
- Difference rate exceeds 20% (major amount difference)
- Supplier entity cannot be verified
- Suspected intentional order splitting (circumventing approval authority)
- The same supplier has three-way match discrepancies for 3 consecutive times
- Involves related-party transactions (suppliers with a related relationship to the company)
Finance Skills — triple-match-automation atomic skill