Medicare Part B Compliance Watchpoints for SNFs
Eric HansenFounder, Burst BillingJuly 20, 20269 min readThere is a window between when a supply gets ordered and when a claim goes out. That window is where compliance lives.
Most billing teams focus on what happens after submission: approvals, denials, remittances. Compliance teams know the real work happens before. The decisions made in that pre-claim window determine whether a facility builds revenue or builds exposure.
The same six places come up where a missed check creates a problem. Each one is a place where catching an error before submission is cheaper, faster, and easier than correcting it afterward.
1. Resident status and consolidated billing
The first place things go wrong, and the quietest.
During a covered Part A stay, consolidated billing generally requires the SNF to submit claims for the services a resident receives, with specific exclusions under 42 U.S.C. § 1395x(s). Bill a bundled item separately and you've created an overpayment with a 60-day clock on returning it.
The risk is not intentional. It is assuming status without verifying it. A documented status check for the dates under review is the catch that prevents the overpayment.
2. Documentation completeness
A claim is only as strong as what supports it.
Four elements connect a claim to a covered service: the item or supply, the resident's medical need, the physician order, and the proof of delivery or use. Any one missing, and the claim is exposed on audit. See the full documentation requirements for Part B supplies.
Label each file: complete, incomplete, unclear, or excluded. That habit gives the team a consistent way to pause a weak file before it goes out.
3. Coverage and code alignment
HCPCS Level II codes identify the supplies and products that CPT doesn't cover, including surgical dressings, ostomy, urological, and tracheostomy supplies, and orthotics. A code existing in the system is not the same as that code being covered for the conditions in front of you.
The Medicare Coverage Database spells out Local Coverage Determinations: the specific coverage conditions, modifiers, quantity limits, and documentation requirements for each item. See how LCDs govern Part B coverage. Confirming coverage before submission is not optional.
The error to catch: using a code because it looks close, without confirming the LCD conditions line up.
4. Supplier and vendor visibility
Vendors provide useful invoice and delivery detail. What they can't provide is visibility into how billing decisions get made under your facility's name.
If you're using a third-party supplier, ask for records that connect each item back to the chart and the claim decision. If the reporting is too general to show that chain, the gap is yours to answer for. Under 42 CFR 411.15(p)(2) and the BBA 1997 framework, the facility holds the billing relationship with Medicare.
A vendor arrangement that obscures that chain creates compliance exposure the facility may not see until an audit.
5. Denial and appeal patterns
A denial is an error that already got out. The question is whether your process reads it.
A repeated denial reason points upstream. It points to a documentation habit, a coding issue, a status assumption, or a weak intake step. Track denial reasons by type and review them monthly. If the same reason appears 3 months running and the workflow hasn't changed, the process isn't correcting.
An appeal with strong documentation is winnable. A pattern of denials with no corresponding workflow change is a compliance gap, not a billing problem.
6. Audit-ready file discipline
An audit doesn't arrive with a warning, and it doesn't wait for you to organize a response.
For each submitted claim, the facility should be able to show: what was reviewed, what documentation supported the claim, who approved it, and where the records are stored, without searching across email threads, EHR notes, vendor files, and billing exports.
Build the record as the decision happens. The audit file is a byproduct of a process that documents its reasoning, not a project that starts when someone asks.
What the six watchpoints cover, in one place
| Watchpoint | The error it catches | The exposure it prevents |
|---|---|---|
| Resident status and consolidated billing | Status assumed, not verified | A bundled item billed to Part B; an overpayment to repay within 60 days |
| Documentation completeness | Order present, proof of use missing | A claim that fails audit for lack of support |
| Coverage and code alignment | Code used without confirmed LCD conditions | A denial, or a claim that can't be defended |
| Supplier and vendor visibility | Third-party billing without facility oversight | Answering for a claim you never reviewed |
| Denial and appeal patterns | Same denial reason repeating without response | A fixable gap that compounds quietly |
| Audit-ready file discipline | Records scattered across systems at audit time | A scramble, or a failure, when the auditor asks |
The principle underneath all six is the same. Don't submit what you can't support. Don't assume when status or coverage is unclear. Don't let the dollar move faster than the documentation.
That holds some items back. It also means every item that does move forward is one you can defend.
"In billing, the claims you held back and the reasons you wrote down are your proof that the process is working. Show me a facility that never excludes a thing, and I'll show you one that isn't looking."
When someone asks what compliance-first Part B billing looks like in a SNF, the answer is this: a workflow that answers six questions before a claim goes out, not after it comes back.
Schedule a free 30-minute assessment with Burst to see where your current workflow stands on each watchpoint. You'll get the findings in writing.
Compliance note
This article is for general educational purposes only and does not replace facility-specific compliance, billing, legal, or payer guidance. SNFs should verify coverage, coding, documentation, and submission decisions against applicable CMS guidance, payer rules, and their own compliance policies.
References
Related
Written by
Eric Hansen
Founder, Burst Billing
Eric Hansen is the founder of Burst Billing. He has spent over a decade helping skilled nursing facilities recover missed Medicare Part B supply reimbursement through cleaner documentation, tighter vendor workflows, and risk-free billing reviews.
More from Eric →Frequently asked questions
- Six: resident status and consolidated billing, documentation completeness, coverage and code alignment, supplier and vendor visibility, denial and appeal patterns, and audit-ready file discipline. Each one is a place where reviewing before submission prevents a more expensive correction afterward.
- Before, and throughout the review process. Compliance shapes the first status check, the documentation review, the coding decision, and the exclusion call. Building it into the workflow before submission is what keeps reimbursement work from creating audit exposure.
- Because they are evidence the process is working. An exclusion log shows the review applied judgment and reveals patterns worth examining. A billing process that never excludes anything is not clean billing. It is not looking closely enough.
- Treat each denial as process data. A reason that repeats points upstream to a documentation gap, a coding issue, or a status problem. Review denial trends monthly and change the workflow when a reason repeats. If the same reason appears without a corresponding correction, the process is not learning.
- The file is organized before anyone asks. For each submitted claim, the facility can show why it was reviewed, what documentation supported it, who approved it, and where the records are stored, without reassembling pieces from scattered systems. Building the file as the decision happens is what makes it audit-ready.
- During a covered Part A stay, consolidated billing generally requires the SNF to submit the claims for most services the resident receives, with specific exclusions. The risk is assuming a resident's status without verifying it, which can result in billing a bundled item separately and creating an overpayment. Verify status for the dates under review.
- A simple one: don't submit what you can't support, don't assume when status or coverage is unclear, and don't let reimbursement move ahead of documentation. It holds back some items. It strengthens every claim that does move forward.
See what your facility may be missing
A 30-minute reimbursement assessment will surface eligible Part B supply revenue you're not capturing today. No upfront cost. No commitment.