Back to Details

break-trace

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Root-cause a break

对账差异根源分析

Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.
给定一条差异行（key、GL数值、subledger数值、分类、可能原因），追溯至源头并生成根源分析说明。

Trace path

追溯路径

  1. Pull the GL side — via the internal-gl MCP, fetch the journal entry or posting that produced this GL line: entry id, posting date, source system, batch id, preparer.
  2. Pull the subledger side — via the subledger MCP, fetch the matching transaction: trade id, trade/settle dates, counterparty, source feed, FX rate used.
  3. Diff the attributes — line up posting date, FX rate/date, account mapping, quantity sign, amount sign. The differing attribute is usually the cause.
  1. 提取GL侧数据 — 通过internal-gl MCP，获取生成该GL行的日记账分录或过账记录：分录ID、过账日期、源系统、批次ID、制单人。
  2. 提取subledger侧数据 — 通过subledger MCP，获取匹配的交易：交易ID、交易/结算日期、交易对手、源馈送数据、使用的FX汇率。
  3. 对比属性差异 — 对齐过账日期、FX汇率/日期、科目映射、数量符号、金额符号。存在差异的属性通常即为原因。

Cause → statement

原因→说明

Write the root cause as a single sentence in the form "⟨side⟩ ⟨did what⟩ because ⟨reason⟩", e.g.:
  • "GL posted on settle date (T+2) while subledger posted on trade date — timing break, will clear on 2026-05-07."
  • "Subledger used WM/R 4pm rate; GL used Bloomberg close — FX break of 12 bps on the base amount."
  • "Security ABC123 maps to GL account 11420 in the mapping table but the subledger fed 11410 — mapping break, raise to reference-data."
  • "Subledger posted the trade twice (trade ids 88412 and 88419 are duplicates) — duplicate post, suppress 88419."
将根源原因以**"⟨某一方⟩ ⟨操作行为⟩，原因是⟨具体理由⟩"**的单句形式撰写，例如：
  • "GL于结算日（T+2）过账，而subledger于交易日过账——时间差异，将于2026-05-07自动消除。"
  • "subledger使用WM/R下午4点汇率；GL使用Bloomberg收盘价——基础金额存在12个基点的FX差异。"
  • "证券ABC123在映射表中对应GL科目11420，但subledger馈送的是11410——映射差异，需提交至reference-data团队处理。"
  • "subledger重复过账该交易（交易ID 88412和88419为重复记录）——重复过账，需屏蔽88419。"

Output

输出结果

For each traced break, return:
json
{
  "key": "...",
  "root_cause": "one sentence as above",
  "owner": "ops | reference-data | accounting | upstream-system",
  "expected_clear_date": "YYYY-MM-DD or null",
  "action": "monitor | adjust | raise-ticket | suppress"
}
Only the resolver writes adjustments — this skill diagnoses, it does not post.
针对每条追溯后的差异，返回：
json
{
  "key": "...",
  "root_cause": "如上格式的单句说明",
  "owner": "ops | reference-data | accounting | upstream-system",
  "expected_clear_date": "YYYY-MM-DD or null",
  "action": "monitor | adjust | raise-ticket | suppress"
}
仅调整人员可进行调整操作——本技能仅负责诊断，不执行过账。