Last updated: 2026-09-17

eClinicalWorks sits under a lot of mid-size ambulatory groups, and billing there runs on the same spine as the chart and the schedule, so the work a medical biller does looks different from billing run out of a system bolted on beside the record. The duties come first, because a group that can name them writes a sharper job description than one asking for help with billing. Multi-site groups come next, since five sites under one tax identification number carry the role differently than a solo office does. Then the visit itself, followed forward from the moment it lands on the schedule until the claim leaves. Tracing a denial backward to a registration error is that same chain read in reverse, and it's the skill that separates a careful biller from a fast one. Catching a coding mismatch before submission saves the round trip entirely. Secondary claims earn a section of their own, because a group with a Medicare-heavy panel lives inside coordination of benefits. An underpayment comes after, since a paid claim can still be a wrong claim. Credit balances and refunds are the work nobody volunteers for and every auditor asks about. Supporting several locations is where one remote hire holds up or drowns. Logins and permissions decide what that person reaches on day one, along with the clinical line they never cross. Where the arrangement breaks down closes the practical half, with what Honest Taskers charges and how it recruits. Which sources stand behind the facts on this page ends it.

What does a biller do in eClinicalWorks?

A biller in eClinicalWorks does the revenue work attached to a chart somebody else already wrote. The visit gets booked by a front desk assistant, documented by a provider, and coded from that documentation. Billers pick the account up where clinical facts turn into a claim, and hold it until the balance reads zero or the payer says no for the last time.

Seven duties fill most of a billing week inside a mid-size ambulatory group.

• Coverage checks ahead of the visit, confirming the plan on file is the plan that will pay the claim.
• Charge review, reading the provider's documentation against the charges that carry the claim.
• Claim edits, because the scrub list holds a claim back before any payer sees it.
• Submission and acknowledgment, since a claim sometimes leaves the practice and never reaches the payer.
• Payment posting, down to the contractual adjustment and the patient balance a paid claim leaves behind.
• Denial work, which starts by reading the remark code rather than by resubmitting the claim.
• Patient billing calls, explaining what a statement charged and why the plan paid the claim the way it did.

Two groups running the same software hand a remote biller different screens. Permissions, work queue names, charge entry rules and the order in which staff touch an account are local build decisions, so somebody with four years on the platform still needs a written map of yours. Ask for that map in week one, not after the first batch of rejections.

Which multi-site groups does a biller serve in eClinicalWorks?

A biller in eClinicalWorks serves mid-size ambulatory groups, most of them multi-specialty, and many of them running several service locations under one tax identification number. That shape explains why the billing job reads the way it does. Billers at a solo therapy practice never build a multi-payer secondary queue, because one provider and one assistant don't generate it. Hospital systems run claims through a central business office with tooling of their own.

Four group shapes account for most of the demand.

• Primary care groups of ten to sixty providers, where claim volume rather than claim complexity fills the day.
• Multi-specialty groups, where one biller covers internal medicine, cardiology and orthopedic claim rules in the same afternoon.
• Specialty groups with heavy Medicare panels, where secondary claim work and coordination of benefits fill the week.
• Groups that grew by acquisition, where each site arrived with its own registration habits and its own claim history.

Payer mix is the other half of the description. A group like this bills commercial plans, Medicare, Medicaid managed care plans, and sometimes workers' compensation and auto carriers, each with a filing window and an appeal address of its own. That's why breadth beats depth in any single plan for a biller working here.

Ownership shifts with size. In a ten-provider group one biller runs the whole cycle, from the coverage check through the final patient balance. Past roughly thirty providers the job splits into specialists, and somebody owns charge entry while somebody else owns denials and appeals. Settle which version you're hiring for before the job description goes out.

How does a biller follow a visit from schedule to claim in eClinicalWorks?

A biller follows a visit from schedule to claim by checking each handoff in order, beginning at the appointment and ending at the payer's acknowledgment. Because the chart, the schedule and the claim sit on one connected chain in this setting, every handoff leaves a trace a biller reads later.

