Investigate a mismatch between the general ledger and a supporting ledger by tracing both sides to their original entries. Compare transaction details and return a concise cause, responsible team, expected resolution date, and recommended action.
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.
Review the instructions the agent will receive before you install.
Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.
Write the root cause as a single sentence in the form "⟨side⟩ ⟨did what⟩ because ⟨reason⟩", e.g.:
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Complete an existing financial model template by entering historical data and forecast assumptions, then linking the income statement, balance sheet, and cash flow statement with formulas. Check statement balances, cash consistency, and scenario behavior as each section is completed.
Prepare a period-end accrual schedule for expenses incurred but not yet fully recorded. Apply company policy, subtract amounts already booked, cite supporting records, and draft journal entries for controller approval, including reversal notes where required.
Review quarterly updates and financials across portfolio companies to identify practical AI opportunities. Rank them by estimated profit impact, speed, and feasibility, then outline first steps and approaches that other companies can reuse.
Check spreadsheet formulas for errors, broken references, inconsistent calculations, and unit mismatches. Review a selected range, one sheet, or an entire financial model, then receive findings ranked by severity with suggested fixes.
Analyze price differences between bond futures and cash bonds, identify the cheapest bond to deliver, and compare implied financing rates with market rates. Present valuation tables and historical context to assess potential basis trades.
Assess whether bonds are expensive, cheap, or fairly priced by comparing yields with government rates and credit risk benchmarks. Combine spread breakdowns, historical context, and interest rate scenarios into tables and a recommendation.