Automated reconciliation
Skill GAJETOso/financeskills/skills/automated-reconciliation
AI-powered skills for financial professionals. Comprehensive collection of finance, accounting, audit, and compliance skills for AI agents. IFRS/GAAP compliant with industry-specific applications.
npx -y skills add GAJETOso/financeskills --skill automated-reconciliationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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."
SKILL.md
3.0 KB, as published. Nobody here has run it
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
-
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)?
-
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
- Data Cleaning (Standardizing vendor names: "AWS" vs. "Amazon Web Svcs").
- Deterministic Matching (Exact matches on IDs).
- Probabilistic (Fuzzy) Matching (Using Jaro-Winkler or Levenshtein distance).
- 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.pyto 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.