invoice-health-check
Skill4 starsChanged 7 months agoMITView on GitHub
Use when scoring invoice completeness, billing accuracy, customer clarity, and collection risk before sending an invoice or publishing a shareable invoice review.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- cfo-briefingSkill
- contract-to-invoiceSkill
- dunning-emailsSkill
- finance-close-checklistSkill
- payment-reconciliationSkill
- revenue-recognition-qaSkill
- usage-billing-reviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to review an invoice for correctness, clarity, and collection risk before it goes out.
- Distinctive: line 18
Check required invoice fields: legal entity, customer name, billing contact, invoice number, date, due date, terms, currency, tax details, …
- Distinctive: line 19
Check billing logic: products, quantities, rates, discounts, credits, billing period, proration, taxes, and totals.
- Distinctive: line 20
Check customer clarity: line descriptions, usage details, support contact, and explanatory notes for unusual charges.
- Distinctive: line 21
Check collection risk: overdue history, invoice complexity, missing PO, disputed account, weak contact, and large variance from prior …
- Distinctive: line 36
Do not approve an invoice if contract support is missing for material charges.
- Distinctive: line 37
Do not add tax, legal, or payment language unless source policy supports it.
- Distinctive: line 38
Do not send the invoice.
- Distinctive: line 39
Keep the score explainable and source-backed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Invoice Health Check
Use this skill to review an invoice for correctness, clarity, and collection risk before it goes out.
Inputs
- Invoice draft or export.
- Customer account details, contract or order form, payment terms, billing policy, tax requirements, and prior dispute history.
- Optional benchmark: company invoice checklist or brand tone.
Workflow
- Check required invoice fields: legal entity, customer name, billing contact, invoice number, date, due date, terms, currency, tax details, remittance instructions, and payment link.
- Check billing logic: products, quantities, rates, discounts, credits, billing period, proration, taxes, and totals.
- Check customer clarity: line descriptions, usage details, support contact, and explanatory notes for unusual charges.
- Check collection risk: overdue history, invoice complexity, missing PO, disputed account, weak contact, and large variance from prior invoice.
- Score the invoice from 0-100 and explain the drivers.
Output
Return:
- Invoice health score.
- Pass/fail checklist.
- Material issues and recommended fixes.
- Collection-risk notes.
- Customer-safe explanation for non-obvious charges when requested.
Guardrails
- Do not approve an invoice if contract support is missing for material charges.
- Do not add tax, legal, or payment language unless source policy supports it.
- Do not send the invoice.
- Keep the score explainable and source-backed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

