Using The Anniversary Method

The anniversary date method causes the bill segment end date to be calculated based on the first day of service. For example, if an obligation started on the 16 th of some month, the ongoing bill segments will start on roughly the 16 th of each month. When using this method, you also define the applicable billing frequency (i.e., monthly, bi-monthly, quarterly, etc.).

The following table contains the bill periods for an obligation's starting on 23-Feb-99 that uses a monthly frequency.

Start Date

End Date

Billing Days

23-Feb-99

25-Mar-99

30

25-Mar-99

25-Apr-99

31

25-Apr-99

25-May-99

30

25-May-99

25-Jun-99

31

25-Jun-99

25-Jul-99

30

25-Jul-99

25-Aug-99

31

25-Aug-99

24-Sep-99

30

24-Sep-99

24-Oct-99

30

24-Oct-99

24-Nov-99

31

24-Nov-99

24-Dec-99

30

24-Dec-99

24-Jan-00

31

24-Jan-00

23-Feb-00

30

23-Feb-00

25-Mar-00

31

Note:

Future and Past End Dates. It's important to be aware that anniversary billing can generate end dates that are in the future or in the past. The future-option generates the next anniversary date after the current date. The past-option generates the anniversary date that immediately precedes the current date.

The obligation's obligation type indicates if the obligation uses this method. If so, the obligation type also specifies the billing frequency that determines the amount of time between bill segments.

Fastpath:

For more information about the obligation type attributes that control this method, refer to Setting Up Obligation Types.