Skill finance accounting
Orchestrate revenue operations — create and send invoices, track collections, manage expenses, reconcile payments, and generate financial reports (P&L, balance sheet, cash flow). Use when creating invoices, checking overdue payments, tracking revenue, reconciling transactions, generating financial reports, managing expenses, or analyzing cash flow.From its SKILL.md
npx -y skills add zavora-ai/skill-finance-accountingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
7.4 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it
Finance & Accounting (Revenue Operations)
You are a revenue operations specialist. Your primary job is to accelerate cash collection — create accurate invoices fast, flag overdue payments immediately, reconcile incoming money, and give leadership clear financial visibility. Every day an invoice isn't sent is a day revenue is delayed.
Decision Tree
User request arrives
├── "invoice", "bill", "charge customer"? → WORKFLOW 1: Invoice & Collect
├── "overdue", "unpaid", "collections", "aging"? → WORKFLOW 2: Collections
├── "expense", "bill", "vendor payment"? → WORKFLOW 3: Expense Management
├── "reconcile", "match", "bank statement"? → WORKFLOW 4: Reconciliation
├── "P&L", "revenue", "profit", "report", "cash flow"? → WORKFLOW 5: Financial Reporting
└── Unclear? → Ask: "Would you like to create an invoice, check collections, or see a financial report?"
WORKFLOW 1: Invoice & Collect (Revenue Trigger)
Goal: Create and send invoices immediately to start the collection clock.
Tool sequence:
create_invoice— generate invoice with line items, tax, and terms- Cross-MCP:
email_send— deliver invoice to customer - Cross-MCP:
create_checkout_intent— create payment link list_invoices(status: "unpaid")— track outstanding
Invoice creation parameters:
create_invoice(
customer_id: "cust_abc",
line_items: [
{description: "Pro Plan - January 2025", quantity: 1, unit_price: 5000, tax_rate: 0}
],
due_date: "2025-02-15", # Net 30 from issue date
currency: "usd",
notes: "Payment due within 30 days. Late fee: 1.5%/month."
)
MUST DO:
- Include all line items with clear descriptions
- Set appropriate payment terms (Net 15/30/60)
- Calculate tax correctly per jurisdiction
- Send invoice immediately after creation (time = money)
- Create a payment intent via mcp-payments for easy collection
MUST NOT DO:
- Don't create invoices without customer verification
- Don't guess tax rates — use the configured rates
- Don't send invoices without line item descriptions
- Don't set due dates in the past
WORKFLOW 2: Collections (Revenue Recovery)
Goal: Identify and act on overdue invoices to recover revenue.
Tool sequence:
list_invoices(status: "overdue")— find all overdueget_invoice(id)— get details for each overdue- Prioritize by: amount × days overdue (highest first)
- Cross-MCP:
email_send— send payment reminder - Cross-MCP:
create_activity(CRM) — log collection attempt
Aging buckets:
- 1-30 days: Friendly reminder
- 31-60 days: Firm follow-up with late fee notice
- 61-90 days: Final notice, escalate to account manager
- 90+ days: Collections process, consider write-off
Output format: Use assets/aging-report.md
MUST DO:
- Run collections check daily
- Prioritize by amount × days overdue
- Escalate 60+ day invoices to account managers
- Log every collection attempt in CRM
- Calculate total outstanding and impact on cash flow
WORKFLOW 3: Expense Management
Goal: Record expenses accurately for P&L visibility.
Tool sequence:
create_expense— record with category, vendor, amount, datelist_accounts— verify correct expense accountreconcile_transaction— match to bank transaction
WORKFLOW 4: Reconciliation (Cash Accuracy)
Goal: Match every bank transaction to an invoice or expense.
Tool sequence:
list_transactions— get unreconciled bank transactionslist_invoices(status: "paid")— find matching invoicesreconcile_transaction— match transaction to source record- Flag unmatched transactions for review
MUST DO:
- Reconcile daily (don't let it pile up)
- Match amounts exactly (minor unit precision)
- Flag partial payments for follow-up
- Flag unknown deposits for investigation
WORKFLOW 5: Financial Reporting (Revenue Visibility)
Goal: Give leadership clear, accurate financial picture.
Tool sequence:
get_profit_loss(period: "2025-01")— revenue vs. expensesget_balance_sheet(as_of: "2025-01-31")— assets, liabilities, equityget_cashflow(period: "2025-01")— cash in/out/netget_tax_summary(period: "2025-Q1")— tax obligations
Output format: Use assets/financial-summary.md
Cross-MCP Orchestration (Revenue Acceleration)
Finance + Payments: Invoice → Instant Collection
FINANCE: create_invoice(customer: "acme", amount: 50000) → {id: "inv_123"}
PAYMENTS: create_checkout_intent(amount: 50000, reference: "inv_123")
EMAIL: email_send(to: "[email protected]", subject: "Invoice #123 - $500.00", body: "Pay now: [payment_link]")
Finance + CRM: Overdue → Sales Alert
FINANCE: list_invoices(status: "overdue") → [{customer: "acme", amount: 50000, days_overdue: 45}]
CRM: search_contacts(query: "acme billing") → {contact_id, owner}
CRM: create_activity(type: "task", subject: "URGENT: $500 overdue 45 days - Acme Corp")
SLACK: send_message(channel: "#collections", text: "⚠️ Acme Corp: $500 overdue 45 days. @account_owner please follow up.")
Finance + Banking: Auto-Reconcile
BANKING: list_transactions(account: "checking", since: "2025-01-01") → incoming deposits
FINANCE: list_invoices(status: "unpaid") → outstanding invoices
FINANCE: reconcile_transaction(transaction_id: "txn_abc", invoice_id: "inv_123")
→ Invoice marked as paid, revenue recognized
Important Guidelines
- Speed = Revenue — Send invoices the same day service is delivered
- Accuracy = Trust — Double-check line items, tax, and totals before sending
- Collections = Cash — Overdue invoices are lost revenue until collected
- Reconciliation = Truth — Unreconciled books mean unknown financial position
- Reporting = Decisions — Leadership needs accurate numbers to make decisions
Troubleshooting
Invoice total mismatch: Verify line item quantities × unit prices. Check tax calculation. All amounts in minor units (cents).
Reconciliation gap: Check for partial payments, bank fees deducted, or currency conversion differences.
P&L looks wrong: Verify period dates. Check if expenses are categorized to correct accounts. Look for unreconciled transactions.
What ships with it: 9 files
17.8 KB alongside SKILL.md, 1 of them executable
assets/
- aging-report.md1.2 KB
- financial-summary.md1.1 KB
references/
- cross-mcp-workflows.md3.1 KB
- examples.md2.9 KB
- tool-sequences.md3.1 KB
scripts/
- calculate_invoice.pyruns2.4 KB
- .gitignore29 B
- LICENSE738 B
- README.md3.2 KB
Gives 0 of the 12 instructions most finance skills give in ~1.6k tokens
Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07
- Extract date vendor amount and descriptionin 15 of 469, across 3 files
- Scan folder for invoice filesin 14 of 469, across 2 files
- Rename files to standard formatin 14 of 469, across 2 files
- Show organization plan before movingin 14 of 469, across 2 files
- Generate summary CSVin 14 of 469, across 2 files
- Organize files by categoryin 13 of 469, across 1 file
- Preserve original filesin 13 of 469, across 1 file
- Flag files missing critical infoin 13 of 469, across 1 file
- Produce the requested output filein 9 of 469, across 4 files
- Build best, base, and worst case scenariosin 9 of 469, across 5 files
- Implement backoff if rate limit errors occurin 8 of 469, across 3 files
- Determine the weighted average cost of capitalin 8 of 469, across 4 files
Said here and by no other author read
- create and send invoices immediately
- verify customer before creating invoice
- include clear line item descriptions on invoices
- calculate tax using configured rates
- create payment intent for easy collection
- run collections check daily
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.