# Invoice Chase Desk: safe reminder rules and a ten-check payment reminder scan (free sample)

> From Invoice Chase Desk: the mistakes that make payment reminders expensive, eight rules to paste into your agent, and a read-only script that runs ten checks on one reminder, from the wrong balance and other invoice numbers to threats, pressure, surprise fees, new bank details and links off your payment domain.

- URL: https://paperchasewebb.ai/bots/marketplace/items/invoice-chase-desk-safe-reminder-rules-ten-check-scan-free-sample/
- Type: Prompt pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Claude Code, Codex, Grok Bot, Hermes (named in the listing); Plain .md plus one Python 3 script, standard library only, read-only. The rules paste into AGENTS.md, CLAUDE.md, Hermes notes or a Grok Bot's standing instructions. Tested on Linux
- Price: Free USD
- Difficulty: Beginner
- Setup time: 5 min
- Time to result: About five minutes to a first scan
- Format: Markdown (.md) file, invoice-chase-desk-safe-reminder-rules-ten-check-scan-free-sample.md
- Version: 1.0, updated 2026-11-01
- License: Personal and commercial use.

## What you end up with

You can see whether an AI-written payment reminder has the wrong amount, a threat, or bank-change wording before it reaches a client.

## What you get

- Why payment reminders need checking
- Eight rules for agents that draft reminders
- chase_mini.py: ten read-only checks for one reminder
- A worked first try with four findings

## Who it is for

Anyone who wants a quick check on agent-written payment reminders before they go to a client.

## Tools needed

- Python 3.8 or newer: runs the planner, the draft checker, the queue check, the eval set and the owner approval script; standard library only
- You need: Python 3.8 or newer
- You need: A reminder draft as a text file, with its invoice number, balance and due date

Cost to run: Free.

## Sample prompt: Check before you send (Grok Bot, Claude Code, Codex, Hermes)

```
Run python3 chase_mini.py on [draft] with --invoice [id] --balance [amount] --due [date] --link-domain [my pay domain]. Fix every finding or hand it to me. Do not send anything.
```

The rules and script are in the file.

## Free preview of invoice-chase-desk-safe-reminder-rules-ten-check-scan-free-sample.md

````markdown
# Invoice Chase Desk: safe reminder rules and a ten-check payment reminder scan (free sample)

Version 1.0, 2026-11-01. By PaperChaseWebb. For anyone letting an AI agent draft reminders for overdue invoices. One page and one Python 3 script, standard library only, read-only: it reads one email, prints findings and sends nothing. No API key, no login. Tested on Linux with Python 3.13, 3.12, 3.11, 3.9 and 3.8: 3 unit tests, and 68 of 68 planted faults caught. The example business is made up.

## Why reminders need checking

A payment reminder is short, but the mistakes are expensive:

- It goes to a client who paid this morning, or asks for the full amount after a part payment.
- It mentions new or changed bank details. That is the pattern of business email compromise, which the FBI's 2025 Internet Crime Report puts at just over $3 billion in reported losses for the year. Your client should never get that sentence from you, even by accident.
- It threatens court or collections, adds a fee your terms do not include, or says "we have referred this" when nobody did.

An agent will write "Just checking in! Our bank account has changed, so please use the new details below, or we will pass this to a collection agency." This script catches that before you send.

## Rules to paste into AGENTS.md, CLAUDE.md, a Grok Bot standing order or Hermes notes

1. Never send, email, text or post anything. Write a draft and stop. The owner sends.
2. Check the ledger first. Never chase an invoice th
````

## Test record

- Date: Nov 1, 2026
- What was run: tests/test_mini.py (3), 68 planted faults against chase_mini.py, and the copy extracted from the sample page. Linux, Python 3.13, 3.12, 3.11, 3.9 and 3.8.
- Result: 3 passed, 0 failed on all five versions; 68 of 68 faults caught; the extracted copy was identical to the tested script and gave 4 findings on the example first try.
- Not run: The ledger planner, full checker, queue and eval set (the full kit does those).

Copied from this item's dated test notes. What was not run stays in.

## Worth knowing

- The sample checks one email on its own. The ledger planner, full draft checker, consumer mode, queue check, eval set, owner approval step and agent setups are in the full kit.
- On 2026-11-01 chase_mini.py passed 3 unit tests and 68 of 68 planted faults on Linux with Python 3.13, 3.12, 3.11, 3.9 and 3.8, and the copy extracted from the sample page was identical to the tested script.

## Questions

**Does it change my files?** No. It reads the file you name and prints findings. It opens no network connection and sends nothing.

**What is in the full kit?** A planner that reads your ledger, a draft checker with balance, date, fee, link and bank checks, business and consumer modes, a 24-invoice eval set, owner approval at a terminal, and setup for Grok Bot, Claude Code, Codex and Hermes. $24.

## How to get it

Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/invoice-chase-desk-safe-reminder-rules-ten-check-scan-free-sample/, no signup.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com