AR aging and collections dashboard

Who it's for

Controllers, AR owners and CFOs chasing collections, and the sales or CS leads who own the customer relationship.

What's in it

• Total open AR, past due and over 60 days
• DSO
• Aging buckets as bars
• The largest past-due accounts with days late and collection status

The prompt

Works in Claude, ChatGPT, Gemini and Copilot. Fill in the [brackets], then paste your data under it.

Build an AR aging and collections dashboard from the aging report below.
- Tiles: total open AR, total past due, total over 60 days, DSO (trailing 90 days: [VALUE or "calculate it"]).
- Aging buckets: Current, 1–30, 31–60, 61–90, 90+ as horizontal bars with amounts, colored from blue (current) to red (90+). Under the bars, say what percent of AR is past due vs. our target of [PERCENT].
- Table of the 6 largest past-due accounts: customer, amount past due, days past due, status note. Tag anything over 60 days in red.

My aging report:
[paste the aging report export]

Build it as ONE self-contained HTML file:
- Put all the data inside the file. No API calls, no fetch, no external data.
- Use plain HTML, CSS and JavaScript (inline SVG for charts is fine). If you need a chart library, load it from cdn.jsdelivr.net.
- Add a "data as of" date under the title.
- Make it readable on a laptop and print cleanly to one page if possible.

Data you need

• AR aging report (QuickBooks, Xero, NetSuite or your billing tool)
• Optional: notes on each overdue account

Make it and share it

1. 1Gather the numbersExport or copy: AR aging report (QuickBooks, Xero, NetSuite or your billing tool); Optional: notes on each overdue account.
2. 2Paste the promptCopy the prompt into Claude, ChatGPT, Gemini or Copilot, fill in the brackets and paste your data under it.
3. 3Check itTie the totals back to your source reports before anyone else sees it.
4. 4Put it on the fridgeUpload the HTML file to Dashfridge, or connect your AI and say "put this on the fridge". Publish it and invite your team.

Keep it current

How often: Weekly, or before every collections call. Update the same dashboard each time instead of sending a new file, so your team keeps one link and every past version is kept. Your AI can do the refresh for you: see dashboards that update every week.