Charge Capture Reconciliation: Matching Completed Encounters to Submitted Claims

A medical practice completes 45 patient encounters in one day. The clinical team finishes documenting the visits, and the billing department processes the charges.

Everything appears normal until the practice manager compares the encounter records with the billing reports.

Several completed visits have no corresponding charges. Another encounter has an office visit charge, but a separately documented procedure has not been reviewed for billing. One claim was transmitted to the clearinghouse but never accepted for payer processing.

The services were performed, yet the billing records do not fully reflect what happened during patient care.

These problems can remain unnoticed because many practices monitor submitted claims and unpaid balances without consistently verifying what happened before claim submission.

Charge capture reconciliation is the process of matching completed patient encounters and documented services with recorded charges, submitted claims, and their processing acknowledgments to identify missing, duplicate, or unresolved billing activity.

The objective is not to create a charge for every appointment. It is to confirm that every completed service has been reviewed and reached an accurate billing outcome.

For medical practices, this requires looking beyond the number of completed visits or claims submitted.

A reliable reconciliation process should answer three important questions:

1. Was each completed encounter reviewed for appropriate charges?
2. Did the recorded charges accurately reflect the documented, billable services?
3. Did those charges reach an appropriate submitted claim or another verified billing outcome?

This guide explains how to connect clinical activity with billing records, identify where transactions stop matching, and understand what a complete encounter-to-claim reconciliation should verify.

What Is Charge Capture Reconciliation in Medical Billing?

Charge capture reconciliation in medical billing is the process of comparing healthcare services recorded in clinical systems against charge entry and claim submission records to confirm that all appropriate billable services have been accounted for.

It connects what happened during patient care with what the practice ultimately reported for reimbursement.

For example, a physician may complete a patient appointment and finalize the clinical documentation.

The encounter appears as completed in the electronic health record (EHR).

However, the corresponding charge may never reach the practice management system.

Unless the billing team compares the two records, the encounter could remain unnoticed because there is no submitted claim to follow up on.

Another situation involves a charge that was successfully entered but became stuck in a claim-edit queue.

The billing report shows that a charge exists, yet the insurer has not received an accepted claim.

Both situations require reconciliation, but the underlying problems occur at different stages.

What Should a Complete Reconciliation Confirm?

A complete review should establish a traceable relationship between the services performed and their billing disposition.

In practical terms, the billing team should be able to identify:

• The completed patient encounter and relevant clinical documentation.
• The services reviewed for billing and the charges entered.
• The claim or claims associated with those charges, when applicable.
• Whether those claims were submitted and accepted for processing.
• Any documented reason a service was bundled, nonbillable, held, or handled through another billing arrangement.

For example, a completed postoperative visit may not generate a separately payable professional claim because the service is included in an applicable global surgical package.

That is not automatically a missed charge.

The reconciliation record should show that the encounter was reviewed and the appropriate billing rule was applied.

Similarly, a completed visit with an unsigned or incomplete note may require documentation before coding and billing can proceed.

The encounter remains an open exception until the necessary review has been completed.

The goal of reconciliation is accurate and complete billing, not maximizing the number of charges regardless of clinical documentation or payer rules.

Pro Medical Billing Solutions (PROMBS) supports healthcare practices through charge capture reconciliation and medical billing audits that help identify missing charges, incomplete billing workflows, and inconsistencies between clinical and financial records.

Why Completed Encounters Do Not Always Become Submitted Claims

A completed encounter does not automatically move into the insurance billing process.

Most medical practices rely on several activities after the patient receives care.

Clinical documentation must be completed, appropriate services must be identified and coded, charges must reach the billing system, and claims must pass applicable submission checks.

An interruption at any stage can prevent a completed encounter from reaching the payer.

Clinical Documentation Is Complete but the Charge Is Missing

Consider an internal medicine practice where the physician completes a follow-up visit and signs the encounter note.

The EHR correctly records the service.

However, the expected charge does not appear in the billing system.

The cause may be a missed charge entry task, an incorrect encounter status, or a failed transfer between systems.

If the billing team reviews only its charge entry report, the visit may not appear as an exception because no charge record exists.

Comparing completed encounters against billing transactions helps identify this type of gap.

Our separate guide on unbilled encounters and charge lag explains why completed services can remain outside the claim submission process.

For this article, the important distinction is how to identify and verify the missing transaction.

An Encounter Contains More Than One Potentially Billable Service

A different problem occurs when the practice captures one charge but overlooks another documented service.

For example, a patient may receive an evaluation and a minor procedure during the same appointment.

The office visit charge may appear in the billing system, creating the impression that the encounter has been processed.

However, the procedure documented in the medical record may require a separate coding and billing review.

Whether the procedure is separately reportable depends on the clinical documentation, applicable coding rules, payer requirements, and circumstances of the encounter.

The billing team should not automatically submit an additional charge.

Instead, a qualified coder should determine whether the service qualifies for separate reporting and whether the documentation supports it.

This is an example of partial charge capture.

The encounter has a billing record, but that record may not fully account for the services performed.

A reconciliation process that checks only whether each encounter has at least one charge can miss this problem.

Charges Were Entered but Never Reached Claim Submission

Sometimes, the charge is present and accurate, but the claim is never transmitted.

For example, an orthopedic practice may complete charge entry for an office procedure.

The practice management system creates a claim, but the claim remains in a hold queue because of missing provider information or an unresolved billing edit.

The charge entry report shows the service as recorded.

However, the clearinghouse submission report has no corresponding transmitted claim.

If the billing manager checks only whether charges were entered, this problem may go unnoticed.

The reconciliation process should therefore verify the transition from recorded charges to actual claim submission.

The Claim Was Sent but Rejected Before Adjudication

A submitted claim is not necessarily an accepted claim.

For example, a billing team may transmit an electronic claim file that passes an initial technical validation.

However, an individual claim within the file may subsequently fail another required edit.

The billing system may display a submitted status, but the payer has not accepted that claim for adjudication.

The team must examine the available acknowledgment records to determine what occurred.

This distinction becomes particularly important when management reports claim submission volume without checking rejected transactions.

PROMBS provides medical billing services that include charge entry, claim preparation, clearinghouse workflows, and insurance claim follow-up.

Connecting these activities helps practices identify where submitted billing activity is delayed or rejected.

Charge Capture vs. Charge Entry vs. Claim Submission

Charge capture, charge entry, and claim submission are closely related, but they describe different activities.

Confusing these stages can lead practices to believe an encounter has been fully billed when it has only completed one part of the process.

Charge Capture: Identifying What Was Performed

Charge capture begins with identifying the healthcare services provided during an encounter and determining which services require billing consideration.

For example, a physician documents an office visit and performs a procedure.

The clinical and coding records should support an appropriate review of the services provided.

The objective is to identify potentially billable activity accurately, including services that may be bundled or subject to other reporting restrictions.

Charge capture does not automatically mean that every documented activity should appear as a separate claim line.

Charge Entry: Recording the Appropriate Charges

Charge entry occurs when the practice records the relevant codes, units, modifiers, and other necessary billing details in the practice management system.

For example, the coding team may determine that a documented procedure is separately reportable.

The corresponding charge is then entered or transferred into the billing system.

However, the charge may still require additional validation before a claim can be created and released.

A charge entry record proves that a transaction was recorded. It does not prove that the claim reached an insurer.

Claim Submission: Transmitting the Billing Information

Claim submission is the process of sending the appropriate claim information to the payer, commonly through a clearinghouse.

Before transmission, billing software may validate claim details and identify missing or inconsistent information.

After transmission, the team should review available acknowledgment records to verify whether the submitted transaction was accepted or rejected.

For electronic Original Medicare claims, the CMS Checking Medicare Claim Status fact sheet explains the role of 999 acknowledgments and 277CA claim acknowledgments.

A 999 acknowledgment relates to the initial transaction-level processing. A 277CA provides information about individual claim acceptance or rejection.

These acknowledgments are not proof that an insurance claim has been approved for payment.

That occurs later in the adjudication process.

How the Three Stages Fit Together

Billing stage	What it establishes	What it does not establish
Charge capture	A documented service was identified and reviewed for billing	That an accurate charge was entered
Charge entry	Billing information was recorded in the system	That a claim was submitted
Claim submission	A claim was transmitted for processing	That the payer accepted or paid it
Claim acknowledgment	The submitted file or claim received a processing response	That reimbursement is guaranteed

