Last updated: 2026-09-17

Medical billing in a one-provider practice runs on a seam. Which parts of the revenue cycle one person owns comes first, because a solo physician hiring for this needs to know whether they're buying charge entry or the whole thing. Why the chart and the money sit apart comes next, since that split is the reason this job exists in the setting at all. Turning a signed note into a billable charge is where each morning starts. Confirming a plan before the appointment sits ahead of that on the calendar, because a charge built on last year's card fails twice. Routing a claim out of the office follows, down whatever path somebody wired up years ago. Reading a scrubber rejection comes next, inside a day of sending. Applying an insurer payment is where money lands against the charge, one line at a time. What goes to an outside billing service earns its own section, since plenty of small offices split the job and then find nobody worked the aged claims. Keeping a ledger accurate is the quiet half of the week, and a wrong balance on a statement costs more trust than it collects. Which logins a remote hire needs comes after that, one named account at a time. Where the arrangement falls short closes the hiring question, and the sources supporting these facts end the page.

Which parts of the revenue cycle does a biller own in Practice Fusion?

A biller owns the stretch of the revenue cycle running from a signed note to a posted payment, which in a small ambulatory practice means a workflow that crosses at least two systems. The clinical record lives in one place. Charges, claims and remittance land somewhere else, and in a solo office nobody else is watching the space in between.

Seven jobs fill most of a billing week.

• Reading the signed encounter and confirming what the documentation supports before any charge gets built.
• Checking patient coverage ahead of the visit, so the charge isn't built against a plan that lapsed.
• Building the charge with the modifiers, units, place of service and rendering provider a payer expects.
• Releasing the charge as a claim, then confirming the clearinghouse accepted it rather than assuming it went.
• Working every rejection back to a cause the practice can fix instead of resending the same charge.
• Posting each payment and adjustment against the charge line it belongs to, then reconciling the batch to the deposit.
• Carrying whatever charge the patient still owes through statements, phone calls and an approved payment plan.

Two offices running the same software hand a biller different screens, different permissions and different queue names, because how the chart connects to the money is a local decision each practice makes. Ask for a written map of yours during onboarding rather than after the first stalled batch.

Why do the chart and the money sit apart in a Practice Fusion practice?

The chart and the money sit apart because a small office buys its clinical record and its claim path at different times, from different people, for different reasons. Nobody designs that split. It accumulates one decision at a time, and the biller inherits it. Cloud software of this kind lives in solo and two-provider offices where one person covers the whole business side, and sometimes that person is a part-time virtual assistant working the practice's hours from somewhere else, covering scheduling, charge entry and denial management in the same week.

Five settings account for most of this work.

• A solo physician practice where the biller is also the front desk, so charge entry competes with the phone.
• Two-provider family medicine, where one biller covers claims, payment posting and patient balance calls.
• Pediatrics, where coverage shifts at almost every well visit and eligibility work eats the biller's week.
• Part-time and telehealth practices with low claim volume where the biller still codes and sends every encounter.
• Single-specialty clinics whose payer mix is narrow enough that one rejection pattern explains most of what the biller works.

Pay bands for this role aren't a mystery either. The Bureau of Labor Statistics publishes employment and wage data for medical billing and related administrative occupations in its "Occupational Employment and Wage Statistics" program (Bureau of Labor Statistics, 2025). A practice setting a pay band for an in-house hire reads the current Occupational Employment and Wage Statistics release for its own metro area rather than guessing. What that data won't tell you is how much of the revenue cycle a single biller is expected to carry, which is the part small practices get wrong.

How does a biller turn a signed note into a billable charge in Practice Fusion?

A biller turns a signed note into a billable charge by reading the note first, then building the charge line from what the documentation supports rather than from what the schedule promised. Those two things drift apart more than anyone expects, and the schedule isn't the record. A visit booked as a follow-up becomes a longer problem visit, a planned procedure doesn't happen, and the charge has to match the note.

