[01]Β LOOP
FinanceintervalHardened

Reconciliation on Autopilot

Inspired by End Close β€” continuous transaction reconciliation for high-volume payments. Deterministic matching rules handle the bulk volume, AI investigates exceptions with full context, and ops triages an inbox until close is audit-ready.

Inspired by End Close

by Trooper

Kickoff prompt
/loop 30m Start the "Reconciliation on Autopilot" loop.

Inspired by End Close (https://endclose.com).

Goal: all transactions matched or exceptions triaged with audit trail and compliance report ready
Max iterations: 24
Between iterations run: Report unreconciled transaction count, open exception count, and match rate vs prior cycle
Exit when: match rate meets target and every open exception has owner, evidence, and resolution or approved escalation

## Before you start
- Connect Stripe (required) β€” Pull payment processor transactions and payout events
- Connect Gmail (optional) β€” Send customer outreach drafts for approval
- Connect Slack (required) β€” Notify finance ops on material exceptions
- Connect Google Sheets (required) β€” Export reconciliation summaries and exception inbox
- Attach Loop runner (required) β€” Self-pace iterations and run checks between passes.
- Attach Human approvals (required) β€” Queue external sends and high-impact changes for sign-off.
- Attach Operations brief (required) β€” Summarize queue state and blockers each pass.
- Bank feeds / warehouse (read via api) β€” Ledger and payout source data
- ERP / general ledger (write via api) β€” Post cleared entries with human approval

## Steps
1. Ingest sources: Pull new transactions from payment processors, banks, warehouse/ledger exports, and internal systems. [tools: Stripe, Bank feeds]
2. Apply matching rules: Run deterministic rules (amount, vendor code, invoice number, date within range). Auto-reconcile high-confidence matches. [tools: Google Sheets]
   Command: node scripts/reconciliation-report.js --since 24h
3. Investigate exceptions: For unmatched items: gather warehouse data, analyze open invoices/payouts, draft customer outreach if needed, and propose a resolution. [tools: Gmail, ERP]
4. Triage inbox: Queue exceptions for ops review β€” assign owners, add comments, approve or adjust AI-suggested resolutions. [tools: Slack, Google Sheets]
5. Close and report: Update sources of truth, emit webhooks for cleared payouts, and export audit-ready reconciliation summary. [tools: ERP, Stripe]

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Guardrails:
- Do not force-match transactions or weaken rules to hit the exit condition
- Never post ledger or ERP entries without explicit human approval
- Every exception must include source events, supporting evidence, and an auditable action log
- Escalate material variances and regulatory-sensitive items to finance leadership
- Suggest rule improvements from resolved exceptions β€” do not auto-deploy rule changes without review

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Ingest sources

Pull new transactions from payment processors, banks, warehouse/ledger exports, and internal systems.

Tools: Stripe, Bank feeds

2. Apply matching rules

Run deterministic rules (amount, vendor code, invoice number, date within range). Auto-reconcile high-confidence matches.

Tools: Google Sheets

node scripts/reconciliation-report.js --since 24h

3. Investigate exceptions

For unmatched items: gather warehouse data, analyze open invoices/payouts, draft customer outreach if needed, and propose a resolution.

Tools: Gmail, ERP

4. Triage inbox

Queue exceptions for ops review β€” assign owners, add comments, approve or adjust AI-suggested resolutions.

Tools: Slack, Google Sheets

5. Close and report

Update sources of truth, emit webhooks for cleared payouts, and export audit-ready reconciliation summary.

Tools: ERP, Stripe

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Do not force-match transactions or weaken rules to hit the exit condition
  • Never post ledger or ERP entries without explicit human approval
  • Every exception must include source events, supporting evidence, and an auditable action log
  • Escalate material variances and regulatory-sensitive items to finance leadership
  • Suggest rule improvements from resolved exceptions β€” do not auto-deploy rule changes without review

More Finance loops