contract-to-invoice
Skill4 starsChanged 7 months agoMITView on GitHub
Use when extracting billing obligations from contracts, order forms, SOWs, pricing tables, or amendments and comparing them against draft or issued invoices.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- cfo-briefingSkill
- dunning-emailsSkill
- finance-close-checklistSkill
- invoice-health-checkSkill
- payment-reconciliationSkill
- revenue-recognition-qaSkill
- usage-billing-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 compare what a customer contract says should be billed against what an invoice shows.
- Distinctive: line 45
Do not interpret ambiguous legal terms as final.
- Distinctive: line 46
Do not approve an invoice for sending when material terms are missing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Contract To Invoice
Use this skill to compare what a customer contract says should be billed against what an invoice shows.
Inputs
- Contract, order form, SOW, amendment, or pricing excerpt.
- Invoice draft or issued invoice.
- Billing period, subscription start and end dates, renewal terms, usage terms, and discounts.
- Any billing policy for proration, taxes, credits, or minimums.
Workflow
- Extract billing terms: customer, product, quantity, price, discount, term, billing frequency, start date, end date, minimums, overages, taxes, payment terms, and special conditions.
- Compare extracted terms to invoice lines.
- Recalculate invoice expectations where enough data exists.
- Classify exceptions:
- Missing line.
- Extra line.
- Incorrect quantity.
- Incorrect rate.
- Incorrect billing period.
- Missing discount or credit.
- Tax or payment-term mismatch.
- Ambiguous contract language.
- Identify whether each exception is customer-facing, accounting-only, or requires legal or sales review.
Output
Return:
- Contract billing summary.
- Invoice comparison table with expected value, invoice value, variance, source reference, and confidence.
- Exception list with severity and owner.
- Questions for sales, legal, billing, or the customer.
Guardrails
- Quote short source snippets only when needed and keep them minimal.
- Do not interpret ambiguous legal terms as final. Escalate ambiguity.
- Do not approve an invoice for sending when material terms are missing.
- Preserve source references so reviewers can verify every variance.
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.