Charge capture is the process of identifying and recording billable services and supplies as accurate charges in a healthcare organization’s billing system. It connects the clinical record to the billing record: what happened, for whom, when, which provider performed it, and which charge belongs to that service.
A pharmacy can document a completed vaccine visit yet have no corresponding charge in its medical billing system. It can also have a charge created automatically and a second one entered manually for the same service. Charge capture includes finding both discrepancies so the team can resolve missing charges and prevent duplicate billing.
Charge capture, charge entry and medical coding
People sometimes use these terms interchangeably because one person or software screen can handle several of them. They describe different work.
Charge capture identifies the services and supplies that belong in billing and connects them to the correct encounter. Charge entry records the resulting billing details in the financial system. A charge can be entered manually or created from structured clinical data.
Medical coding assigns the appropriate codes to the documented diagnoses, procedures and supplies. For professional medical claims, that can involve CPT, HCPCS Level II and ICD-10-CM codes. Our CPT versus ICD-10 guide explains their different roles. A billing template can suggest codes, but staff still need to confirm that they describe the actual service.
Claim submission sends the assembled claim to the payer through the configured route. Adjudication is the payer's processing decision about that claim. A charge saved in a billing system hasn't necessarily been submitted, and a submitted claim hasn't necessarily been paid. CMS describes electronic billing as an exchange with its own format and content requirements.
These activities can overlap. A clinician might select a procedure during documentation, with the system creating a charge that a biller reviews later. Another organization may send completed documentation to a coding or billing team before any charge is entered. The relevant question is where the performed service becomes an identifiable billing item in your own system.
What information belongs with a charge?
For a professional medical claim, a useful charge record connects the patient and encounter to the service date, performing provider and location, procedure or supply and charge amount, with diagnosis, modifiers and units as applicable to the service and payer. The clinical record supplies the supporting facts; the billing configuration supplies approved mappings and prices. Requirements vary with the service and payer.
Keep the charge amount separate from the expected payment. The submitted charge is the provider’s billed amount for that service line. A payer's allowed amount, adjustments, payment and patient responsibility are determined through the applicable contract and claim processing. Increasing the recorded charge doesn't establish that the payer owes more.
Hospitals maintain a charge description master, or chargemaster, listing individual items and services with their established gross charges. CMS explains the distinction between those undiscounted charges and other prices. A pharmacy's professional medical billing system may instead use service templates and a fee schedule. In either case, a catalog entry must be matched to the service actually performed; its presence in the software doesn't establish separate coverage.
For Medicare, CMS's medical review guidance explains that reviewers assess coverage, coding, payment and billing using supporting documentation. When the note and proposed charge disagree, return the specific discrepancy to the person who can establish what occurred. Don't fill a missing clinical fact by selecting the most convenient billing option.
How a pharmacy service reaches billing
A pharmacy may document clinical services in a different application from the dispensing system. Its medical claims can also follow a different route from prescription claims. Confirm the payment arrangement and benefit for the service before deciding which system should create the charge. The medical versus pharmacy benefit guide covers that distinction.
For Medicare diabetes self-management training (DSMT), the CDC's DSMES medical billing playbook for pharmacies describes pharmacy software, clearinghouses and medical billing services as claim-submission options. A pharmacy using that arrangement needs to know when the billing team has received the completed encounter and what remains on hold. Sending a note and receiving confirmation that a claim was submitted are separate events.
Start with the encounter, charge and claim views already available in the pharmacy's tools. If the clinical and billing records aren't linked, the needed improvement is a reliable handoff between those records. Creating another list of patient information can add work without showing whether billing received the service.
Who is responsible?
The clinician establishes what was performed and documents the supporting facts. The coding or billing team applies the relevant billing requirements and resolves missing or inconsistent charge information. A manager or designated billing lead makes sure completed services haven't disappeared between those responsibilities.
In a small pharmacy, one person may hold several roles. Even then, distinguish a clinical clarification from a configuration fix. A biller can correct an incorrect service mapping; only someone with the appropriate knowledge and authority should clarify an incomplete clinical record through the organization's amendment process.
One vaccine visit, two possible billing problems
Consider a hypothetical pharmacy with an established medical-billing arrangement for a particular vaccine service. The pharmacist completes the encounter documentation. Later, the billing lead sees the visit marked complete but finds no linked medical claim.
The lead first checks the actual service record and existing billing history. In this example, the patient, service date, vaccine product and administration are documented, and the pharmacy's applicable enrollment and payer requirements have already been verified. The lead finds that an automatic charge-creation rule excluded this service, so no charge reached the billing queue.
The team can now create and review the missing billing item through the supported process, then correct the rule for future eligible encounters. Before changing the rule broadly, it checks whether the exclusion was intentional for another payer or service. The fix is supported by the documented encounter and the verified payment route, rather than the appointment's “complete” label alone.
Now change one fact: the transmission history already contains a claim for that same service, but the appointment doesn't display the link. Creating another claim would repeat work already sent. The lead reconciles the existing claim with the encounter and corrects the linkage or status display instead. If the submitted claim itself needs a change, the team follows the payer's correction process; our claim frequency code guide explains the distinction between an original, replacement and void.
If the team can't establish whether the service was performed, whether a prior submission covers it, or which billing arrangement applies, it holds the proposed charge for review. A missing link is a reason to investigate those facts, not enough evidence to send another bill.
Finding missed, delayed and duplicate charges
Review completed clinical encounters alongside their charge or claim records for the same service period. Comparing only the number of appointments with the number of claims is unreliable: some appointments are canceled, some services aren't separately billed, and one claim can contain multiple service lines. Match the underlying patient, encounter, date and service through the identifiers your systems support.
For an encounter without an expected billing item, determine whether the service is awaiting documentation, held for a billing requirement, already billed elsewhere in the configured workflow, or intentionally excluded. Record the specific unresolved issue in the existing task or billing queue when another person must follow up. A hold needs an owner who can resolve that issue; it shouldn't disappear into a generic “not billed” total.
Look in the other direction too. A charge with no supporting encounter, the wrong service date or a repeated service line requires review even when the overall claim count looks correct. These checks help distinguish a true omission from a duplicate or incorrect entry. For a submitted claim that hasn't paid, check its current status and payer response to choose the appropriate correction or payment follow-up. Nonpayment alone doesn't establish a missing charge.
Measuring delay without hiding missing services
Charge lag measures the interval between the service date and the charge's posting date. HFMA's MAP Keys define the measure using posting and service dates for charge codes. Keep that separate from the interval to claim submission or payment, which answers a different question.
Use the same definition and service population when comparing periods. A shorter average lag among posted charges can coexist with completed encounters that never generated a charge. Review that unresolved group alongside the lag measure, and separate documentation holds from mapping failures so the team can address the cause. Set an internal review cadence around service volume and the applicable payer filing requirements; there isn't one pharmacy-wide deadline established by the term “charge capture.”
What to ask charge-capture software to demonstrate
A product may capture charges through manual entry, mobile entry, a service template, a clinical-data interface or automated suggestions. Before buying another tool, ask the current supplier to demonstrate which of those functions already exists and what event triggers it. A signed note, a recorded administration and a booked appointment are different triggers with different implications.
Use a fictional completed encounter to follow the service into its charge and claim. Have the supplier show where staff can review the source facts, adjust an incorrect mapping and see whether the claim was submitted. Then repeat the demonstration with a missing clinical detail, a canceled service and an already submitted claim. Those variations reveal how the system handles exceptions and duplicate risks.
Ask who maintains codes, fee schedules and payer-specific templates, and whether staff can see the history of a changed or canceled charge. If the clinical and billing tools are separate, identify who resolves a failed transfer and how the receiving system confirms receipt. An automated suggestion that lacks enough evidence should remain available for review rather than silently become a submitted claim.
When comparing products, include setup, interfaces, training, support and any separate claim-transmission charges in the quote.
