Last updated: 2026-09-17

Billing inside a health system big enough to run Epic breaks into more pieces than billing inside a two-provider clinic, and a job posting that ignores the split hires the wrong person. What a biller does on one of those teams comes first, because the honest answer is one slice of the revenue cycle rather than all of it. The divide between professional billing and hospital billing follows, since a single visit can produce two claims under two rule sets. Claim edit queues come next, because a queue is where a claim waits when an internal rule caught it before a payer could. Getting a clean claim out the door covers what has to be true at submission, meaning patient identity, active coverage, any authorization, the charge itself and the filing deadline. Payment posting and remittance reconciliation follow, where the automated part is easy and the exceptions become somebody's morning. Denials earn their own section, since a reason code is a diagnosis rather than a verdict. Aged accounts receivable comes after that, with the payer, dollar and deadline math deciding which account gets a touch today and which waits. Patient balances sit at the end of the cycle, once every payer has finished and the guarantor account carries what's left. Access is the section a hiring manager should read twice, because one login reaches an enormous record set. What a biller can't do closes the scope question. The limits of hiring a remote biller for Epic cover what a staffing arrangement won't fix, alongside the Honest Taskers terms, and the sources behind every fact here end the page.

What does a biller do in Epic?

A biller in Epic works one slice of the revenue cycle rather than all of it, because a health system that size divides the cycle among teams, each with its own work queues. The single-desk version of the job, where one medical biller posts the charge, releases the claim, calls the payer and mails the statement, belongs to small practices. At a hospital-affiliated group the work is cut by function, by billing stream and by payer group. New billers inherit a queue, not a caseload.

Six functions cover most billing seats at that size.

• Charge review, where a charge waits until somebody confirms the codes, modifiers and service date hold up before it becomes a claim.
• Claim edit work, where a claim stopped by an internal or payer front-end rule sits until a biller corrects it.
• Payment posting, where a remittance lands against the claim, the clean lines post themselves and the exceptions need a person.
• Denial management, where a denied claim gets classified, corrected or appealed inside the payer's deadline.
• Accounts receivable follow-up, where a claim with no payer response gets a status check and a documented next step.
• Patient billing, where the balance left after the claim pays moves to the guarantor account and a statement.

Which of the six a biller holds is the first thing to settle in an interview, and a generic job posting skips it. Builds are local too. Two health systems on the same EHR name queues differently and write different charge review rules, so a biller with four years elsewhere, like any virtual assistant joining a billing team, still needs a written map of yours.

How does a biller split professional billing from hospital billing in Epic?

A biller splits professional billing from hospital billing by working one stream or the other, because the two ride on different claim forms, different code sets and different payer rules even when they describe the same visit. Professional billing covers what the clinician did, meaning the exam, the procedure, the interpretation. Facility billing covers what the building supplied, meaning the room, the nursing hours, the equipment and the supplies. One outpatient surgery throws off a professional claim from the surgeon and a facility claim from the hospital, and a payer pays the first while denying the second more than anyone outside billing expects.

The differences run deeper than the claim form.

• Professional billing goes out on the CMS-1500 claim format, carrying procedure codes, modifiers and a place-of-service code matching where the charge happened.
• Facility billing goes out on the UB-04 claim format, carrying revenue codes and a bill type, and for a Medicare inpatient stay the payment ties to the diagnosis-related group rather than each charge line.
• Coverage checks differ, since a plan's facility benefit and authorization rule aren't the professional benefit behind the claim for the same patient.
• Denial patterns differ, so a claim denial a professional biller reads every week may never reach a hospital biller's queue.

The Centers for Medicare and Medicaid Services publishes the Medicare coding and billing rules that sit behind the two streams.

Hiring follows the split. Job postings that say medical biller and mean facility work collect professional billers, who then spend a month learning revenue codes nobody mentioned. Name the stream in the first line of the job description, name the service areas, and say whether the seat touches inpatient accounts.

How does a biller work a claim edit queue in Epic?

A biller works a claim edit queue by opening the oldest or highest-dollar item, reading which rule stopped the claim, correcting the fact behind that rule at its source, and releasing the claim once the underlying record is right. Catching a claim before submission costs far less than fixing a denial after it.

