Back to Cookbook
KiloClaw

Reconciliation Autopilot

Close faster by making reconciliations exception-driven, not spreadsheet-driven

A standardized reconciliation workflow that pulls source data, proposes matches, isolates exceptions, and produces an audit-ready reconciliation pack for review and sign-off.

House RecipeWork10 min setup

INGREDIENTS

🌐Browser✉️Email📅Calendar📄Google Docs🔔Notifications

PROMPT

Create a skill called "Reconciliation Autopilot" for our accounting team. We need a standardized reconciliation workflow for bank/cash/subledger accounts that: - Ingests statement/export data plus GL/subledger transactions for a defined period - Normalizes data into a single workspace - Matches transactions using exact match, rule-based match, then fuzzy match with tolerances - Produces an exception queue with likely root causes and required follow-ups - Generates an audit-ready reconciliation pack per account - Requests reviewer sign-off and archives outputs with timestamps Ask me for: - Account list and reconciliation cadence - Data sources and access method - Matching rules and tolerances Then output: - The reconciliation pack - The exception queue with owners and due dates - A short sign-off summary

How It Works

Bank/cash/subledger reconciliations often become the bottleneck that delays the rest of close work.

This recipe turns reconciliations into a repeatable, exception-first workflow with a clear audit trail.

What You Get

  • Reconciliation pack per account (matched items, timing items, open exceptions)
  • Exception queue with required follow-ups and owners
  • Close-ready sign-off note (who reviewed, when, what remains open)

Setup Steps

  1. Define the accounts to reconcile (bank, credit card, clearing, key balance-sheet accounts)
  2. Connect source-of-truth exports (bank/PSP statements, subledger exports, GL transactions)
  3. Configure matching rules, tolerances, and timing-difference logic
  4. Run the workflow daily/weekly or during month-end close
  5. Review the exception queue and sign off the reconciliation pack

Tips

  • Run a pre-close cadence so month-end is mostly exception resolution
  • Start with deterministic rules first, then layer in fuzzy matching
  • Lock signed packs to preserve auditability
Tags:#accounting#reconciliation#close#automation#controls