Why Collections Always Dip After a System Change

Every practice management migration produces a collections dip. Vendors rarely mention it, which turns a predictable event into an alarming one.

Where the dip comes from

Enrollment. Electronic claim submission, remittance, and funds transfer are enrolled per payer per system. That takes weeks, and until it completes, claims go out slower and payments post manually.

Charge entry slows. Staff who entered charges without thinking now think about every screen. Charge lag rises for a month or two, and everything downstream inherits it.

Configuration errors surface as denials. Fee schedules, payer IDs, place-of-service defaults. Each is small and each produces a batch of denials that arrive a few weeks later — which is why the worst-looking week is usually not the go-live week.

Legacy A/R gets stranded. Old claims live in the old system. If nobody is assigned to work them there, they age while attention is on the new one.

What to do about it

• Start payer enrollment well before go-live. It is the longest pole and the most ignored.
• Keep read access to the old system, and assign someone to its A/R by name.
• Expect elevated denials in weeks three to six and staff for it.
• Hold cash reserve for roughly one payment cycle.

The honest framing

The dip is not evidence the migration failed. Its duration is what tells you something — a return to baseline within a couple of cycles is normal, and one that persists past a quarter means something is configured wrong rather than merely new.