Five edits account for most of a working day.

• Coverage that wasn't active on the service date, or a primary and secondary payer recorded in the wrong filing order.
• A subscriber identifier or member name that doesn't match what the payer holds, which rejects a claim before adjudication.
• A missing or expired authorization, or one the payer approved for fewer units or a date span that doesn't cover the charge.
• A billing provider not enrolled with that payer, or the wrong national provider identifier on the account.
• A code combination the payer's edit rejects, a missing modifier, or units above what the plan allows.

Fixing at the source separates a biller who clears a queue from one who recycles it. Overtyping a plan on the claim and leaving the registration record wrong buys one clean claim and the same edit again next week. So the correction belongs in the account, and the pattern belongs in a note to whoever owns registration or coding.

Queues at this size get carved by payer, facility and service area, so a biller is measured on the age of one queue rather than on the whole receivable. Which records a biller may correct is a permission question the client settles before day one, and nobody should be guessing at it in week two.

How does a biller get a clean claim out the door in Epic?

A biller gets a clean claim out the door by confirming six facts before release, and the order matters because each one blocks the next. Identity, coverage, authorization, provider enrollment, codes and the filing deadline decide whether a claim adjudicates or bounces.

Six checks carry a claim through a payer's front end.

• Patient identity and demographics matching the payer's member record, since a name or birth date mismatch rejects the claim outright.
• Coverage active for the service date, with plan, subscriber and payer filing order recorded so a secondary claim follows the primary.
• An authorization or referral on file where the payer demanded one, carrying the number, the approved units and a covering date span.
• A billing provider enrolled with that payer under the right identifier, tax identification number and place of service for the charge.
• Codes and modifiers matching the documentation, so the payer reads what happened rather than what was scheduled.
• Submission inside the payer's timely filing window, the one deadline no appeal reliably rescues.

Most of what breaks a claim was broken before a biller ever saw it. Registration collected last year's plan, nobody asked about a second policy, the authorization covered four visits and the patient came six times. Reporting those patterns back by department saves more claims than fixing them quietly. Outside a health system the same cycle sits with one or two people, and our medical billing guide walks it end to end.

Payer count is what makes this hard at a health system. Groups contracted with dozens of plans across Medicare, Medicaid managed care, commercial coverage, workers compensation and veterans benefits hold dozens of front-end rule sets, and the habit that clears one payer's edit trips another's.

How does a biller post payments and reconcile remittances in Epic?

A biller posts payments and reconciles remittances by matching every electronic remittance advice to the deposit that funded it, letting automated posting take the clean lines, and working by hand the ones nothing matched.

Five exceptions account for most of the manual work.

• A remittance line that won't match an open account, because the claim number the payer holds differs from what went out.
• A partial payment where the contractual adjustment has to be separated from the balance a secondary payer or the patient still owes.
• A takeback, where the payer recoups an earlier payment by offsetting it against today's deposit and the account has to be reopened.
• A zero-pay remittance where the payer sent denial codes instead of money, which belongs in the denial queue the same day.
• A credit balance created when a second payer pays a charge the first already covered, which turns into a refund with a deadline.

Reconciliation to the bank keeps posting honest. A deposit that doesn't tie out to the posted batch means either money that landed nowhere or money posted twice, and each costs more to unpick a month later. At a health system one check covers professional and facility claims together, and the remittance file lands days apart from the funds.

Underpayment detection deserves its own pass through the day's payments. A payer paying less than its contracted rate posts as a payment rather than as a denial, so nobody notices unless somebody compares the allowed amount against the fee schedule.

How does a biller work a denial in Epic?

A biller works a denial by reading the claim adjustment reason code and remark code on the remittance, classifying what went wrong underneath it, then choosing between a corrected claim and a formal appeal, because those paths carry different deadlines and need different evidence.

Six families cover most of what lands in a denial queue.

