Do medical billers assign CPT and ICD-10-CM codes?

Sometimes one employee performs both coding and billing, especially in a small practice, but the functions are different. Coding assigns supported codes from the clinical record. Billing uses the coded encounter to construct, transmit, reconcile, and follow the claim. A biller should route a coding question to the appropriate coding process rather than changing a code only to make a denial disappear.

What is the difference between a clearinghouse rejection and a payer denial?

A clearinghouse rejection usually means the transaction failed before normal payer adjudication because of a data, format, identifier, or routing problem. A denial means the payer processed the claim and returned an adverse payment decision. Rejections are generally corrected and retransmitted; denials may require correction, documentation, policy review, or an appeal depending on the reason.

What does A/R aging mean in medical billing?

A/R aging groups unpaid balances by how long they have been outstanding, often into buckets such as 0–30, 31–60, 61–90, and older. Age is only one priority signal. Filing deadlines, appeal deadlines, dollar value, payer status, missing documentation, and whether another team must act first can make a younger account more urgent.

Is payment posting an entry-level medical billing task?

It can be. The important skill is understanding what the remittance means rather than merely typing the payment amount. New staff should learn how payments, contractual adjustments, patient responsibility, and denials are represented on the ERA and how the organization handles unmatched or ambiguous lines before they work independently.

What a Medical Biller Actually Does All Day

A medical biller is not simply the person who “sends the bill.” The job is queue management across the revenue cycle. A normal day can include claims that never passed a clearinghouse edit, claims that reached a payer and came back denied, electronic remittances that need to be posted correctly, and old accounts whose next action depends on filing limits or payer follow-up. In a small physician office, the same person may also verify insurance, enter charges, answer patient billing questions, and correct registration problems. In a larger organization, those duties are divided across specialized teams, but the biller still needs to understand what happened before and after the claim reaches the payer.

8:00 a.m.: clear the failures that happened overnight

The first useful screen is usually an exception queue. Clearinghouse acknowledgments can show that a claim never made it to the payer because a required identifier, subscriber field, diagnosis pointer, or formatting rule failed. That is different from a denial: a rejection at this stage means the transaction still needs to be corrected and transmitted successfully. A careful biller opens the underlying account rather than repeatedly clicking “resubmit.” The aim is to find the bad source field, correct it once, and make sure the same defect is not being copied into every new claim for that patient, provider, or plan.

A realistic biller day, not a classroom checklist

08:00 — review clearinghouse rejections, eligibility exceptions, and claims held by front-end edits
09:30 — validate new charges, provider identifiers, payer order, diagnosis pointers, modifiers, units, and place of service before release
11:00 — work denials with appeal or timely-filing risk before routine low-dollar follow-up
13:00 — post ERA/EFT activity, contractual adjustments, denials, and patient responsibility to the correct service lines
14:30 — work 31–60, 61–90, and older A/R using payer status, value, deadline, and last action rather than age alone
16:00 — run an exception report and leave dated notes so tomorrow’s queue starts with known next actions

Charge entry is quality control, not copying numbers

In many offices, charge entry is where a biller confirms that the claim can be constructed from the documented encounter. The biller may not be the person deciding the code assignment, but should recognize obvious mismatches: the wrong rendering provider, a missing referring NPI where required, a diagnosis pointer that does not point to the intended diagnosis, a line with the wrong number of units, or a plan that should not be primary. The NUCC 1500 form and its 837P crosswalk are useful because they show how familiar paper-form concepts map into the electronic professional claim. The screen may look different in every practice-management system; the data relationships do not.

After adjudication, the work changes from submission to reconciliation

When an ERA arrives, the biller has to distinguish the amount paid from the amounts adjusted. Group codes, Claim Adjustment Reason Codes, and Remittance Advice Remark Codes explain why the payer changed a line and whether the remaining amount is contractual, patient responsibility, or something that needs follow-up. Posting a remittance incorrectly can create a second problem: a patient may receive a statement for an amount the contract says the provider must write off, or an appealable denial can disappear into an adjustment bucket. A strong biller therefore treats payment posting as reconciliation, not data entry.

A/R work is where judgment becomes visible

A/R follow-up should not be a blind oldest-to-newest calling list. A 92-day claim with a short contractual deadline, a high-dollar denial waiting on records, and a new low-dollar claim with no exception should not receive equal attention. Billers learn to prioritize by filing or appeal risk, amount, denial category, payer responsiveness, and whether another team must act first. Notes matter because the account may be touched by a different person next week. A useful note records what source was checked, the payer reference or trace number, what was learned, what was sent, and the exact date or event that should trigger the next follow-up.

Where the coder stops and the biller takes over

The coder’s central question is whether the diagnoses and services are represented correctly from the clinical documentation under the applicable coding rules. The biller’s central question is whether the claim carrying those codes is complete, routed correctly, adjudicated as expected, and reconciled to the correct payer and patient balances. In a small practice, one employee may do both jobs, but it is still useful to separate the decisions. A biller should not invent a code change simply because a payer denied a line, and a coder should not be expected to solve subscriber order, clearinghouse routing, or unpaid A/R.

What employers notice in a new biller

Speed matters only after the workflow is understood. Supervisors notice whether a new biller can tell a rejection from a denial, read a remittance without moving every unpaid dollar to the patient, find proof of submission, document a payer call so another person can continue it, and escalate a coding or authorization question instead of guessing. Those skills are more transferable than memorizing the menu path in one software product. If you are evaluating the career, ask an employer what queues you would own in the first 90 days, how denial work is assigned, which reports drive A/R priority, and who reviews exceptions. The answers reveal far more about the real job than the title “medical biller.”

The quiet skill is knowing when not to touch the account

One of the hardest habits for a new biller is resisting the urge to “fix” every unpaid line personally. A claim held because the subscriber ID is wrong belongs with registration data; a denial that turns on documentation may need coding or clinical review; a payment that cannot be matched may belong in a cash-posting exception queue. The biller still owns the follow-through, but ownership does not mean changing fields outside the role’s authority. A useful daily note therefore names both the next action and the next owner. That distinction is what keeps an A/R queue from becoming a pile of silent edits that nobody can reconstruct later.

This is also why a good first job teaches escalation paths, not just keystrokes. Ask who can change demographic data, who can alter codes, who approves write-offs, who handles authorization disputes, and who owns patient complaints. Those boundaries reveal whether the organization has a real revenue-cycle process. They also give a beginner a safer way to work quickly: classify the failure, collect the evidence, route it correctly, and set a dated follow-up instead of improvising a correction.