The distinction matters because a practice may report excellent charge entry completion while still experiencing missing claims or clearinghouse rejections.

Charge capture reconciliation should trace the service through these stages instead of treating charge entry as the final checkpoint.

Which Reports Are Needed for Encounter-to-Claim Reconciliation?

A practical encounter-to-claim reconciliation can begin with three reports.

The first identifies completed clinical encounters.

The second shows charges recorded in the billing system.

The third identifies submitted claims and their acknowledgment results.

These reports provide the information needed to determine whether activity is moving correctly between clinical documentation and insurance billing.

1. Completed Encounter Report From the EHR

The completed encounter report identifies services that occurred during the selected reporting period.

It should include the encounter identifier, patient record identifier, date of service, rendering provider, service location, and encounter status.

Depending on the EHR, it may also contain information about documented procedures, note completion, and other clinical activities.

For example, a cardiology practice may export all encounters completed on Monday.

The report includes routine follow-up visits, consultations, and encounters involving additional diagnostic services.

This becomes the starting population for reconciliation.

However, the practice should not simply count every appointment marked as scheduled.

Canceled visits, no-shows, encounters entered in error, and other records that do not represent completed services should be excluded or handled according to their actual status.

The source report must accurately reflect the clinical activity being reviewed.

2. Posted Charge Report From the Billing System

The second report identifies charges entered or transferred into the practice management system.

It should provide enough information to connect each charge with the relevant encounter.

Useful details include the encounter or account reference, date of service, provider, procedure code, units, charge entry date, and current charge status.

For example, the EHR may show that 40 patient encounters were completed.

The billing system may contain 43 charge lines associated with those encounters.

That difference does not automatically mean the billing team created duplicate charges.

Some encounters may legitimately contain multiple reported services.

Likewise, 40 completed encounters and 40 charge records do not prove that charge capture is complete.

One encounter could have an unsupported duplicate charge while another is missing a required billing record.

The reconciliation team must review the relationship between the encounters and the underlying services rather than relying only on aggregate totals.

PROMBS’s medical coding services support documentation-based coding reviews that can help clarify whether charges accurately represent the services performed.

3. Submitted Claim and Acknowledgment Report

The third report identifies claims generated from the billing system and their processing results.

It should show the associated claim number, submitted service lines, payer, transmission date, clearinghouse response, and available payer acknowledgment status.

For example, a charge may appear in the billing system but remain in a claim-edit queue.

Another charge may be linked to a submitted claim that was rejected because of missing subscriber information.

A third claim may have been accepted for adjudication.

These represent different outcomes even though all three encounters have entered the billing system.

The reconciliation report should distinguish them.

A claim should not be marked as payer-accepted merely because the clearinghouse submission process was initiated or a file-level acknowledgment was received.

The billing team should use the available claim-level acknowledgment and payer response information to establish its actual status.

This allows the practice to identify claims that need correction or resubmission instead of assuming they are already being processed.

Match the Reports Using Consistent Identifiers

The reports are most useful when their records can be linked reliably.

An encounter identifier is often the strongest starting point, but not every practice management system or clearinghouse retains the same identifier in every report.

Billing teams may need to use a combination of patient record reference, date of service, provider, location, charge identifier, and claim control number.

For example, the EHR may label a visit as Encounter E-2045, while the billing system assigns Charge C-7812 and Claim CL-9906.

A reliable reconciliation process should preserve the relationship between those records.

When identifiers do not transfer consistently between systems, the mismatch itself may deserve investigation.

The reports should also use a consistent service-date population and an appropriate extraction cutoff.

A claim created after the reporting cutoff should not automatically be classified as missing simply because it was absent from an earlier snapshot.

Patient information should be handled through approved, appropriately secured systems with access limited to authorized personnel.

Why One Completed Encounter Does Not Always Equal One Claim

A common misunderstanding in charge capture reconciliation is that every completed encounter should produce exactly one insurance claim.

In medical billing, that relationship is not always one-to-one.

One encounter may involve multiple services, several claim lines, a separate billing arrangement, or no separately payable claim.

For example, a patient may have an office visit and a procedure during the same appointment.

Depending on the coding rules and documentation, the services may appear as separate lines on one professional claim.

In other situations, professional and facility billing may be handled separately by different billing entities.

The practice must understand which entity is responsible for each component before attempting to reconcile the records.

Multiple Services May Be Reported on One Claim

Consider a physician who performs two distinct services during the same encounter.

If both services are independently reportable under the applicable rules, they may appear as separate claim lines.

The reconciliation process should therefore compare the documented services with the actual charge lines.

Finding one claim associated with the encounter does not prove that both services were captured.

Similarly, the presence of multiple claim lines does not automatically mean the claim contains duplicate charges.

Each line must be supported by the clinical documentation and applicable coding requirements.

Some Encounters Are Included in Other Billing Arrangements

Certain encounters may not result in a separate professional claim.

For example, a routine postoperative visit may be included in a global surgical package.

Other encounters may involve services bundled under applicable payment rules or handled through a different contractual arrangement.

The reconciliation process should document these legitimate exceptions.

A completed encounter without a separate claim should not remain permanently unresolved if a qualified review establishes that no separate claim is appropriate.

Some Clinical Activities Require Additional Review

Not every procedure or service recorded in an EHR is automatically separately reimbursable.

For example, a clinical record may contain several orders, activities, and treatment details.

Only services meeting applicable billing and documentation requirements should be reported.

A charge capture review must therefore include coding judgment rather than automatically converting every clinical record into another claim line.

Accurate reconciliation means accounting for every completed encounter and appropriate billable service, not forcing the number of encounters and claims to match.

Common Discrepancies Between Encounters, Charges and Claims

Once the reports are connected, the billing team can begin identifying records that do not have a valid corresponding billing outcome.

These discrepancies generally fall into several categories.

Completed Encounter With No Charge

The EHR shows that the patient visit occurred, but no charge appears in the practice management system.

The billing team should verify whether the service requires separate billing and whether the necessary documentation is complete.

If the service is billable and properly documented, the missing charge may need to be entered through the appropriate workflow.

If the encounter was legitimately nonbillable or included in another arrangement, that outcome should be documented.

Encounter With Partially Captured Charges

The billing system contains at least one charge, but the documented encounter includes another service that may require separate reporting.

For example, a practice may capture an evaluation and management service while a separately documented procedure has not been reviewed by the coding team.

This requires a detailed comparison between the medical record and the posted charge lines.

The presence of one charge is not enough to close the reconciliation.

Charge Recorded Without a Supporting Encounter

A charge appears in the billing system, but the team cannot find an appropriate supporting clinical encounter or service record.

This may indicate an incorrect account mapping, a duplicate entry, a charge transferred from another system, or potentially unsupported billing information.

The team should investigate the source before submitting or adjusting the charge.

Some legitimate charges originate from ancillary systems rather than a conventional office encounter, so the absence of an ordinary visit record does not automatically establish an error.

Charge Entered but Claim Not Submitted

The charge has been recorded correctly but remains in a claim hold, work queue, or unresolved billing edit.

The appropriate next action depends on the reason the claim was not released.

For example, the claim may require missing insurance information, clinical clarification, or a coding correction.

The reconciliation record should show why the account remains pending and which employee is responsible for resolving it.

Claim Transmitted but Not Accepted

The claim submission system shows a transmission, but the clearinghouse or payer acknowledgment identifies a rejection.

For example, the billing team may need to correct a subscriber identifier or a required claim field.

The claim should remain open for reconciliation until the rejection is appropriately resolved and the corrected submission receives the necessary acknowledgment.

Simply transmitting another claim without investigating the previous status may create duplicate billing problems.

Duplicate or Incorrectly Linked Claims

A completed encounter may be associated with multiple submitted claim records.

This does not automatically mean the claims are duplicates.

The records may involve corrected claims, reversals, different billing components, or other legitimate transactions.

However, if the practice identifies a potentially duplicate submission, the billing team should review the claim history before taking additional action.

The goal is to distinguish legitimate billing transactions from errors that could cause payer rejections, denials, or post-payment adjustments.

Why Charge Capture Reconciliation Must Go Beyond Counting Claims

A medical practice may compare its daily encounter count with the number of claims submitted and conclude that reconciliation is complete when the figures match.