What a clean charge carries is where the skills that separate a careful biller from a fast one show up.

• The date of the encounter and the rendering provider the payer expects on this charge.
• Diagnosis codes drawn from the assessment, ordered so the primary one supports the charge being billed.
• Procedure codes at the level the note supports, with any modifier that explains what a payer would otherwise read as a duplicate charge.
• Units, place of service and referring provider wherever the charge needs them.
• The patient's current plan and subscriber ID, effective on the date of service the charge carries.

Nothing leaves before the note is signed. A biller who builds charges off an unsigned note is guessing at the service level, and the corrected claim costs more than the day of delay would have. When the documentation doesn't support what was scheduled, the question goes back to the provider in writing, with the specific gap named. Nobody wins an argument about a code three months later.

How does a biller confirm a plan before the appointment in Practice Fusion?

The biller confirms a plan before the appointment by running eligibility against what the record holds and reading the whole response, because an active plan and a covered service aren't the same finding. Eligibility comes back with more than a yes. Most of the useful detail sits below the first line.

Eligibility responses get read down to five details.

• Effective dates, so coverage that lapsed in January doesn't get billed for a March encounter.
• Copay, deductible remaining and coinsurance, which set the balance the patient owes once coverage applies.
• Network status for this exact coverage, since a practice can be in network with one product and out with another from the same payer.
• Referral or authorization requirements attached to the coverage, gathered before the visit instead of after the rejection.
• Secondary coverage and coordination of benefits, so the claim reaches the right payer first.

Patients hand over last year's card more readily than this year's. A photo of the front and the back at check-in, saved to the record, settles half the eligibility arguments that follow. The other half comes from mid-year plan changes nobody reported, which is why a biller reruns eligibility on established patients rather than trusting what the chart says. Small practices skip this step because it feels like front-desk busywork. It's the cheapest denial prevention available. For the vocabulary and the sequence behind all of this, our medical billing guide walks the revenue cycle from eligibility through collections.

How does a biller route a claim out from Practice Fusion?

Billers route a claim out by releasing the charge into whatever path the practice has wired up, and in nearly every small office that path runs through a clearinghouse before the plan ever sees it. The clearinghouse checks format, applies payer-specific edits, routes the file, and sends back an acknowledgment. How the chart, the charge and that clearinghouse connect is a local decision each practice makes, so ask your own office how a claim leaves rather than assuming the wiring matches the last practice you worked in.

Release is a threshold, and five facts govern what happens after it.

• A claim leaves the practice only after the charge is released, which is a deliberate action rather than a save.
• The clearinghouse returns an acknowledgment, and a missing acknowledgment means a claim that never left.
• Every payer keeps its own edits, so the same claim passes at one plan and rejects at another.
• A secondary claim follows the primary payment and carries the adjustment detail the second payer needs.
• Timely filing runs from the date of service, so a claim sitting unsent burns days the payer won't hand back.

Federal rules sit underneath all of it. The Centers for Medicare and Medicaid Services publishes the Medicare coding and billing rules (Centers for Medicare and Medicaid Services, 2025), and a biller working a practice with any Medicare volume reads those pages rather than a vendor summary of them.

How does a biller read a scrubber rejection in Practice Fusion?

A biller reads a scrubber rejection by starting at the reason code, fixing the record it points at, and resubmitting the same day, because a claim the scrubber stopped never reached the payer and no clock stopped while it sat. Speed matters more here than anywhere else in the cycle, because nothing's protecting the filing window. A rejection worked on day one is a two-field correction. The same rejection found later in an aging report costs a phone call and sometimes the whole claim.

Six causes explain most rejections in a small practice.

