Accounting Enhancements

The accounting section now runs with each execution of the activity but it only writes accounting detail once for each Chart of Accounts entry. The criteria to determine when the accounting records are to be run depends on how the Chart of Accounts is configured. COA entries that are based on math variables or non-fund specific allocations (general accounting) will use values in the transaction math and these will write with the first successful execution of the activity (when there are no non-overridden business rule errors). This is standard Accounting processing today.

If the accounting entries are based on fund (separate accounting), then they will wait until all AsValuation records for the activity are moved into an active state (see Valuation status below), there are no non-overridden business rule errors generated from the new PostAssignmentValidateExpressions rule and the element <GenerateAccounting> has the value of Yes. All three conditions must be met even though the valuation records may be active before the activity moves into a final active state.

If there are no PostAssignmentValidateExpressions validation errors and all of the valuation records are in an active state, even if the Activity is still in an NUV Pending status, then the Accounting records for each fund can be written. Upon subsequent executions of the activity, the accounting will run again but will check to see if fund accounting records already exist for the activity.

Configuration Requirements

PAVE rule for Premium Transaction

PostAssignmentValidateExpression Rule that Controls Processing and Accounting for Premium Transation

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us