Chase every unpaid invoice with a Grok Bot for finance tasks

Money actions stay behind approval in every template here. The Bot proposes the payment, the refund or the send, and you answer Allow once, Deny or Always allow. Keep a Require Approval rule on anything that moves money, because a Require Approval rule beats an Always Allow rule when both match the same action.

The subscription audit routine runs on the 2nd of each month. It reads the card statement, groups charges by vendor, and flags every renewal that rose since last month alongside every charge from a vendor nobody has mentioned in 90 days. It names the vendor and the amount, which is the only version of that report anyone acts on.

An approval governs the action it is attached to and nothing else. Approving a payment does not undo a payment already sent, so the safe pattern is one approval per invoice rather than an Always allow rule covering a whole vendor. Every finance template ships with that rule written into the routine.