• A subscriber ID or member number on the claim that doesn't match what the payer holds for that patient.
• Patient name or date of birth spelled differently on the claim than on the plan's own file.
• Missing or wrong NPI or taxonomy for the rendering provider on the claim.
• Diagnosis pointers that leave a procedure unsupported on the claim line.
• A duplicate claim already accepted for the same encounter and date of service.
• Payer IDs that route the claim to the wrong plan entirely.

Denials are a different animal. A denial means the payer adjudicated the claim and said no, so the fix is an appeal or a corrected claim with documentation attached, not a resubmission of the same file. Structural causes such as a wrong payer ID keep producing bad claims until somebody fixes the setup field behind them. When the same rejection shows up three times in a week, the fault isn't the claim. It's a registration habit nobody has corrected. For the appeal side of that work, see our guide to denial management and how a virtual assistant works denials and appeals.

How does a biller apply an insurer payment in Practice Fusion?

The biller applies an insurer payment by matching each remittance line to the charge it paid, then reconciling the batch total against what reached the bank. Electronic remittance advice makes this faster than paper. It doesn't make it automatic, because the lines a payer adjusts are the lines worth reading.

Every remittance carries five pieces a biller posts separately.

• The allowed amount per charge line, which sets what the payment should be under the contract.
• Contractual adjustments, written off against the line instead of dropped onto the balance after payment.
• Patient responsibility split into deductible, copay and coinsurance, so the ledger shows what's left after the payer's payment.
• Denial and remark codes riding inside the payment file, which are the payer telling a biller what to work next.
• The payment total, reconciled against the deposit so nothing posts twice and nothing goes missing.

Lump-sum posting is the habit to break. A payment dropped against an account balance rather than against its charge lines hides every denial inside the check, and the practice finds out months later when a payer asks for a refund. Card payments taken at the desk need the same discipline, matched to a charge the same day. Unapplied cash sitting on an account isn't revenue. It's a reconciliation problem waiting for somebody's quarter to end.

What does a biller hand to an outside billing service in Practice Fusion?

A biller hands an outside billing service exactly what the two sides put in writing, meaning which work leaves the office, in what form, on what schedule, and who owns the answer when a claim stalls. Small practices buy this help two ways. One is staffing by the hour, where the person works inside your systems and your team still owns the outcome, and the other is a full outsourced service priced as a share of collections, where the billing companies involved own the result and report back on it.

Settling the split takes five questions before the first claim moves.

• Who builds the charge from the encounter, and who is allowed to change a code after the claim is built.
• Ownership of clearinghouse rejections, and the number of days allowed, since a rejected claim nobody owns ages in silence.
• Who calls the patient about a balance the claim left behind, and what that caller is allowed to say about coverage.
• How the claim file and the remittance move between the practice and the service, under a signed business associate agreement.
• Which reports come back, and on what cadence, so the practice sees aged claim detail instead of a collections total.

Both models work. What fails is a split nobody wrote down, where the in-house biller assumes the service is working the aged bucket and the service assumes the practice is fixing registration errors at the source. Put a name against every queue. Then read the aging report together once a month, out loud, until the gaps stop appearing.

How does a biller keep a ledger accurate in Practice Fusion?

Billers keep a ledger accurate by posting every adjustment the day it's known and refusing to leave an unexplained balance on a statement. A patient who calls about a bill deserves a straight answer in one sentence. When the ledger can't supply that sentence, the practice loses the payment and the goodwill together.

Housekeeping on a ledger comes down to five rules.

• Credit balances reviewed monthly, because a patient overpayment held past its refund window is a compliance problem rather than a cushion.
• Unapplied patient payments matched to a charge instead of parked on the account.
• Duplicate accounts merged, so one patient doesn't carry two balances and receive two statements.
• A written small-balance threshold the practice set, applied to every patient the same way each month.
• Statement cadence with a stop rule, so a patient gets a call about coverage before a collections letter.

Write-offs need a reason code, not just a keystroke. A ledger full of adjustments labeled "other" can't tell the practice whether it's losing money to payer contracts, to timely filing, or to a biller who cleared a queue the easy way. The working habits behind a clean ledger show up in our rundown of medical billing skills, and they're worth testing in an interview rather than taking on trust.

