The first claims are out, but the payments do not arrive together. Some are electronic, some are in the mail, and some remittances have not reached the billing team yet. The first two months are about establishing a workable billing rhythm, not expecting a mature revenue cycle overnight.
Published October 31, 2026Reviewed November 1, 2026OneSource RCM
Go-live starts a payment cycle, not a mature revenue stream
A new practice begins without an established payment history. A practice changing billing companies may also bring older balances, incomplete records, and payments still arriving from earlier work. Sending the first claims does not instantly produce a predictable collection pattern. The first 60 days are primarily a ramp-up period: complete encounters enter billing, initial responses arrive, and payment and remittance pathways gradually become established. They are not a deadline for every balance to be reconciled or a mature financial analysis to be available.
Days 1-14: concentrate on the handoffs
Early work centers on access, configuration, complete encounter information, submission, and actionable rejections. The practice remains responsible for accurate registration, insurance information, eligibility checks, documentation, and timely responses to requests. An unsigned note or incorrect policy can delay the start of payer processing. Correcting a known submission problem is different from researching every newly unpaid claim. Routine monitoring does not mean a daily claim-by-claim report or a separate status meeting for each payment that has not yet arrived.
The payment clock does not start at the visit
A fictional Monday visit may not be ready to bill until the note is signed on Friday. If the complete claim reaches the payer the following week, its service date alone does not show how long the payer has had it. New-payer claims, enrollment changes, and initial setup can add time. Submission, acceptance, adjudication, payment issuance, delivery, deposit, and posting are separate steps. No universal payment date follows from the go-live date, and an unpaid recent visit is not automatically overdue.
Days 15-30: expect a mixture of payment methods
One payer may already send EFT while another issues paper checks. EFT and electronic remittance enrollment are separate processes, and some setups require information from an initial payment before electronic access can be completed. A portal can show paid while a check is still in the mail. Another payment may already be sitting unopened at the practice. This mixed period is normal enough that repeatedly calling payers about every recent unpaid balance can create work without advancing payment.
The practice mailbox is part of the revenue cycle
Open payer mail regularly and send checks, explanations of benefits, remittance details, and relevant notices through the agreed secure channel. Deposit payments according to the practice's process and provide the information needed for posting. The billing team cannot see a paper remittance that has not been shared. Uploading a document to an unmonitored EHR folder is not the same as routing it through the agreed workflow. Keep the payment and its explanation together where possible so the record can be reconciled when it reaches the normal posting cycle.
A consistent handoff for payer mail supports the billing workflow while paper and electronic payments overlap. Photo: Unsplash.
A portal marked paid is not automatically a missing-payment case
Before treating a recent payment as missing, allow for the payer's disbursement and delivery process and check the practice's mail and deposit records. Electronic remittance, EFT, and paper check timing do not always match. Check tracing, stop-payment, or reissue requests have payer-specific waiting periods and should not become the default response during the first few weeks. When a payment is genuinely outside the relevant window, provide the available details for targeted research. Do not submit duplicate claims simply because cash has not reached the bank yet.
Days 31-60: let the cycle develop
Payments may continue to arrive unevenly as additional payers complete their first processing and payment cycles. Posting follows receipt of the necessary remittance information and the normal work cadence; a current-month payment may not yet appear in a report. The emphasis remains on consistent submission, handling actionable responses, and completing payment setup. This period does not imply repeated payer calls on all open claims, weekly financial reconciliations, or a promise that every payment route will be electronic by day 60.
Reporting should follow the operating cadence
Reporting follows the agreed monthly or periodic cadence and the information available in the EHR. An early report can show activity without yet explaining mature collection performance. Missing remittances, paper checks in transit, incomplete mail handoffs, and posting timing can make a snapshot misleading. There is no special day-15 or day-30 reconciliation package implied by go-live. Detailed payment questions and mature trend analysis are generally more useful around 90+ days, when more of the initial cycle has had time to complete. That is context for interpretation, not a new reporting guarantee.
Why charges this month do not equal cash this month
Deposits may relate to older visits, patient payments, or work submitted before the transition. Recent charges may still be in normal processing, and charges are not the same as contracted allowed amounts. Service date, submission date, payment date, posting date, and deposit date answer different questions. A bank total and an EHR total can differ without proving a billing error. Avoid rebuilding every claim in a parallel spreadsheet to explain a recent snapshot; first consider whether the reporting period and available payment information are comparable.
A report is a snapshot of available information, not proof that a recent unpaid balance is overdue. Photo: Unsplash.
Questions work best with context and time for research
Written questions belong in the agreed secure channel, with the report, period, and specific concern identified. Email-first communication allows a researched response and keeps the history in one place. Routine updates follow the established cadence rather than a recurring meeting or a fresh claim-by-claim audit on request. For a payroll concern, identify the relevant period and issue rather than sending the entire ledger for re-verification. During ramp-up, checking practice mail and supplying remittances may resolve more than another request for payer status. Urgent, actionable exceptions should still be identified as such.
Around 90+ days: aging becomes more informative
Once more initial payments, remittances, and postings have had time to arrive, older unresolved balances and recurring patterns become easier to distinguish from ordinary timing. This is a more useful stage for broader aging review and targeted follow-up than the first few weeks. It is not a rule to ignore claims until day 90, a promise that every account will be settled then, or a replacement for payer-specific deadlines. Follow-up depends on the actual claim age, status, payer requirements, and information available.
Inherited A/R follows a different starting point
A transition may include inherited work already well beyond the new claims' processing window. Older denials, filing or appeal deadlines, and unresolved balances require their own priorities within the agreed scope. They do not become new claims just because a new billing team takes over. Separating inherited A/R from post-go-live claims also avoids attributing every historical balance to the new workflow. The timing guidance for a newly submitted claim should not be used to defer an older actionable issue.
Known errors and deadlines still need attention
A rejected batch, a known enrollment or access problem preventing submission, a payer request with a due date, or an approaching filing or appeal deadline should be routed promptly. Those are actionable exceptions, not reasons to chase every recent balance. The distinction matters: fixing a known barrier helps work move, while repeated status checks on claims still in normal processing may not. No calendar-based ramp-up period overrides an actual deadline or an identified submission problem.
What a realistic first-60-day expectation looks like
The goal is a workable operating rhythm: complete encounters enter billing, actionable responses are handled, payer mail reaches the right people, and payments and remittances are posted through the normal process. Early cash flow may remain uneven. Detailed reconciliation and broader aging questions become more meaningful as the payment history matures, often around 90+ days. A useful partnership is hands-on operationally and cadence-driven, not an ongoing micro-level review of every claim. Clear handoffs and reasonable processing time make later reporting more useful.
Keep reading
Explore related guides on practice launches, payment timelines, and the work between claim acceptance and payment.
