Defining Aging Codes

Aging codes are used to default aging options for your customers. A customer's aging options, if defined, override aging options defined at the company level when you process aging for a customer. This procedure describes how to set up aging codes.

To define aging codes

  1. Access Aging Code (AR15.8).
  2. Define aging codes, descriptions, and aging periods. Use the following guidelines to enter field values:
    Current

    This defines the separation between current and future aging periods. Current and future aging columns contain transactions that are not past due (for due date aging) or past invoice (for invoice date aging).

    If you leave this field blank, the future period is used for all transactions that are not past due and the current period is used for all transactions due on the As of Date.

    If you select a value, any transaction that is due between As of Date and that number of days beyond will show in the current column.

    Aging Periods

    Type the last days of the four aging periods. Type the periods in consecutive, ascending order.

    If leave these fields blank, "30 60 90 120" defaults.

    A total of seven aging periods exist: Future (period length determined by the number typed in the Current Days field), Current, four periods defined in the aging periods fields, and one period beyond the last Aging Period you define.

    Credits Payments Disputes

    Select aging options for credits, payments, and disputes.

    • Aged to last debit memo

    • Not aged - current column

    • Aged respective to date

    Method

    You can also select whether to age by due date or transaction date.

    Status

    Select the status of the aging code.

Related Reports and Inquiries

To Use
List aging codes

Operational Setup 2 (AR215).

Select "Aging" in the Report Option field.