financial-reconciliation-exception-queue

Reconcile exported invoice and bank-transaction CSV files with deterministic reference, currency, amount, date-window, and counterparty rules. Use when finance operations, accounting support, SaaS payments, project billing, or a small business needs explainable matches, discrepancy evidence, ambiguous-candidate handling, unmatched-record workorders, deduplication state, and an audit trail without logging into a bank, changing ledgers, making payments, or sending financial data to an AI provider.

作者：暂未提供 | 来源记录：ClawHub

Financial Reconciliation Exception Queue

Inputs

- Invoice CSV with invoice ID, date, counterparty, amount, currency, reference, and status.
Bank transaction CSV with transaction ID, date, description, amount, currency, and direction.
Policy JSON with amount tolerance, date window, text threshold, and allowed invoice statuses.
Optional previous-state JSON containing unresolved deduplication keys.

Outputs

- summary.json: counts, match rate, and new/suppressed exceptions.
INLINECODE1 and matches.json: explainable confirmed candidates.
INLINECODE3 and exceptions.json: all current discrepancies.
INLINECODE5: only new exceptions requiring human action.
INLINECODE6: deterministic steps and input hashes.
INLINECODE7: open keys for the next run.

Three-step workflow

1. Validate and normalize both exports without changing their source files.
Match exact references first, then unique amount/date/counterparty candidates.
Review exceptions and make any ERP, bank, or accounting change manually in the authorized system.

Run

CODEBLOCK0

Boundaries

This workflow does not log into banking software, initiate payments, post journal entries, convert currencies, call an external AI service, or decide tax/accounting treatment. Ambiguous candidates and discrepancies remain human decisions.

See README.md and references/ for the schema, review policy, recovery steps, and acceptance checks.

financial-reconciliation-exception-queue