invoice-math

Classifies overdue invoices into aging buckets and assigns reminder tiers for dunning.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill invoice-math
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoice-math
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/invoice-math
Command: npx skills add https://github.com/kortix-ai/suna --skill invoice-math

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chasing overdue invoices inconsistently leads to over-contacting customers, sending the wrong tone of reminder, or escalating accounts that should go straight to a human. This Skill provides deterministic rules for turning an invoice's age and balance into the correct reminder action.

Core Features & Use Cases

  • Aging Buckets: Classifies invoices by days past due (from due date, not issue date) into five buckets from "Upcoming" to "Delinquent".
  • Reminder Tiers: Maps each bucket to a specific reminder tier, from courtesy notices to final notices, with defined tone and content expectations.
  • Dunning Cadence Controls: Enforces at most one reminder per invoice per run, a 72-hour minimum gap between reminders, and escalation only when an invoice crosses into a new bucket.
  • Stop-for-Human Triggers: Blocks sending and hands off to a person when an invoice exceeds the approval threshold, is disputed, or is marked for collections or legal.
  • Use Case: An agent reviewing a list of open invoices can load this Skill to decide which invoices get a first reminder, which get a final notice, and which must be held for human review, without double-messaging any customer.

Quick Start

Load the invoice-math skill and review my open invoices to decide which reminder each one should receive today.

Frequently Asked Questions about invoice-math

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which payment reminder to send for an overdue invoice?

Measure the invoice's age in days from its due date, then map it to an aging bucket: 1-7 days gets a first reminder, 8-30 days a second reminder, and 31-60 days a final notice. Invoices 61+ days past due are held for a human instead of being contacted.

How often should dunning reminders be sent to the same customer?

Send at most one reminder per invoice per run, and never send two reminders to the same invoice within 72 hours. Check the last-sent log before sending, and only escalate to a firmer tier when the invoice crosses into the next aging bucket.

When should an overdue invoice be escalated to a human instead of automated reminders?

Hold an invoice for human review when it is 61 or more days past due, exceeds the account's approval threshold, is flagged as disputed, or is marked for collections or legal. In these cases no reminder is sent and the invoice is surfaced in the summary.

Should invoice aging be calculated from the due date or the issue date?

Aging is measured from the invoice due date, not the issue date. The buckets even include an "Upcoming" range of -7 to 0 days, which triggers a courtesy notice before payment is due.

What happens when an invoice is paid during a dunning sequence?

Once an invoice is paid, all reminders stop immediately. The payment is noted in the run summary so no further reminders are scheduled for that invoice.