Skilled nursing product in development

Ease currently serves behavioral health organizations and is planning a skilled nursing product. Discuss planned scope and availability.

SNF controllers and business-office conversion leads

SNF Accounts Receivable Conversion: Reconcile Runoff and Transferred Balances

Plan SNF AR conversion with an opening-balance bridge, separate credit balances, post-cutover cash routing and explicit collection and accounting ownership.

Quick answer

Choose which receivables will remain in legacy runoff and which will transfer into the new operating ledger. Reconcile each balance to a dated source, preserving claim, payer, entity and supporting-history references. Test post-cutover cash, corrections and credits before release. A software move does not itself change ownership, establish collectibility or authorize billing a resident.

Choose the servicing path before exporting balances

An SNF can start new billing in one system while older receivables remain collectible through a controlled legacy process. It can also transfer selected balances while retaining their supporting history elsewhere. Neither arrangement is complete until the team can explain where an old claim is worked, where a payment is posted and how consolidated reporting avoids double counting.

Separate three design choices: legacy runoff, balance-level transfer and detailed transaction-history conversion. A balance transfer creates an opening amount with preserved references; it should not be described as full claim-history conversion. Runoff still requires usable access and supported staff responsibilities until its closure conditions are met.

ONC's September 2016 EHR Contracts Untangled, section 9, discusses transition services, data portability and access to previous software. This historical guidance does not determine ownership of receivables, accounting treatment or rights under a particular contract. Finance and transaction advisers must establish those facts for the actual arrangement.

Freeze a dated, balance-level source population

Create a signed-off extract with a cutoff and timezone, source ledger version, entity and account keys. Retain service period, claim identifier and version, payer/responsibility category, original aging basis, debit or credit amount, open dispute and supporting-record location. Record unapplied cash separately rather than silently assigning it to the oldest resident account.

Use a stable conversion crosswalk. A resident can have several stays, claims and payer balances; matching on name and total alone cannot identify which one moved. Preserve historical source identifiers even when a new account number is assigned.

Set a controlled interval between the first extract and final load. Every receipt, adjustment and new posting in that interval needs inclusion in a dated delta or an explained exclusion. “The files were exported on Friday” does not define which Friday transactions are included.

Reconcile an original fictional opening bridge

All amounts and decisions below are invented. They are not accounting instructions or expected collection rates. Assume reviewers have approved which items may transfer and which remain in runoff.

Source account item Debit AR Credit balance Destination
A, insurer balance $12,000 $0 Transfer
B, insurer balance $8,000 $0 Legacy runoff
C, approved responsibility balance $4,000 $0 Transfer
D, credit under review $0 $600 Transfer as separately identified credit
Total $24,000 $600 Net source position $23,400

The transfer population has $16,000 debit AR and $600 credits, net $15,400. Runoff contains $8,000 debit AR. Together they explain the $23,400 source net position. Keep debit and credit control totals as well as net dollars; an erroneous $600 reduction of A with D omitted would preserve net dollars but lose the credit population.

Now assume A receives a supported $2,000 payment after extraction but before final load. The final transferred debit total should be $14,000 and credits remain $600, net $13,400. Runoff is unchanged at $8,000. The final combined position is $21,400, a $2,000 reduction from the source cutoff.

If the original $15,400 transfer file was already loaded, use the approved correction route and preserve its link to the $2,000 receipt. Loading a replacement file without controlling the first load can duplicate opening entries. A job-completed message does not prove the final population.

Route cash that arrives after the switch

Test a later $3,000 payment for B, which remains in runoff. Under this specimen's approved design, post it against B in the legacy ledger, reducing runoff from $8,000 to $5,000. The transferred net position stays $13,400. Combined remaining balances become $18,400.

The receiving bank account might be shared by operational arrangement; that does not move B's balance into the new system. Send the posting team the claim/remittance identity and maintain a cash-to-ledger bridge. A new-system cash dashboard must not report the same $3,000 as payment against a second opening receivable.

CMS Medicare remittance guidance distinguishes claim/line adjustments from provider-level adjustments that are usually unrelated to a particular claim. Its Medicare context reinforces why an unexplained deposit difference should not become an arbitrary converted resident balance. It does not supply a conversion or acquisition-accounting rule.

Test corrections, statements and access boundaries

Use a review worksheet with expected account, source reference, ledger, posting event and downstream report for each case:

  • A payment reverses after conversion: the linked reversal reaches the correct transferred account without recreating the original opening entry.
  • B needs a historical corrected claim: the authorized worker can retrieve the original evidence and follow the applicable payer process through the approved servicing route.
  • D's credit is resolved: the reviewed disposition retains who authorized it and where any refund or other movement belongs.
  • A payer changes responsibility: a qualified reviewer determines the actual obligation before any resident statement is produced.

Retain disputes, unbilled work and unsupported adjustments as explicit populations. Conversion should not turn an unresolved claim into a collectible resident balance or reset its age merely because the import timestamp is recent.

For each population, name four owners or approved roles: receivable ownership, collection servicing, cash handling and record-access authority. They may differ, especially during an acquisition or outsourced arrangement. A software user account does not establish all four permissions.

Close runoff using evidence-based exit conditions

Define closure through remaining balances, pending corrections, unapplied cash, credits and access obligations, rather than a calendar date alone. Reconcile the final runoff report to the shared finance view and preserve a route for later payment, recoupment or record questions.

Approve the transition only when finance can reproduce the opening bridge, account samples, delta events and both post-cutover payment paths. That decision establishes which balances the new operating ledger can support and which obligations remain elsewhere; it does not erase them.

Questions & answers

Must every old claim move into the new billing system?

No universal conversion design applies. Compare supported legacy runoff with balance transfer and detailed-history conversion. Each choice needs authorized access, a collection owner, reporting treatment and tested retrieval of supporting evidence.

Is a matching net AR total sufficient?

No. Debit and credit populations, account identity, payer responsibility, aging dates and open exceptions can be wrong while net dollars match. Reconcile gross populations and account-level relationships as well as totals.

Who posts a payment received after cutover for an old claim?

The approved transition design must name the servicing ledger, posting team, cash owner and reporting bridge. Receipt date alone does not identify the correct account or establish who owns the receivable.

Primary sources

Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.