Automate Revenue Recognition Compliance

This skill models revenue recognition under ASC 606/IFRS 15, covering financial system implementation and automated compliance. It structures every scenario around the mandatory five-step model: identify the contract, identify distinct performance obligations, determine the transaction price, allocate that price across obligations using standalone selling prices, and recognize revenue as each obligation is satisfied. A performance-obligation class determines whether each obligation should be recognized at a point in time or over time, based on whether the customer simultaneously receives the benefit, whether the work creates or enhances an asset the customer controls, or whether the asset has no alternative use with a right to payment.

Transaction-price determination covers variable consideration (an expected-value calculation weighting bonus and penalty components by their probability, with a constraint that excludes the variable amount entirely when confidence falls below a threshold, to prevent future revenue reversal) and contract modification handling (classifying a modification as a separate contract, a termination-and-recreation, or a cumulative catch-up, based on whether the added goods are distinct and priced at standalone selling price). An industry-specific software/SaaS model allocates a single contract value across license, support, and implementation components by their standalone selling prices, then recognizes each on its own schedule - license at delivery, support ratably over the contract term, implementation by percentage of completion.

Automated compliance validation is provided as SQL control queries: checking every active contract has performance obligations mapped, flagging revenue recognized against unsatisfied obligations, and validating that allocated transaction price sums to the full contract value. The monthly close process runs six steps - contract review, performance obligation assessment, variable consideration reassessment, automated revenue calculation, exception review, and management review - tracked against KPIs like contract liability ratio, revenue recognition rate, modification frequency, and days from contract to revenue.

def calculate_expected_value(self):
    """Expected value method for variable consideration"""
    expected_variable = 0
    
    for component in self.variable_components:
        if component['type'] == 'bonus':
            expected_variable += component['amount'] * component['probability']
        elif component['type'] == 'penalty':
            expected_variable -= component['amount'] * component['probability']
            
    return self.base_price + expected_variable

Use this skill when the transaction price isn't fixed or the contract isn't a clean one-time sale - variable consideration with bonuses or penalties, a modification mid-contract, or a bundled SaaS deal spanning license, support, and implementation each recognized on a different schedule.

It is not a fit for general financial modeling or accounting outside revenue recognition specifically - it's scoped to the five-step model and its industry-specific applications, not to broader GAAP or IFRS compliance.

Inputs are contract terms, performance obligations, pricing components (fixed and variable), and any modifications. Outputs are a five-step revenue recognition model with satisfaction-method classification, variable-consideration calculations with constraint applied, a modification-type classification, an allocated revenue-recognition schedule, and SQL compliance-validation queries.

Revenue accounting and finance-systems teams implementing ASC 606/IFRS 15 who need concrete, working models rather than starting from the standard's text alone - performance-obligation satisfaction logic, variable-consideration constraint handling, contract-modification classification, and SaaS-specific allocation - plus five named implementation pitfalls to avoid: bundling errors, premature revenue timing, unconstrained variable consideration, misclassified modifications, and poor CRM-billing-accounting system integration. Data-model guidance also calls for maintaining audit trails for every contract modification and revenue adjustment, version-controlling contracts to track changes over time, and building a standardized standalone-selling-price library by product or service rather than re-deriving SSP on each new deal.