How charge entry and claim submission work

Charge entry rarely appears on a list of revenue cycle problems, because nothing about it looks broken. Claims go out. Money comes back. The trouble is upstream of the reports everybody reads: a claim submitted eleven days after the service was rendered is already eleven days old when the payer receives it, and no amount of follow-up gets those days back.

It is the cheapest problem in the cycle to fix, and the least often measured.

Measure the lag first

Before changing anything, count the days between date of service and date of submission, by provider and by location. The distribution matters as much as the total: where a few outliers — often one provider or one service line — carry most of the delay, that is a different problem from a slow process.

That distribution matters more than the average. A practice with a two-day median and one provider running at three weeks does not have a charge entry problem; it has a documentation problem with one person, and hiring capacity will not solve it.

What the seat actually does

• Takes the day’s encounters and enters procedure and diagnosis codes, units, modifiers, place of service, rendering and billing provider, and referring provider where required.
• Checks the charge against the eligibility record and the authorization record already on the account.
• Runs the claim through the scrubber and clears the edits it is authorized to clear.
• Submits, and confirms acceptance — at the clearinghouse and, where available, at the payer.
• Works clearinghouse rejections the same day.
• Reconciles the day’s schedule against the day’s charges, and reports anything seen but not billed.
• Queries the clinician or coder where documentation does not support what is being billed.

The sixth line is the one most often left out of a job description and the one that finds money nobody knew was missing.

Clean beats fast

There is a temptation to judge this queue purely on speed, and speed matters — but a claim that leaves quickly and comes back rejected has not saved anybody time. It has consumed a submission cycle, a correction, a resubmission and an entry in somebody’s worklist.

Scrubbing before submission is where the trade sits. The checks worth building in are the boring ones: the payer identifier matches the plan verified at eligibility, the authorization number and date range are on the claim where required, the modifier set matches the code combination, the place of service matches where the service was actually rendered, the rendering provider is enrolled with this payer, and the diagnosis supports the procedure at the level the payer expects.

Each of those takes seconds at entry and a fortnight to resolve after a denial.

Rejections are a different queue

A clearinghouse rejection is not a denial and should never sit in a denial worklist. It failed a format or eligibility edit before adjudication, which means it can usually be corrected and resubmitted within hours by the person who built it.

The failure mode here is a rejection report nobody owns. Files come back, nobody opens them, and a fortnight later a batch of claims that were never actually received starts appearing on the ageing report as though a payer were sitting on them. Assign the rejection report to the charge entry seat, with a same-day standard, and this category of loss disappears.

Where documentation becomes a billing problem

Charge entry is the first point at which somebody outside the exam room reads what was recorded, and therefore the earliest and cheapest moment to ask a question. A note that does not support the level being billed, a missing laterality, an absent time statement on a time-based code — all of these are trivial to resolve the same week and expensive to resolve after a payer disputes them a year later.

This requires a query route that clinicians will actually use: short, specific, and not a meeting. What it must never become is the seat deciding for itself what the clinician meant.

What to define before handing over the queue

What the seat may correct alone

Obvious transposition, a missing place of service, a payer identifier that does not match the verified plan — most practices are comfortable with these being fixed. Code selection is not one of them. Draw the line explicitly.

The submission schedule

When batches go out and by when the day’s charges must be entered. “Same day” and “next business morning” are both workable standards; “promptly” is not.

The rejection standard

Who works rejections, by when, and what happens to one that cannot be corrected without clinical input.

The missing-charge reconciliation

Which schedule report is the source, who receives the exception list, and what the expected response time is.

The query route

How a question reaches a clinician, in what format, and what happens when it is not answered within a defined period.

How to assess it

• What is charge lag by provider this month, and is the distribution tightening?
• What proportion of claims are accepted on first submission?
• How quickly are rejections corrected, and are any older than a day?
• How many services appeared on the schedule with no corresponding charge, and what happened to them?
• Which scrubber edits recur, and can they be prevented at entry rather than caught?
• Are queries to clinicians being answered, and within what period?

When outsourcing makes sense

Charge entry suits a dedicated offshore seat particularly well because it is daily, rules-based work with a clear finish line, and because it benefits from being done by somebody whose entire day is that queue. It also benefits from time zone difference: charges entered overnight are ready when the office opens.

Questions worth asking a provider:

• Will the seat work in your billing system, or produce a file somebody has to import?
• Who owns clearinghouse rejections, and to what standard?
• Is the schedule-to-charge reconciliation part of the service?
• What is the daily handover — what do you receive each morning?
• Where is the line between correcting an entry error and changing a code?
• Is it a dedicated full-time seat, or shared capacity?

How Soft Home Global staffs this

Soft Home Global provides trained full-time back-office seats from Rawalpindi, Pakistan. Charge entry and claim submission is published at $1,500 per seat per month, billed per seat with a one month minimum.

The seat works inside your system on US hours: entering the day’s charges to your standard, checking each claim against the eligibility and authorization records already on the account, clearing the scrubber edits you authorize it to clear, submitting, confirming acceptance, working rejections the same day, and reconciling the schedule against entered charges so nothing rendered goes unbilled.

Anything that requires a coding decision or a clinical clarification is queried rather than assumed, on the route you define. Where the practice also uses a coding seat, the two sit next to each other, so a query is a handoff rather than an email into a general inbox.

The number to pull first

Charge lag by provider for the last ninety days, and first-pass acceptance rate for the same period. Those two numbers describe almost everything that happens before a payer has any say in the matter, and both are entirely within the practice’s control.

If the lag has a long tail, the answer is not more billing capacity. It is finding out why one part of the practice takes three weeks to close a note.