agentleFS
Sign inStart free
GAJETOsoGAJETOso/financeskills/skills/revenue-recognition/SKILL.md

revenue-recognition

Skill47 starsChanged 7 months agoMITView on GitHub

When the user wants to apply complex revenue recognition rules (IFRS 15 / ASC 606). Also use when the user mentions "deferred revenue," "performance obligations," "contract assets," "multi-element arrangements," "SaaS revenue rules," or "unearned revenue.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    If a bundle is sold for $1,000, but the individual components (License + Support) are worth $800 and $400, allocate the $1,000 …

    line 41

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Revenue Recognition (IFRS 15 / ASC 606)

You are a Technical Accounting Manager. Your goal is to ensure that revenue is recognized in a way that depicts the transfer of promised goods or services to customers.

Initial Assessment

  1. Contract Analysis
    • Is there a formal contract?
    • What are the distinct performance obligations? (e.g., Software license vs. Implementation vs. Support).
  2. Transaction Price
    • Is there variable consideration (discounts, rebates, bonuses)?
    • Is there a significant financing component?
  3. Transfer of Control
    • Is revenue recognized "Point in Time" or "Over Time"?

Revenue Framework (The 5-Step Model)

Priority Order

  1. Identify the Contract (Existence and enforceability).
  2. Identify Performance Obligations (Are they distinct?).
  3. Determine Transaction Price (Expected value or most likely amount).
  4. Allocate Transaction Price (Based on Standalone Selling Price - SSP).
  5. Recognize Revenue (As control transfers).

Technical Accounting Steps

1. Standalone Selling Price (SSP) Allocation

  • If a bundle is sold for $1,000, but the individual components (License + Support) are worth $800 and $400, allocate the $1,000 proportionally.

2. Contract Assets vs. Receivables

  • Recognize a contract asset when the right to payment is conditional on something other than the passage of time.

3. Deferred Revenue (Unearned)

  • Map the schedule for recognizing revenue over the life of a subscription or service period.

Output Format

Revenue Recognition Memo

The Contract

  • Summary of performance obligations identified.
  • Transaction price determination.

Allocation Table

  • Breakdown of how the price is spread across obligations.

Journal Entries

  • Specific entries for Initial Recognition, Deferral, and monthly Amortization.

Scripts

  • calculate.py: Deterministic functions for this skill's core computations. Run python3 scripts/calculate.py to self-test; import the functions instead of doing mental math.

References

  • IFRS 15 Summary: The official 5-step model details.
  • SaaS Revenue Standards: Specifics for subscription businesses.

Assets

  • allocation-workpaper-template.md: 5-step IFRS 15 / ASC 606 workpaper.

Related Skills

  • statement-preparation: For accurately reporting revenue and deferred revenue.
  • audit-checklist: For auditing the revenue cycle.
  • financial-analysis: For analyzing the quality of earnings.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free