When a product is earned over time, such as a membership term, multi-day event, or multi-year package, recognizing all revenue on the sale date would overstate earnings. Revenue recognition schedules prevent that by releasing the product’s revenue over time, based on a schedule Rhythm builds when the sale posts.
Recognition follows that schedule and each fiscal period’s close, not whether the invoice is paid or when payment arrives. For example, when a payment comes in for a membership that uses deferred revenue, Rhythm debits cash and credits deferred revenue right away. As each fiscal period closes, the schedule moves the scheduled amount from deferred revenue into recognized revenue. See Close the Current Period for what closing does to scheduled entries.
How a Schedule Is Built
If a product’s or package’s Accounts Receivable account is set to a revenue G/L account instead of a true receivable account, revenue can look overstated. In that setup, receivables and payments post against the revenue account instead of staying separate from revenue. If recognized revenue looks inflated, check that the product’s AR account is a receivable account, not a revenue account.
A product gets a revenue recognition schedule only when deferred revenue recognition is turned on and the setup includes a deferred revenue account. If you turn on that setting later, Rhythm does not create schedules for sales that posted before the change. Only sales posted after the change get a schedule. When both setup requirements are in place, Rhythm builds the release schedule in one of three ways, based on the product setup:
Automatically, month by month. Rhythm releases the deferred revenue in equal monthly amounts over the period the sale covers. For a membership, Rhythm uses the membership term dates from the order behind the invoice. If both dates are not available, Rhythm uses a one-year period from the batch date instead. For an event, the period runs through the event’s end date, so the event must have an end date for Rhythm to build the schedule. If one sale includes both an event line and a membership line, Rhythm recognizes each line based on its own dates within the same transaction. The event portion follows the event’s dates, and the membership portion follows the membership term. If more than one entry for the same invoice lands in the same recognition month, Rhythm keeps those entries separate instead of combining them.
On the product's own fixed dates and percentages. Some products release revenue on specific dates and percentages instead of spreading it evenly. These manually entered dates are common for event-related items, such as registration packages and function tickets, where an automatic membership term or event end date does not apply. The percentages do not need to total exactly 100 because the final date takes any remaining difference, whether positive or negative. If a product's Deferred Revenue Recognition setup names only the event's end date, with no earlier release dates, Rhythm recognizes the whole invoice amount in that one month instead of spreading it across the months before the event. If you expected earlier partial recognition and see everything post at once, check the product's fixed dates.
From relative-date rules. A product can use rules that calculate release dates based on the month the sale was posted. Each rule covers a range of sale months and defers revenue into a range of recognition months. Both ranges include the full first and last months, so a range from March through May runs through May 31 at 11:59 pm. Selecting one month, such as January, covers the whole month, from January 1 through January 31. To defer everything into one target month, choose that same month for both ends of the recognition range. For example, to recognize revenue from October, November, and December sales entirely in January of the next year, set the rule’s sale range to October through December and its recognition range to January of the next year through January of the next year. When more than one rule matches, Rhythm uses only the first matching rule. If a transaction does not fall within any rule, Rhythm uses the product’s default deferral option instead, so review that default carefully because it applies to every transaction the rules do not cover.
In every case, if the sale’s line item has revenue splits, each monthly or scheduled release uses the same split the invoice line used when it posted. This also applies to products that use fixed deferral dates, so deferred amounts follow the invoice line’s split instead of being divided equally. See How Posting Creates Ledger Entries for how splits work. Rhythm copies the split percentages onto the schedule when it is built, so changes to a product’s splits do not affect existing schedules. For a membership invoice that combines deferred revenue with fixed-amount revenue splits, Rhythm divides each split’s fixed amount across the membership term the same way it divides the total sale amount. If your association has deferral schedules created before that behavior applied, they do not recalculate on their own. Unpost and repost the batch containing the invoice to regenerate a corrected schedule.
Limits and Refusals
A revenue recognition period cannot run longer than sixty months. If the automatic period for a sale would be longer than that, the transaction fails to post. The message shows the number of months and the sixty-month maximum, including when an invalid or outlier date caused the issue instead of a normal long period, so you can see exactly what to check.
If a schedule date falls before the batch that created it, Rhythm moves that date forward to the batch date instead of scheduling it in the past. The same rule applies to reversing entries created by a credit, write-off, or refund. If the reversal would otherwise fall in a past-dated period, Rhythm uses the current batch date instead. For an event product, if the sale posts after the event has already ended, every scheduled release moves to the batch date. The whole amount is then recognized in that one month instead of being spread out. Moving an entry to the batch date does not recognize it immediately. Like any other scheduled entry, it is recognized only after the fiscal period containing that batch date is closed.
A deferral schedule also cannot be created after the fact for a missed membership deferral once it would affect fiscal periods that are already closed. If a membership deferral was missed, address it before the affected periods close.
What Happens When the Sale Changes
If you issue a credit memo, write-off, or refund for an invoice that already has a revenue recognition schedule, Rhythm reduces or reverses the existing schedule so the credited line stops releasing revenue it is no longer entitled to. This reversal happens only in specific cases. For credit memos and write-offs, the business unit must use accrual accounting. For refunds, the business unit must use cash accounting. Outside those cases, Rhythm does not write a reversal, and the original schedule continues releasing the full amount.
When Rhythm writes a reversal, it spreads the reversal across all entries from the original schedule, including months that have already been recognized. Because past-dated entries move to the batch date, the reversal usually appears as a larger-than-usual negative revenue release in the period when the credit, write-off, or refund is posted. It is not spread back across the months it corrects.
If the invoice’s order is cancelled before the invoice’s batch posts, Rhythm skips the revenue recognition schedule entirely when the business unit uses accrual accounting. Deferred revenue is still credited at posting, but without a schedule to release it, that balance stays on the books until you address it another way. For a membership with more than one order in its history, deferral totals follow the invoice attached to the membership’s current order, not any cancelled order that came before it. That means cancelling and replacing an order should not duplicate deferrals.
After an order is cancelled, you may still see more than one deferral or schedule-related record for it. That is not necessarily a duplicate. Rhythm keeps the original schedule with any offsetting or replacement entries as part of your accounting history instead of removing them.
Deferred-revenue subledger entries and a visible recognition schedule are not the same thing. An invoice can have deferred-revenue postings without an actual schedule attached, so check both separately if something looks off. If the sale included a discount, you may also see a separate revenue-account entry for just the discount amount. That is not a duplicate of the larger recognized amount, which was already recognized on its own.
Tip
If a customer’s deferred revenue balance for a cancelled order is not clearing on its own, check whether Rhythm ever created a recognition schedule for it. Under accrual accounting, an invoice whose order was cancelled before posting does not get one, so there is nothing to release it automatically. To recover, either cancel the affected order line and reprocess it so Rhythm builds a new schedule that catches up the current month, or recognize the prior months in your external accounting system and create a journal entry in Rhythm for the remaining months.
Related Reading
Adjusting a schedule that is already running, such as changing its remaining release dates, is covered in its own task article. There is no single screen that lists all deferred revenue and lets you reclassify it in one action. You adjust it through the schedule’s own record, or by working from a report together with the batch that created the entries you need to change. To learn what an invoice’s deferred revenue balance represents before it is spread across a schedule, see Invoices.