However, identical totals can conceal meaningful discrepancies.

For example, suppose a practice completes 50 encounters and submits 50 claims.

That appears balanced.

But one completed visit may have no associated claim, while another encounter may have an unintended duplicate submission.

The totals still match even though the underlying records do not.

Likewise, the presence of one charge for every encounter does not prove that all appropriate services were captured.

The practice must also consider whether documented procedures, units, and other reportable services are accurately represented.

This is why an effective reconciliation process needs to work at the encounter, charge, and claim level.

Through its medical billing and coding audit services, PROMBS helps medical practices examine billing discrepancies, charge entry problems, and gaps between clinical documentation and claim processing.

These reviews can support more reliable billing workflows and identify issues that aggregate claim counts may overlook.

Building the Foundation for an Accurate Encounter-to-Claim Worklist

Charge capture reconciliation becomes useful when the practice can explain what happened to an individual completed encounter.

For example, a billing manager should be able to determine whether a visit has appropriate charges, whether those charges reached a submitted claim, and whether the claim was accepted for adjudication.

When the records do not match, the discrepancy should remain visible until someone verifies the appropriate next action.

The practice should not automatically treat every unmatched encounter as lost revenue.

Some cases involve incomplete documentation, legitimate nonbillable services, or claims that are still undergoing normal processing.

Others involve missing charges, claim holds, interface failures, or rejected submissions that require attention.

The purpose of reconciliation is to distinguish these situations and create a traceable record of what must happen next.

PROMBS supports healthcare practices through charge capture, medical coding, claim submission, clearinghouse management, billing audits, and revenue cycle reporting.

By connecting these activities, practices can improve visibility between completed patient care and the billing records used to request reimbursement.

Charge capture reconciliation is not complete when the numbers in two reports match. It is complete when the underlying clinical services and billing transactions have been accurately accounted for, or any remaining exceptions have been clearly identified for resolution.

How to Perform Charge Capture Reconciliation Step by Step

To perform charge capture reconciliation, compare completed patient encounters in the EHR with posted charges in the billing system, match those charges to submitted claims, and verify the available clearinghouse and payer acknowledgments. Any unmatched or incomplete record should be assigned for investigation.

This process sounds straightforward until the reports contain hundreds of transactions from multiple providers.

A completed appointment may generate several charge lines. One charge may be held for review while another has already reached the payer. A claim may also appear as submitted even though the clearinghouse or payer rejected it.

These situations cannot be identified reliably by comparing encounter counts with claim counts alone.

A practical reconciliation process needs to follow individual records and explain what happened at each stage.

The following eight steps provide a repeatable workflow that medical practices can use to identify missing charges, incomplete billing activity, and unresolved claim submission problems.

Step 1: Define Completed Encounters and Legitimate Exclusions

Before comparing billing records, determine which encounters belong in the reconciliation.

Start with the EHR’s completed encounter report for a defined date-of-service period.

For example, a medical practice may review all encounters performed during the previous business day.

However, the report should distinguish completed clinical services from appointments that were canceled, rescheduled, or marked as no-shows.

A canceled appointment should not automatically be treated as a missing insurance claim.

The same principle applies to encounters that do not require separate billing.

For example, a routine postoperative visit may fall within the applicable global surgical period and may not qualify for a separately payable professional claim.

That encounter should still be accounted for, but its reconciliation outcome may be documented as included in the global surgical package.

Another encounter may involve a capitated payment arrangement or a service billed by a different entity.

The billing manager must understand these distinctions before deciding whether a charge is missing.

The correct starting point is a list of completed services requiring a verified billing disposition, not an assumption that every appointment should produce exactly one claim.

Establish a Consistent Reporting Cutoff

Timing is another important consideration.

Suppose a patient encounter was completed late Monday, but the provider did not finalize the documentation until Tuesday morning.

If the billing manager exports the charge report at midnight, the visit may appear unmatched even though the practice’s normal documentation process has not finished.

This does not mean the encounter should disappear from reconciliation.

It means the worklist should identify the actual reason it remains pending.

For example, a practice may review the previous day’s encounters each morning and retain encounters awaiting documentation in a separate exception queue.

The report should record both the service date and the extraction cutoff.

This helps employees distinguish normal processing activity from encounters that have exceeded the practice’s expected turnaround time.

Step 2: Export EHR Encounters and Billing Records

The next step is collecting the data needed to follow each encounter through the billing process.

Most practices can begin with three reports:

Completed encounter report: Identifies clinical encounters and documented services.

Posted charge report: Identifies charges entered or transferred into the practice management system.

Submitted claim and acknowledgment report: Identifies claims released for submission and their available processing responses.

The reports should cover the same relevant service-date population, even if charge entry and claim submission occurred on later dates.

For example, an encounter completed on October 20 may generate charges on October 21 and a claim on October 22.

If the billing manager searches only for claims submitted on October 20, that encounter could be incorrectly classified as unbilled.

The reports should therefore retain the date of service and enough transaction identifiers to connect records across different processing dates.

Match Records Using Reliable Identifiers

An encounter ID is useful, but it may not appear in every system.

For example, an EHR may assign Encounter E-1024, the billing system may generate Charge C-8806, and the clearinghouse may report Claim CL-4502.

The reconciliation process needs to preserve the relationship between those records.

Useful identifiers include the patient account reference, encounter ID, service date, rendering provider, charge ID, billing entity, claim number, and clearinghouse transaction reference.

When a shared encounter ID is unavailable, a combination of fields may help identify a potential match.

However, a match based only on patient and service date can be unreliable.

A patient may have more than one encounter on the same day, or the professional and facility components may follow different billing workflows.

Ambiguous matches should be reviewed rather than automatically accepted.

The files should remain within an appropriately secured billing environment, with access limited to authorized staff.

PROMBS supports these processes through medical billing services that include charge entry, claim processing, clearinghouse workflows, and billing reconciliation.

Step 3: Match Completed Encounters With Posted Charges

After organizing the records, compare each completed encounter with the charges recorded in the practice management system.

Begin by identifying encounters with no matching charge transactions.

For example, a primary care practice may show that a physician completed a follow-up visit, but the billing report contains no charge connected to the encounter.

The billing specialist should investigate whether the service was properly documented and whether a separate charge is appropriate.

Possible findings include an incomplete note, a charge entry error, a failed system transfer, or a legitimate nonbillable outcome.

The team should not automatically create a charge merely because no billing transaction appears.

The clinical record and applicable billing requirements must support the action.

Check the Reverse Direction Too

Once completed encounters have been matched to charges, reverse the comparison.

Identify charges that cannot be connected to an appropriate encounter or supporting service record.

For example, the billing system may contain two identical charge entries associated with one documented procedure.

This could indicate a duplicate transaction.

Alternatively, an unmatched charge may originate from an ancillary system rather than a conventional office encounter.

The billing specialist should verify its source before deciding whether it represents an error.

This two-way comparison helps identify both missing activity and potentially unsupported billing records.

It is more reliable than reviewing only encounters without charges.

Step 4: Identify Missing and Partially Captured Charges

A major limitation of basic reconciliation is that it often stops once an encounter has at least one charge.

However, a patient encounter may involve several services, and only some of them may have been recorded.

For example, a physician completes an office visit and performs a minor procedure.

The office visit charge appears in the billing system, but the documented procedure has not been reviewed for separate reporting.

A simple encounter-to-charge match would classify the visit as complete.

A more detailed review would identify an unresolved question about the additional service.

Partial charge capture occurs when an encounter has some recorded charges but may be missing other appropriate, documented billable services.

The billing team should review the documented services, procedure codes, units, modifiers, and relevant charge records.

A qualified coder must determine whether each service is separately reportable.

For example, an evaluation and management service performed on the same day as a procedure does not automatically qualify for separate reimbursement.

The coding decision depends on the documentation and applicable rules.

Similarly, a procedure recorded twice in a clinical workflow does not automatically justify two billed units.

The objective is to ensure that the recorded charges accurately represent the services provided.

Why This Matters Beyond Small Medical Practices

A 2026 internal audit of UT MD Anderson’s Pathology and Laboratory Medicine division identified a similar issue.

Its existing reconciliation process primarily checked whether completed cases or tests had associated charges. The audit found that this approach could overlook missing professional or technical charge components and incorrect quantities.

