To review contract activity aging

  1. Access Activity Aging Report (AR257).
    Note: To reduce processing time, select "N" in the Qualify Future Applications field, if you do not have future dated applications and the "as of" date specified is today's date. Select "Y" if you do have future dated applications and the "as of" date is not today's date.
    Note: 

    • The report is created as of the date you specify, which allows an accurate aging for non-historical transactions at any point. The activity customer print on the report.

    • Fully paid and fully applied transactions are not selected once they become historical. Applications, transactions, and payments become historical once they have been processed by Transaction Status Update (AR198) according to the value of the History Update Periods field on Company (AR01.1). For more information, see the field help for History Update Periods onCompany (AR01.1).

  2. On the Activity tab, select the activity or activities to be included in the report by selecting one of the following: an activity group list, an activity group, an activity list, or up to six specific activities.
  3. On the Aging Rules tab, define the aging options or leave the fields blank to accept the defaults. You must type the aging periods.
  4. On the Format tab, indicate whether to include detail (individual) or summary transactions on the report and whether to include unrealized gain/loss amount for transactions in the report, and select a report sequence option.

    • If the Report Sequence is Activity Group/Contract, the sort order will be by activity group, then by contract, then by currency. Subtotals are by currency and by contract (if currency has not changed), and by activity group (if currency has not changed). Report totals are only printed if currency has not changed across the report. Page breaking will occur at the lowest level (currency within contract).

    • If the Report Sequence is Activity, the sort order will be by activity, then by currency. Subtotals are by currency, and by activity (if currency has not changed). Report totals are only printed if currency has not changed across the report. Page breaking will occur at the lowest level (currency within activity).

    • If the Report Sequence is Contract, the sort order will be by contract, then by currency. Subtotals are by currency, and by contract (if currency has not changed). Report totals are only printed if currency has not changed across the report. Page breaking will occur at the lowest level (currency within contract).

    • If the Report Sequence is Activity Group/Activity, the sort order will be activity group, then activity, then currency. Subtotals are by currency, and by activity (if currency has not changed), and by activity group (if currency has not changed). Report totals are only printed if currency has not changed across the report. Page breaking will occur at the lowest level (currency within activity).

    If the currency changes across the report, no report total will be printed. However, subtotals will be printed if currency has not changed for that subtotal level.

    • Example 1: Assume a report where the requested sort is Activity Group/Activity, there are two activities for a given activity group, and each Activity has a specific currency.

      There will be currency-specific subtotals for each activity, and no activity group or report totals.

    • Example 2: Assume a report where the requested sort is by Activity, and, for a single activity, there are transactions with different currencies.

      Within that activity, there will be currency-specific subtotals, and no activity or report totals.