340B Reconciliation
Reconcile 340B activity with source-level traceability.
Unifhi connects dispensing, eligibility, encounter, purchasing, claims, and financial data in one governed reconciliation workflow.
Match activity across existing systems, surface exceptions for review, and preserve the path from source record to resolution.
The Challenge
The answer exists across multiple systems.
340B activity may involve the EHR, pharmacy system, split-billing or third-party administrator platform, wholesaler data, claims, contract pharmacy feeds, and financial records. Each system holds part of the transaction history. When records do not align, teams often reconstruct the sequence manually.
Records do not match cleanly
Identifiers, dates, quantities, statuses, and transaction formats may differ across sources.
Exceptions lack context
An unmatched or potentially duplicate record may require reviewers to search several applications before they can understand what happened.
Financial activity is difficult to trace
Savings, purchases, reversals, adjustments, and other financial events can be difficult to connect back to the operational records that produced them.
Audit preparation requires evidence
Teams need a consistent history of source data, matching logic, decisions, and adjustments.
The Solution
One governed process across the 340B systems already in place.
Unifhi does not replace your EHR, pharmacy platform, third-party administrator, split-billing system, wholesaler, or financial applications. It connects the relevant data and coordinates reconciliation across them.
Bring records together and normalize
Receive dispensing, eligibility, encounter, purchasing, claims, and financial data — translated into consistent definitions while preserving each original record and its lineage.
Match related activity
Apply approved matching and business rules to associate records across systems.
Surface exceptions
Identify unmatched, inconsistent, unresolved, or potentially duplicate activity for investigation.
Preserve resolution history
Retain the source data, applied rules, reviewer decisions, adjustments, and final disposition associated with each exception.
Reconciliation Workflow
From fragmented records to explainable resolution.
-
01
Connect
Ingest the required records from pharmacy, clinical, purchasing, claims, TPA, wholesaler, and financial sources.
-
02
Normalize
Map identifiers, dates, quantities, statuses, and transaction types into a consistent reconciliation model.
-
03
Match
Apply configured matching criteria and program rules to associate related activity across systems.
-
04
Investigate
Route exceptions to reviewers with the relevant source records, history, and financial context attached.
-
05
Resolve and trace
Capture the reviewer's decision, supporting information, adjustment, and final outcome in a traceable record.
Operational and Financial Visibility
See what matched, what did not, and where to investigate.
Unifhi gives program and financial teams a shared view of reconciliation activity.
Reconciliation status
Monitor matched, unmatched, pending, resolved, and aging activity across connected sources.
Exception patterns and priorities
Identify recurring differences by pharmacy, location, source, or rule — and focus reviewers on the exceptions with the greatest urgency or value.
Financial context
Understand the value associated with unmatched, reversed, adjusted, or unresolved activity.
Source-level explanation
Move from a measure or exception back to the records, matching logic, decisions, and adjustments behind it.
Configuration and Governance
Configure the reconciliation model around your program.
Unifhi represents source formats, matching logic, validation rules, exception categories, and review paths as governed configuration. Subject-matter experts review and test the configuration before production use.
Approved rules drive deterministic matching and workflow execution. Reviewers remain responsible for judgments and final resolution when an exception requires human interpretation.
When a source format, partner, or operating requirement changes, the relevant configuration can be updated and validated without rewriting the core platform.
Why Unifhi
Built for programs that must explain every record.
Work across existing 340B systems
Connect the systems involved without introducing another replacement system.
Make exceptions reviewable
Give reviewers the records, logic, history, and financial context required to investigate an exception.
Maintain end-to-end traceability
Preserve the relationship between source data, matching rules, reviewer actions, adjustments, and outcomes.
Connect operations to financial results
Relate reconciliation conditions to purchases, reversals, adjustments, savings, and other available financial activity.
Technology that supports oversight — not a substitute for program judgment.
Unifhi supports reconciliation, investigation, traceability, financial visibility, and audit preparation. It does not determine legal eligibility, guarantee program compliance, or replace the responsibilities of covered entities and their program experts.
FAQ
340B reconciliation questions
Does Unifhi replace our TPA or split-billing platform?
No. Those systems continue to perform their existing functions. Unifhi connects relevant data across them and provides a governed reconciliation, exception, and intelligence layer.
What 340B data can Unifhi reconcile?
Depending on the implementation, Unifhi can work with dispensing, patient, eligibility, encounter, purchasing, claims, reversal, adjustment, contract pharmacy, wholesaler, TPA, and financial records.
How does Unifhi identify potential duplicate or unmatched activity?
Unifhi applies approved matching, validation, and business rules across connected source records. It surfaces activity that meets configured exception conditions for review by qualified program staff.
Does Unifhi guarantee 340B compliance?
No. Unifhi supports reconciliation, traceability, investigation, audit preparation, and program oversight. Covered entities and their qualified advisors remain responsible for program decisions and compliance.
How does Unifhi support audit preparation?
The platform preserves source records, transformations, matching logic, exceptions, reviewer decisions, and adjustments so teams can reconstruct how activity moved through the reconciliation process.
Can we begin with a limited scope?
Yes. An implementation can begin with a selected pharmacy relationship, source system, transaction type, or exception category and expand after the reconciliation model is validated.
Related Solutions
Bring 340B reconciliation into one traceable process.
Tell us which systems hold the records, where exceptions accumulate, and what your team must reconstruct manually. We will map the sources, matching rules, review process, and financial context involved.