What the source did
- His account is about multifamily property. He gave his Grok Bot the company's general ledger for the whole year and told it to find duplicate payments.
- It flagged a bunch. Most were fine: the same work order split across units, and installment payments.
- One wasn't. A landscaper had billed them twice for the same job.
- His bookkeeper called the landscaper, who gave a credit of just under $700. "We never would have caught it," he wrote.
- He called it his first real money with Grok Bot: money already paid, got back for free.
- He shared no template; the prompt below is ours.
“$700 isn't life changing. But it's money I already paid and got back for free.”— MultifamilyJunkies (@multifamjunk), X
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Grok Bot, the company's general ledger for the whole year, and the invoices to check each flag against. He shared no template; ours is built from his post.
- Where it breaks
- False positives: legitimate repeats like the same work order split across units and installment payments. Each flag needs a human check against the invoices.
- Human checkpoint
- The bot only flags. A person (his bookkeeper) checks each flag against the invoice and contacts the vendor; the bot never contacts vendors, pays or edits the books.
- Tools involved
- Grok Bot, The company's general ledger for the whole year, The vendor invoices, to check each flag
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Copy the prompt
Ours Our version, built from his post. He shared no template. Fill in the [BRACKETS].
Audit this general ledger for duplicate payments. Never contact anyone.
I'm uploading the company's general ledger for the whole year.
1. Find payments that could be duplicates: the same vendor paid the same amount more than once.
2. For each one, list the vendor, dates, amounts, and any invoice or work order numbers in the ledger.
3. Sort the flags. Mark likely legitimate repeats, such as the same work order split across units or installment payments, and say why. Mark the rest "check".
4. Total the amount at stake in the "check" pile.
Only flag. Never contact a vendor, pay, buy, cancel, delete, or edit the books.
Approval rule
🛡
The bot only flags. A person (his bookkeeper) checks each flag against the invoice and contacts the vendor; the bot never contacts vendors, pays or edits the books. Sending, buying, posting, and deleting always need a human.
Set it up
- Export the company's general ledger for the whole year.
- Upload it and paste the prompt.
- Go through the flags. Expect most to be fine; set aside legitimate repeats like split work orders and installments.
- Check each remaining flag against the vendor's invoices.
- Have your bookkeeper (or you) contact the vendor about any real double bill and ask for a credit.
Common failures
⚠
- False positives. Legitimate repeats, like the same work order split across units and installment payments, get flagged too; most of his flags were these.
- Acting on a flag without the invoice. Each flag needs a human check against the invoices before anyone contacts the vendor.
Variations
- Make it a standing control. A commenter, @JakeLatimer26, wrote: "The bigger win is a standing control, like matching invoice numbers and vendors before anything gets approved."
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy