AugmentClaude

Finance & Accounting

Prepare journal entries, reconcile accounts, analyze variances, and generate financial statements.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/finance-notque/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Finance and accounting workflows — journal entries, reconciliation, variance analysis, financial statements, audit support, month-end close, SOX testing. Use when preparing journal entries, reconciling accounts, analyzing variances, generating statements, or supporting audits.

What this skill does

Finance & Accounting

Umbrella skill for finance and accounting workflows. Detects the domain from the user's request, loads the right reference files, and executes. All output is working material for qualified professionals — not financial advice.

Scope: Journal entries, reconciliation, variance analysis, financial statements, audit/SOX support, month-end close. Use csuite for strategic finance decisions, data-analysis for ad-hoc analytics.


Mode Detection

Classify into exactly one mode before proceeding.

ModeSignal PhrasesReference to Load
JOURNAL ENTRYbook, accrue, accrual, depreciation, prepaid, payroll entry, revenue recognition, deferred revenue, journal entryreferences/journal-entries.md
RECONCILIATIONreconcile, bank rec, subledger, GL-to-sub, intercompany, reconciling items, agingreferences/reconciliation.md
VARIANCEvariance, flux, budget vs actual, period-over-period, price/volume, waterfall, bridgereferences/variance-analysis.md
STATEMENTSP&L, income statement, balance sheet, cash flow, financial statements, GAAP presentationreferences/financial-statements.md
AUDIT/SOXSOX, control testing, sample selection, workpaper, deficiency, material weakness, ITGC, auditreferences/journal-entries.md + references/reconciliation.md
CLOSEmonth-end close, close calendar, close checklist, close day, hard close, soft closereferences/reconciliation.md + references/journal-entries.md

Always load references/llm-finance-failure-modes.md as a guard rail regardless of mode.


Workflow

Phase 1: CLASSIFY

  1. Detect mode from user request
  2. Load the corresponding reference file(s)
  3. Load references/llm-finance-failure-modes.md
  4. Confirm scope with user if ambiguous

Phase 2: GATHER

Collect the data needed for the task:

ModeRequired Inputs
JOURNAL ENTRYEntry type, period, account codes, amounts or source data
RECONCILIATIONGL balance, comparison source (bank statement, subledger, counterparty), period
VARIANCECurrent period data, comparison period data, materiality thresholds
STATEMENTSTrial balance or financial data, comparison periods, presentation preferences
AUDIT/SOXControl area, testing period, population data, prior results
CLOSEClose calendar dates, task ownership, current status

If the user provides partial data, ask for the minimum additional data needed. Do not fabricate account codes, balances, or transaction details.

Phase 3: EXECUTE

Follow the mode-specific workflow from the loaded reference file. Key constraints apply across all modes:

Debit/Credit Rules (always enforce):

Account TypeNormal BalanceTo IncreaseTo Decrease
AssetDebitDebitCredit
LiabilityCreditCreditDebit
EquityCreditCreditDebit
RevenueCreditCreditDebit
ExpenseDebitDebitCredit
Contra AssetCreditCreditDebit
Contra RevenueDebitDebitCredit

Verification gates (every journal entry):

  • Debits = Credits (balanced entry, no exceptions)
  • Account codes come from user data, never invented
  • Amounts traced to source calculations
  • Period is explicit and correct
  • Reversal flag set for accruals

Verification gates (every reconciliation):

  • Both sides reconcile to the same adjusted balance
  • Every reconciling item is categorized (timing, adjustment, investigation)
  • Items aged >60 days flagged for escalation

Verification gates (every variance):

  • Decomposition components sum to total variance (verify arithmetic)
  • Materiality threshold applied before narrative generation
  • Narratives are causal (why), not circular ("revenue was higher due to higher revenue")

Phase 4: VALIDATE

Before presenting output:

  1. Arithmetic check: Verify all calculations. Re-derive totals from components. Because LLMs miscalculate, re-check every sum, difference, and percentage (see failure modes reference).
  2. Completeness check: All required sections present per the reference file template
  3. Anti-hallucination check: No fabricated account numbers, GAAP citations, or standards references. If uncertain about a specific GAAP rule, say so.
  4. Consistency check: Treatment matches prior period (if prior period data provided)

Phase 5: DELIVER

Present output in the format specified by the reference file for the mode. Include:

  • The working artifact (entry, reconciliation, analysis, statement)
  • Supporting calculations
  • Items flagged for professional review
  • Suggested next steps

LLM Failure Modes in Finance

See references/llm-finance-failure-modes.md for the complete failure mode catalog (calculation errors, fabricated standards, materiality misapplication, period errors, account code fabrication). Universal failure modes (hallucination, overconfidence, generic output) are in skills/shared-patterns/llm-domain-failure-modes-base.md.


Failure Modes by Mode

Journal Entry Failure Modes

Failure ModeWhy It Fails
Unbalanced entry presented as completeViolates fundamental accounting equation
Missing reversal flag on accrualsCreates double-counting in the next period
Round-number estimates without calculation basisSignals fabrication, fails audit
Booking to "Miscellaneous Expense"Lacks specificity for variance analysis and audit trail
Same person prepares and approvesViolates segregation of duties

Reconciliation Failure Modes

Failure ModeWhy It Fails
Forcing the rec to balance by plugging a numberHides real differences that may indicate errors or fraud
Carrying items forward indefinitely without investigationStale items may represent losses or control failures
Reconciling to an unverified sourceBoth sides must come from authoritative sources
Skipping intercompany for "immaterial" entitiesIntercompany must eliminate to zero in consolidation

Variance Analysis Failure Modes

Failure ModeWhy It Fails
Circular narrative ("revenue is higher because revenue increased")No causal explanation
"Timing" without specifying what shifted and when it normalizesUninvestigable claim
"Various small items" for a material varianceMust decompose until below materiality
Ignoring offsetting variancesNet favorable can hide serious unfavorable components
Missing outlook (one-time vs recurring)Variance without context is useless for forecasting

Financial Statement Failure Modes

Failure ModeWhy It Fails
Assets not equal to liabilities + equityBalance sheet does not balance
Mixing functional and nature expense classificationGAAP requires consistency within a statement
Omitting non-cash items in cash flow reconciliationIndirect method requires all non-cash adjustments
Current/non-current misclassificationDebt maturing within 12 months must be current

Related skills