Accounts receivable is where finance teams quietly lose the most time. Every month-end, someone exports the AR ledger, rebuilds the same aging buckets in Excel, chases down payment promises buried in email threads, and drafts collection notices that all sound slightly wrong. A single skipped follow-up can push an invoice from 30 days to 90 days, and by then the probability of collection has already dropped sharply.
The deeper problem is not effort — it is inconsistency. Two analysts can look at the same aging report and prioritize completely different accounts. Collection emails get written from scratch every time, so tone and escalation logic drift. And the aging report itself is a snapshot with no narrative: it tells you what is overdue but not why, not what to do next, and not which accounts deserve a phone call versus a polite reminder.
ChatGPT closes that gap by turning your raw AR data into structured, repeatable output. It can segment accounts by risk and relationship, draft tiered collection sequences that match your tone, and convert a flat aging table into a commentary-ready summary for the CFO. The work still requires your judgment — but the drafting, sorting, and first-pass analysis collapse from hours to minutes.
Before you prompt: prepare your AR data
Output quality tracks input quality. Export your AR ledger to CSV or markdown with these columns at minimum: customer name, invoice number, invoice date, due date, amount, days past due, payment terms, and account owner. Add two fields that most teams omit but that dramatically improve results: a customer tier (strategic, standard, transactional) and a notes column capturing prior promises, disputes, or relationship sensitivities.
Strip anything you would not want pasted into a third-party tool. If your organization restricts customer data, anonymize names to Customer A, Customer B, and so on — the logic holds, and you can re-map afterward. Once your file is clean, the prompt below produces a prioritized, segmented worklist rather than a generic list of overdue invoices.
First, read these files completely before responding:
[ar_aging_export.csv] — full AR ledger with customer name, invoice number, invoice date, due date, amount, days past due, payment terms, customer tier, and account owner notes
[collections_policy.md] — our escalation rules, grace periods, dispute handling procedure, and approved tone for each contact stage
Here is a reference for what I want to achieve:
[Upload a prior month’s collections worklist as markdown, or describe one: a table sorted by collection priority with a risk score, recommended action, and owner per account]
Here’s what makes this reference work:
It ranks by recoverability, not just days past due. It separates disputes from delinquencies. It assigns one clear next action per account. It flags accounts needing a phone call versus an email. It keeps the total list short enough to act on in a single day.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A markdown table plus a short narrative summary, 400-600 words total
Recipient’s reaction: My collections analyst should open this and immediately know their top 15 calls without re-reading the ledger
Does NOT sound like: A raw data dump, a generic reminder list, or anything that treats a strategic account the same as a one-off buyer
Success means: Every account over 60 days past due has a named owner, a recommended action, and a one-line rationale
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
Notice what that prompt does structurally. It separates the data file from the policy file, so the model applies your escalation rules rather than inventing its own. It supplies a reference output so the format is fixed. And it forces a planning step before execution — which is where most AR prompts fail, because the model starts generating a table before it has understood your dispute-handling rules.
Turning the aging report into a narrative
The second high-value use case is the aging report commentary. Controllers and CFOs rarely need another pivot table; they need three paragraphs explaining what moved, what it means, and what management is doing about it. This is where ChatGPT earns its keep, provided you give it the prior period for comparison and your materiality threshold.
The prompt below produces board-ready commentary with variance explanations, concentration risk flags, and a forward-looking collection outlook. Feed it both periods, state your materiality cutoff, and let it draft. You will still edit — but you will be editing a draft instead of staring at a blank page at 11 p.m. on close night.
First, read these files completely before responding:
[current_month_aging.csv] — this month’s aging by bucket, customer, and business unit
[prior_month_aging.csv] — last month’s equivalent file for variance comparison
[commentary_standards.md] — our materiality threshold, required disclosures, prohibited forward-looking language, and house tone
Here is a reference for what I want to achieve:
[Upload last quarter’s approved aging commentary as markdown, or describe it: four short sections — total AR movement, bucket migration, top account drivers, outlook and actions]
Here’s what makes this reference work:
It leads with the number that matters, not the process. It explains variance in cause-and-effect terms. It names accounts only when they exceed materiality. It avoids hedging language. It ends with specific, dated actions rather than vague commitments.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: Four-section markdown commentary, 500-700 words
Recipient’s reaction: The CFO should be able to forward this to the audit committee with light edits only
Does NOT sound like: A data appendix, a list of every account, or anything speculative about customer intent
Success means: Every variance over the materiality threshold is explained with a cause and a management action
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
Start with one workflow, not both. Run the collections worklist prompt first — it delivers faster, more visible relief to the team actually making calls. Once the format is stable, save your prompt as a reusable template with the file references locked in, and refresh the data each cycle. The aging commentary prompt is the natural second step, because by then you will have cleaner inputs and a clearer sense of what the CFO actually reads.
One practical caution: never let the model send anything. Use it to draft, sort, and summarize; keep human review on every customer-facing message and every number that reaches a board pack. The value is in removing the blank-page problem and the manual sorting, not in removing accountability.
Published on 9 October 2026 on growwithgpt.com