---
id: daily-finance-billing-ops
name: "finance-billing-ops"
url: https://skills.yangsir.net/skill/daily-finance-billing-ops
author: affaan-m
domain: finance
tags: ["finance", "billing", "pricing", "audit", "revenue-operations"]
install_count: 2600
rating: 4.40 (3 reviews)
github: https://github.com/affaan-m/everything-claude-code
---

# finance-billing-ops

> 财务账单操作，验证产品定价、退款政策、团队席位逻辑是否与官网和销售文案一致，发现计费漏洞

**Stats**: 2,600 installs · 4.4/5 (3 reviews)

## Before / After 对比

### 计费验证

**Before**:

手动测试不同场景的计费逻辑，对比官网承诺，发现一个计费 Bug 需要数天的测试和分析

**After**:

自动验证所有计费路径，对比承诺与实际行为，快速识别定价漏洞和逻辑不一致

| Metric | Before | After | Change |
|---|---|---|---|
| 验证时间 | 3天 | 0.5天 | -83% |

## Readme

# finance-billing-ops

# Finance Billing Ops

Use this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.

This is broader than `customer-billing-ops`. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.

## Skill Stack

Pull these ECC-native skills into the workflow when relevant:

- `customer-billing-ops` for customer-specific remediation and follow-up

- `research-ops` when competitor pricing or current market evidence matters

- `market-research` when the answer should end in a pricing recommendation

- `github-ops` when the billing truth depends on code, backlog, or release state in sibling repos

- `verification-loop` when the answer depends on proving checkout, seat handling, or entitlement behavior

## When to Use

- user asks for Stripe sales, refunds, MRR, or recent customer activity

- user asks whether team billing, per-seat billing, or quota stacking is real in code

- user wants competitor pricing comparisons or pricing-model benchmarks

- the question mixes revenue facts with product implementation truth

## Guardrails

- distinguish live data from saved snapshots

- separate:

revenue fact

- customer impact

- code-backed product truth

- recommendation

- do not say "per seat" unless the actual entitlement path enforces it

- do not assume duplicate subscriptions imply duplicate value

## Workflow

### 1. Start from the freshest billing evidence

Prefer live billing data. If the data is not live, state the snapshot timestamp explicitly.

Normalize the picture:

- paid sales

- active subscriptions

- failed or incomplete checkouts

- refunds

- disputes

- duplicate subscriptions

### 2. Separate customer incidents from product truth

If the question is customer-specific, classify first:

- duplicate checkout

- real team intent

- broken self-serve controls

- unmet product value

- failed payment or incomplete setup

Then separate that from the broader product question:

- does team billing really exist?

- are seats actually counted?

- does checkout quantity change entitlement?

- does the site overstate current behavior?

### 3. Inspect code-backed billing behavior

If the answer depends on implementation truth, inspect the code path:

- checkout

- pricing page

- entitlement calculation

- seat or quota handling

- installation vs user usage logic

- billing portal or self-serve management support

### 4. End with a decision and product gap

Report:

- sales snapshot

- issue diagnosis

- product truth

- recommended operator action

- product or backlog gap

## Output Format

```
SNAPSHOT
- timestamp
- revenue / subscriptions / anomalies

CUSTOMER IMPACT
- who is affected
- what happened

PRODUCT TRUTH
- what the code actually does
- what the website or sales copy claims

DECISION
- refund / preserve / convert / no-op

PRODUCT GAP
- exact follow-up item to build or fix

```

## Pitfalls

- do not conflate failed attempts with net revenue

- do not infer team billing from marketing language alone

- do not compare competitor pricing from memory when current evidence is available

- do not jump from diagnosis straight to refund without classifying the issue

## Verification

- the answer includes a live-data statement or snapshot timestamp

- product-truth claims are code-backed

- customer-impact and broader pricing/product conclusions are separated cleanly

Weekly Installs531Repository[affaan-m/everyt…ude-code](https://github.com/affaan-m/everything-claude-code)GitHub Stars157.6KFirst Seen11 days agoSecurity Audits[Gen Agent Trust HubPass](/affaan-m/everything-claude-code/finance-billing-ops/security/agent-trust-hub)[SocketPass](/affaan-m/everything-claude-code/finance-billing-ops/security/socket)[SnykWarn](/affaan-m/everything-claude-code/finance-billing-ops/security/snyk)Installed oncodex501opencode485gemini-cli482kimi-cli481cursor481antigravity481

---
*Source: https://skills.yangsir.net/skill/daily-finance-billing-ops*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-finance-billing-ops/markdown*