The report recommended improving reconciliation to verify the completeness of expected charges.

The findings are described in the 2026 Pathology and Laboratory Medicine Charge Capture Review.

For independent physician practices, the lesson is straightforward.

Finding one charge associated with an encounter does not necessarily mean every appropriate service has been captured.

PROMBS provides medical coding services that support documentation-based coding reviews and help practices investigate missing, duplicate, or inaccurately recorded charges.

Step 5: Verify That Recorded Charges Became Submitted Claims

After matching the completed encounters with appropriate charge records, determine whether those charges reached claim submission.

A charge can be correctly entered without ever being transmitted to the payer.

For example, a billing system may contain a complete office visit charge, but the corresponding claim remains in an edit queue because the provider’s information is incomplete.

The charge exists, yet no accepted insurance claim has resulted.

The reconciliation specialist should review the claim generation and submission records.

Important questions include whether a claim was created, whether it was released for transmission, which charges or service lines were included, and whether the intended payer received the transaction.

Compare Charge Lines With Claim Lines

The team should verify more than the existence of a claim number.

For example, a medical practice may enter three supported charge lines for an encounter.

If the generated claim contains only two of those lines, the missing line needs investigation.

There may be a legitimate reason.

One service might be bundled, billed separately, or held pending documentation.

Alternatively, a system configuration or claim preparation error may have omitted the line.

The reconciliation specialist should determine which explanation applies.

This is especially important when charge data moves between separate EHR, practice management, and clearinghouse systems.

Investigate Claims Remaining in Hold Queues

A charge may be prevented from reaching submission because of missing insurance details, incomplete documentation, coding edits, or billing configuration problems.

The worklist should identify the reason for the hold.

For example:

“Charge entered October 20. Claim held because rendering provider information requires verification. Assigned to billing specialist for review.”

That is more useful than a general status reading “Not billed.”

Once the problem is resolved, the billing team should confirm that the appropriate claim was actually released.

A corrected charge or cleared billing edit is not sufficient proof that the claim reached the payer.

Step 6: Review Clearinghouse and Payer Acknowledgments

Once a claim has been transmitted, verify its available acknowledgment results.

This step is often overlooked because billing systems may display a successful transmission status before the payer has accepted the individual claim.

For electronic Original Medicare claims, the acknowledgment process includes two important stages.

999 Implementation Acknowledgment: Indicates whether the submitted transaction file passed applicable front-end processing checks.

277CA Claim Acknowledgment: Provides claim-level information identifying whether claims passed the next stage of acceptance checks or were rejected.

According to the CMS Checking Medicare Claim Status fact sheet, these editing stages can take up to three days.

CMS also advises against resubmitting a claim while it is undergoing the initial editing process because an unnecessary submission can create a duplicate.

For Medicare, accepted claims receive tracking identifiers such as an Internal Control Number for Part B or a Document Control Number for Part A.

The workflow and acknowledgment availability for commercial and other payers can vary.

Why a Successful 999 Is Not Enough

Consider a medical practice that transmits an electronic claim file containing 25 claims.

The file receives a successful 999 acknowledgment.

The billing manager might assume that all 25 claims are now being processed.

However, the subsequent claim-level acknowledgment may identify individual claims that failed additional edits.

Those rejected claims have not successfully entered the intended adjudication process.

They require appropriate review and correction.

The distinction is also described in Highmark’s electronic claim submission guidance.

The reconciliation process should therefore distinguish between a file-level acknowledgment and the acceptance of the individual claim.

Payer Acceptance Is Not Payment Approval

Even when a claim has been accepted for adjudication, the payer may later pay, partially pay, or deny it.

Charge capture reconciliation primarily verifies whether the clinical activity moved through the appropriate billing and claim acceptance stages.

Payment decisions belong to later revenue cycle activities, including denial management, payment posting, and accounts receivable follow-up.

This distinction keeps the reconciliation process focused without confusing claim acceptance with successful reimbursement.

Step 7: Assign Exceptions to the Correct Department

Once mismatches are identified, they should be assigned to the employee or department capable of resolving them.

For example, an incomplete clinical note may require action from the treating provider.

A questionable modifier may require a qualified coding specialist.

A failed system transfer may require support from the EHR administrator or technical team.

A clearinghouse rejection may require the billing specialist to correct the affected claim information.

The worklist should identify one accountable owner, even when several departments need to contribute.

For example, an encounter should not remain indefinitely assigned to both the clinical and billing teams without anyone responsible for confirming its resolution.

The owner should document the missing information, next action, and review date.

Use Specific Exception Descriptions

Consider the difference between these two records.

Weak exception note: “Charge missing. Follow up.”

Actionable exception note: “Encounter E-102 completed October 20. Clinical note signed. No corresponding charge found in the practice management export. Assigned to charge entry specialist to verify interface transfer and billing disposition.”

The second note helps employees understand the problem without repeating the initial investigation.

It also allows a manager to determine whether the case is progressing.

Step 8: Recheck and Document Each Resolution

The final step is verifying that the corrective action produced the intended result.

An employee marking an exception as complete is not enough.

For example, if an encounter originally had no charge, the billing manager should confirm that an appropriate charge was recorded or that a legitimate nonbillable outcome was established.

If a claim was held, the team should confirm whether it was released.

If a claim was rejected, the team should verify that the issue was resolved and that the corrected submission received the appropriate acknowledgment.

Some cases may remain open because documentation, coding clarification, or another required action is still pending.

A worklist should not classify those accounts as resolved simply because someone attempted a correction.

A reconciliation exception should close only when the practice has evidence of an appropriate billing outcome or a documented reason that no separate claim is required.

That outcome does not necessarily mean the claim has been paid.

It means the encounter has passed the defined reconciliation checkpoint or has been legitimately accounted for.

Practical Example: Reconciling Six Completed Encounters

Consider a multi-provider medical practice reviewing six completed patient encounters.

The billing manager exports the EHR encounter report, posted charge report, and clearinghouse acknowledgment records.

At first glance, several encounters appear to have associated billing activity.

However, a more detailed reconciliation identifies different outcomes.

Sample Encounter-to-Claim Reconciliation Worklist

Encounter	Reconciliation finding	Next action
E-101	Appropriate charges matched to a claim accepted for adjudication	Close reconciliation with claim reference
E-102	Completed encounter with no charge	Verify documentation and investigate missing charge
E-103	Office visit charge posted; additional documented procedure requires billing review	Coding specialist verifies separate reportability
E-104	Charges recorded, but claim remains in a billing hold	Resolve claim-edit issue and verify submission
E-105	Claim transmitted, but 277CA shows a claim-level rejection	Correct the issue and verify the new acknowledgment
E-106	Completed encounter reviewed as included in a global surgical package	Record supported non-separately billable outcome

All encounters and findings are illustrative. Actual billing decisions must follow documentation, coding rules, and payer requirements.

The report identifies six completed encounters, but only one currently has a verified payer-accepted claim.

Another has a documented, legitimate billing outcome without a separate claim.

Four encounters still require investigation or additional processing.

However, that does not mean four claims were necessarily missed.

Each issue must be evaluated individually.

Encounter E-102: Completed Visit With No Recorded Charge

The EHR shows that the physician completed the visit and signed the clinical note.

The charge entry report contains no associated charge.

The billing specialist reviews the encounter and confirms that the service needs a coding and billing assessment.

Suppose the investigation identifies that an EHR interface failed to transfer the relevant charge information.

The specialist should verify the documentation, correct the transfer problem through the approved process, and confirm that the resulting billing record is accurate.

The case remains open until the appropriate charge and claim workflow, or another valid disposition, is verified.

Encounter E-103: A Partially Captured Encounter

The practice management system contains an office visit charge, but the clinical record also documents a procedure.

A simple reconciliation would find the office visit charge and classify the encounter as matched.

However, a qualified coder must determine whether the additional procedure is separately reportable.

If the coding rules support separate reporting, the missing charge requires appropriate action.

If the procedure is bundled or not separately billable, the worklist should record that outcome.

The billing team should not automatically add a procedure code based only on its appearance in the clinical note.

Encounter E-104: Recorded Charge but Unsubmitted Claim

The encounter has appropriate charges in the billing system.

However, the associated claim remains in a hold queue because required billing information needs correction.

The specialist investigates the hold, resolves the supported issue, and confirms that the claim is transmitted.

The reconciliation should then check the available acknowledgment result before closing the claim-submission exception.

This prevents the practice from treating charge entry completion as equivalent to payer receipt.

Encounter E-105: Transmitted Claim Rejected Before Adjudication

The claim was transmitted successfully, but its claim-level acknowledgment identifies an error that prevented acceptance.

The billing specialist reviews the rejection details and determines the correction required.

For example, the submitted subscriber information may not match the payer’s records.

After verifying the correct information, the team follows the applicable correction and resubmission procedure.

The account should remain open until the next acknowledgment confirms an appropriate outcome.

It should not be counted as successfully accepted merely because it was transmitted again.

Encounter E-106: Legitimate No-Separate-Claim Outcome

The encounter is a routine postoperative service included in the applicable global surgical package.

A qualified review confirms that no separate professional claim is appropriate under the relevant circumstances.

The billing team records that disposition and closes the reconciliation.

This is an important part of accurate reporting.

An encounter that legitimately does not require separate billing should not remain in a missing-charge queue or trigger an unnecessary claim.

How to Build an Encounter-to-Claim Reconciliation Worklist

A reconciliation worklist should connect the clinical encounter with its billing and claim records.

It should also make unresolved problems easy to assign and monitor.

For a small medical practice, the worklist may be maintained in an authorized billing system or a properly secured internal spreadsheet.

Larger practices may use automated exception queues that connect the EHR, practice management system, and clearinghouse.

The essential information remains similar.

Fields Every Worklist Should Include

A useful worklist should record the encounter ID, date of service, rendering provider, relevant charge IDs, claim ID, and current processing status.

For mismatched records, it should also identify the exception type, assigned owner, next action, review date, and supporting evidence.

For example, a record might show:

Encounter: E-2045

Exception: Claim held after charge entry

Reason: Rendering provider information requires verification

Owner: Billing specialist

Next action: Verify provider information and resolve the claim edit

Closure evidence: Corrected claim submitted and appropriate claim-level acceptance confirmed

This format makes the required outcome clear.

It also creates an audit trail explaining why the account was considered resolved.

Use Standard Exception Categories

Rather than allowing employees to enter different descriptions for the same problem, practices can use standard exception categories.

For example:

• No charge found.
• Documentation incomplete.
• Possible partial charge capture.
• Charge requires coding review.
• Claim not created.
• Claim held before submission.
• Claim rejected before adjudication.
• Potential duplicate or unsupported charge.
• Legitimate non-separately billable outcome.

These categories help management identify recurring problems.

For instance, if most exceptions involve claims held for incomplete provider information, the practice may need a targeted workflow or system configuration review.

If many encounters are missing charges after a specific interface update, technical investigation may be appropriate.

Define What Counts as a Closed Exception

An exception should have a documented resolution.

For example, a missing charge exception may close when the appropriate charge is entered and its downstream billing outcome is verified.

A suspected duplicate charge may close when the team confirms the legitimate transaction structure or corrects a verified error.

A nonbillable encounter may close after the relevant clinical or coding review establishes why no separate claim is required.

This prevents employees from clearing the worklist merely by changing status labels.

PROMBS’s medical billing and coding audit services can help practices investigate these exceptions and identify whether missing charges, inaccurate records, or system problems are affecting claim processing.

How to Handle EHR Interface Failures, Duplicate Charges and Claim Holds

Some reconciliation problems occur repeatedly because of the way clinical and billing systems communicate.

When multiple encounters show the same discrepancy, the practice should investigate the underlying workflow rather than correcting each record without examining the cause.

EHR Interface Failures

An EHR interface transfers information between clinical and financial systems.

If the transfer fails, a completed encounter or recorded service may never reach the billing work queue.

For example, a practice may discover that several encounters from one location have no matching charge records.

The billing manager should determine whether the transactions were generated, transmitted, received, rejected, or incorrectly mapped.

This may require reviewing interface logs, error queues, and the relevant system identifiers.

If the system did not create the expected billing transaction, a technical correction may be needed.

If the transaction was received but placed under the wrong account, the issue may involve data mapping.

The team should also determine whether correcting the interface will cause previously failed messages to be replayed.

Before replaying transactions, verify whether any affected charges were entered manually during the outage.

Otherwise, the correction could create duplicates.

Duplicate Charges and Repeated Transactions

A duplicate charge may occur when a service is entered manually and later transferred again through an automated interface.

Another possibility is that an employee repeats a submission because the first transmission status was unclear.

However, multiple charges or claims associated with one encounter are not automatically duplicates.

A single visit can involve several reportable services, corrected claim transactions, or different billing components.

The team should compare procedure details, units, service dates, billing entity, and transaction history.

When a true duplicate is confirmed, the practice should follow the appropriate correction procedure rather than simply deleting records without preserving an audit trail.

Claims Stuck in Billing Holds

Claim holds can result from coding discrepancies, incomplete provider information, missing patient details, or other claim edits.

For example, several claims may be waiting because the billing system requires a provider identifier that was not correctly transferred from the EHR.

If the same hold affects multiple claims, correcting records one by one may not solve the ongoing problem.

The billing manager should determine whether the issue originates from a system configuration, registration procedure, charge entry workflow, or another source.

Once corrected, the team should test affected claims and verify that new transactions no longer encounter the same hold.

Our guide on revenue cycle workflow errors explains how information gaps between clinical and billing departments can contribute to these problems.

How to Verify That Reconciliation Corrections Actually Worked

Completing a reconciliation task does not necessarily mean the underlying problem has been fixed.

For example, an employee may manually enter a missing charge and successfully submit the claim.

That resolves the individual account.

However, if the original EHR interface problem remains, new encounters may continue generating the same exception.

The billing manager should therefore review both individual resolutions and recurring patterns.

Test New Encounters After a Workflow Correction

Suppose the practice updates an EHR interface after discovering missing charges from one service location.

The next reconciliation should examine newly completed encounters from that location.

The team should verify that the appropriate charge records are being generated and correctly linked to the clinical source.

Where relevant, it should also check whether the charges are progressing through claim submission.

If missing records continue appearing, the original corrective action may have been incomplete.

Keep Historical Corrections Separate From New Exceptions

When measuring improvement, distinguish older encounters that required cleanup from newly completed encounters processed after the change.

For example, the billing team may resolve 20 historical charge exceptions during the week.

That is useful progress, but it does not prove that the current charge capture process is performing correctly.

Management should also determine whether new encounters continue developing the same problems.

This distinction helps practices evaluate prevention separately from backlog resolution.

Confirm the Billing Outcome, Not Just the Work Performed

The final reconciliation review should answer whether every investigated encounter has an appropriate disposition.

For a billable service, that may include an accurate charge, a corresponding claim, and the required acknowledgment status.

For an encounter that does not require a separate claim, the disposition should be supported by the appropriate billing or coding review.

For an unresolved exception, the record should continue identifying its owner and next action.

The purpose of charge capture reconciliation is not simply to make every row in a report appear matched. It is to verify that completed services have been accurately accounted for and that billing exceptions receive an appropriate resolution.

PROMBS supports healthcare practices through charge capture, medical coding, claim submission, clearinghouse management, and revenue cycle reporting.

These services help connect clinical activity with billing records while identifying discrepancies that require further investigation.

How to Reconcile Multiple Charges From a Single Encounter

One of the most common mistakes in charge capture reconciliation is assuming that a completed patient encounter should always produce one charge or one insurance claim.

In reality, an encounter can involve several documented services, multiple charge lines, or a billing arrangement that does not require a separate claim for every activity.

For example, a physician may evaluate a patient and perform a procedure during the same appointment. The practice management system might contain an office visit charge, while the clinical record documents additional services requiring coding review.

If the billing team checks only whether the encounter has a charge, the record may appear complete even when part of the documented activity has not been evaluated for billing.

To reconcile encounters with multiple services, practices should compare the documented clinical services with the individual charge lines, confirm which services qualify for separate reporting, and verify that the appropriate charges appear on the relevant claims.

This is more reliable than comparing the total number of encounters with the total number of claims.

Match Each Documented Service to an Appropriate Billing Outcome

Consider an orthopedic practice where a patient receives an office evaluation and a minor procedure during the same visit.

The EHR contains documentation for both activities.

The practice management system, however, shows only the office visit charge.