• Eligibility denials, where coverage wasn't active or the payer on the claim wasn't the payer on the service date.
• Authorization denials, where no authorization existed, the number didn't match, or the service ran past the approved span.
• Coding denials, where a code combination, a missing modifier or a diagnosis that doesn't support the procedure stopped the claim.
• Medical necessity denials, where the payer's own coverage policy says the service wasn't covered for that diagnosis.
• Coordination of benefits denials, where the payer wants another plan billed first or wants updated other-coverage details from the patient.
• Administrative denials for a duplicate claim, a missing attachment, or a filing deadline that already passed.

An appeal needs more than a resubmission. The payer's own form or portal, a letter naming the policy the denial cited, records showing the service happened as billed, and a submission inside the appeal window are the floor. Track outcomes by denial family, since that's the only way anyone learns which department keeps producing the same denial. The appeal packet itself gets more room in our guide to denial management and how a virtual assistant works denials and appeals.

How does a biller follow up on aged accounts receivable in Epic?

A biller follows up on aged accounts receivable by sorting open accounts by payer, aging bucket and dollar value, then working the ones where a touch today changes the outcome before a deadline closes. Age by itself is a weak sort. A ninety-day balance with a payer that allows a year to file is a different problem from a sixty-day balance with an appeal clock already running.

Four moves make up nearly every follow-up touch.

• An electronic claim status check, which answers whether the payer has the claim at all before anyone waits on hold.
• A payer portal lookup, which shows adjudication detail and the denial reason the remittance abbreviated.
• A phone call for the accounts a portal won't explain, ending with the payer's reference number, a representative's name and a promised date.
• An escalation to the payer's provider representative or to the contracting team when one denial pattern hits many accounts at once.

Documentation is what makes the next touch worth anything. Accounts move between billers at a health system, so a note reading "called payer" without a date, a reference number and a next step wastes whoever picks it up.

Write-off authority needs a rule and a threshold. Unlimited adjustment rights make a control problem, and no rights at all clog the queue with balances that cost more to chase than to clear. Set the dollar line, name who approves above it, and read the adjustment report monthly. The judgment behind those calls is one of the things our rundown of medical billing skills covers in the hiring context.

How does a biller handle a patient balance in Epic?

A biller handles a patient balance by touching it only after every payer has finished, moving what's left to the guarantor account, and checking that adjustments and coverage posted correctly before a statement leaves the building. The most common patient billing mistake isn't a blunt phone call. It's a statement mailed while a claim is pending, or while a secondary payer was never billed.

Five checks belong in front of every statement.

• Every payer on the patient's account adjudicated, with the secondary claim sent and coordination of benefits recorded.
• The contractual adjustment posted, so the patient sees the allowed amount instead of the gross charge.
• An itemized breakdown ready to send, since a patient asking what a charge line means is asking a fair question.
• Payment plan terms written down, covering the monthly amount, the start date and what happens when the patient misses one.
• Financial assistance screening offered where the organization publishes a charity care policy, so a patient who qualifies doesn't reach collections first.

The conversation is where a remote biller earns the seat. Somebody calling about a balance wants to know what the payer applied to a deductible, why this visit cost more than the last, and what happens next. Answer those three, stay inside the script for anything clinical, and route a medical necessity question elsewhere.

Bad debt referral needs written rules too. How many statements, how many days, which balances go to an outside agency, and which get held because a financial assistance application is open. Every statement is also a disclosure of protected health information, governed by the HIPAA Privacy and Security Rules the US Department of Health and Human Services publishes.

What access does a remote biller need in Epic?

A remote biller needs a named account in the client's own environment, a security template the client's access team assigns, the billing stream and service areas the seat covers, named work queues, and a connection method the client controls.

Six controls define a remote billing seat.

• A named user account for one biller, never a shared login, so the audit log shows who opened which account.
• A security template limiting what the biller can adjust or write off, with a dollar threshold above which somebody else approves.
• Scope by billing stream and by facility, so a professional biller isn't browsing an entire hospital's records.
• Named work queues rather than open search, because a biller working from a queue makes minimum necessary access easy to prove.
• Connection through a remote method the client controls, such as a virtual desktop or a VPN, with multi-factor authentication every time the biller logs in.
• A revocation step written into offboarding and run the same day, against every system the biller could reach.

One login reaches a record set covering every patient the organization has seen, so minimum necessary stops being a policy sentence and becomes a build decision. Settling which screens a remote hire reaches is the same conversation our explainer, can a virtual assistant work in your EHR, walks through.

Honest Taskers professionals are HIPAA-trained under a dedicated HIPAA compliance officer, with quarterly HIPAA and data privacy training, and a Business Associate Agreement is signed when a professional will access protected health information. Remote working conditions are screened before placement, covering a dedicated password-protected work computer, a minimum internet speed with a backup connection, power backup and a private workspace. Honest Taskers describes its security environment as SOC 2 audit ready.

What can a biller not do in Epic?

A biller cannot make a clinical decision, assign a code the documentation doesn't support, or change a clinical record to make a claim pay, and no filing deadline moves that line. The boundary sits at judgment rather than at a screen. Reading a payer's coverage policy and reporting what it says is clerical. Deciding that a service was medically necessary is not.

Five things stay outside the billing seat.

• Choosing or changing a diagnosis or procedure code on a claim beyond what the documentation and the assigned coder support.
• Judging medical necessity on a denied claim, since that judgment sits with the clinician and with the payer's own reviewer.
• Editing, adding to or backdating clinical documentation to support a charge already on a claim.
• Waiving a copay, a deductible or a claim balance outside the organization's written policy and approval thresholds.
• Giving a patient clinical advice during a call about a claim or a balance, however fair the question sounds.

Honest Taskers staff do administrative and clinically adjacent work and never give clinical advice or make clinical decisions. The talent pool includes licensed nurses and physicians, which describes how the company recruits rather than what a placement does, so a nurse working your denial queue is doing administrative work under your protocols. Published occupational descriptions draw the same line. The US Bureau of Labor Statistics groups billing and posting clerks with financial clerks in its "Occupational Outlook Handbook" (Bureau of Labor Statistics, 2025), where the listed duties are preparing bills, posting payments and keeping financial records rather than clinical judgment.

What are the limits of hiring a remote biller for Epic?

The limits of hiring a remote biller for Epic come down to three, and none of them argues against hiring one. Access provisioning is the first.

Getting a remote biller into a health system's environment takes approvals the hiring manager doesn't control. A security template gets chosen, training gets finished, attestations get signed, and a queue assignment gets approved by people in three departments. Plan for weeks rather than days.

Platform experience isn't your build. Queue names, security templates, charge review rules and work list ownership are local decisions, so a biller who spent three years in the same system elsewhere still needs a map of your setup and a week beside somebody who knows it.

A biller fixes claims and doesn't fix the process that broke them. Registration errors, missing authorizations and late charge entry start in departments a remote biller never works in, so somebody inside has to own the upstream repair. Billing companies taking a percentage of collections own the outcome; a staffing arrangement hands you a person and leaves the outcome with your team.

On terms, Honest Taskers recruits in the Philippines, Latin America, India and Pakistan, and its professionals work the client's US time zone and approved schedule. Rates run $10.00 to $12.65 an hour depending on the role, candidate background, schedule and location, which puts twenty hours a week at roughly $800 to $1,012 a month and forty hours at roughly $1,600 to $2,024. 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 for a billing seat because payer knowledge and queue habits live in the person rather than in a handover document. For the wider view of remote support here, read how a virtual assistant works in Epic.

Where do these Epic biller facts come from?

These Epic biller facts come from three separate places. Honest Taskers rates, recruiting geography, time zone policy, trial terms, retention figure and compliance posture come from the company's own published rate card and service terms. Claim form requirements and Medicare billing policy come from the Centers for Medicare and Medicaid Services, business associate obligations from the US Department of Health and Human Services, and the clerical occupation description from the Bureau of Labor Statistics. Everything above about queues, edits, remittance exceptions, denial families and follow-up reflects general revenue cycle operations at hospital-affiliated organizations rather than any one build. No screen name, menu path or module name for the platform appears here, because those details are local and can't be verified from outside. Nothing here carries a claim volume, a turnaround time or an hours-saved figure either.

Organizations weighing a staffing arrangement against an outsourced billing service can compare providers in our ranking of best virtual medical biller companies.

Request candidates with experience in your specialty and software.