Account Records for Transactions with Suspense
When an activity processes that has suspense configuration, the system will locate the suspense record through the suspense number saved with the activity. The system will compare the amount entered in the activity to the amount left in the associated suspense record.
-
If the amount entered in the activity is less than or equal to the remaining suspense amount it will add the amount to the attached amount and leave the suspense records status as open.
-
If the attached amount is equal to the original suspense amount, the status of the suspense record is set to closed.
-
If the amount entered is more then the suspense amount an error will generate at the activity level indicating there is not enough funds in the suspense record to apply to the policy.
Only one record for suspense is used during the suspense record's life, which is continuously updated with attached amounts until the record is in a closed status. Additions and reverses will happen to the one record according to the activity processing.
There are constant hard code suspense statuses that cannot be configured. However, additional statuses can be created and stored in the AsCodes table via AsCodeSuspenseStatus. Additional statuses may be needed if the GenerateSuspense rule is used to configure the creation of suspense records for transaction processing.
Hard Coded Suspense Statuses
01: NotApplicable
02: Pending
12: Deleted
15: Open
16: Closed
Additional Suspense Status Examples
03: Processed
04: Reversed
Copyright © 2009, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices