cenrus
Request a pilot

Turn separate records into one review decision.

Cenrus connects payer adjudication, provider requests, and available payment evidence. It tells review teams which cases match, which differ, and which need judgment.

Request a pilotSee how it works

Reconciliation

case_rec_02f27

Review needed

Payer assigned

$193.24

Provider requests

$440.00

Difference

$246.76

Verdict

Amount discrepancy

The provider request exceeds payer assigned patient responsibility by $246.76.

Synthetic case

Reconciliation workspace

Choose a provider request scenario

Source records

Three records, one case

5 matching signals
01

Patient responsibility

$193.24
02

Statement amount

$440.00
03

No supported record

Not available

Matching signals

Strong match
Patient account
7291
Service date
Feb 27, 2026
Provider
Northstar Imaging
Procedure
Diagnostic imaging
Requested amount
$246.76 difference

Reconstructed allocation

What the payer assigned

Submitted charge
$440.00
Payer adjustment
−$246.76
Payer payment
$0.00
Assigned by payerPatient responsibility
$193.24

Cenrus verdict

Review

Amount discrepancy

The provider requests $246.76 more than the payer assigned responsibility.

Provider request$440.00
Payer responsibility$193.24

Reconcile the financial state, not just the document.

Each record answers a different question. Cenrus preserves those differences, then compares the evidence that the customer provides.

01

Payer adjudication

The payer record shows submitted charges, adjustments, deductible, copay, coinsurance, patient responsibility, and available payer payment information.

02

Provider request

The statement shows what the provider wants to collect, along with account, service, provider, and charge details that support matching.

03

Payment evidence

Receipts, transactions, and supported customer records add evidence of what the patient already paid. Cenrus labels the source and strength of each record.

Payer event
Provider request
Payment evidence

Cenrus decision

Verdict, evidence, confidence, next action

Find the right payer event before comparing amounts.

Cenrus scores independent signals from both records. It escalates the case when those signals conflict or fail to identify one clear match.

Candidate match

Provider statement ↔ payer claim

  • Patient accountExact
  • Service dateExact
  • ProviderHigh similarity
  • Procedure contextSupported
  • Requested amountCompared

A

Build candidates

Cenrus looks for payer events around the service dates and provider context in the statement.

B

Score independent signals

Account numbers, dates, provider identity, procedure context, and amounts support or weaken each match.

C

Escalate ambiguity

Cenrus returns an ambiguous match or human review verdict when the evidence does not support one clear association.

Show how the payer reached patient responsibility.

A total alone does not explain a claim. Cenrus reconstructs deductible, copay, coinsurance, adjustments, and available payments for reviewer inspection.

Payer allocation

Professional claim

2026-02-27
Submitted charge
$440.00
Payer adjustment
−$246.76
Deductible
$193.24
Copay
$0.00
Coinsurance
$0.00
Payer payment
$0.00
Patient responsibility
$193.24
Synthetic sample

A clear $246.76 difference

This synthetic case demonstrates how Cenrus compares a provider request with payer adjudication.

If the provider requests $193.24

Cenrus classifies the request as consistent with payer adjudication when the records match with sufficient confidence.

If the provider requests $440.00

Cenrus identifies the same $246.76 difference shown as the payer adjustment and routes the case for review.

Give reviewers the decision and its basis.

Every response keeps the conclusion close to the evidence. Reviewers see what matched, what differed, and why the case followed a specific path.

01

Verdict

A narrow classification tied to the records available now.

02

Compared values

The provider request, payer allocation, and available payment evidence.

03

Match evidence

The account, date, provider, procedure, and amount signals used.

04

Next action

Remove from the first pass, investigate, wait for adjudication, or review the match.

Fit the engine into the queue that already exists.

Cenrus starts with the current review process. The customer sends a provider bill, Cenrus reconciles the records, and the result returns to the customer system.

  1. 01

    Patient authorizes payer access

    Cenrus maintains the approved connection and synchronizes available payer records.

  2. 02

    Customer sends a bill

    The workflow provides the statement and available account or payment context.

  3. 03

    Cenrus returns a verdict

    The response includes financial comparisons, match signals, confidence, and a next action.

  4. 04

    Events keep state current

    Cenrus emits updates when a claim or patient responsibility changes.