A decision reviewers can inspect.

Cenrus returns a narrow classification and shows the records behind it. The response states what the evidence supports and where a person needs to decide.

Request a pilot See how it works

Case resultvr_19324

Amount discrepancy

$246.76 difference

Payer assigned

$193.24

Provider request

$440.00

Recommended actionReview discrepancy

Seven outcomes cover the first review decision.

Each outcome maps to a clear review action.

Consistent with payer

The provider request agrees with payer assigned patient responsibility within the approved comparison rules.

Evidence included: Matched payer event, compared values, financial allocation, and the signals that support the association.
Next action: Apply the customer-approved routine path or keep the result available for audit.

Amount discrepancy

The provider request differs from the patient responsibility found in the matched payer adjudication.

Evidence included: Provider requested amount, payer assigned amount, the difference, allocation details, and match signals.
Next action: Send the case to a reviewer with the discrepancy already calculated.

Claim not found

Cenrus did not find a payer claim that the available bill evidence can support as the correct match.

Evidence included: Search window, available provider and service details, candidate results, and connection state.
Next action: Check source data, authorization, service details, or payer availability.

Claim not adjudicated

A likely claim exists, but the payer has not provided a final financial allocation that supports reconciliation.

Evidence included: Claim status, dates, available identifiers, and the missing adjudication fields.
Next action: Wait for a payer update or move the case to the customer review path.

Patient responsibility changed

The payer assigned amount differs from the prior payer state observed for the same claim.

Evidence included: Prior and current values, observed timestamps, record versions, and the financial fields that changed.
Next action: Reopen or update the prior reconciliation in the customer workflow.

Ambiguous match

Two or more payer events remain plausible, or the matching signals conflict.

Evidence included: Ranked candidates, signal level scores, conflicts, and the evidence missing from the bill.
Next action: Ask a reviewer to select the correct payer event or supply more context.

Human review required

The configured verdict and confidence rules do not automate this exception.

Evidence included: The assembled records, detected exception, confidence factors, and any unresolved data gaps.
Next action: Route the prepared case to a reviewer for judgment.

Keep the conclusion close to the proof.

A verdict without its basis creates another system for reviewers to check. Cenrus packages the decision with the values, matching evidence, confidence, and next action.

Reconciliation result

Amount discrepancy

Confidence: high

Financial comparison

Payer assigned: $193.24
Provider request: $440.00
Difference: $246.76

Match signals

AccountExact
Service dateExact
ProviderSupported

Recommended next action

Review whether the payer adjustment explains the unsupported portion of the provider request.

The payer record does not establish the provider's current account balance.

Verdict

The smallest classification supported by the available records.

Compared values

The exact financial amounts that agree, differ, or changed.

Match evidence

Signals that tie the provider request to the payer event.

Confidence

A calibrated control for routine handling or human escalation.

Next action

A clear step for the customer workflow.

Uncertainty changes the workflow, not the language.

Confidence reflects the support for a specific conclusion. It does not turn incomplete evidence into certainty.

HIGH

Strong support

The records align across independent matching signals and the compared financial values support the verdict. Customer-approved policy controls any routine path.

MIXED

Conflicting signals

Some evidence supports the result while other evidence weakens it. Cenrus exposes the conflict and sends the case to review.

LOW

Insufficient support

The available records cannot support a reliable association or financial conclusion. Cenrus returns ambiguity or human review required.