Six handoffs carry a visit to a submitted claim.

• The appointment, where a wrong location quietly becomes a wrong place of service code on the claim.
• Registration, where demographics and the coverage on file either match the card or send the claim out wrong.
• The eligibility response, which confirms coverage for that date or returns a message somebody reads before the claim exists.
• Provider documentation, which sets the ceiling on what any code on the claim is allowed to say.
• Charge capture, where documented work becomes the charge line the claim will carry.
• The edit and submission step, where the claim clears the scrub list, leaves for the clearinghouse, and returns acknowledged or rejected.

What makes the chain worth walking is that it runs in both directions. A claim that paid teaches nothing. The one that didn't pay names the handoff that broke, and reading the trace back through those six points is most of the job.

How does a biller trace a denial back to registration in eClinicalWorks?

A biller traces a denial back to registration by reading the denial code first, then walking the account backward through the remittance, the eligibility response and the coverage record captured at check-in. The denial arrives three weeks after the visit. Its cause is three weeks old and sitting at a location the biller has never seen, and it's one registration field, such as the subscriber name, taken from the wrong side of the card.

Five denial reasons point straight back at a front desk.

• Coverage terminated before the date of service, which means the card on file was real and expired by the time the claim went out.
• Member identification numbers wrong by one character, which send the claim back without comment.
• Subscriber mismatch, where the patient is a dependent and the claim went out under the patient's own name.
• Coordination of benefits missing, where the payer holds the claim until the member confirms which coverage pays first.
• The wrong plan chosen from a dozen similarly named ones, which routes the claim to an address that isn't expecting it.

Correcting the account is the easy half. Update the coverage, rebill, and the money arrives. The half most groups skip is telling the location that caused it, by name, with the account number and the field that was wrong. One denial report grouped by location and reason turns a stack of corrections into a single conversation with one front desk supervisor. Without it the same registration error returns every week, and the biller becomes permanent cleanup. Readers new to the revenue cycle will find the general version in our medical billing guide.

How does a biller catch a coding mismatch before submission in eClinicalWorks?

A biller catches a coding mismatch before submission by reading the charge against the provider's own note rather than against the claim edit alone. An edit engine catches what it was built to catch. It doesn't know that the note describes one procedure while the charge says another.

Five mismatches show up again and again in ambulatory billing.

• Diagnosis codes that don't support the procedure billed, which send the claim back as not medically necessary.
• Modifiers missing on a second procedure performed the same day, which reads to the payer as a duplicate claim.
• Units that don't match the documented time or quantity, which invites payment on the claim at the wrong level.
• A place of service code carried over from the main office when the claim belongs to a satellite location.
• Drug identifier or dosage detail left off an injection charge, which the payer rejects before the claim is adjudicated.

Where the biller stops matters as much as what the biller finds. The mismatch gets flagged and routed to the coder or the provider who wrote the note. Nobody in a billing seat edits documentation, adds a diagnosis the record doesn't carry, or picks a higher level code because the payer pays better for it. That boundary isn't a style preference. It's the difference between a correction and a false claim. Patterns worth watching, grouped by provider and by reason, sit in our guide on how to reduce claim denials.

How does a biller handle a secondary claim in eClinicalWorks?

A biller handles a secondary claim by posting the primary payment and its remittance detail first, then sending the claim onward with that detail attached. Secondary payers process nothing until they see what the primary allowed, paid and left as patient responsibility, line by line.

Four things decide whether a secondary claim pays.

• Coordination of benefits on the account, naming which payer is primary and from what date.
• The primary remittance posted at line level, because a secondary payer reads allowed, paid and adjustment amounts per charge.
• Crossover status, since some primary payers forward the claim automatically and others leave the biller to send it.
• The secondary filing window, which starts at the primary remittance date rather than at the date of service.

