Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Warranty claim case type

Updated on January 27, 2021

Use the Warranty claim case type to support warehouses, onsite repairs, and replacement processes.

  • A dealer manages claims to quickly and effectively involve multiple manufacturers in the process while implementing specializations that are necessary for common cases.
  • An assessor and assessor manager manage claims to ensure that all financial aspects of a claim unit are complete and that all of the claim-related correspondence is closed.

For more information about the dealer, assessor, and assessor manager portal, see Warranty portals.

A Warranty claim consists of the following subcases:

  • Claim unit

A Claim unit supports the entire claims process. It is related to a single repair line in the repair order. The remaining steps in the claim lifecycle include validation, analysis, settlement, and recovery. This ensures that business rules are applied consistently to all claims, regardless of how each claim was created. A dealer can create a claim unit through multiple channels, including online entry, batch entry, online repair order, and batch receipt of repair orders. When a claim unit is created by the repair order, business rules are applied to the repair data in the claim segmentation process and the appropriate type of claim is automatically created.

  • Claim file

A Claim file contains all claim units that are associated with a particular repair order. A claim file represents the loss event and contains common information about the repair order.

Claim validation determines the claim disposition, which automatically approves or denies the claim, or sends the claim to be manually reviewed. The claim is paid in the settlement process.

You can create a Warranty claim unit using the following options:

The complete Warranty claim case flow is detailed in the following figure.

Figure: Warranty claim process flow

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us