This does not automatically mean the practice should add a procedure charge.

A qualified coding specialist should first verify whether the procedure is separately reportable and whether the documentation supports the applicable coding requirements.

If separate reporting is appropriate, the team should investigate why the charge is missing.

If the service is bundled or otherwise not separately billable, the reconciliation should record that outcome.

The same principle applies when the billing system contains multiple charges.

For example, three charge lines may legitimately represent three supported services. However, they could also include an unintended duplicate or an incorrect unit count.

The goal is to establish whether the charges accurately reflect the documented care.

Check Units and Modifiers, Not Just Procedure Codes

A charge may exist but still contain inaccurate billing details.

For example, a medical practice may record the correct procedure code but report an incorrect number of units.

A basic encounter-to-charge match would not necessarily identify this issue.

The reconciliation team should therefore consider procedure codes, units, modifiers, and supporting documentation when reviewing higher-risk services.

The CMS National Correct Coding Initiative (NCCI) establishes correct coding edits intended to prevent inappropriate reporting of certain code combinations under Medicare.

CMS also explains that modifiers should be used only when the clinical circumstances support them.

For example, modifier 25 may be appropriate for a significant, separately identifiable evaluation and management service performed on the same date as a procedure, when the relevant requirements are satisfied.

It should not be added automatically simply because an E/M code and a procedure appear on the same encounter.

Practices should apply current coding requirements, payer policies, and documentation standards rather than attempting to create additional charges whenever the clinical record contains more than one service.

PROMBS provides medical coding services that support CPT, HCPCS, ICD-10, and modifier accuracy through documentation-based coding reviews.

Account for Professional, Facility and Global Billing

Some healthcare services involve different billing entities or payment arrangements.

For example, a physician may perform a procedure at a hospital outpatient facility.

The physician’s professional service and the facility’s services may follow separate billing workflows.

A physician practice should not classify every facility charge as missing from its own professional billing report.

Similarly, some postoperative visits are included in a global surgical package.

According to CMS global surgery guidance, Medicare payments for many surgical procedures include related postoperative visits during the applicable global period.

The practice should determine whether a completed postoperative encounter requires separate reporting, a specific informational submission, or documentation of an included service.

These decisions depend on the actual circumstances and applicable rules.

A successful reconciliation accounts for every relevant service without creating duplicate, unsupported, or incorrectly separated charges.

How to Prevent Duplicate or Unsupported Medical Charges

Charge capture reconciliation should identify missing billing activity, but it must also protect the practice from inaccurate charges.

For example, a medical practice may discover that an EHR interface failed to transfer charges for several encounters.

Employees begin entering the missing charges manually.

Later, the technical team repairs the interface and retransmits the original transactions.

Without appropriate duplicate controls, the billing system may now contain two charges for the same service.

A process intended to recover missed billing activity could create a different financial and compliance problem.

Review Repeated Transactions Before Releasing Claims

When a potentially duplicate charge appears, the billing specialist should compare the encounter, service date, provider, procedure, units, and source transaction.

For example, two identical procedure codes on the same date may represent an unintended duplicate.

However, they could also involve distinct, properly documented services.

The presence of repeated codes alone does not establish an error.

The team should investigate the clinical circumstances and applicable coding requirements before changing or releasing charges.

Use System Controls Without Relying on Them Completely

Billing systems can help detect potentially repeated transactions.

For example, a duplicate warning may identify identical codes associated with the same patient, provider, and service date.

That warning can prompt further review.

However, automated edits cannot reliably determine every clinical circumstance.

A legitimate repeated procedure may require supporting documentation, while an unsupported charge may pass a basic duplicate check because its details differ slightly.

Automated controls should therefore direct questionable records to a qualified reviewer rather than automatically approving or rejecting every flagged transaction.

Preserve the Original Billing History

When a charge is corrected or removed, the practice should retain an appropriate record of the original transaction and the reason for the change.

For example, a charge entered under the wrong encounter may need reassignment through the billing system’s approved correction procedure.

Simply deleting the transaction without preserving its history can make later investigations more difficult.

This is especially important when claims have already been submitted or paid.

An error discovered after submission may require a payer-specific correction or another appropriate action.

The practice should not assume that modifying the internal charge record automatically updates the insurer’s claim.

Investigate Unsupported Charges as Seriously as Missing Charges

A reconciliation process should work in both directions.

The first review identifies completed services that may be missing appropriate charges.

The second identifies charges that do not have clear clinical support or an appropriate billing source.

For example, a charge might appear in the practice management system even though the corresponding clinical encounter was canceled.

The team should determine whether the transaction resulted from incorrect scheduling information, an automated system error, or another legitimate service record.

If the charge is unsupported, the practice should follow the appropriate correction process.

The HHS Office of Inspector General’s General Compliance Program Guidance provides a voluntary framework for compliance activities, including monitoring, auditing, and responding to identified concerns.

For medical practices, the underlying principle is that charge capture accuracy should be measured by appropriate billing, not simply the number or dollar value of charges entered.

How Often Should Practices Perform Charge Capture Reconciliation?

A medical practice should not wait until the end of the month to discover that completed encounters have been sitting outside the billing process.

By that time, employees may need to revisit older clinical records, clarify documentation, and investigate transactions that should have been addressed much earlier.

Daily exception reviews, weekly reconciliation checks, and monthly trend analysis provide a practical structure for monitoring charge capture accuracy.

The appropriate frequency depends on patient volume, service complexity, staffing, and how the practice’s EHR and billing systems operate.

Daily: Identify New Billing Exceptions

A daily review should focus on newly completed encounters and transactions that have not reached the expected next stage.

For example, the billing team may identify encounters with no associated charge, charges awaiting coding review, or claims held before submission.

The reviewer should determine whether each exception represents normal processing activity or a problem requiring attention.

A visit completed late in the afternoon may still be within the practice’s documentation workflow.

However, an encounter with a finalized note and no charge several days later may require additional investigation.

Daily reviews should concentrate on exceptions rather than manually rechecking every successfully processed transaction.

Weekly: Confirm Exceptions Are Moving Toward Resolution

A weekly reconciliation review should examine open exceptions and determine whether assigned corrective actions have been completed.

For example, a billing specialist may have identified ten encounters requiring provider clarification.

The weekly review should show which encounters received the necessary information, which charges were entered, and which cases remain unresolved.

It should also identify recurring problems affecting the same provider, service location, or interface.

If multiple encounters remain in a billing hold for the same reason, management should investigate the underlying problem instead of continuing identical individual corrections.

Monthly: Evaluate Charge Capture Performance

The monthly review should focus on trends.

For example, a practice may compare how many encounters developed reconciliation exceptions during successive reporting periods.

It can also examine whether charge entry delays are concentrated within particular specialties or departments.

The purpose is to identify persistent workflow weaknesses.

A monthly report should not simply state that 200 exceptions were closed.

Management should also know whether new exceptions are occurring less frequently and whether the closed records reached appropriate billing outcomes.

PROMBS supports these activities through revenue cycle management services, including charge entry, claim submission, billing reporting, and workflow monitoring.

Which KPIs Measure Charge Capture Reconciliation Performance?

A practice can submit a high number of insurance claims and still overlook completed encounters that never entered billing.

Similarly, a low clearinghouse rejection rate does not prove that all appropriate charges were captured.

These measures describe different stages of the revenue cycle.

Charge capture reconciliation KPIs should measure whether completed encounters receive appropriate billing dispositions, how long transactions take to progress, and whether unresolved exceptions are being corrected.

Recommended Charge Capture Reconciliation Dashboard

KPI	What it measures
Encounter reconciliation completion rate	Percentage of reviewed completed encounters with a verified final billing disposition
Missing charge exception rate	Percentage of reviewed encounters identified with an unresolved missing-charge issue
Charge lag	Time between the date of service and the applicable charge entry date
Charge-to-claim submission lag	Time between finalized charge entry and claim transmission
Unresolved exception aging	How long outstanding reconciliation problems remain open
Initial claim acceptance rate	Percentage of initial submitted claims accepted at the defined acknowledgment stage
Partial charge capture findings	Number or percentage of audited encounters with verified missing, inaccurate, or incompletely reviewed charge components

These metrics should use consistent populations and definitions.

For example, an encounter reconciliation completion rate can include services that were appropriately billed and encounters legitimately determined not to require a separate claim.