Crossover is where money disappears quietly. Assume every claim forwards itself and you find a year-old pile of secondary balances nobody billed, half of them past filing by the time anyone looks. Checking forwarding status on each primary remittance takes seconds, and it's the cheapest habit in the whole role.

Medicare coding and billing guidance is published by the Centers for Medicare and Medicaid Services (Centers for Medicare and Medicaid Services, 2025), and a biller working Medicare balances reads that source rather than a payer representative's summary of it. Write down what the group settles in the hard cases, because a second biller hitting the same plan combination six months later shouldn't have to relearn it.

How does a biller work an underpayment in eClinicalWorks?

A biller works an underpayment by comparing what the payer allowed against the contracted rate for that code, that plan and that location before accepting the adjustment. An underpaid claim looks exactly like a paid claim on a report. Nothing flags it, so somebody has to go looking.

Four checks separate a real underpayment from a correct payment.

• The allowed amount on the claim against the fee schedule loaded for that payer and that contract year.
• Adjustment codes on the remittance, which say whether the claim was cut by contract, by bundling or by a downcode.
• The location on the claim, since a group with several sites sometimes holds different contracted rates by site.
• Appeal windows for a payment dispute, which run shorter on an underpaid claim than on a denial with several payers.

The trap here is the automatic contractual adjustment. Post the remittance, let the system write off the difference, and the underpayment vanishes into a write-off nobody reads again. Spot-checking a sample of paid claims each week against the contract catches a wrongly loaded rate months before a year-end reconciliation would.

Pattern matters more than size. One claim short by a few dollars isn't worth an appeal letter. The same code short by the same amount across a quarter is a contract problem, and it belongs in front of whoever negotiates with that payer rather than in a denial queue.

How does a biller manage credit balances and refunds in eClinicalWorks?

A biller manages credit balances and refunds by working the credit list on a fixed schedule and proving where each overpayment came from before any money leaves the practice. Credit balances aren't a bookkeeping curiosity. They're somebody else's money sitting in your account, and the rules about returning it don't care that the posting error was honest.

Four causes create most credit balances in a group practice.

• Duplicate payment, where the same remittance posted twice against one claim.
• Both plans paying as primary, which happens when coordination of benefits updated after the first payment posted.
• Patients paying an estimate at check-in, then the payer sending a payment larger than the estimate assumed.
• Posting errors, where a payment landed on the wrong account or on the wrong date of service inside the right one.

Direction of the refund is the part that goes wrong. Money a payer overpaid goes back to that payer, money a patient overpaid goes back to that patient, and a credit doesn't get netted against an unrelated balance on the same account unless the practice's own written policy allows it. Medicare overpayments carry their own reporting and return obligations, and a group sitting on aged credits during an audit answers for them whether or not anybody meant to keep the money.

The workable version is boring on purpose. Review the credit list monthly, write the cause beside each line, refund what's owed to whoever is owed it, and keep the aging short enough that the list never becomes a project.

How does a biller support several locations in eClinicalWorks?

A biller supports several locations by working one shared queue that carries the location on every account, rather than by running a separate process per site. One tax identification number across five service addresses is still five sets of front desk habits, and billing data is the only place those differences appear in a single view.

Five things vary by location even inside one group.

• Place of service and the facility address that tie a claim to the location where the visit happened.
• Payer contracts, since a location added by acquisition sometimes carries its own rates and its own participating plans.
• Provider enrollment per location, without which a clean claim still denies for a non-participating provider at that address.
• Registration quality, which moves with staffing and training at each location and surfaces as a denial pattern weeks later.
• Patient payment collected at check-in, which varies by location and changes how much balance is left to bill.

Reporting by location is what makes one biller workable across five sites. Denials grouped by location and reason become a short weekly note to each office manager, and the offices that read it stop appearing on it. The ones that don't keep showing up.

Escalation needs a name at every site as well. A biller who can't reach the person who registered the patient is left guessing, and a guess costs a rebill. For the wider administrative version of remote work in this platform, see our overview of how a virtual assistant works in eClinicalWorks.

