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.
Trace path
- 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.
- Pull the subledger side — via the subledger MCP, fetch the matching transaction: trade id, trade/settle dates, counterparty, source feed, FX rate used.
- Diff the attributes — line up posting date, FX rate/date, account mapping, quantity sign, amount sign. The differing attribute is usually the cause.
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."
Output
For each traced break, return:
{
"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.
Hermes Profile Notes
This skill was packaged from pi-financial-services source path plugins/vertical-plugins/fund-admin/skills/break-trace for the Hermes financial-services profile. Use institutional data connectors first when available, cite sources, and stage outputs for qualified human review.
Common Pitfalls
- Do not present drafts as investment, legal, tax, or accounting advice.
- Do not use web search as the primary source when an institutional MCP/data connector is available.
- Do not execute transactions, contact clients, post to a ledger, or approve onboarding. Stage outputs for review.
Verification Checklist
1---2name: break-trace3description: Use when financial-services work requires root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break..4license: MIT5---67# Root-cause a break89Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.1011## Trace path12131. **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.142. **Pull the subledger side** — via the subledger MCP, fetch the matching transaction: trade id, trade/settle dates, counterparty, source feed, FX rate used.153. **Diff the attributes** — line up posting date, FX rate/date, account mapping, quantity sign, amount sign. The differing attribute is usually the cause.1617## Cause → statement1819Write the root cause as a single sentence in the form **"⟨side⟩ ⟨did what⟩ because ⟨reason⟩"**, e.g.:2021- "GL posted on settle date (T+2) while subledger posted on trade date — timing break, will clear on 2026-05-07."22- "Subledger used WM/R 4pm rate; GL used Bloomberg close — FX break of 12 bps on the base amount."23- "Security ABC123 maps to GL account 11420 in the mapping table but the subledger fed 11410 — mapping break, raise to reference-data."24- "Subledger posted the trade twice (trade ids 88412 and 88419 are duplicates) — duplicate post, suppress 88419."2526## Output2728For each traced break, return:2930```json31{32 "key": "...",33 "root_cause": "one sentence as above",34 "owner": "ops | reference-data | accounting | upstream-system",35 "expected_clear_date": "YYYY-MM-DD or null",36 "action": "monitor | adjust | raise-ticket | suppress"37}38```3940Only the resolver writes adjustments — this skill diagnoses, it does not post.4142## Hermes Profile Notes43This skill was packaged from `pi-financial-services` source path `plugins/vertical-plugins/fund-admin/skills/break-trace` for the Hermes financial-services profile. Use institutional data connectors first when available, cite sources, and stage outputs for qualified human review.444546## Common Pitfalls471. Do not present drafts as investment, legal, tax, or accounting advice.482. Do not use web search as the primary source when an institutional MCP/data connector is available.493. Do not execute transactions, contact clients, post to a ledger, or approve onboarding. Stage outputs for review.505152## Verification Checklist53- [ ] Inputs, assumptions, dates, and currencies are explicit.54- [ ] Numbers tie across tables, models, decks, and memos.55- [ ] Sources are cited and institutional data is preferred where available.56- [ ] Output is labeled draft / for human review where appropriate.
changhochien