Third Party Contract Charges on Organization Accounts Do Not Age as Expected Using an Aging Set with Basis Date of 'Current Due Date'
(Doc ID 2879884.1)
Last updated on JUNE 30, 2022
Applies to:PeopleSoft Enterprise CS Student Financials - Version 9.2 and later
Information in this document applies to any platform.
When running Credit History for an organization using an Aging Set with Basis Date of 'Current Due Date', third party contact charges on the organization account are not processed. There is no Future Due Aging Category on the Aging set.
After linking the student to the third party contract, the third party contract credit gets applied to the eligible student charges, and the third party contract charge is posted to the organization account. It's then expected that Credit History should be processing that charge posted to the organization account based on the Aging Set setup. Why is the organization third party contract charge not processed by Credit History?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document