/
/
Know the sales story before you chase an overdue invoice
For finance teams who want overdue Harvest invoices shown with recent Chorus conversations, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Reminders land without knowing the sales story
Finance sees an overdue invoice in Harvest but not whether sales is negotiating with that customer in Chorus. Checking means looking up each name in both systems, so reminders often go out at the wrong time.
Without PopdockAI
- List overdue invoices in Harvest
- Search each client name in Chorus
- Read recent conversations and emails
- Chase without knowing about a dispute
With PopdockAI
- Overdue invoices are grouped by client with totals
- Latest Chorus conversations and emails are added
- A dispute is named only when the text says so
- Nothing is drafted or sent
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find Harvest invoices that are at least `{min-days-overdue}` days overdue (default 14) and add the recent Chorus conversation history for each client so the follow-up can be informed, looking back `{lookback-days}` days in Chorus (default 60).
**Step 1: Find the overdue invoices in Harvest**
Call `harvest-get-invoices` with `state` set to open and `due-date.to` set to today minus the minimum days. Keep only invoices with a `due-amount` above zero. Group them by `client-name` and total the `due-amount` per client.
**Step 2: Look each client up in Chorus**
For each client, starting with the largest amount due and stopping after 10 clients, call `chorus-get-engagements` with `account-name.contains` set to the client name and `date.from` set to the start of the Chorus window. Then call `chorus-get-emails` with `account-name.contains` set to the client name and `sent-time.from` set to the same date. If a client has no match in Chorus, record "no Chorus account found" and move on.
**Step 3: Report**
A table with one row per client: client, invoices overdue, total due, oldest due date, last Chorus conversation (date, subject, owner), emails in the window. Then a short list of clients where a recent conversation suggests a dispute or a stalled relationship, quoting the `subject` or `meeting-summary` text that led you to say so. Do not draft or send any message.
**Rules & Guidelines:**
* Harvest tools (names starting harvest-) come from the harvest server and Chorus tools (names starting chorus-) come from the chorus server. Both servers must be connected.
* This is read-only. Do NOT call any Harvest create, update, delete or restart tool (for example `harvest-clients-create`, `harvest-contacts-create`, `harvest-invoices-create`, `harvest-estimates-create`, `harvest-invoices-update`, `harvest-time-entries-create`). Chorus has no write tools here.
* Chorus calls its customers accounts and Harvest calls them clients. The only link is the name, so match on exact name first, then a case-insensitive contains match, and always show which kind of match was used.
* Hourly rates, cost rates and invoice amounts are sensitive: show them only because the user asked for billing context.
* If more than 10 clients are overdue, say how many were not looked up.
**Validation:**
* If no invoices are overdue, say so and stop without calling Chorus.
* Never describe a conversation as a dispute unless its text says so.Who it's for
One answer, three teams that use it
Accounts receivable
Time the reminder well
See whether a late client has recent sales conversations before you write, so the reminder does not cut across a live discussion.
Which Harvest invoices over 30 days overdue have a recent Chorus conversation?
Account owners
Protect the relationship
Know which of your clients are overdue and what was last discussed with them, before finance reaches out.
Show overdue Harvest invoices for my clients and what we last discussed in Chorus.
Credit controllers
Spot a possible stall or dispute
Get the conversation text that suggests a stalled relationship, quoted rather than assumed, for the largest balances.
For invoices overdue by 14 days or more, did any Chorus conversations mention a problem?
How it works
What PopdockAI does when you ask
You set how overdue and how far back to look. Your AI assistant reads invoices in Harvest and conversations in Chorus, linked by client name, and reports. It looks up at most 10 clients and says what it skipped.
Ask
You give a minimum days overdue and a Chorus look-back window.
Find
It lists open Harvest invoices past that mark and totals the amount due per client.
Look up
For up to 10 clients it finds their latest Chorus conversations and emails by name.
Report
You get a table per client and a short list where the text points to a dispute or stall.
What PopdockAI provides
The tools behind the answer
Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.
harvest-get-invoices
chorus-get-engagements
chorus-get-emails
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Chase invoices with the full picture
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
