Last updated on JULY 27, 2017
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, BI - Billing
BILLING creates duplicate bills for the same bill cycle
If you run BILLING to create a bill, cancel this bill (via a credit note), manually generate a bill though the UI and then run BILLING again, it will create a duplicate bill for the same bill cycle.
Process is to run BILLING daily so as to pick up any account corrections. At some point the bills are frozen/completed for that month, however they can still be corrected afterwards (e.g. if a client notifies us of an incorrect bill). For example, customer has 1 account and the account is on last day of month bill cycle:
On May 1st the bill for April was generated/frozen/completed for the account by running the BILLING Batch.
On May 2nd a credit note was created which canceled the April bill.
On May 2nd all the transactions are disaggregated and the transactions are fixed.
On May 2nd the TFM batches are run.
On May 2nd the BILLING batch is run but this time no bill is created for the account in April - as expected as there is an existing bill for that period and bill cycle
On May 3rd a new April bill is manually generated through the UI (account context menu -> add bill)
On May 3rd the TFM batches are run again.
On May 3rd the BILLING batch is run but this time a second new April bill is created for the account - We were expecting the billing batch not to create a bill as it has one for that period and bill cycle.
User guess is that BILLING looks at the most recently created bill to determine bill cycle code (CI_BILL.BILL_CYC_CD). As the manual bill does not have an bill cycle code the BILLING job generatea another April bill.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms