Billing & Revenue Cycle Management
End-to-end claims management built specifically around DMEPOS billing, from first submission through final collection.
Most billing companies will tell you they submit claims and follow up on denials. That’s a description of a job title, not an explanation of the work. What determines whether a DME operation gets reimbursed consistently is what happens at every stage between an order coming in and a payment clearing. That means what gets checked, what gets documented, and what gets caught before it becomes a denial.
Revenue doesn’t begin when a claim is submitted. It begins earlier, with understanding what the patient’s plan actually covers, reviewing whether the documentation supports the requested item, confirming what the payer requires, and making sure the file is actually ready to move forward before it does. Below is what happens at each of the seven stages, and how each one prepares the file for the next.
How We Manage Every Stage of Your Revenue Cycle
Seven connected stages, not seven unrelated tasks.
Eligibility Verification
“Do we understand the patient’s actual coverage?”
Eligibility verification is not the same as confirming that a member has active insurance. Active coverage tells you almost nothing about whether the specific DME benefit, purchase benefit, or cost-sharing structure that applies to the requested item is favorable, limited, or excluded. Our staff check eligibility through the applicable payer systems and review the plan information available for the requested equipment.
Not every payer portal returns every field below in the same format, and benefit structures vary by plan. This reflects the categories of information staff work to confirm, not a guaranteed data set for every plan.
Clinical Review
“Does the documentation actually support the requested equipment?”
After eligibility, our team reviews the requested product against the supporting documentation on file (the applicable HCPCS code, diagnosis, medical records, and the order or prescription), along with any other documentation a specific payer requires. The purpose is to determine whether what’s on file appears to support the request, and to identify gaps before the file moves forward, not to make the clinical decision itself. That determination stays with the prescribing physician; our review is a documentation check against the applicable payer’s requirements.
Prior Authorization
“Does this payer require authorization, and if so, what’s the status?”
Payer portals and online lookup tools can indicate whether an authorization requirement applies, and they’re used as a starting reference point. They aren’t treated as the final word for every individual plan and item, since portal information doesn’t always reflect a member’s specific situation. Where confirmation is needed, our authorization staff verify the requirement directly with the payer and document what was communicated. Not every authorization requires a phone call, and not every payer requires the same process, but where the portal information is unclear or the item is borderline, that verification step happens before the team relies on it.
Portal / Online Lookup
Used as an initial reference point for whether a requirement may apply to the specific plan and item.
Payer Confirmation (When Needed)
Staff communicate directly with the payer to confirm the requirement and any documentation needed, and log the response.
Shipment Readiness
“Has the file actually reached the right checkpoint before it ships?”
Shipment readiness exists as a separate checkpoint because the preceding stages don’t automatically mean a file is ready to move. Depending on the payer and the case, the team confirms where the file stands on eligibility, clinical documentation, authorization, and the order and supporting documentation before shipment proceeds.
Shipment readiness is a workflow checkpoint, not a payment guarantee.
Claim Submission & Documentation
“Can this claim and its documentation actually go out consistently?”
Before a claim goes out, the team reviews the claim information and supporting documentation for consistency against the applicable payer’s requirements and the patient’s file. Not every payer requires the same documentation, so this is a check against that specific payer’s requirements, not a fixed checklist applied identically everywhere.
After submission, the team monitors claim status and follows up when the payer indicates action or additional information is needed. Where our workflow includes a status check the following business day, that’s an internal operational practice, not a payer requirement or a payment timeline we’re promising.
Payment Posting & Reconciliation
“What did the payer actually do with this claim?”
Payment posting isn’t recording a deposit. When payer payment or remittance information comes in, the team reviews it (amount paid, patient responsibility where applicable, adjustments, denial or non-payment information, and remaining balance), and posts it to the corresponding claim. Where the client relationship and payer arrangement support it, a discrepancy between an expected and received amount may prompt further review; contracted rates, allowed amounts, and plan design vary, so this isn’t checked against a single universal benchmark.
Denial Management & Appeals
“If this claim wasn’t resolved, what did the payer actually say, and what’s the appropriate next step?”
A denial isn’t just a notice that a claim failed. The team first identifies the specific reason the payer cited (which may involve missing or insufficient documentation, an order or authorization issue, a coding or claim-data issue, or a coverage or eligibility limitation, among other payer-stated reasons), rather than assuming the cause.
Effective denial management means understanding why a claim was denied before deciding what to do about it. Not every denial has a viable path to resolution, and the reason cited determines what, if anything, can be done next. We don’t treat every denial as automatically appealable.
Common Questions
How is this different from billing software we could just buy ourselves?
Software can flag some errors against a rule set. It doesn’t review whether a referral’s documentation actually supports the requested item, confirm a payer’s authorization requirement when portal information is unclear, or judge whether a specific denial has a viable path to resolution. Those are judgment calls made by people working the file, using software as one tool among several.
Do you take over our existing denied claims, or only new claims going forward?
Both, generally. Existing denials are reviewed to identify the payer’s stated reason and whether a corrected claim, reconsideration, or appeal appears to be an appropriate next step, rather than assuming an existing denial is closed.
How do you handle the fact that Medicare and commercial payer rules are different?
Medicare requirements, including those tied to DME MAC review, are treated separately from commercial payer requirements, which vary by payer, plan, network status, and product. A Medicare-specific rule isn’t applied to a commercial claim, and one payer’s requirement isn’t generalized across all payers.
What happens if a claim is denied for something outside your control, like an authorization we didn’t tell you had lapsed?
We identify what happened, document it, and pursue the applicable next step, such as a corrected claim, reconsideration, or appeal, where one appears available. Tracking authorization windows against delivery schedules as part of the file review is meant to reduce how often this kind of gap occurs in the first place, though it can’t eliminate it entirely.
How much visibility do we get into what’s happening with our claims?
Reporting is provided on a regular basis, and status on a specific claim, authorization, or denial can be requested outside of that schedule as well.
What does a denied claim actually cost us, beyond the lost reimbursement?
Reworking a denied claim takes staff time regardless of whether it’s ultimately resolved. Reviewing documentation and authorization status before a claim is submitted is intended to reduce how often that rework is needed, though it doesn’t eliminate denials entirely.
Revenue Cycle Readiness Checklist
- DME-specific benefit and plan details reviewed, not just active/inactive status
- Clinical documentation reviewed against the requested item before the file moves forward
- Authorization requirement and status confirmed and documented, when applicable
- Order and supporting documentation assembled before shipment
- Claim and supporting documentation reviewed for consistency before submission
- Remittance and payment information reviewed against the claim, not simply posted
- Denials reviewed for the payer’s stated reason before deciding on next steps
What This Includes
- Claims submission & documentation review
- Prior authorization support
- Denial management & appeals
- Payment posting & reconciliation
- Collections follow-up
- Regular performance reporting
See Our Other Services
Credentialing, enrollment, accreditation, and compliance, all built to support this core revenue cycle.
View All Services