It should not include unresolved encounters merely because someone assigned them to a work queue.

How to Calculate the Encounter Reconciliation Completion Rate

Consider a medical practice reviewing 60 completed encounters from a defined reporting period.

After reconciliation, the billing manager confirms that:

• 46 encounters have reached the appropriate verified claim or billing outcome.
• 6 encounters have documented, valid reasons for not producing separate insurance claims.
• 4 encounters remain pending clinical documentation.
• 2 encounters contain charges held before claim submission.
• 2 encounters have unresolved claim-level rejections.

In this illustrative example, 52 encounters have verified final billing dispositions.

The remaining eight have open exceptions.

Encounter Reconciliation Completion Rate = (52 ÷ 60) × 100 = 86.7%

This percentage tells the practice how much of the reviewed population has been accounted for under its defined reconciliation endpoint.

It does not mean that 86.7% of claims were paid.

It also does not mean that the remaining 13.3% represents lost revenue.

Some pending encounters may become properly billable after documentation is completed, while others may ultimately have valid non-separately billable outcomes.

The rate should be calculated using the same methodology across reporting periods.

Measure Charge Lag and Claim Submission Lag Separately

Charge lag measures the time between the date of service and the date charges are entered.

Charge-to-claim submission lag measures the additional time between finalized charge entry and claim transmission.

For example, a patient receives care on Monday.

The billing team enters the charge on Wednesday and submits the claim on Friday.

Using elapsed calendar days, the charge lag is two days, while the additional charge-to-claim submission lag is another two days.

These stages should be tracked separately because they have different causes.

A longer charge lag may result from documentation or charge entry problems.

A longer submission lag may indicate coding review delays, unresolved claim edits, or other billing holds.

The practice should also examine median performance and older outliers rather than relying only on an average.

A small group of very delayed encounters may otherwise remain hidden in an acceptable-looking monthly figure.

Track Exception Aging by Reason and Department

A single total of unresolved encounters is useful, but it does not reveal why those encounters remain open.

For example, 30 unresolved encounters could include:

• Documentation awaiting provider completion.
• Possible partial charges requiring coding review.
• Charges stuck in an EHR interface.
• Claims held because of billing edits.
• Claims rejected before payer adjudication.

These problems require different actions.

A practice should therefore track exception age by the verified reason and responsible department.

For example, if documentation holds are consistently older than interface-related exceptions, management may need to review its clinical documentation workflow.

If clearinghouse rejections remain unresolved for several days, the practice may need to strengthen acknowledgment monitoring and claim correction procedures.

Avoid Treating Submitted Charges as Recovered Revenue

An audit may identify $20,000 in gross charges that were not previously recorded.

That finding does not mean the practice recovered $20,000.

Some services may be bundled, incorrectly documented, outside filing deadlines, or subject to contractual reimbursement lower than billed charges.

A more accurate financial evaluation distinguishes identified gross charges, correctly submitted claims, expected reimbursement where supportable, and actual payments received.

For example, a previously missing charge may ultimately produce payment, but the collected amount should be reported only after it is received and reconciled.

A successful reconciliation program improves visibility and billing accuracy. Financial recovery must be measured separately.

How to Investigate Repeated EHR-to-Billing Transfer Problems

Medical practices often use an EHR for clinical documentation and a separate practice management system for financial transactions.

These systems may exchange charge information automatically.

However, a technically functioning connection does not necessarily guarantee that every completed service reaches the correct billing account.

For example, an interface may transfer the primary office visit charge correctly while failing to map certain procedure codes or units.

The billing team may see a matching charge for every encounter and overlook incomplete transactions.

This makes repeated transfer problems particularly important to investigate.

Identify Whether the Error Begins at the Source or During Transfer

Suppose a practice discovers that several completed encounters have no corresponding charges.

The first question is whether the EHR generated the expected charge information.

If it did not, the issue may involve clinical workflow configuration or charge generation.

If it generated the information but the practice management system never received it, the problem may involve the interface.

If the receiving system accepted the transaction but assigned it to an incorrect encounter or provider, the problem may involve data mapping.

These findings should determine which team owns the corrective action.

A billing employee cannot permanently fix an interface problem by entering every missing charge manually.

Likewise, a developer cannot resolve a documentation gap by changing the interface.

Review Failed, Replayed and Incorrectly Mapped Transactions

When investigating an interface problem, compare source transaction identifiers with receiving-system records.

For example, the EHR may show that 30 charge messages were generated, but the receiving system processed only 27.

The technical team should determine what happened to the three unmatched messages.

Possible explanations include failed transmission, rejected data, incorrect mapping, or delayed processing.

However, a successful message count alone does not prove that all charge details transferred correctly.

The practice should review representative records to confirm procedure codes, units, providers, and encounter relationships.

If failed transactions are replayed after a repair, employees should verify that manual corrections made during the outage do not create duplicate charges.

Test Whether the Correction Works on New Encounters

After repairing an interface or updating a charge configuration, test new transactions.

For example, if the system previously omitted certain procedure charges, review recent encounters involving those services.

Confirm that the correct charges were generated and received.

Then verify that those charges reached the intended claim or another appropriate billing outcome.

The billing team should retain the historical exceptions until they are individually resolved.

A technical correction may prevent future errors without automatically fixing charges that were already missed.

Our article on revenue cycle workflow errors explores how communication and system handoff problems affect claim processing.

For charge capture reconciliation, the main objective is to prove that the corrected workflow consistently connects clinical activity with accurate billing records.

When Should a Practice Conduct a Charge Capture Audit?

Routine reconciliation can identify missing charges and claim holds, but a focused audit may be necessary when the same problems continue or when the practice cannot explain discrepancies between clinical activity and billing results.

A charge capture audit should examine whether documented services were appropriately coded, entered, submitted, and accounted for, while also identifying duplicate or unsupported charges.

The audit should move beyond aggregate reports and review representative encounters and their underlying records.

Warning Signs That Justify an Audit

A medical practice should consider a charge capture audit when completed encounters repeatedly lack billing records, partial charges are found during routine review, or claims remain in unresolved submission queues.

An audit may also be appropriate after an EHR migration, practice management software change, billing vendor transition, or major charge interface update.

Other warning signs include unexplained differences between clinical procedure volumes and charge reports, repeated duplicate charges, and claims rejected because of recurring data transfer problems.

These symptoms do not automatically prove that the practice has lost reimbursement.

They indicate that additional investigation may be needed.

What Should the Audit Review?

A useful audit should select encounters from a defined period and compare them with the corresponding charge and claim records.

The sample should include different providers, service locations, and service types when relevant.

For example, a multispecialty practice may need to include both routine office visits and encounters involving procedures.

The auditor should determine whether the documented services support the billing records.

The review should also identify whether charge information reached the billing system correctly and whether the intended claims were submitted and acknowledged.

Importantly, the audit should examine transactions in both directions.

That means identifying completed encounters without appropriate billing records and charges that do not have adequate supporting source information.

For services with multiple billing components, the audit should evaluate whether the relevant units and separately reportable services were accurately represented.

Example: A Targeted Audit Finds Two Different Problems

Consider a practice that selects 40 completed encounters involving a frequently performed outpatient procedure.

During the review, the coding auditor discovers that four encounters contain documentation for a potentially separately reportable service that was not reviewed during charge entry.

The auditor also finds two encounters with repeated charges that may have originated from a replayed interface transaction.

The practice should not immediately add four new claims and delete two charges.

First, a qualified reviewer should determine whether the additional services were separately billable.

Next, the billing team should confirm whether the repeated transactions are true duplicates or legitimate separate services.

Once the findings are verified, the practice can follow the appropriate correction process.

The audit should also investigate why those issues occurred.

For example, a missing-charge pattern may indicate an incomplete charge entry template, while the repeated transactions may indicate an interface control weakness.

The objective is to correct both the individual records and the processes that created the errors.

What Should the Final Audit Report Include?

The report should identify verified discrepancies, affected records, likely root causes, corrective actions, responsible departments, and the method for testing improvements.

Any financial findings should distinguish gross charges from potential collectible reimbursement.

The audit should also identify compliance concerns requiring further review.

For example, an unsupported charge may need investigation even if the claim was successfully paid.

Similarly, a missed charge should not be submitted unless documentation, coding requirements, and applicable filing rules support the claim.

