PCMI / PCRS

PCMI’s PCRS is administration software for extended warranty and service contract programs, policy issuance, contract terms, claims adjudication, and dealer or agent commission tracking, built for programs that span automotive, home warranty, and consumer product lines. ProPay integrates with PCMI / PCRS so that the claim itself, intake, triage, authorization, parts, and payment, is executed on top of it, rather than replacing it.

What ProPay does with PCMI / PCRS

ProPay reads coverage and claim context from PCMI / PCRS, contract terms, coverage limits, and claim adjudication records, and writes the resulting claim progress back as the work happens. At first notice of loss, ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates that coverage against what PCMI / PCRS holds before dispatch.

ProPay’s homeowner triage runs over SMS, capturing model and serial numbers, photos, and symptom detail directly from the homeowner’s phone, with 80 to 83 percent of homeowners responding after a claim is opened. That conversation, not a call center script, is what feeds the record in PCMI / PCRS.

Where a truck roll is warranted, ProPay applies your configured business rules, repair versus replace, auto-approval inside a threshold, then sources parts across suppliers, tracks the order through delivery and return, and validates the resulting invoice against the authorization record before payment releases. Every step writes back to PCMI / PCRS as the record of what happened.

How the PCMI / PCRS connection works

PCRS exposes a documented API for policy and claims data, which is where ProPay reads and writes directly.

Where PCMI / PCRS doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking PCMI / PCRS to change. Modules go live independently, FNOL, triage, authorization, parts, and payment can each be switched on against PCMI / PCRS one at a time.

What stays in PCMI / PCRS

Contract terms, policy holder records, and the underlying financial reserve accounting for each program stay in PCRS exactly as they do today.

What changes is how much of the routine claim work a person has to do by hand inside PCMI / PCRS. ProPay handles the repetitive execution and routes exceptions to a human, so your team spends its time on the claims that actually need judgment.

Data handling and security

Each ProPay client, including the connection to PCMI / PCRS, runs on a company-specific instance, one carrier’s claim data and contract terms are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.

Every recommendation ProPay makes against PCMI / PCRS’s data carries a confidence level and the inputs behind it, and is logged. Recommendations above your configured thresholds route to a person rather than executing automatically.

Deploying the integration

A dedicated Forward Deployed Engineer works alongside your team to build and maintain the PCMI / PCRS connection, mapping fields and handling the edge cases specific to how your program is configured inside PCMI / PCRS today.

Frequently asked questions about ProPay and PCMI / PCRS

Does ProPay replace PCMI / PCRS?

No. ProPay works on top of PCRS rather than replacing it. PCRS remains the system of record for policy terms and claim adjudication history.

How does ProPay connect to PCMI / PCRS?

PCRS exposes a documented API for policy and claims data, which is where ProPay reads and writes directly. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does PCMI / PCRS still control after ProPay is connected?

Contract terms, policy holder records, and the underlying financial reserve accounting for each program stay in PCRS exactly as they do today.