Bills require information unique to the tax type, tax role and bill type in order to calculate charges. In addition, the business rules governing the applicable charges and the computations themselves can be complex. Unlike other system objects, the product does not expect bill details to be manually maintained. Instead the bill details and associated assessments are created by background processes invoked at specific times in the bill’s lifecycle.
The product supports the following bill lifecycle, covering the most typical scenarios for billing:
Bills are initially created in a Pending status with minimal information other than the tax role, obligation and revenue period.
When bills transition to the Generated state, algorithms are invoked to capture the value details and create the calculation lines and bill segments that form the basis of the assessed charges.
If generation is successful, the bills transitions directly to the Ready To Complete state.
If there are any bill generation exceptions, the bills transitions to the Error state for manual correction.
When bills transition to the Completed state, algorithms are invoked to finalize the bill. The product expects that the algorithms that create financial transactions for the bill’s obligation will be invoked at this time.
If a bill needs to be reversed, it must be manually transitioned to the Canceled state. The product expects that the algorithms that reverse the financial transactions for the bill will be invoked at this time.
Refer to the base business object for bills C1-TaxBill for more details.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]