Skip to main content
Recognition frequency and interval control how often DualEntry creates recognition schedule lines for a performance obligation, independently of billing. This page covers setting them. For how the two fields combine and when a non-monthly cadence is worth configuring, see How Recognition Frequency and Interval Work.

Prerequisites

Before you set recognition timing, confirm the following:
  • Revenue recognition is enabled for your organization.
  • The obligation uses a schedule-driven recognition method (for example, straight-line or daily pro-rata), not usage or milestone.
  • You know the target frequency and interval (see How Recognition Frequency and Interval Work for common configurations).

Configure recognition timing

On the contract form, open the performance obligation Recognition tab (and the matching fields in the Revenue Recognition step in view mode). These controls are available for schedule-driven recognition methods so you can correct or set cadence without deleting the obligation.
  1. Choose the recognition method (for example, straight-line even periods or prorate daily).
  2. Set Frequency and Interval for recognition.
  3. Set recognition start and end dates as usual.
  4. Configure Invoicing separately if billing should use a different cadence.
The same frequency picker is shared between recognition and invoicing controls, but the stored values are distinct: recognition_frequency / recognition_interval versus billing frequency / interval. Changing only the invoicing cadence leaves recognition lines on their existing schedule, and changing only recognition leaves billing alone. After you save, DualEntry rebuilds the recognition schedule from the new cadence for open periods. Review the Revenue Recognition preview step (or the contract schedule views) to confirm line dates match the intended every-Nth pattern before you activate the contract. If the contract is already active, confirm that locked periods are not affected before you rely on the updated open-period lines.

Next steps

Last modified on September 1, 2026