/message Object Created from Invoice Reminder Collections Action Has Incorrect Bill POID
(Doc ID 2479131.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
It is observed that /message object created as a result of invoice reminder collections action has incorrect Bill POID.
1. Create an account on Oct 1st with monthly frequency and 30-day payment term
2. Generate Bill on Nov 1st and bill due date is set to Dec 1st (30 days payment term)
3. Run billing on Dec 1st
4. Run Collections immediately
Since Nov 1st bill is not paid, account entered Collections.
Collections scenario has invoice reminder action configured to be executed on 0th day (i.e. Dec 1st).
Invoice reminder action executed on same day as per configuration (i.e. Dec 1st).
As a result of this action, a /message object gets created with Dec 1st bill POID.
Below is the flist that fetches Bill POID from billinfo which is Dec 1 Bill POID in this case:
The question here is, though account/billinfo entered into Collections because Nov 1st or its previous bills were overdue, but /message object created as a result of invoice reminder collections action was populated with Dec 1st-Jan1st bill POID whose due date is in Jan 2019.
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
|Questions and Answers|
|As the Bill POID present in /message object is not yet crossed its due date and Invoice reminder is created for this bill, shouldn't the /message has Nov1st-Dec1st bill POID?|
|Any collections action that doesn't have balance impact could trigger auto billing?|