Client engagement · Healthcare Financial Services

Healthcare Reimbursement Reconciliation

Reimbursement review depends on connecting the right contract terms with claims and payments. SOLLUS maintained data workflows supporting post-payment auditing for eight hospital systems.

Hospital systems supported
8

The business challenge

Bring payment records and contract terms together.

Payment discrepancies are difficult to investigate when claims, procedure mappings, contractual pricing, and remittances are maintained separately. Analysis also needs to account for changing agreements and effective dates. Claim corrections, coding changes, and delayed payment updates can create apparent discrepancies that require validation before further review.

The engagement

SOLLUS supported a specialized healthcare services organization's post-payment insurance reimbursement auditing operations. The work supported eight hospital systems, some comprising multiple hospitals, across inpatient and outpatient workflows, and included claims associated with Medicare, Medicaid, and TRICARE.

Electronic claim files (837), payment and remittance files (835), and recurring client data updates supplied billing and payment context alongside contract terms and service mappings. QA checks helped distinguish data timing and coding differences from potential reimbursement discrepancies.

SOLLUS's contribution

The work behind the result.

  • Developed and maintained Alteryx workflows for data preparation, cleansing, transformation, and recurring processing.
  • Used Python for more complex processing and MySQL for database development and maintenance.
  • Maintained contractual pricing information, medical procedure code mappings, and related tables as agreements and rates changed.
  • Connected expected reimbursement calculations with actual payment records, supported discrepancy identification and validation, and prepared internal and external reports.
  • Processed recurring payment updates and validated workflow outputs, report totals, and account-level results before posting them for audit review.

Conceptual workflow

How the information connects.

Reconciliation brings two information streams together. Current contractual terms and correctly mapped services provide the context for comparing expected and actual payments.

Contractual information

Reimbursement schedules, procedure mappings, effective dates, applicable pricing rules

Claims and payments

Service records, submitted claims, insurer remittances, actual payments

Both information streams inform reconciliation.

  1. 01

    Prepare and process

    Alteryx and Python

  2. 02

    Manage data

    MySQL

  3. 03

    Map contract terms

    Service context and effective dates

  4. 04

    Reconcile payments

    Expected versus actual reimbursement

  5. 05

    Identify exceptions

    Differences requiring investigation

  6. 06

    Validate and report

    Quality assurance and review outputs

Conceptual workflow. Open the full diagram.

Illustrative reporting example

Reimbursement reconciliation review

Invented providers, insurers, procedure identifiers, and dollar values illustrate an exception-review report. No patient information, client rates, or real claim records are used. A variance flags a difference for investigation; it does not establish an amount owed or recovered.

Synthetic review batch

Illustrative data — not a client report

Claims reviewed
120
Expected reimbursement
$120,000
Actual reimbursement
$114,000
Payment variance
−$6,000
Exceptions
18

Reconciliation status

Matched
102
Awaiting investigation
12
Under review
6
Synthetic claim excerpt — three examples from the illustrative batch; variance = actual − expected
ProviderInsurerProcedure IDExpectedActualVarianceStatus
Example Provider ADemo Health ADEMO-101$1,200$1,100−$100Investigate
Example Provider BDemo Health BDEMO-202$800$800$0Matched
Example Provider CDemo Health ADEMO-303$1,500$1,350−$150Under review

Business value

A reliable foundation for investigating differences.

The workflows connected medical claims, negotiated reimbursement terms, and actual payments to support the identification and investigation of payment discrepancies. Maintained contract information and code mappings supplied the context needed for review.

Capabilities

  • Financial reconciliation
  • Workflow automation
  • Contract data management
  • Quality assurance

Tools and methods

  • Alteryx
  • Python
  • MySQL

Talk with SOLLUS

Do your payment records tell the whole story?

Talk with SOLLUS about contract data, reconciliation workflows, and reports that help teams investigate differences.

Based in Virginia Beach, serving Hampton Roads and businesses nationwide.

Tom DabbsPresident | SOLLUStom.dabbs@sollus.us757-255-8547

Selected Client Projects

Explore related work.