Epic Systems Migration Reconciliation Framework

Epic systems migration reconciliation is the framework that proves — with auditor-grade evidence — that every downstream finance, HCM and SCM data row in Epic landed correctly in Oracle Fusion. It runs continuously through the migration and parallel-run window, reconciling at three tiers (Clarity vs Cogito source, Fusion staging vs Clarity post-transform, Fusion posted vs Clarity at load instant) per fiscal period per service area per account class. Output: signed evidence packs that satisfy SOX 404, HIPAA §164.312(b), Joint Commission, CMS cost report, and OIG audit defense in one artefact. Reconciliation framework includes variance disposition workflows, escalation thresholds and CFO sign-off gates — not just dashboards.

Validation answers the question "did this load succeed?" — per-load, row-by-row, mostly automated. Reconciliation answers the question "is the total picture consistent?" — fiscal-period-wide, with controller and internal audit sign-off, intended to satisfy external auditors. They are related but not identical. Validation is a precondition for reconciliation: every load has to pass validation before its data is included in the reconciliation evidence pack. Reconciliation aggregates the validation results across the period, applies materiality thresholds, walks variances with the responsible accountable owner, and produces a signed artefact. A migration without reconciliation will fail the first external audit even if every load "passed validation".

Six core components. (1) Three-tier reconciliation harness — Clarity-Cogito, Fusion-staging-Clarity, Fusion-posted-Clarity. (2) Materiality thresholds — typically zero variance on AR balance, $50/item on inventory cost averaging, zero on worker count, configurable per domain. (3) Variance disposition workflow — every non-zero variance assigned to an accountable owner (controller for finance, HR director for worker, pharmacy/perioperative/lab leads for inventory) with disposition due date. (4) Escalation thresholds — variances aging past disposition due-date escalate to CFO and CIO. (5) Period-end evidence pack assembly — signed PDF + machine-readable JSON. (6) Auditor self-service retrieval — SOX/HIPAA/Joint Commission auditors retrieve packs directly via secured portal.

Yes — and AR is the highest-stakes domain because the variance threshold is zero. Resolute AR aging per service area at the period-end snapshot must reconcile to the Fusion GL AR balance per service area at the same instant to the cent. The Cogito period-end AR snapshot is the cross-check reference — Cogito has historically been the CFO's number anyway. The reconciliation framework runs the three-way (Resolute AR aging × Cogito snapshot × Fusion GL) tie-out per period and produces the signed evidence. Any non-zero variance halts further period-end activities until disposed by the controller. This is the single most common reason healthcare migrations slip a quarter — and Syntra ETL's framework is engineered to clear it cleanly.

340B is a federal drug pricing program for safety-net providers that requires demonstrable audit trail of 340B-eligible vs non-340B drug purchases and dispenses. In Willow, 340B-eligible dispenses are flagged at the transaction level. After migration to Fusion Inventory, the 340B flag must be preserved per transaction and the running 340B inventory split per location must reconcile. The epic systems migration reconciliation framework includes 340B-specific tie-out: Willow 340B-flagged dispenses sum-checked against Fusion Inventory 340B-flagged consumption per location per period. Variance threshold is zero — 340B audits by HRSA are strict and unforgiving. The reconciliation evidence pack includes a 340B-specific section retrievable for HRSA audit defense.

CMS cost report (Form 2552-10 for hospitals) is due May 31 federal for most fiscal years (state and provider type vary). It depends on accurate AR aging, contractual adjustment history, supply consumption split by Medicare/Medicaid/commercial, and worker FTE data. The epic systems migration reconciliation framework ties cost-report deadlines to the parallel-run window — typically you do not cutover within 60 days of cost-report due date, and the reconciliation evidence pack includes a cost-report-feeder section that maps directly to cost-report worksheet line items. This eliminates a parallel cost-report-preparation effort. Your reimbursement consultant retrieves the cost-report section from the evidence pack.

Five sign-offs per fiscal period evidence pack. Controller signs Tier 3 — Fusion posted reconciliation to Clarity at load instant. CFO signs the consolidated period-end reconciliation (Resolute AR × Cogito snapshot × Fusion GL trial balance tie-out). HR director signs worker master reconciliation. Pharmacy/perioperative/lab leads sign Willow/OpTime/Beaker inventory reconciliation. Internal audit signs the overall pack as control evidence. External auditor (typically Big Four or healthcare-specialist firm) retrieves the pack for SOX 404 walkthrough — they don't sign, but their retrieval and acceptance is recorded as part of the audit trail. The two-consecutive-clean-month gate to cutover requires all five sign-offs present on both packs.

Standard recommendation is two full month-end close cycles in parallel before cutover — that is the two-consecutive-clean-month gate. For a regional health system this is ~8–10 weeks elapsed from first parallel period to cutover decision. Academic medical centres with complex Resolute configurations and multi-IDN consolidation typically run 3 months parallel — ~12–14 weeks elapsed. The parallel window includes daily delta reconciliation, weekly variance review with the controller, monthly evidence pack assembly with full sign-off chain, and a final pre-cutover walkthrough with internal audit. Within this window the legacy ERP continues to be the operational system; Fusion is parallel-run, reconciled, and demonstrated to be ready before cutover.