usage-billing-review
Skill4 starsChanged 7 months agoMITView on GitHub
Use when reviewing metered usage invoices against usage exports, pricing rules, minimum commitments, credits, customer entitlements, and billing exceptions.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- cfo-briefingSkill
- contract-to-invoiceSkill
- dunning-emailsSkill
- finance-close-checklistSkill
- invoice-health-checkSkill
- payment-reconciliationSkill
- revenue-recognition-qaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 validate usage-based billing before an invoice goes to the customer.
- Distinctive: line 36
Do not assume internal, test, or failed usage is billable unless source policy says so.
- Distinctive: line 37
Do not smooth or alter usage data without preserving the original source values.
- Distinctive: line 38
Do not approve billing for unknown meters or unmapped customer IDs.
≈ “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
Usage Billing Review
Use this skill to validate usage-based billing before an invoice goes to the customer.
Inputs
- Usage export with customer ID, meter name, period, quantity, unit, and source timestamp.
- Pricing terms, rate cards, tiers, included units, minimum commitments, and overage rules.
- Draft invoice lines.
- Known exceptions such as test accounts, internal usage, credits, outages, or contract overrides.
Workflow
- Confirm the billing period and customer identifiers match across usage, contract, and invoice data.
- Aggregate usage by billable meter and compare it with the invoice.
- Apply pricing rules in this order: included usage, credits, tiering, minimums, overages, discounts, and taxes if provided.
- Flag usage anomalies: sudden spikes, negative usage, duplicate records, missing days, unknown meters, and units that do not match the contract.
- Classify variances by customer impact and materiality.
Output
Return:
- Billing readiness summary: ready, ready with minor cleanup, blocked, or requires approval.
- Meter comparison table with usage quantity, billed quantity, expected charge, invoice charge, variance, and evidence.
- Exception queue with owner and recommended resolution.
- Customer-safe explanation for material usage variance when requested.
Guardrails
- Do not assume internal, test, or failed usage is billable unless source policy says so.
- Do not smooth or alter usage data without preserving the original source values.
- Do not approve billing for unknown meters or unmapped customer IDs.
- Escalate material variances before invoice release.
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.