The basics of revenue integrity come down to one question: does every service performed turn into a correct charge, supported by the record, at the right price? A basic revenue integrity program checks charge capture, the chargemaster, the documentation behind charges and pricing each month. It looks for both missed charges and charges that should not exist.
What does a revenue integrity function cover?
A revenue integrity function covers four areas: charge capture, the chargemaster, documentation that supports each charge, and pricing. Its job is to make sure the bill matches what was done and what the record shows, before and after the claim goes out. It sits between the clinical record and the billing office.
Charge capture
Charge capture is the step where a performed service becomes a line on the patient's account. A missed charge loses money. A charge entered twice, or for a service that did not happen, bills the payer for something that was not done. Revenue integrity checks that the two lists, services done and charges posted, match.
The chargemaster
The chargemaster is the master price list. The federal hospital price transparency rule, at 45 CFR 180.20 (eCFR, current as of 2026-10-14), defines it as "the list of all individual items and services maintained by a hospital for which the hospital has established a charge." Clinics keep a similar fee schedule. Each line ties a description to a code, a price and, for hospitals, a revenue code.
Documentation behind each charge
A charge is only as good as the record that supports it. If the visit note does not describe the service, the charge cannot be defended in an audit. Revenue integrity samples charges and reads the record behind each one. Checking that the codes match the clinical documents is a coding audit, which has its own method in the guide on how coding audits catch automated coding mistakes.
Pricing
Pricing checks that each chargemaster line carries the price the organization approved, that it is updated when it should be, and that the public price files match the internal one. Under 45 CFR 180.50, a hospital must update its public standard charge information "at least once annually."
Revenue integrity versus revenue cycle operations and coding compliance
Revenue integrity, revenue cycle operations and coding compliance overlap but own different problems. Revenue cycle operations moves claims and money through the process. Coding compliance makes sure codes follow the rules and the record. Revenue integrity makes sure the charges that start the process are complete, supported and correctly priced.
Who owns which problem
| Problem | Owner | Example |
|---|---|---|
| A claim is denied for a missing field | Revenue cycle operations | The billing team fixes and resends it |
| A code does not match the documentation | Coding compliance | A coder reviews the note and corrects the code |
| A procedure was done but never charged | Revenue integrity | The charge is found in reconciliation and added within the filing limit |
| A chargemaster line has an outdated code | Revenue integrity | The line is fixed before more claims use it |
| A payer pays below contract | Revenue cycle operations | The team disputes the payment |
The handoffs matter more than the boxes. Revenue integrity often finds a problem it does not fix itself: a pattern of missed charges in one department goes back to that department's charge entry process. A denial trend that traces to one chargemaster line comes back from the denial team. Deciding whether to fix a claim or dispute a payer's decision is its own skill, covered in corrected claim vs reconsideration vs appeal.
In a small practice, one billing manager may hold all three roles. The split still helps, because it names the question being asked: is the claim moving, is the code right, or is the charge complete?
Charge capture reconciliation for revenue integrity
Charge capture reconciliation for revenue integrity compares three lists for each day: services scheduled, services performed and charges posted. Every performed service should have a posted charge, and every posted charge should have a performed service. A gap in either direction is a finding to resolve before the claim leaves.
The daily match
- Start from the schedule. Pull every appointment and procedure for the day, including add-ons booked on the day.
- Mark what was performed. Use the visit notes, procedure logs or encounter forms. Cancelled and no-show visits drop out.
- Compare to posted charges. Each performed service should have a charge with the right date, provider and code.
- List the gaps. A performed service with no charge is a missed charge. A charge with no performed service is a possible overcharge. A charge posted days later is a late charge.
A fictional reconciliation
This example is made up for illustration. On a fictional clinic day, the schedule held 42 visits. Two were no-shows, leaving 40 performed. Charges were posted for 38 of them on the day. One visit, for patient Robin Example, had its charge posted three days later, which makes it a late charge. One injection given during a visit for patient Casey Sample had no charge at all, a missed charge. A third charge was found for a visit that was cancelled, a charge that should be reversed.
Finding late and missed charges
Late charges usually trace to a person or a step: a provider who signs notes days later, or paper encounter forms batched at the end of the week. Missed charges cluster around add-on services, supplies and procedures done during another visit. Track gaps by department and provider so the pattern points at a process. For Medicare institutional claims, the Medicare Claims Processing Manual, chapter 1 (Rev. 13725, issued 04-10-26), section 130.1.3, says most charges found after billing go out as a late charge bill (type xx5), while some, such as inpatient accommodation charges, must go as an adjustment request. How the filing limit applies to each is covered in where each clock starts at Medicare.
Chargemaster reviews in a revenue integrity program
Chargemaster reviews in a revenue integrity program check each line's code, revenue code, description and price against current code sets and the organization's pricing decisions. Plan a full review once a year, with smaller reviews after each code update. A wrong line affects every claim that uses it until someone fixes it.
Code updates
Codes change on a published schedule. The CMS HCPCS overview page says the American Medical Association "annually republishes and updates CPT codes." The CMS HCPCS quarterly update page (last modified 09/23/2026) posts the official Level II update files each quarter. The CMS ICD-10 codes page lists new diagnosis and procedure codes effective October 1, 2026, with procedure code updates also issued for April. After each update, find every chargemaster line that uses a deleted or changed code and fix it before the effective date.
Revenue codes
Hospital chargemaster lines also carry a revenue code, the four-digit code that groups charges on the UB-04. The Medicare Claims Processing Manual, chapter 25 (Rev. 12423, 12-20-23) says the provider enters revenue codes in form locator 42 "to identify specific accommodation and/or ancillary charges," and that the codes are available from Medicare contractors and from the NUBC's official UB-04 data specifications manual. A review checks that each line's revenue code fits the service and the department, for example that a supply is not grouped as a room charge.
Prices
The price review compares each line with the approved price list and looks for lines that never changed when others did. It also checks that the same service is not listed twice at two prices. For hospitals, 45 CFR 180.20 defines the "gross charge" as "the charge for an individual item or service that is reflected on a hospital's chargemaster, absent any discounts," so the public file and the chargemaster should agree.
Which revenue integrity metrics show lost revenue?
The revenue integrity metrics that show lost revenue are the late charge rate, the missed charge rate and the charge correction rate. Each compares a count of problem charges with all charges in the same period. Rising numbers point at a process that is losing money or creating rework.
Working formulas
There is no single published standard for these three, so define them in writing and keep the definitions fixed. These working definitions are used in this post:
| Metric | Formula | What a rise means |
|---|---|---|
| Late charge rate | Charges posted more than your set number of days after the service date ÷ all charges posted in the period | Charges are entered slowly, delaying claims |
| Missed charge rate | Performed services found with no charge during reconciliation ÷ performed services reviewed | Services are done and never billed |
| Charge correction rate | Charges changed or reversed after posting ÷ all charges posted in the period | Charge entry is error-prone and creates rework |
A fictional example: in a month with 4,000 charges, 120 were posted more than three days late, a late charge rate of 3.0%. Reconciliation of 500 sampled services found 6 with no charge, a missed charge rate of 1.2%. Staff changed or reversed 88 charges after posting, a charge correction rate of 2.2%. The numbers are invented; set your own baseline from your first three months.
Monthly checklist
| Check | Source documents | Owner | Red flag |
|---|---|---|---|
| Charge capture reconciliation | Schedule, visit notes, procedure logs, charge report | Revenue integrity analyst | A performed service with no charge, or a charge with no service |
| Late charge review | Charge report with posting and service dates | Billing manager | Late charges clustered by one provider or department |
| Charge corrections | Adjustment and reversal log | Billing manager | One charge code corrected again and again |
| Documentation sample | Visit notes and the matching claims | Coding lead | A charge the note does not support |
| Chargemaster code check | Chargemaster, latest code update files | Chargemaster coordinator | A deleted or changed code still active |
| Price check | Chargemaster, approved price list, public price file | Finance lead | A price that differs between lists |
| Eligibility and payer match | Eligibility records, posted claims | Front-end lead | Charges billed to a plan that was not verified |
| Overbilling review | Duplicate charge report, credit balance report | Revenue integrity analyst | Duplicate charges or unexplained credits |
The eligibility row links two functions: a charge billed to the wrong plan is lost revenue even when the charge itself is right. Setting up those checks is covered in insurance eligibility verification automation.
These rates belong next to the wider dashboard numbers. The formulas for weekly figures such as clean claim rate and days in AR are in RCM KPI dashboard metrics and their formulas.
Revenue integrity reviews that only look for underbilling
Revenue integrity reviews that only look for underbilling are a common mistake. A one-way audit counts missed charges as recovered revenue and stops. It ignores duplicate charges, charges for services not performed and codes the record does not support. Those are overbilling, and they create money that must be paid back.
Why one-way audits fail
An audit that only looks for missed charges teaches staff that the goal is more charges. It reports a win every month while the same process that misses one charge may double another. The findings are lopsided by design, so they cannot show whether charge entry is accurate, only that it is incomplete.
What overbilling turns into
An overbilled Medicare or Medicaid claim that was paid becomes an overpayment, with a federal deadline to report and return it once it is identified. The deadline, the reporting routes and the consequences of keeping the money are set out in how fast a payer overpayment must be returned. The practical point is that an audit that finds overbilling starts a clock, so the review has to look for it on purpose.
Making the review two-way
Count findings in both directions in the same report: missed and late charges on one side, duplicate, unsupported and wrongly priced charges on the other. Sample charges that were billed, not only services that were not. Route every overbilling finding to the credit balance queue, where the refund steps are laid out in credit balance and patient refund processing.
Where document data fits
Charge reconciliation depends on reading many documents: encounter forms, claims, statements and remittances. Schema Care turns claims, billing statements and medical records into structured fields, each with a confidence score and a link to its place on the page, so a reviewer can trace a charge back to its source. The list of documents it reads is on the homepage. Choosing what to charge and what to correct stays with your billing and coding staff.