Invoice & Vendor Follow-up
Finds the invoice threads that stopped, with age and amount, and drafts the nudge.
Inputs
- Mailbox, through Email
references/config.md for the ageing buckets, the chase ladder and who is never chased
Procedure
- Find invoice threads over the window: invoices sent or received, payment queries, disputes,
remittance advice.
- Determine the state of each thread from the last message only: awaiting their reply,
awaiting ours, resolved, or ambiguous. Ambiguous is a valid answer and must not be guessed.
- Age from the last message in the thread, not from the invoice date, and bucket by config.
- Extract counterparty, invoice reference, amount as written, direction (we owe / they owe),
last contact date, who spoke last, and the source link.
- Rank by age within direction. Money we owe sits above money owed to us, because a missed
payable costs a relationship and a late receivable costs interest.
- Draft one follow-up per counterparty, at the ladder step matching the age bucket.
Output
| Counterparty | Ref | Amount | Direction | Last contact | Age | Waiting on | Ladder step | Source |
Then: totals by direction and bucket, threads marked ambiguous and why, drafts prepared.
Definition of done
Every open thread is aged and attributed to a side, ambiguous ones are named rather than forced,
and every counterparty due a chase has one draft.
Nothing outstanding is a good week. Say it in one line.
When there is no data
- No invoice threads in the window: say so, state the window, stop.
- A thread with no amount anywhere: list it with amount UNKNOWN rather than dropping it.
- A thread where the last message is an automated receipt: treat as awaiting their reply and say
the attribution came from an automated message.
Boundaries
- Draft, never send. Especially never send a chase to a counterparty on the config exclusion
list, which exists for relationships being handled by a person.
- Never state an amount as owed. The ledger is the source of truth.
- Never escalate a ladder step on your own. The user chooses the step.
- Never contact anyone outside the organization without approval.
Self-check
- Is every age measured from the last message, not the invoice date?
- Is every ambiguous thread labelled rather than guessed?
- Did I keep exclusions out entirely?
1---2name: invoice-vendor-followup3description: Finds invoice and payment threads in the mailbox that have gone unanswered, ages them, and drafts the follow-up to each counterparty. Use when the user asks what invoices are outstanding, which vendors have not replied, to chase payment or payment queries, or to prepare the aged follow-up list before a finance review.4metadata:5 source: https://skillmd.com/skills/kesslernity/invoice-vendor-followup6---78# Invoice & Vendor Follow-up910Finds the invoice threads that stopped, with age and amount, and drafts the nudge.1112## Inputs13- Mailbox, through **Email**14- `references/config.md` for the ageing buckets, the chase ladder and who is never chased1516## Procedure171. **Find invoice threads** over the window: invoices sent or received, payment queries, disputes,18 remittance advice.192. **Determine the state of each thread** from the last message only: awaiting their reply,20 awaiting ours, resolved, or ambiguous. Ambiguous is a valid answer and must not be guessed.213. **Age** from the last message in the thread, not from the invoice date, and bucket by config.224. **Extract** counterparty, invoice reference, amount as written, direction (we owe / they owe),23 last contact date, who spoke last, and the source link.245. **Rank** by age within direction. Money we owe sits above money owed to us, because a missed25 payable costs a relationship and a late receivable costs interest.266. **Draft one follow-up per counterparty**, at the ladder step matching the age bucket.2728## Output29| Counterparty | Ref | Amount | Direction | Last contact | Age | Waiting on | Ladder step | Source |3031Then: totals by direction and bucket, threads marked ambiguous and why, drafts prepared.3233## Definition of done34Every open thread is aged and attributed to a side, ambiguous ones are named rather than forced,35and every counterparty due a chase has one draft.3637**Nothing outstanding is a good week.** Say it in one line.3839## When there is no data40- No invoice threads in the window: say so, state the window, stop.41- A thread with no amount anywhere: list it with amount UNKNOWN rather than dropping it.42- A thread where the last message is an automated receipt: treat as awaiting their reply and say43 the attribution came from an automated message.4445## Boundaries46- **Draft, never send.** Especially never send a chase to a counterparty on the config exclusion47 list, which exists for relationships being handled by a person.48- Never state an amount as owed. The ledger is the source of truth.49- Never escalate a ladder step on your own. The user chooses the step.50- Never contact anyone outside the organization without approval.5152## Self-check53- Is every age measured from the last message, not the invoice date?54- Is every ambiguous thread labelled rather than guessed?55- Did I keep exclusions out entirely?