mcpField
R
revenue-recognition-policy-review

revenue-recognition-policy-review

github.com/sylphxaiOther137 installsUpdated today
Repository

About revenue-recognition-policy-review

A skill for converting revenue recognition, pricing, billing, and contract-change questions into review plans with owners, controls, and approval gates. It is intended for teams coordinating finance, accounting, and product operations.

Key features

  1. 01Identify contracts and performance obligations
  2. 02Classify revenue-related changes
  3. 03Define recognition triggers and evidence
  4. 04Create control checklists and launch gates

Use cases

  1. 01Assess recognition effects of upgrades or downgrades
  2. 02Review prepaid credits, refunds, or cancellations
  3. 03Plan finance review and reconciliation for contract changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill revenue-recognition-policy-review

After installing, type/revenue-recognition-policy-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/revenue-recognition-policy-patterns.md

Details

From the project README

Revenue Recognition Policy Review

Use this skill to convert revenue recognition, pricing, billing, contract modification, deferred revenue, and finance handoff questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify product motion, contract type, performance obligations, pricing model, billing cadence, delivery/activation event, refund/credit terms, modification path, and finance owner.
  2. Read references/revenue-recognition-policy-patterns.md.
  3. Classify the change as new sale, renewal, upgrade, downgrade, usage overage, prepaid credit, implementation service, refund, cancellation, bundle, marketplace transaction, or contract modification.
  4. Define recognition trigger, evidence source, accounting review, billing/revenue reconciliation, customer communication, exception approval, and control owner.
  5. Produce recognition-impact review, state machine, decision table, event schema, control checklist, and launch gate.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not treat invoice date, cash receipt, entitlement grant, and revenue recognition as automatically equivalent.
  • Do not launch new pricing, credits, bundles, or contract changes without finance/accounting review.
  • Do not hide refunds, concessions, side letters, usage corrections, or implementation obligations from revenue controls.
  • Do not present accounting conclusions as legal/accounting advice; route final policy to qualified owners.

Output format

Revenue context:
Audience / source of truth / risk boundary:

Recognition policy plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Controls, exceptions, and finance handoffs:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported