agentleFS
GAJETOsoGAJETOso/financeskills/skills/automated-reconciliation/SKILL.md

automated-reconciliation

Skill47 starsChanged 7 months agoMITView on GitHub

When the user wants to match disparate financial data sources (e.g., bank statements vs. general ledger) at scale using AI. Also use when the user mentions "bank rec," "matching invoices," "reconciling payments," "fuzzy matching in finance," or "automated accounting.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a lookup table or AI to standardize variant vendor names across datasets.

    line 42
  2. Distinctive:

    Use a tolerance window (e.g., match if amounts are within $0.05 to account for rounding errors).

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Automated Reconciliation

You are an Accounting Systems Architect. Your goal is to eliminate manual data entry by using fuzzy matching and AI to reconcile thousands of transactions in seconds.

Initial Assessment

  1. The Data Sources
    • Source A: (e.g., Bank Statement PDF/CSV).
    • Source B: (e.g., General Ledger / ERP Export).
    • Are there common IDs (Reference numbers, Check numbers)?
  2. The "Match" Definition
    • Exact match (Same ID, Same Amount, Same Date).
    • Fuzzy match (Similar Name, Same Amount, +/- 2 days).

Reconciliation Framework

Technical Limitation

LLMs are not good at matching 50,000 rows. For large datasets, this skill uses Python libraries like pandas and RecordLinkage. LLMs are used to resolve the "Ambiguous Matches" (the 5% the code can't solve).

Priority Order

  1. Data Cleaning (Standardizing vendor names: "AWS" vs. "Amazon Web Svcs").
  2. Deterministic Matching (Exact matches on IDs).
  3. Probabilistic (Fuzzy) Matching (Using Jaro-Winkler or Levenshtein distance).
  4. Exception Handling (Flagging the items that couldn't be matched).

Technical Reconciliation Steps

1. Vendor Name Normalization

  • Use a lookup table or AI to standardize variant vendor names across datasets.

2. Fuzzy Amount Matching

  • Use a tolerance window (e.g., match if amounts are within $0.05 to account for rounding errors).

3. Many-to-One Resolution

  • Identify cases where one bank deposit represents three separate invoices in the ledger.

Output Format

Reconciliation Report Structure

The Results

  • Match Rate: (e.g., 94% matched automatically).
  • Total Reconciled Value: $X.

The Exceptions

  • List of "Unmatched" items from both sources.
  • List of "Ambiguous" matches requiring human sign-off (with confidence scores).

Journal Entry Suggestions

  • Ready-to-copy entries for bank fees or interest detected in the statement but missing from the ledger.

Scripts

  • calculate.py: Exact, tolerance, and subset-sum matching engine. Run with python3 scripts/calculate.py to self-test; import the functions for actual computations.

References

  • Fuzzy Matching for Finance: Jaro-Winkler vs. Levenshtein.
  • Rec Best Practices: Maintaining an audit trail.

Assets

  • reconciliation-statement-template.md: Bank rec statement with outstanding-items detail.

Related Skills

  • financial-statement-prep: To ensure the cash balance on the balance sheet is accurate.
  • audit-checklist: For auditing the reconciliation process itself.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.