Sort Your Invoice Follow-Ups Before You Board
The Departure
You're headed to the next client, and the unpaid-invoice list is still waiting. Send every overdue customer the same nudge and you might chase someone who paid yesterday, reopen a dispute, or ask for the full amount after a partial payment. Give the assistant the sorting job before travel turns it into another hotel-evening task.
The Co-Pilot
Tool: Gemini Chat with Argon
The Use Case: Turn an approved invoice snapshot into a review queue and unsent payment-status reminders.
The Build: Google announced new small-business tools on October 20, including finance skills, which are beginning a staged rollout. That's a useful reason to revisit this job. You don't need a new accounting connection to try the smaller version below.
We tested ordinary Chat with eight fictional invoices, not the new finance skill. Gemini correctly kept a disputed invoice, a recently reminded customer, a paid invoice, a future due date, a missing date, and an unmatched reported payment out of the draft queue. It prepared two reminders, including one for the correct $4,000 remaining after a $2,200 payment on a $6,200 invoice.
But the review still mattered. Its checklist described one customer's reported payment as $1,200 when the source confirmed only a $1,200 outstanding balance. The table correctly held that invoice. A correct status doesn't make every explanation a confirmed fact.
Make a small numbered SNAPSHOT. Include a cutoff date and time zone, invoice IDs, currency, billed amount, posted payments, due dates, disputes, unverified payment reports, and last-reminder dates. Explicitly mark missing information. Use only records you're authorized to handle in an assistant; start with fictional customers.
The Prompt:
Prepare my before-boarding receivables review queue from only the numbered SNAPSHOT below. Use its stated cutoff, never today's assumed date. For every invoice, show ID, source ID, currency, billed minus posted payments, due date, status and reason. Use DRAFT only when overdue, undisputed, no payment is awaiting verification, and no reminder was sent in the last three calendar days. Use HOLD for disputes, unverified payments or recent reminders; PAID for zero balance; NOT DUE for future due dates; NEEDS INFO for missing dates or amounts. Never convert currencies or total them together. Draft a separate polite reminder under 75 words for each DRAFT row, naming the invoice, remaining balance and original due date. Ask for payment status; do not invent fees, payment links, promises or new terms. End with the exact items I must verify before sending. Do not browse, connect apps, send, schedule, edit records or create external files. Stop in this conversation for my review.
The three-day pause is an example rule you control, not Google's default. Keep each source ID attached so you can check the row instead of trusting a polished reminder. Never interpret DRAFT as permission to send.
The Upgrade
Topic: Prepare the queue before takeoff; refresh it before sending.
Export a small, current slice. Start with the relevant customers from one trip. Include partial payments and exceptions, not just the overdue total. Exclude bank details and unrelated records. If you don't own this process, get the approved snapshot from whoever does.
Delegate the sorting while you pack. In Gemini, choose Chat and Argon where available, paste the prompt and snapshot, and keep the browser open until it finishes. Google lists Argon for AI Pro/Ultra subscribers. Check every status, subtraction, currency, and source. This doesn't prove background Task mode or laptop-off execution.
Refresh, then decide. Before manually sending a draft, check new receipts, disputes, payment arrangements, and reminders sent since the cutoff. Confirm the recipient and exact payment amount. A fresh payment can make a perfectly accurate old draft inappropriate.
If you want this to run while you fly, treat a recurring job in your already-approved agent setup as a separate experiment. Prove its source access and completion first. This Chat test establishes snapshot preparation only.
The Landing
Try eight fictional invoices before your next trip. Include one partial payment, one dispute, and one reported payment that hasn't cleared. Keep the workflow only if you can trace each proposed reminder back to the source and explain why the others stayed unsent.
Safe travels,
Marcellus