Separate active balances from historical billing detail during an EHR migration, with transaction evidence, reconciliation, ownership, and acceptance tests.
A billing migration should distinguish an opening balance from the transaction and claim history needed to explain, reconcile, and continue work on that balance. A total can transfer accurately while staff lose the evidence required to manage the remaining work.
This guide describes migration scope and acceptance for behavioral health organizations. It does not prescribe accounting entries, claim actions, retention, or payer treatment. Qualified financial, billing, legal, and compliance staff should review the actual plan and obligations.
EHR migration balances versus billing history starts with categories
List opening balances, charges, claim artifacts, submission references, payer responses, payments, adjustments, reversals, credits, unapplied amounts, follow-up notes, and supporting documents relevant to the organization.
The ASTP/ONC EHI export test method provides a certification-related export reference. It does not establish that a receiving system can recreate every financial workflow from an export. Inspect the actual files and proposed destination representation.
Assign an owner for each category. Finance can define balance and accounting questions, while billing can define the history needed for claim follow-up. Technical staff map and import data after those decisions are understood.
Define the opening-balance basis
Record the entities, accounts, payers, periods, date basis, cutoff, and transaction categories included. An account-level net balance can differ from payer-level or claim-level balances, and the intended grouping should be explicit.
Use a fictional account with several claims and a credit. A net total can look correct while hiding an incorrect allocation between claims or responsibility categories. Acceptance should inspect the relationship, not only the sum.
Have authorized finance staff define how the opening representation relates to the organization's ledger and close process. This guide does not establish the appropriate accounting treatment or imply that one imported transaction type fits every arrangement.
Preserve the evidence needed for follow-up
Staff continuing work need to know what was submitted, what response arrived, what action was taken, and what remains unresolved. A balance without that history can lead to repeated investigation or unsupported duplicate activity.
The CMS Medicare remittance advice page provides payment and adjustment context. Preserve actual source evidence and applicable scope rather than assuming a summary status contains everything needed for later review.
Test a fictional open claim with a partial payment and an unresolved question. Ask a receiving staff member to identify the next action using only the migrated or otherwise retained evidence. If they need the former system user's memory, the scope is incomplete for that purpose.
Keep historical representation distinct from new activity
A historical claim may be imported as structured data, an attachment, a reference, or another approved form. The organization should understand how that representation differs from a newly prepared claim in the receiving system.
Do not assume recreating a historical claim as active is appropriate. Authorized billing staff should define how duplicate submission is avoided and how later corrections follow applicable instructions. The migration plan should preserve what actually occurred.
Record labels and permissions that distinguish opening data, historical evidence, and post-cutover transactions. A current balance screen should not make an old payment appear newly received or an imported claim appear newly submitted.
Reconcile payments, adjustments, and credits separately
Use a fictional test pack containing partial payment, reversal, adjustment, credit, unmatched payment, secondary work, and a corrected transaction. Write expected relationships before the import test.
Compare record-level evidence as well as totals. One missing transaction and one duplicate can offset each other. A correct net balance does not establish correct transaction history or responsibility.
| Migration layer | Acceptance question |
|---|---|
| Opening balance | Does it match the approved scope and cutoff? |
| Claim history | Can staff identify actual submissions and responses? |
| Payments | Are sources, dates, and relationships understandable? |
| Adjustments | Are reasons, approvals, and reversals retained appropriately? |
| Credits and unapplied amounts | Is unresolved financial work still accountable? |
| Follow-up | Can a new reviewer identify the next action? |
| Later activity | Is post-cutover work distinguishable from imported history? |
Keep detailed financial and patient evidence appropriately restricted. The project summary can link to authorized reconciliations without containing every underlying transaction.
Plan changes between extract and cutover
Billing activity continues while the migration is prepared. Define how new payments, corrected claims, adjustments, and source changes are captured during that interval. A successful early import does not establish the final opening position.
Record the final update method, cutoff, owners, validation, and acceptance decision. Identify work that remains in the legacy system during transition and how staff avoid acting on the same item in two places.
Test a fictional payment arriving after the initial extract. Ask how it reaches the approved receiving representation and how the organization verifies it was not omitted or counted twice. Preserve the evidence supporting the final reconciliation.
Decide how legacy evidence remains usable
If some history stays outside the new system, define access, export, search, support, and responsibility through appropriate agreements and policies. Retention and availability decisions need qualified review; non-import does not automatically mean disposal is permitted.
Have a receiving biller retrieve a fictional source response or payment record through the proposed retained route. A contract promising access is useful, but the organization should also test practical usability.
Document limitations in the written scope. A readable historical attachment can be acceptable for one purpose while insufficient for another. The buyer needs to know the tradeoff before accepting the migration.
Make acceptance a joint financial decision
Ask finance and billing reviewers to approve their respective definitions and evidence. The technical importer can establish that a job completed, but should not approve financial meaning on behalf of every department.
Record passed cases, unresolved differences, authorized controls, and blockers. Put configuration, external access, manual work, and unverified vendor claims into the proposal. A broad migrate AR promise is less reviewable than a category-level acceptance plan.
Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask vendors to demonstrate the proposed opening balance and historical follow-up workflow. Related material includes the RCM overview, migration source inventory, and month-end evidence pack.
The useful result is a reconciled opening position with usable history and accountable unresolved work. It preserves the difference between transferring a number and transferring the ability to explain it.
Related reading
Frequently Asked Questions
Does importing an AR total migrate the full billing history?
No. An opening balance and the underlying charges, claims, payments, adjustments, responses, and follow-up evidence are different data categories. Define and test each proposed scope.
Should every historical claim be recreated as a new active claim?
Do not assume that. Authorized billing and finance staff should decide the appropriate representation, preserve history, and prevent unsupported duplicate activity under applicable instructions.
What should a billing migration acceptance test include?
Use fictional open claims, partial payments, adjustments, credits, unmatched payments, secondary work, and later corrections. Reconcile balances and verify that staff can identify the next action.
Who should approve financial migration results?
Assign authorized billing and finance reviewers for definitions, reconciliations, historical evidence, and opening balances. Technical import completion is not a substitute for their acceptance.
