Skill

Official

break-trace

Root-causes a reconciliation break by tracing it to the originating GL journal entry and subledger transaction, then stating what differs and why.

data-engineering

npx claudepluginhub anthropics/financial-services --plugin gl-reconciler

Popularity

Parent stars

25,275

Parent forks

3,494

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/gl-reconciler:break-trace

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.

SKILL.md

40 lines · ~474 tokens

Similar Skills

break-trace

25.3k

Root-causes a reconciliation break by tracing it to the originating GL journal entry and subledger transaction, then stating what differs and why.

fund-admin

reconciliation

12.3k

Guides account reconciliations by comparing GL balances to subledgers, bank statements, or third-party data; covers processes, differences, and item categorization for bank recs, GL-subledger ties, intercompany.

finance

reconciliation

Designs and operates reconciliation processes for data accuracy across portfolio management, custodian, and clearing systems. Useful for daily position/cash/transaction matching, break investigations, multi-custodian normalization, and regulatory prep.

client-operations

Stats

LanguagePython

Parent stars25,275

Parent forks3,494

MaintenanceFair

Last CommitMay 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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.

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.