Researching Claims

This chapter covers the following topics:

Overview

Oracle Channel Revenue Management provides claim research tools, which you can use to obtain information about customers, transactions, and accruals that are associated with claims. You can view claim details, identify duplicate claims, split a claim and find the cause for the claim.

Information in this section will enable you to:

The process of investigating, resolving, and settling claims is a time consuming and costly manual process. If you choose to enable rule based settlement, you can automate the investigation and resolution of claims, implement direct approval based on the system parameter defaults you specify, and approve all claims pending your approval using the Claims: Mass Approval page. You can navigate to this page from the Claims page. For more information on this method of automation, see Implementing Rule Based Settlement in the Oracle Accounts Receivable Deductions Settlement Implementation Guide.

Viewing Claim Details

The claim details page includes the following information:

Reverting Claim Status

For the check settlement method, Oracle Channel Revenue Management issues an invoice into the Payables system against which a check is issued to the vendor. When the check is created the claim is closed. Occasionally, a Payables invoice may be cancelled before it creates a check. For example, if the claim contains errors and the approver did not notice. In order to handle these type of exceptions:

Handling Exceptions for Oracle Payables Settlement Methods

Use the concurrent program Update Claims – Payable Settlement Methods to handle exceptions for settlements related to Oracle Payables. This concurrent program lets you:

  1. Reopen a claim when the corresponding invoice is canceled in Oracle Payables.

  2. Synchronize settlement documents and vendor information from Oracle Payables invoice to Oracle Channel Revenue Management claims when check, check status, or vendor information is updated in an Oracle Payables invoice.

Splitting Claims

Claim split enables you to split a claim into multiple smaller claims and facilitates the process of research and settlement. Split claims share the same master claim number, with the addition of a suffix as an identifier. When a claim is split, you can see the balance and the running total of the amount that is assigned to the new claims. If the entire amount of the claim is not allocated to the split claims, then the unassigned balance remains on the original claim. Splitting a claim enables you to:

The following example shows in more detail how a claim with multiple reasons might be split.

You send an invoice to a customer for $100,000. You receive a check for $20,000 that includes an $80,000 deduction. Because the customer does not give any reason for the deduction, you create a deduction in Oracle Receivables by using the default reason--Unknown.

After some investigation, you determine that the customer has deducted $30,000 for promotions, $40,000 due to shipping errors, and $10,000 due to pricing errors. You can split the claim one of two ways:

Deduction Number Status Amount Reason
DED1 Cancelled $0 Unknown
DED1_1 Open $30,000 Promotions
DED1_2 Open $40,000 Shipping Errors
DED1_3 Open $10,000 Pricing Errors
Deduction Number Status Amount Reason
DED1 Open $30,000 Promotions
DED1_1 Open $40,000 Shipping Errors
DED1_2 Open $10,000 Pricing Errors

Notice that each claim number includes the original number of DED1. This number is used in Oracle Receivables for tracking purposes. All the outstanding balances and amounts that are processed for the root claim and each of the split claims are tracked in Oracle Channel Revenue Management.

Note: After a claim is split, the parent and the child claim are treated as separate claims during claim research. The fund balances in a child claim cannot be modified.

Rules for Splitting Claims With Claim Lines

The following guidelines and examples will help you split claims with claim lines. For the application to automatically split a line, the line amount must be for the full amount of the claim. In this example, the line is for less than the full amount; therefore, you must manually assign the line amount to the split claims.

For example, assume the total amount of a claim is $400.

Procedure for Splitting Claims

Splitting a claim into multiple smaller claims facilitates the process of research and settlement. You can split claims to settle only a portion of a claim, and to facilitate the investigation of a claim caused by multiple reasons. Split claims share the same master claim number, with the addition of a suffix as an identifier.

To split a claim, log in to Oracle Channel Revenue Management as Oracle Trade Management User.

As a prerequisite, an open claim should exist.

Navigation: From the Claim tab, click the Claims subtab, then the claim. In the Claim Main page, click the Split subtab.

Notes:

The new claims are generated after you click Update.

Duplicate Claims

Sometimes, customers may raise multiple claims for the same transaction. There may also be multiple deductions referring to the same offer or invoice. These claims and deductions are termed as duplicate claims. Before settling a claim, you can search for duplicate claims and deductions based on the reference numbers or names. After you identify a duplicate claim, you can mark it as duplicate after which the duplicate claim is removed. You can also mark multiple claims as duplicate. Both the deduction and claim serve as a reference to each other for future audits.

The Duplicates subtab enables you to automatically search for related claims and gives you a summary view of all claims with similar or same customer debit memo numbers or invoice numbers, thus allowing you to identify duplicate or invalid customer claims more quickly.

For example, a customer deducts, and references the debit memo number as DM0123. Due to an error, the customer again deducts using the same debit memo but this time the number is read as DMO123 (the letter O instead of the number zero). When you access the Duplicates function, you can automatically see a listing all the claims with similar customer debit memo numbers. You can drill down into each of them and determine further if they are really duplicates.

Marking a Claim as Duplicate

Duplicate claims are multiple claims and deductions, which the customers raise against the same transactions and invoices.

To mark a claim as duplicate, log in to Oracle Channel Revenue Management as Oracle Trade Management User.

As a prerequisite, an existing claim with duplicates should exist.

Navigation: From the Claim tab, click the Claims subtab, then the claim. In the Claim Main page, click the Duplicates subtab.

If any duplicate claims exist, they are displayed here.

Notes:

Verify if the information is duplicate and make a note of the claim numbers that have duplicate information. Click Main, and select the duplicate claim number in the Duplicate LOV, and Click Update.

Claim History and History Rules

Claim history enables you to record various changes made to a claim during the course of investigation. The Administrator sets up history rules to define the fields and information that must be captured in Claim history.

After the history rules are set up, the system records all the changes that are made to the selected fields, and enables you to trace back all the changes that have been made to the claim. This provides every claim with a complete audit trail. If a customer conducts post-audit activities and disputes the resolution of different claims, the organization can produce complete documentation of all the changes that were made to the claim resulting in resolution for the disputes.

For example, History Rules may be created for a customer contact point. Every time the customer contact is changed, it is captured in Claim history. You are assigned to the claim and you interact with the customer contact--John during research and obtain certain information. Later on, John leaves the customer organization, and the new customer contact is Mary. You change the Contact field on the claim from John to Mary. Because this field is set up with History Rules, the change is automatically captured in the History of a claim. In future, if any disagreement arises over the information supplied by the customer, you can trace back that the information had come from the original contact person John.