The cutover happened. Claims are being worked by your own team. The first month is where a plan meets the parts of the job nobody wrote down.
Five things break, they break in roughly the same order at every practice, and all five are predictable enough to prepare for.
What goes wrong in the first month of in-house billing?
Enrolment gaps that reject claims for reasons that look like coding errors, claims in flight that nobody claimed, the local payer knowledge that left with the previous arrangement, a posting rhythm that has not formed yet, and the first payer to change something while everybody is still learning.
One: enrolment rejections that look like something else
Claims come back rejected and the team starts debugging codes and modifiers, because that is what a rejection usually means.
Frequently it is enrolment. Electronic claim or remittance enrolment under the new arrangement has not completed for that payer, and every claim to them rejects until it does.
The tell is that rejections cluster by payer rather than by code. Check enrolment status before debugging anything, because a week spent on the wrong cause is a week of volume.
Two: the claims nobody claimed
Claims submitted before the cutover come back after it. Denials arrive for an arrangement that has ended, remittances land against claims your team did not send, and appeals sit unfiled because nobody agreed whose job they were.
If that agreement was made in writing before the change, this does not happen. If it was not, this is where the largest permanent loss of the transition sits, and it runs quietly until a filing deadline closes.
Recoverable in week two. Gone by month three.
Three: the knowledge that walked out
Every payer relationship has quirks that live in somebody’s head. Which one needs a phone call rather than a portal submission. Which representative actually resolves things. What an appeal has to contain to succeed. Where the timely filing limits sit.
None of that is in a system, and a new team rebuilds it one frustrating call at a time.
First-pass rates dip during that period and it is not a competence problem. It is a knowledge problem with a natural duration, and the only thing that shortens it is having captured the knowledge before the previous arrangement ended.
Four: posting rhythm has not formed
Payment posting is the least visible function and the first one to slip when a team is busy learning everything else.
A backlog of a few days becomes a backlog of a few weeks quickly, because catching up needs capacity beyond the daily flow and the daily flow is already stretched.
Then every other number goes wrong. Receivables look higher than reality, collections look lower for the period, and nobody can tell whether the transition is working.
Watch remittances received against payments posted, in days, weekly. It is the earliest signal that the team is underwater and the cheapest thing on this page to correct.
Five: the first payer change
Payers adjust edits and policies continuously, and one will do it during your first month.
An established team notices because the rejection pattern looks unfamiliar against months of normal. A new team has no baseline, so an unfamiliar rejection reads as something they did wrong, and the correction takes longer.
Nothing prevents this. Knowing it is coming shortens the reaction, and grouping rejections by payer and reason from week one gives the team the baseline they otherwise spend three months building.
What to watch weekly for the first quarter
Four numbers, and monthly is too slow for all of them.
Claims submitted against claims acknowledged, which catches silent batch failures.
Rejections grouped by payer, which separates enrolment problems from coding problems in the first week rather than the fourth.
Remittances received against payments posted, in days, which catches the backlog forming.
Claims in flight from before the cutover, counted down as each resolves, which is the only way to know whether that work is being finished or quietly dying.
What this means for you
None of the five is a sign the decision was wrong. They are the standard shape of a first month and they resolve.
What separates an expensive transition from a manageable one is whether somebody is watching weekly, because every item above is cheap in week one and expensive by month three.
Grab 30 minutes with us. Prep nothing. You will see what is still in flight from before the change and what is at risk.
Questions people ask
What goes wrong in the first month of in-house billing?
Enrolment gaps that reject claims for reasons resembling coding errors, claims in flight nobody claimed, the payer knowledge that left with the previous arrangement, a posting rhythm that has not formed, and the first payer to change something.
Why are my claims rejecting after switching to in-house billing?
Check enrolment before debugging codes. If rejections cluster by payer rather than by code, electronic claim or remittance enrolment has probably not completed for that payer, and every claim to them rejects until it does.
Who works claims submitted before the cutover?
Whoever agreed to in writing beforehand. Without that agreement the answer is nobody, and denials go unappealed while remittances go unposted until filing deadlines close. This is the largest permanent loss in most transitions.
Why does first-pass rate drop after going in house?
Because payer knowledge is not in any system. Which payer needs a call, which representative resolves things, what an appeal must contain. A new team rebuilds that over months, and the dip is a knowledge problem rather than a competence one.
What should I watch weekly after bringing billing in house?
Claims submitted against acknowledged, rejections grouped by payer, remittances received against payments posted in days, and the countdown of claims still in flight from before the change.