revenue-recognition-analyzer
ASC 606 five-step model implementation skill for revenue recognition analysis and documentation
What this skill does
# Revenue Recognition Analyzer ## Overview The Revenue Recognition Analyzer skill implements the ASC 606 five-step revenue recognition model. It provides systematic analysis of contracts with customers to determine appropriate revenue recognition timing and amounts. ## Capabilities ### Contract Identification (Step 1) - Contract existence verification - Collectability assessment - Commercial substance evaluation - Contract combination analysis - Contract modification handling - Portfolio approach application ### Performance Obligation Analysis (Step 2) - Distinct good/service identification - Series guidance application - Promise evaluation - Immaterial promise assessment - Shipping and handling evaluation - Warranty classification ### Transaction Price Determination (Step 3) - Fixed consideration identification - Variable consideration estimation - Constraint application - Significant financing component - Noncash consideration valuation - Consideration payable to customer ### Allocation Calculation (Step 4) - Standalone selling price determination - Observable price usage - Estimation approaches (adjusted market, expected cost plus margin, residual) - Discount allocation - Variable consideration allocation - Change in transaction price handling ### Revenue Timing Assessment (Step 5) - Point in time recognition criteria - Over time recognition criteria - Output method application - Input method application - Progress measurement - Completion determination ### Variable Consideration Estimation - Expected value method - Most likely amount method - Constraint assessment - Update requirements - Reversal risk evaluation - Historical data analysis ## Usage ### New Contract Analysis ``` Input: Contract terms, deliverables, pricing structure Process: Apply five-step model systematically Output: Revenue recognition conclusion, journal entries, documentation ``` ### Contract Modification ``` Input: Original contract, modification terms, cumulative revenue Process: Evaluate modification accounting treatment Output: Prospective or cumulative catch-up adjustment calculation ``` ## Integration ### Used By Processes - Revenue Recognition and ASC 606 Compliance - Financial Statement Preparation - External Audit Coordination ### Tools and Libraries - Contract analysis tools - Revenue recognition templates - ERP revenue modules ## Best Practices 1. Document each step of the five-step model 2. Maintain contract population inventory 3. Develop revenue recognition policies by transaction type 4. Build standalone selling price database 5. Create decision trees for common scenarios 6. Establish review procedures for non-standard terms
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.