Revenue Recognition logo

Revenue Recognition

CommunityPopular
cbrock84
revenue-recognition

Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.

Overview

Publishercbrock84
Repositoryheadcount
Skill namerevenue-recognition
Stars
1.6K
Forks
237
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cbrock84 on GitHub. Read the source before you install it.

Installation

Install the Revenue Recognition AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cbrock84/headcount.git /tmp/headcount
mkdir -p .claude/skills
cp -r /tmp/headcount/plugins/finance/skills/revenue-recognition .claude/skills/revenue-recognition
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Revenue Recognition in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Revenue Recognition on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Revenue Recognition is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Revenue recognition

Cash received is not revenue earned. The gap between them is where deals get restructured after signature and where quarters get restated.

This structures the question and tells you what to ask. Revenue recognition is a technical accounting matter under standards such as ASC 606 and IFRS 15 — conclusions on a material or unusual contract need your auditors or a qualified accountant, not a checklist.

The shape of the question

Recognition follows the transfer of control to the customer, worked through in five steps: identify the contract, identify the distinct performance obligations, determine the transaction price, allocate it across the obligations, then recognize as each is satisfied.

Most disputes happen at step two and step four. What sales sold as one thing is frequently several obligations for accounting purposes — software plus implementation plus support — and the price has to be allocated across them on standalone selling price, not on how the quote was written.

Terms that change the answer

These belong in a pre-signature review, because after signature the only remedy is an amendment the customer has no reason to agree to:

  • Acceptance clauses — a customer right to reject can defer recognition until acceptance.
  • Termination for convenience — a short-notice exit can shorten the contract term for accounting purposes, however long the stated term is.
  • Contingent or milestone fees — variable consideration, constrained until it is probable there will be no significant reversal.
  • Material rights — a renewal or upgrade priced below standalone value can itself be a performance obligation carved out of today's price.
  • Extended payment terms — payment far from delivery can introduce a financing component.
  • Side letters. Any promise made outside the contract is still part of the contract. They are the single most common cause of restatement, and by construction finance does not know they exist.

Working with sales

Recognition treatment is a deal input, not a post-signature discovery. A concession that costs nothing commercially can move revenue across a period boundary, and by the time finance sees the signed paper the trade has already been made.

Give revenue:chief-revenue-officer and revenue:pricing-and-packaging a small set of standard structures that recognize cleanly, and route anything outside them through review before signature — alongside legal-risk:contract-review, which owns the legal exposure the same clauses create.

Deferred revenue is an obligation

The deferred balance is work owed, not money banked. Track it by cohort and obligation so you can answer what it is composed of and when it releases. A balance nobody can decompose is one that surprises you.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Subledgers that carry recognition schedules: NetSuite Advanced Revenue Management, Zuora Revenue, Maxio, Chargebee, Stripe Revenue Recognition, and similar.

Spreadsheet schedules hold up until contracts carry multiple performance obligations or take mid-term modifications. That is the point to move, not a revenue threshold.

Never

  • Recognize on invoice date or cash receipt as a shortcut.
  • Allocate price across obligations the way the quote happened to be laid out.
  • Let a side letter exist.
  • Conclude a material or novel contract's treatment without your auditors.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Revenue Recognition AI skill do?

Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.

Why use Revenue Recognition on TypingMind?

Because you install it once and use it with any model. Revenue Recognition is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Revenue Recognition in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cbrock84/headcount/tree/main/plugins/finance/skills/revenue-recognition. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Revenue Recognition?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Revenue Recognition?

As many as you like. As long as a model supports skills, you can use Revenue Recognition with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Revenue Recognition AI skill free?

Yes. It is published on GitHub by cbrock84 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