B2B Invoice AR Reminder Agent with Approval Gate
An agent reads open invoices from QuickBooks or Xero, skips blocked accounts, and drafts tiered payment reminders in Gmail that a person approves one by one before anything is sent.
The problem
Chasing unpaid invoices is easy to put off. In a small B2B business it usually falls to the owner or a part-time bookkeeper, who has to open the accounting system, work out what is overdue, check whether a customer has a dispute or a payment plan, write a polite email, and remember to follow up again. When it gets busy, reminders go out late, go out with the wrong tone, or go to a customer who was already promised more time, which hurts the relationship. This recipe sets up an agent that pulls open invoices on a schedule, removes any account marked blocked, disputed, on a payment plan, or in legal, sorts the rest into reminder tiers by days overdue, and drafts emails in Gmail for review. The client approves every reminder before it is sent. The agent never changes invoices, applies payments, or contacts blocked accounts.
Who it's for
- B2B service firms, agencies, wholesalers, and contractors who invoice on net terms from QuickBooks Online or Xero
- Businesses with roughly 15 to 300 open invoices at a time and no dedicated collections person
- Owners or bookkeepers who send reminders by hand from Gmail and want consistent, well-timed drafts
- Teams that already track disputes or payment plans somewhere, even informally, and can turn that into a status field
- Outsourced bookkeepers who manage AR for several clients and need a clear approval trail per client
Not a fit when
- Consumer debt collection or any accounts already handed to a collection agency or attorney; those carry separate legal rules
- Businesses that want reminders sent automatically without review; this recipe requires approval for every send
- Situations where invoice data in the accounting system is unreliable, such as payments not recorded for weeks
Tools
| QuickBooks Online or Xero | Source of open invoices, due dates, balances, and customer contacts; read access only for the agent |
| Google Sheets | Account status list (active, blocked, disputed, payment plan, legal) and reminder log with approver and send date |
| Zapier, Make, or a scheduled export | Pulls open invoice data on a schedule, such as every weekday morning, and passes it to the agent |
| Claude or a similar LLM | Applies tier rules, writes reminder drafts in your voice, and explains why each invoice is in its tier |
| Gmail | Holds reminder drafts; the client reviews, edits, and sends each one from their own account |
| Slack or email digest | Tells the approver how many drafts are waiting and lists any accounts skipped and why |
Inputs you need first
- Read-only or reporting access to open invoices with invoice number, customer, amount due, issue date, due date, and payment link if you use one
- A customer status list showing which accounts are blocked, disputed, on a payment plan, or in legal, with an owner for each
- Your payment terms and reminder schedule, for example a reminder at 3, 15, 30, and 45 days past due
- Two to four approved reminder templates, from friendly to firm, written or approved by the business owner
- The Gmail account reminders should come from, plus any CC rules such as copying the account manager
- A named approver for reminders and a backup for when they are away
Step-by-step build
Write the hard rules first
Put these rules at the top of a shared doc and in the agent instructions, word for word. One: the client approves every reminder before it is sent. Two: any account with status blocked, disputed, payment plan, or legal is skipped entirely and never drafted. Three: the agent never creates, edits, voids, or credits invoices and never applies or records payments. Four: escalating to a firmer tone still requires approval. Five: if invoice status or account status is unclear, the invoice is skipped and listed for a person. These rules come before every other step.
Build the account status list
Create a Google Sheet tab called Accounts with columns: customer_name, customer_id, billing_email, status, status_reason, status_owner, status_updated. Allowed status values are active, blocked, disputed, payment_plan, and legal. Fill it from your accounting system's customer list, then go through it with the owner and mark every account that should not get a reminder. Treat a blank status as do not contact until someone fills it in. This list is the gate: if it is wrong, reminders go to the wrong people, so give one person responsibility for keeping it current.
Define reminder tiers
Set tiers by days past due and write the tone for each. Example: Tier 0, due in 3 days, a courtesy note with the invoice attached. Tier 1, 1 to 14 days overdue, friendly. Tier 2, 15 to 29 days, a direct request for a payment date. Tier 3, 30 to 44 days, firm, mentioning your terms. Tier 4, 45 or more days, no draft; flag it for the owner to call. Adjust these to your terms. Add a rule that no customer gets more than one reminder per invoice in a set period, such as 7 days, using the reminder log to check.
Pull open invoices on a schedule
Use Zapier, Make, a scheduled report export, or a small script with read access to pull open invoices every weekday morning. Bring in invoice number, customer ID, amount due, currency, due date, and payment link if you use one. Match each invoice to the Accounts tab by customer ID, not by name, since names often differ. Drop any invoice whose customer is not active before it reaches the agent. Keeping blocked accounts out of the agent's input entirely is safer than asking the agent to ignore them.
Write the drafting prompt
Give the agent the hard rules, the tier table, your templates, and one invoice group per customer at a time. Ask it to pick the tier, fill the matching template with invoice numbers, amounts, and due dates exactly as provided, and write a subject line. It must not change amounts, invent late fees, threaten legal action, or offer discounts. If a customer has several overdue invoices, combine them into one email listing each. Output should include the tier, a short reason, the draft subject and body, and a flag if anything looks inconsistent.
Create Gmail drafts, never sends
Set the automation to create drafts in the approver's Gmail account using the customer's billing email, with any CC rules applied. Do not use any send action anywhere in the workflow. Add a label such as AR-Review to each draft so they are easy to find. Write a row to a Reminder Log tab with invoice numbers, tier, draft created date, and status Pending. Send the approver a short digest: number of drafts waiting, total amount covered, and a list of skipped accounts with the reason each was skipped.
Test with sample data
Build a test set of 15 to 20 invoices with made-up customers, including tricky cases: one disputed account, one on a payment plan, one with a blank status, one customer with three overdue invoices, one invoice paid yesterday but not yet recorded, and one exactly on a tier boundary. Send drafts to a test inbox. Check that blocked accounts produce no draft, amounts match to the cent, and tone matches the tier. Have the owner read every test draft and mark what they would change, then update templates and rules.
Go live with daily approval
Switch the drafts to the real Gmail account and pick a fixed approval time, such as 9 to 9:30 each weekday. The approver opens each AR-Review draft, checks the invoice in QuickBooks or Xero to confirm it is still open, edits if needed, and sends it or deletes it. After sending, they mark the log row Sent with their name and the date. Any reply that mentions a dispute, hardship, or a payment plan request goes to the status owner, who updates the Accounts tab before the next run.
Maintain and review monthly
Each month, review the reminder log next to your aging report. Look for invoices that got reminders after payment, accounts that should have been blocked, and drafts the approver rewrote heavily. Update templates and tier timing based on what you see. Make sure the Accounts tab was updated for every dispute or payment plan agreed that month. Rotate any shared credentials when staff change, and confirm the workflow still has read-only access and no permission to send email or change accounting records.
Example agent instructions
Adapt this to your business. Placeholders in braces are filled by your automation tool.
You draft accounts-receivable reminder emails for {business_name}. You only draft. A person approves and sends every email.
Hard rules, which override everything else:
- Only draft for accounts with status active. If any account in {invoice_data} has another status, skip it and list it under skipped.
- Never change amounts, due dates, or invoice numbers. Copy them exactly from {invoice_data}.
- Never mention late fees, interest, collections, or legal action unless that exact wording is in the approved template for the tier.
- Never offer discounts, extensions, or payment plans.
- If anything is unclear or inconsistent, do not draft. Put it under needs_review with a reason.
Tier rules:
{tier_rules}
Approved templates:
{templates}
Customer and invoices:
{invoice_data}
Steps:
1. Work out days past due for each invoice using {today}.
2. Group invoices by customer and use the highest tier in the group.
3. If the tier is the owner-call tier, do not draft; add it to needs_review.
4. Fill the template for that tier, list every invoice with number, amount, and due date, and include {payment_link} if one is provided.
5. Keep the tone professional and specific. Sign as {sender_name}.
Return JSON with: customer_id, tier, reason, subject, body, skipped, needs_review.
Human sign-off points
- The client or named approver reviews and approves every reminder draft before it is sent from Gmail; nothing is sent automatically
- The business owner approves the reminder templates and tier timing before go-live and after any change
- The status owner approves every change to an account's status in the Accounts tab, especially removing a blocked, disputed, payment plan, or legal status
- The business owner decides personally on accounts in the owner-call tier before any further contact
Guardrails
- Accounts marked blocked, disputed, payment plan, or legal are filtered out before the agent sees them and are never drafted
- A blank or unknown account status is treated as do not contact
- The workflow has read-only access to accounting data and cannot create, edit, void, or credit invoices or apply payments
- The workflow can create Gmail drafts but has no send action; every send is a human click
- Amounts and invoice numbers are copied from source data, and the approver checks that the invoice is still open before sending
- No more than one reminder per invoice within the set cooldown period, checked against the reminder log
- Firmer tiers still need approval, and no draft threatens legal action or mentions fees unless that wording is in an approved template
- Any reply mentioning a dispute or hardship pauses reminders for that account until the status owner reviews it
Expected time saved
Estimate: if you send about 25 reminders a week and each takes about 8 minutes to look up, check status, and write, while a reviewed draft takes about 2 minutes to check and send, that could save around 2 to 3 hours a week. This assumes payments are recorded promptly and the account status list stays current. Your results depend on volume and data quality.
How to tell it's working
- Average days past due across open invoices, tracked month over month
- Number of reminders sent to accounts that should have been skipped (target is zero)
- Share of drafts approved with light or no edits
- Time from invoice becoming overdue to first reminder sent
FAQ
Why not let the agent send the friendly first reminder automatically?
Even a friendly reminder can go wrong if a payment was just made, a dispute was raised by phone, or the account manager promised more time. Those facts often live outside the accounting system. Requiring approval for every send keeps a person who knows the relationship in control and avoids awkward or damaging emails. Batched daily approval keeps the review effort small.
Can it record payments when a customer replies saying they paid?
No. The agent never applies payments or changes invoices. When a customer says they've paid, a person checks the bank feed or payment processor and records the payment in QuickBooks or Xero as usual. Until that's done, the approver should delete any new draft for that invoice so the customer isn't reminded about something already paid.
Does this work for more than one company or client?
Yes, as long as each company has its own Accounts tab, templates, Gmail sender, and approver. Bookkeepers serving several clients should keep a separate workflow and log per client so data never mixes and each client approves their own reminders. Don't share one sender address across clients, and don't pass one client's data to the agent while drafting for another.
Want this set up for you?
Build it yourself with the steps above, or tell us what you need. We scope the work with you and send a written quote before anything starts.
Sources
Written by Agents Lookup. Official pages for the tools this recipe uses:
- QuickBooks Online MCP server (official page): github.com/intuit/quickbooks-online-mcp-server (checked 2026-11-09)
- Xero MCP server (official page): github.com/XeroAPI/xero-mcp-server (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)
- 中央社新聞 CNA TAIWAN NEWS (official page): ask.cna.com.tw/ask (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)