Reviewing Aging Reports
There are five aging reports available to review.
Customer Aging (AR250) | creates a transaction aging for a customer group above the company. You can run it for a single customer or all customers in the group. |
Company Aging (AR251) | creates a transaction aging for a company. You can run it for a single customer or all customers in the company. |
Report Group Aging (AR252) | creates a summary aging for a process level report group. |
Summary Aging (AR253) | creates a summary aging for all customers assigned to a company. |
National Account (AR255) | creates a transaction aging for an individual or all national account customers. |
Contract Activity Aging (AR257) | creates a transaction aging report for contract activities |
The differences between the As of Date and the Audit/Period fields:
The As of Date ages transactions based on their status as of a specific date. All transactions that have a general ledger date on or before the date you enter will be included. If you leave this field blank, you must select Period End Date in the Audit/Period field. Fully paid and fully applied transactions are not selected once they become historical unless you select Audit.
The Audit/Period field gives you two options:
-
If you select Audit, it will create a time independent aging report based on the date defined in the As of Date field. This option processes more records and can require more time to process.
-
If you select Period End Date, the system will use the current period ending date defined in the GL application for the As of Date.