PROMBS provides medical billing and coding audit services to help practices examine billing inconsistencies, identify workflow weaknesses, and review opportunities for more accurate reimbursement.

How Pro Medical Billing Solutions Improves Charge Capture and Claim Reconciliation

Medical practices depend on accurate communication between clinical documentation, coding, charge entry, and claim submission.

When these activities operate separately, completed encounters may remain unbilled, charges may be recorded incorrectly, or claims may become stuck before reaching the payer.

These problems can be difficult to identify through traditional collections reports because missing charges do not necessarily appear as outstanding accounts receivable.

Pro Medical Billing Solutions (PROMBS) provides medical billing, coding, charge capture, denial management, and revenue cycle services for healthcare providers across the United States.

Our services help practices investigate the gaps between completed patient care and the financial records used to request reimbursement.

Charge Capture and Missing Charge Identification

PROMBS supports medical practices with charge capture, charge entry, and billing record reviews.

These activities help identify completed encounters that have not progressed into the appropriate billing workflow.

For example, a practice may have several completed visits with finalized documentation but no associated charges.

The billing team can investigate whether the transactions were missed, delayed, or handled through another billing arrangement.

If appropriate billing activity is missing, the next step is to verify the documentation and determine whether a valid charge can be entered.

Our objective is to help practices account for legitimate billable services without creating unsupported charges.

Documentation-Based Medical Coding Reviews

Some discrepancies cannot be resolved by a billing specialist alone.

For example, a completed encounter may contain multiple documented services, but the coding team must determine which are separately reportable.

PROMBS provides medical coding support for ICD-10, CPT, HCPCS, and applicable modifiers.

These reviews help practices determine whether the recorded charges accurately represent the documented services and comply with relevant coding requirements.

For example, a coding review may identify an omitted procedure charge or determine that a service was correctly bundled.

Both outcomes are useful for reconciliation.

The purpose is to establish an accurate billing disposition rather than automatically increasing the number of charges.

Claim Creation, Submission and Clearinghouse Follow-Up

Charge entry is only one stage of the revenue cycle.

PROMBS supports claim preparation, claim scrubbing, submission, and clearinghouse follow-up.

These activities help practices identify charges that have not reached the intended claim submission process.

For example, a charge may remain in a claim hold because of incomplete provider or insurance information.

Our billing specialists can investigate the issue and support the appropriate correction process.

We also monitor available claim acknowledgments and rejection information to help distinguish transmitted claims from those accepted for payer processing.

This is important because a practice may have accurately captured its charges while still experiencing delays before claims enter adjudication.

Reconciliation and Billing Audit Support

PROMBS offers charge capture reconciliation through its broader medical billing and coding audit services.

These reviews can help practices investigate whether completed clinical encounters have corresponding billing records and whether the recorded charges are accurate.

For example, an audit may identify missing charges, incorrect units, duplicated transactions, or encounters that remain in unresolved billing queues.

The findings can guide corrective actions involving coding, charge entry, documentation, and system workflows.

When the problem involves an EHR interface or another technical configuration, the relevant practice and system teams may need to assist with implementing the correction.

A useful audit should provide actionable findings, not simply a list of unmatched records.

Exception Tracking and Revenue Cycle Reporting

Practice owners need to know where billing exceptions are occurring and how long they remain unresolved.

PROMBS supports revenue cycle reporting and workflow monitoring to help practices understand claim processing activity.

For example, a practice may want to identify which providers have the most encounters awaiting documentation.

Another practice may need to determine whether claim holds have increased following a system update.

These findings can support more targeted operational improvements.

Reconciliation reporting should also distinguish appropriately billed encounters from valid non-separately billable outcomes.

This prevents practices from treating every encounter without an individual insurance claim as a financial loss.

Ongoing Process Improvement

A one-time audit may identify previously missed or inaccurate charges.

However, the underlying problem may return if the workflow responsible for the discrepancy remains unchanged.

PROMBS supports ongoing billing process reviews and helps healthcare practices identify recurring claim preparation and submission issues.

For example, a practice that repeatedly experiences missing procedure charges may need to revise its charge entry workflow.

A practice that consistently encounters billing holds may need to investigate provider data or claim validation requirements.

These improvements should be tested using new transactions, not assumed successful merely because historical errors were corrected.

Our goal is to help healthcare practices connect clinical documentation with accurate charges, appropriate claim submission, and reliable revenue cycle reporting.

Frequently Asked Questions About Charge Capture Reconciliation

What is charge capture reconciliation in medical billing?

Charge capture reconciliation is the process of comparing completed patient encounters and documented services with posted charges, submitted claims, and available acknowledgment records.

It helps practices identify missing charges, inaccurate billing details, duplicate transactions, and encounters that have not reached an appropriate billing outcome.

How do you reconcile completed encounters to submitted claims?

Begin with a completed encounter report from the EHR.

Match the encounters to charge records in the practice management system, then connect those charges with the related claims and acknowledgment information.

Investigate unmatched records and document whether each encounter was appropriately billed, remains pending, or legitimately does not require a separate claim.

What reports are needed for charge capture reconciliation?

The three core reports are a completed encounter report, a posted charge report, and a submitted claim and acknowledgment report.

Additional documentation, coding records, interface logs, or payment information may be required to investigate particular discrepancies.

Can one patient encounter have multiple charges?

Yes.

A patient encounter may involve several properly documented and separately reportable services.

However, multiple charges must be supported by the clinical record and applicable coding requirements.

The billing team should not assume that every documented activity qualifies for a separate charge.

How can a practice identify partially captured charges?

Partial charge capture can be identified by comparing documented services and procedures against the individual charge lines recorded in the billing system.

For example, an encounter may have an office visit charge while another documented procedure has not been reviewed for billing.

A qualified coding specialist should determine whether the additional service is separately reportable.

Does a submitted claim mean the insurance payer accepted it?

No.

A transmitted electronic claim may pass an initial technical acknowledgment and still fail a later claim-level acceptance check.

For Original Medicare electronic claims, the 999 acknowledgment and 277CA claim acknowledgment describe different stages of processing.

Claim acceptance also does not guarantee payment.

How often should a practice perform charge capture reconciliation?

Daily exception reviews are useful for identifying newly completed encounters that require attention.

Weekly reviews help ensure unresolved issues are progressing, while monthly analysis can reveal recurring billing and system problems.

The exact schedule should reflect the practice’s patient volume and operational needs.

What is the difference between charge lag and charge capture reconciliation?

Charge lag measures the time between a healthcare service and entry of its charges into the billing system.

Charge capture reconciliation verifies whether completed encounters and documented services have appropriate corresponding charges and billing outcomes.

A practice can have a short charge lag but still miss charges or experience claims that never reach the payer.

Can charge capture reconciliation reduce revenue loss?

It can help practices identify appropriately billable services that were omitted or delayed and reveal problems preventing accurate claim submission.

However, the amount ultimately collected depends on documentation, coverage, coding rules, timely filing requirements, contractual reimbursement, and payer adjudication.

A missing charge does not automatically represent recoverable revenue.

How can PROMBS help with charge capture reconciliation?

PROMBS provides medical billing, charge capture, coding, claim submission, billing audits, and revenue cycle reporting services.

Our team can help practices investigate unmatched encounters, review charge accuracy, identify unresolved billing issues, and support processes that connect completed clinical services with appropriate claim submission.

Identify Missing Charges With a Free PROMBS Billing Audit

A medical practice can see patients every day, maintain complete clinical records, and submit hundreds of insurance claims while still experiencing gaps between care delivery and billing.

Some encounters may never generate charges.

Others may contain only part of the appropriate billing information.

Some claims may be created but remain in unresolved hold queues, while others are transmitted without successfully passing the payer’s acceptance checks.

These problems can remain hidden when a practice evaluates billing performance using claim counts or collections alone.

Charge capture reconciliation helps healthcare practices verify that completed patient encounters, documented services, posted charges, and submitted claims are accurately connected.

The purpose is not to bill every clinical activity separately.

It is to account for the services provided, identify appropriate billing opportunities, prevent unsupported charges, and resolve the issues that interrupt the revenue cycle.

By reviewing clinical and billing records together, assigning clear responsibility for exceptions, and measuring whether corrective actions work, practices can build more reliable charge capture processes.