Which logins does a remote biller need in Practice Fusion?

A remote biller needs named logins to the chart, to wherever charges and claims get built, and to the remittance and deposit reports that make reconciliation possible. Access gets granted by the practice, one account at a time, the same way it'd be granted to an on-site hire. The security question underneath all of it stays simple, meaning who opened which patient record and whether the practice can prove it afterward.

Safe access rests on five controls.

• A named login per person rather than shared access, so the audit log shows who opened which patient record.
• Permission to read the signed encounter and build a charge, without access to alter clinical documentation.
• Access to the clearinghouse or payer portal where claims and rejection detail live, at the level the practice grants.
• Read access to remittance and deposit reports, since a biller can't reconcile a payment they aren't allowed to see.
• Multi-factor authentication, plus an access revocation step run across every system the same day an engagement ends.

Honest Taskers staff do administrative and clinically adjacent work and never give clinical advice or make clinical decisions. A biller doesn't pick a code the note won't support, doesn't edit a provider's documentation, and doesn't answer a clinical question that comes up on a balance call. The talent pool includes licensed nurses and physicians, which describes how the company recruits rather than what a placement does. Obligations for anyone handling protected health information on a practice's behalf are published by the US Department of Health and Human Services in the HIPAA Privacy and Security Rules, and a business associate agreement gets signed before a remote biller touches that information.

Where does a remote biller arrangement fall short in Practice Fusion?

A remote biller arrangement falls short in three places worth naming before the job description goes out, and none of them is a reason to skip the hire. The first one surprises practices most.

A biller can't bill what the provider didn't write. Charge quality is capped by note quality, so a practice with thin documentation gets a biller who spends the week querying instead of submitting, and the aged claims grow anyway. Fix the note template first, because the claim isn't where that problem started.

Experience in a platform isn't experience in your wiring. Where charges go, which clearinghouse the practice uses, who holds the payer logins and what the last biller left half-finished are local facts, so budget shadowing time rather than discovering the gaps after the first payer cycle. Narrowing a search to one platform plus one specialty plus a narrow schedule filters three ways at once, and something gives.

The practice still owns the decisions above the biller's desk. Payer contracts, credentialing, fee schedules and the choice of whether an outside service runs the money stay with the owner, and a biller works inside them.

On terms, rates run $10.00 to $12.65 an hour depending on the role, candidate background, schedule and location. Honest Taskers recruits in the Philippines, Latin America, India and Pakistan, and professionals work the client's US time zone and approved schedule. New clients may receive a two-week working trial with their first selected professional, subject to current service terms. Honest Taskers reports 99.6% average monthly retention, which matters on a billing desk because payer patterns live in one person's head. For the questions that separate genuine system experience from a line on a resume, see our guide to what EHR skills to look for in a virtual assistant.

Which sources support these Practice Fusion billing facts?

These Practice Fusion billing facts rest on three kinds of source, and the software vendor isn't one of them. Honest Taskers rates, recruiting geography, trial terms, retention figure and compliance posture come from the company's own published rate card and service terms. Medicare coding and billing rules come from the Centers for Medicare and Medicaid Services, obligations for handling protected health information from the US Department of Health and Human Services, and occupational wage data from the Bureau of Labor Statistics. The charge, claim, rejection, payment and ledger workflow above reflects general ambulatory revenue cycle practice rather than one organization's protocol. No claim volume, aged-receivable, collection-rate, turnaround or hours-saved figure appears anywhere on this page, because none was verifiable. Nothing here states which billing features the platform includes, which partners it connects to, or who owns it, for the same reason.

Practices that have settled how the billing work gets done and want to compare providers next can start with our ranking of the best virtual medical biller companies.

Request candidates with experience in your specialty and software.