# Revenue Recognition rules

Customize rules to handle revenue treatments to your business.

Configure [Revenue Recognition rules](https://dashboard.stripe.com/revenue-recognition/rules) to define revenue treatments specific to your business.

Stripe Revenue Recognition allows you to configure custom rules to handle revenue treatments specific to your business needs. For example, you can configure a rule to:

- __Categorize__ an *invoice* line item as a tax or fee
- __Book__ a transaction amount or invoice line item as a passthrough fee
- __Exclude__ transactions from specific customers or test invoices
- __Amortize__ revenue over a specified time period relative to payment or invoice finalization date
- __Recognize__ revenue after a specific time period to model a future *fulfillment* schedule
- __Allocate__ multiple revenue treatments to a single transaction amount

Rules are typically applied to reports within 24 hours. Rules that have successfully been applied in the latest report have an `active` status. Rules that haven’t remain in a `processing` status.

## Default rules

Stripe Revenue Recognition provides a set of default rules to model the [methodology](https://docs.stripe.com/revenue-recognition/methodology.md) for handling common Stripe resources.

- For invoice line items with service periods, the line item amount amortizes evenly over its service period. If a period isn’t set on an invoice line item, the amount is recognized entirely when the invoice finalizes.
- Other payments not made through an invoice are recognized immediately upon payment if no service period or fulfillment information exists, or by the [imported](https://docs.stripe.com/revenue-recognition/data-import.md) service period or fulfillment data.

![Default rules](images/billing/revenue-recognition/default-rules.png)

## Custom rules

Custom rules override Stripe’s default revenue treatment behaviors where applicable and you can add or modify them on the Stripe Dashboard.

You can apply rules to:

- *Products*
- *Customers*
- [Invoice line items](https://docs.stripe.com/api/invoices/line_item.md)
- [Other payments](https://docs.stripe.com/api/charges.md) (that is, payments that aren’t associated with invoices)

See how to [create a rule and define revenue treatments](https://docs.stripe.com/revenue-recognition/rules/create-a-rule.md). You can also explore sample rules on tax treatment, pass-through fees, exclusion, and custom time periods.

## Rule ordering and hierarchy

Each transaction can only have one rule applied to it when processing revenue reports. In situations where a single transaction fits the “Apply-to” criteria for multiple rules, rule hierarchy determines which rule to apply to the transaction. The higher a rule is ranked on the list, the higher the priority it’s assigned.

You can rearrange the order of the rules by clicking **Change rule order** as shown below:

![Rules](images/billing/revenue-recognition/rules.png)

After clicking **Change rule order**, you can reorder the rules to adjust their priorities.

![Rule order](images/billing/revenue-recognition/rule-order.png)

## Best practices for effectively maintaining your rules

As your business grows, it’s important to make sure you regularly maintain your rules to ensure the accuracy of your revenue reports. The following are some best practices to keep rules correct for your Revenue Recognition reports.

__Know when to create a rule__

When applied correctly, Stripe’s default rules and revenue treatment methodology for handling *subscription* events accurately recognize and defer revenue for businesses who require more control over their unique use.

__Regularly monitor rules to ensure they’re up-to-date__

Billing models, customer types and edge cases can regularly change, and you should evolve your rules accordingly. To make sure that revenue treatments remain predictable, periodically check your rules so they’re up-to-date in terms of hierarchy and effective period.

__Check if your accounting period is open or closed when new rules are applied__

If the effective period for a new rule overlaps with a closed accounting period, it generates corrections if the rules are retroactively applied to transactions from past (closed) accounting periods. If you want to avoid this, reopen your books by opening your accounting period prior to adding the rule.

## See Also

* [Create a rule](https://docs.stripe.com/revenue-recognition/rules/create-a-rule.md)
* [Examples](https://docs.stripe.com/revenue-recognition/rules/examples.md)