$3,410 in unsubmitted claims accumulates each day for a 2-provider sports medicine practice in Northern California. The practice started working with Arintra in early 2025, seeing 22 visits per provider per day at $155 per visit. Its average coding backlog was 3.5 days, leaving nearly $12,000 in unbilled claims on any given morning. Across 22 working days, that delay becomes a recurring cash flow issue.
The math is simple. Few practices run it.
What coding lag means
Coding lag is the time between a patient visit and claim submission. The path includes note completion, code assignment, biller review, and claim transmission. Each step can create a queue, so a visit can remain unsubmitted even when the clinical work is complete.
The key metric is average days from service date to claim submission. The 2-3 day range is an industry benchmark. Manual processes or slow note-signing can push that interval to 5-7 days or longer.
Days in AR, or days in accounts receivable, is the downstream metric. CMS / 14-30 days is the clean claim processing range, while commercial payers often take 15-45 days. Every day of submission delay extends the full cycle.
Why lag compounds
Lag compounds for two reasons, not in a straight line.
First, AR ages. Commercial timely filing windows commonly run 90-180 days, while Medicare allows 12 months. Older claims face more denial exposure when eligibility changes, prior authorization expires, or the episode is harder to reconstruct. A 60-day claim is not equivalent to a 2-day claim within the same timely filing window.
Second, volume compounds. At 40 patients per day, a team has 40 encounters to code. Five days behind creates 200 encounters, a Monday backlog. That week adds 200 more, putting the queue 400 deep. Coders working under backlog pressure make more errors, so lag creates a secondary quality problem.
Where lag starts
The three most common sources are unsigned notes, coder capacity limits, and payer-specific complexity.
Many EHR (electronic health record) systems require note signing before coding can begin. Physicians who sign 2-3 days after a visit build that delay into the coding start. A coder waiting on 3 days of unsigned charts cannot go faster.
A full-time coder handles 50-80 ambulatory encounters per day, depending on specialty and note complexity. A 3-provider family medicine practice at 60 visits per day is at or near the ceiling for a single coder. Volume variation, coder illness, or education time can tip the queue into backlog.
Payer rule complexity is a per-chart cost, not a per-day cost: orthopedic coding carries more steps per encounter than family medicine at equivalent volume, so complexity matters independently of raw volume.
The math in practice
Consider a 3-provider family medicine practice with 20 patients per day per provider, $125 per visit in net reimbursement, and approximately $7,500 in daily revenue.
A 4-day average lag / $30,000 unbilled balance becomes a 2 days / $15,000 unbilled balance when submission moves forward. The difference is not about collecting more, but collecting sooner. For a practice managing payroll, rent, and supplies on monthly cycles, that receivable balance difference is a real liquidity improvement.
For practices facing cash flow crunches during low-volume periods such as holidays, weather, or flu season, the AR balance has direct operational consequences.
The timely filing edge
Most practices know about timely filing windows. What is less appreciated is that the window starts from the service date, not the submission date. For commercial payers with 90-day windows, a 5-day lag leaves 85 days, which sounds comfortable until backlog accumulates.
A 60-day backlog, not unusual during coder vacancy or training, combined with an appeal or resubmission cycle can push a claim to or past the window. Timely filing denials are unappealable in most cases. The claim is gone.
The Medicare 12-month window provides buffer, but commercial payers with 90-day and 120-day commercial payer windows create real constraints for practices that let backlog accumulate. This is not theoretical for practices with coder turnover.
What same-day coding changes
Same-day or next-morning coding eliminates nearly all the described risks. AR reflects current work rather than backlog, timely filing exposure is reduced, and the biller has maximum time to correct front-end errors before submission.
Automated coding that runs when a chart is signed makes this feasible without coder staffing for every day's volume. The physician closes the note in the EHR, code assignment runs immediately, and the billing team's morning work begins with the prior day's encounters coded and ready.
Arintra assigns CPT and ICD-10 codes from completed clinical charts. It does not submit claims and does not retain chart content after the coding transaction completes. Codes are written back to the EHR or billing system. The value is reducing the gap between note completion and billable code availability.
Close the coding lag
Arintra closes the gap between note completion and claim submission.
Request Early Access