> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Recognition Frequency and Interval Work

> How DualEntry's recognition frequency and interval fields combine to set a schedule's cadence, independent of billing frequency.

Recognition frequency and interval control how often DualEntry creates recognition schedule lines for a performance obligation. Billing frequency remains independent, so you can recognize on one cadence and invoice on another. This page explains how the two fields combine and when a non-monthly cadence is worth configuring. For the steps to set them, see [Recognition Timing: Frequency and Intervals](./recognition-frequency-and-intervals).

## How frequency and interval work together

Each time-based obligation has two recognition timing fields that combine into the recognition cadence:

* **Frequency**: the base unit (for example, weekly, monthly, quarterly, or annually).
* **Interval**: how many of those units to skip between recognition lines. `1` means every period. `2` means every other period. `5` means every fifth period.

Common configurations:

| Goal                   | Frequency | Interval                                      |
| ---------------------- | --------- | --------------------------------------------- |
| Monthly recognition    | Monthly   | 1                                             |
| Every other week       | Weekly    | 2                                             |
| Every other month      | Monthly   | 2                                             |
| Every 5 months         | Monthly   | 5                                             |
| Semiannual recognition | Monthly   | 6 (or a semiannual frequency where available) |

New obligations default to monthly recognition with interval `1`. When you add another obligation, DualEntry copies recognition frequency and interval from the previous obligation so multi-line contracts stay consistent unless you change them.

Recognition timing does not replace the recognition strategy. Usage and milestone obligations still recognize from consumption or completion events. Frequency and interval apply to schedule-driven methods where DualEntry must decide how often to place recognition lines across the term.

## When this matters

Use custom intervals when commercial or integration-sourced contracts do not recognize on a simple monthly schedule. Examples include biweekly professional-services recognition, every-other-month managed-service lines, or multi-month straight-line steps that still bill monthly. In those cases the billing schedule can stay monthly while recognition follows the less common cadence your contract requires.

CRM-created contracts (for example, from HubSpot) can set recognition frequency independently of billing. If an imported obligation uses a non-monthly cadence, edit Frequency and Interval on the Recognition tab rather than deleting and recreating the obligation. That keeps allocation, invoices, and audit history on the same contract while you correct timing, and it avoids re-entering SSP and item mapping just to fix the schedule.

## Next steps

* Set frequency and interval on an obligation in [Recognition Timing: Frequency and Intervals](./recognition-frequency-and-intervals).
* Review recognition strategies in [Revenue Recognition](./index).
* Align billing cadence in [Subscription Billing](../platform-configuration/subscription-billing).