Four specialized Grok Bots reconcile bank vs invoices; sample of 3,412 lines finished in 41 minutes leaving only 16 unprovable exceptions
kvinsiX (Twitter) · 2026-11-11
Read originalGrok Bot just closed the month and the only thing it handed back was what it couldn't prove every month two lists should agree: what the bank says happened and what the invoices say should have they almost never do and by hand it eats six working days of staring at rows on a sample March with 3,412 open lines it took 41 minutes and left 16 lines for a human 4 bots, one job each: > Reader, the loader: takes every bank and invoice line, cleans vendors and currencies, keeps the source row on each > Matcher, the weaver: pairs lines only on same vendor, same amount to the cent, dates within 3 days > Snagger, the tagger: hangs a tag on every pair that fails, with the rule it broke and both amounts > Closer, the seal: writes the close note, saves exceptions.md and stops read → match → snag → my yes → close the 16 left over: 9 duplicates, 4 splits, 2 missing, 1 swapped total it never forces a match: if a pair can't be proved it stays open and the ledger stays untouched until i've seen the diff full setup in the article below ↓
Business model
Author runs four specialized Grok Bots (Reader loads & cleans, Matcher pairs only on strict rules, Snagger tags failures, Closer writes the close note and stops) to reconcile bank lines against invoices each month. Manual work previously took six days; on a sample March of 3,412 open lines the process took 41 minutes and handed back only 16 unprovable lines (9 duplicates, 4 splits, 2 missing, 1 swapped total). Rules: same vendor, amount exact to the cent, dates within 3 days. It never forces a match and the ledger stays untouched until the human has seen the diff. Readers can reuse the “single-responsibility bots + strict match rules + exception-only handback + human final yes” month-close pattern.
Workflow
- Reader loads every line, cleans vendors and currencies, keeps source row
- Matcher pairs only on same vendor, exact amount to the cent, dates within 3 days
- Snagger tags each failure with the broken rule and both amounts
- Closer writes close note, saves exceptions.md and stops; waits for human yes
Adaptation plan
Results and numbers are as reported by the original post author (sample March: 3,412 lines, 41 minutes, 16 exceptions; six working days by hand). No multi-month results disclosed. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The post links to the author's separate article about Grok Bot memory, not the reconciliation setup.
Prompt
AgentFlow draft · Untested.
You are one specialized Bot inside a month-close reconciliation system. Execute only your assigned single role; do not exceed it. Variables (user must supply): - BANK_LINES: bank statement export (date, amount, vendor/description, source row). - INVOICE_LINES: invoice list (date, amount, vendor, source row). - ROLE: one of Reader | Matcher | Snagger | Closer. Task (by ROLE): - Reader: load every line, clean vendor names and currencies, keep original source row, output cleaned set. - Matcher: pair only lines that satisfy ALL of: same vendor, amount exact to the cent, date difference ≤ 3 days. Leave anything unprovable unpaired. - Snagger: tag every failure with the rule it broke and both amounts. - Closer: write the close note, save exceptions.md, then stop. Never modify the ledger. Output format: - Structured list or markdown (cleaned lines / pair results / tagged exceptions / exceptions.md). - Clearly mark which items are proved and which remain for human review. Missing / conflict handling: - If a line lacks vendor, amount or date, mark as unprovable and place in exceptions; do not guess. - On amount-unit or currency conflict, stop that line and flag it. - Never force a match on any pair that fails any rule. Confirmation boundaries: - You may only read the provided lines and produce notes/exceptions.md. - Do not modify any ledger, bank record or invoice system. - Final close requires the owner's explicit yes; until then the ledger remains untouched. - Any payment, send or external write is forbidden unless the owner separately and explicitly authorizes it. Untested. Reconstructed from original post description.
Running costs and pitfalls
Results and numbers are as reported by the original post author (sample March: 3,412 lines, 41 minutes, 16 exceptions; six working days by hand). No multi-month results disclosed. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The post links to the author's separate article about Grok Bot memory, not the reconciliation setup. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.