Rerating process is an integrated process of Convergent Charging together with Convergent Invoicing. When is rerating necessary? Note: There are 3 correct answers to this question.

Question

Options

• AWhen address data needs to be corrected on an invoice
• BWhen the general ledger account assignment needs to be corrected
• CPrice tables were not up to date
• DConsumption data measurement was too high
• ECreation of new billable item with new price

• A
  11% (3)
• B
  81% (22)
• D
  7% (2)

Explanation

Rerating re-processes previously rated consumption data through the rating engine, and it becomes necessary when the pricing configuration or financial assignments were wrong at the time of original rating. B is correct because a wrong GL account assignment means the financial postings are incorrect - the billing documents must be reversed and regenerated with corrected account determination, which requires rerating. C is correct because outdated price tables mean consumption was rated against wrong prices; rerating re-applies the correct pricing retroactively. E is correct because introducing a new billable item with a new price requires rerating to generate the new charge correctly against existing or new consumption data.

A is wrong because correcting address data is a document-level fix on the invoice - it doesn't affect how consumption was priced or posted, so the rating engine doesn't need to re-run. D is wrong because if the measurement itself was too high, the issue lies with the input data, not the rating configuration; this is handled through data correction and reversal/rebilling, not rerating.

Memory tip: Think of rerating as "the price or posting was wrong, so re-price it." If the problem is how something was charged (wrong price table, wrong GL, new price model) → rerate. If the problem is something outside the rating engine (bad address, bad meter reading) → fix the data or the document directly, no rerating needed.

No community discussion yet for this question.