Which logins and permissions does a remote biller hold in eClinicalWorks?

A remote biller holds a named login in the practice's own system, scoped to billing and to the accounts they work, alongside separate logins for the clearinghouse and the payer portals the group already uses. The practice grants every one of them a single account at a time, the same way it would for a new hire sitting in the back office.

Six items cover nearly every access conversation.

• Named user accounts, one per person, so the audit log shows which biller had access to which chart and when.
• Permission sets that give access only to billing work, covering charge review, claim submission, payment posting and approved adjustments.
• Clearinghouse access for claim status, rejection reports and acknowledgment files.
• Payer portal access for eligibility, claim status and appeal submission, issued per person rather than shared.
• Secure file transfer for a remittance or a coverage document, granted the same way as system access rather than through an email attachment.
• Revocation of every access on the offboarding day, run against each system including each payer portal.

The clinical line belongs in the same conversation. Honest Taskers staff do administrative and clinically adjacent work and never give clinical advice or make clinical decisions, so a biller reads a note to check whether documentation supports a charge and stops right there. The talent pool includes licensed nurses and physicians, which describes how the company recruits and not what a placement does. Professionals are HIPAA-trained under a dedicated compliance officer, with quarterly HIPAA and data privacy training, and a Business Associate Agreement gets signed when somebody will reach protected health information. Honest Taskers describes its own security environment as SOC 2 audit ready. For the wider set of systems a billing seat touches every day, see our rundown of medical billing tools and software.

Where does a remote biller arrangement break down in eClinicalWorks?

A remote biller arrangement breaks down in four places, and naming them before the job posting goes out costs less than meeting them in month two. None of the four is a reason to skip the hire.

Platform experience isn't experience in your build. Permissions, work queue names and charge entry rules were settled during your implementation, so a biller with years on the software still spends a week learning where your group put things.

A staffing hire doesn't own the billing outcome. Honest Taskers places people who work in your system under your direction, which leaves payer strategy, contract negotiation and the decision about what to appeal with your team. Billing companies that price on a percentage of collections take that ownership and charge for it, so a group that wants the outcome bought rather than staffed is shopping for a different model.

Nobody fixes a front desk they can't see. Registration errors keep arriving until a named person on site owns the correction, so the remote biller is half of a pair rather than a whole answer.

And a biller isn't a coder. The Bureau of Labor Statistics lists assigning clinical codes for insurance reimbursement among the duties of medical records specialists in its "Occupational Outlook Handbook" (Bureau of Labor Statistics, 2025), a separate occupation from claim follow-up. A group needing both hires both, or hires one and says which hat comes first.

On terms, Honest Taskers rates run $10.00 to $12.65 an hour depending on the role, candidate background, schedule and location. Recruiting runs 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, and replacement support is unlimited. Honest Taskers reports 99.6% average monthly retention, which matters in a billing seat because the payer knowledge somebody builds over a year lives with that person, not in a handover document.

Which sources stand behind these eClinicalWorks billing facts?

These eClinicalWorks billing facts stand on three separate sources, and keeping them apart is the point. Honest Taskers rates, recruiting geography, trial terms, retention figure, training and compliance posture come from the company's own published service terms. Medicare coding and billing guidance comes from the Centers for Medicare and Medicaid Services, business associate obligations from the US Department of Health and Human Services (US Department of Health and Human Services, 2025), and the medical records specialist occupation description from the Bureau of Labor Statistics. Everything above about charges, claims, denials, secondary billing, underpayments and credit balances reflects general US ambulatory revenue cycle practice rather than one group's build. No module name, screen name, menu path, version number or price for the platform appears anywhere on this page, because none of it was readable from the vendor's own documentation while this page was written, and a remembered detail isn't verification. Nor does any volume, turnaround or hours-saved figure appear anywhere on it.

Groups weighing a staffing hire against an outsourced service can start with our ranking of the best virtual medical biller companies.

Request candidates with experience in your specialty and software.