Home/Integrations/EHR/Kipu
For behavioral health facilities using KipuThe Census Was Full. Why Wasn't the Revenue?
In facility-based care the claim is largely decided before it is ever submitted: at the benefit check, at admission, and at every continued-stay review after that. Keep Kipu. Find out where the authorized days are going.
Start with the free CareVixis practice assessment. No email required.
The Census Was Full.
The beds were occupied, the programme ran, and the clinical work happened exactly as it should have.
A Delivered Day Is Not Yet a Paid Day.
Between the day being delivered and the day being paid sit authorisation, level of care, documentation and timely filing, and any one of them can quietly disqualify it.
So the Revenue Does Not Match the Census.
You can run a full programme and bill for less of it than you delivered, and nothing in the census will ever tell you which days went missing.
The clinical record says the day happened. The remittance says nobody paid for it.
We Reconcile Delivered Days Against Paid Days.
CareVixis compares days delivered with days paid, reads the remittances behind the difference, and records why each gap exists.
That is where an episode-based programme actually loses revenue.
Keep Kipu.
Kipu is built for this level of care and replacing it is not on the table here. The billing reconciliation sits beside it.
Keep Kipu. Stop losing days you already delivered.
Everything below is the evidence for what you just read.
What Kipu publishes about its own platform, the six places a delivered day stops being a paid day, a ten-question framework you can put to any billing company, and the source for every fact on this page. If you have what you came for, you can stop here.
Why is facility billing decided before the claim is submitted?
Because everything that determines payment happens earlier. What the benefit check actually established. What level of care was authorized, and for how many days. Whether each continued-stay review was completed, submitted and accepted while the patient was still in the building.
By the time the claim goes out, most of its fate is already set. That is why a facility can run at capacity, deliver excellent care, bill cleanly, and still find that a material share of delivered days never turn into revenue.
Kipu Covers the Whole Episode
Facility care is not an outpatient practice with more beds, and Kipu is built for the difference. Everything below is Kipu's own published description.[1]
| What it does | How Kipu describes it |
|---|---|
| One platform for the episode | "Kipu connects admissions, clinical care, compliance, billing, and business intelligence in one platform." |
| End to end | "From first inquiry to final claim, Kipu supports every step of the journey." |
| Across the continuum | Connects those functions "across every location and level of care". |
| Admissions and CRM | Keeps "every lead, referral, outreach touchpoint, admissions workflow, and alumni relationship connected". |
| Clinical record | Documentation support, medication management, labs and telehealth in one connected record. |
| Scale | Kipu states it serves thousands of facilities globally. |
A facility with admissions, clinical and billing in one system has removed the handoffs that lose information. That is a real advantage, and it is not the same as knowing why a payer refused a Tuesday in week three.
Six Places a Delivered Day Stops Being a Paid Day
These are the failures that produce facility write-offs. Notice how few of them are billing errors in the ordinary sense.
The benefit check was optimistic
What was quoted at verification and what the plan actually covers for this level of care are not always the same, and the gap surfaces weeks later as a denial.
Authorization covers a different level than delivered
Authorized for one level, delivered at another. Clinically defensible, financially fatal, and usually discovered after discharge.
A continued-stay review slipped
Reviews are time-boxed. A review completed late, or completed and not accepted, can end payment for days that were still being delivered.
The step-down never reached billing
A patient moves from residential to PHP to IOP during one episode. If the change is in the chart but not in the billing, the claim contradicts the record.
Length of stay outruns the approval
Care continues because the patient needs it. Approved days do not extend themselves, and the unapproved tail is written off quietly.
Single case agreements and out-of-network terms
Negotiated per-case terms are only as good as the claim that matches them. Nobody checks the payment against the agreement unless somebody owns that job.
Almost none of this is visible one claim at a time. It is visible in the pattern: which payer, which level of care, which reviewer, which week of stay. That is the difference between working denials and understanding them.
Where This Fits Around What You Already Run
An illustration of the general flow for a facility keeping Kipu, not a description of any specific configuration.
- Inquiry, verification and admissionBenefits are checked, the level of care is authorized, the episode begins in Kipu.
- Care, reviews and step-downsContinued-stay reviews are submitted; the level of care changes as the patient progresses.
- Claims, clearinghouse and payerDays are billed and adjudicated, in whole or in part.
- The remittance comes backPaid days, denied days, adjustments and the payer's reason codes.
- VixisIQ™Where appropriate data can be obtained and normalized, the remittance information is analyzed by payer, level of care, week of stay and reviewer.
- VixisTrace™A lost day is investigated back to its cause: verification, authorization, review timing, step-down or agreement terms.
- Corrective action, with an ownerWhat changed, who owns it, and whether the same days stop being lost next month.
How Should a Facility Evaluate a Revenue Cycle Partner?
Nine questions for whoever handles your revenue today, for Kipu's own services, and for CareVixis. Facility revenue turns on different things than practice revenue, and the questions should too.
-
Who owns verification, and is it ever checked afterwards?
Ask whether anyone compares what was quoted at VOB against what the payer actually did.
-
Who is accountable for continued-stay review timing?
Not who performs it. Who is accountable when one is late, and who reports the days lost because of it.
-
Can they show lost days by level of care?
If the answer is a total write-off number, they cannot tell you where the problem is.
-
Do they reconcile step-downs between chart and claim?
Ask what catches a level-of-care change that reached the record but not the billing.
-
Are payments checked against single case agreements?
A negotiated rate that nobody verifies is a hope, not a contract.
-
What happens the third time the same payer denies the same week?
Ask for a root cause they found, what changed, and how they knew it worked.
-
Will they work inside Kipu?
Ask what they need from it and what changes if you keep it. CareVixis treats keeping Kipu as a supported outcome.
-
What will leadership see, and how often?
Then the harder version: what would have told you a payer had tightened its criteria six weeks ago?
-
Is the work performed in the United States?
Ask about subcontractors as well as staff. CareVixis is 100% US based and does not outsource.
Using Kipu? Keep It.
Your admissions, clinical and compliance workflows are built in it, across every location you run. Moving a facility platform is a serious undertaking, and it would answer none of the questions on this page.
Keeping your system is a supported outcome, not a fallback. If you later want to move to the CareVixis platform, that move may be offered at no additional migration charge. Keeping the EHR you already have carries no monthly software fee from CareVixis.
Keep Kipu. Stop losing days you already delivered.
Questions Facilities Ask
Do I have to leave Kipu to work with CareVixis?
No. Keeping Kipu is a supported outcome, not a fallback. CareVixis claims no API integration, certification or partnership with Kipu, and what is agreed before any commitment is which revenue-cycle data can be obtained and how.
What is different about billing across levels of care?
A patient can move between detox, residential, partial hospitalization and intensive outpatient during one episode. Each level has its own authorization, its own billing rules and its own documentation expectations, and a step-down recorded clinically but not reflected in billing produces days that will not be paid.
Our denials are mostly utilization review. Is that a billing problem?
It is a revenue problem with a clinical and an administrative half. The administrative half is measurable: whether reviews happened on time, whether the clinical record supported the level billed, and whether the same reviewer or payer accounts for a disproportionate share of lost days.
Kipu offers its own revenue cycle services. Why look elsewhere?
You may not need to, and a facility satisfied with its arrangement should keep it. What CareVixis offers is a different shape: a revenue management company rather than a service attached to the platform, with claim root cause analysis and pattern analysis as the core of the work.
Does CareVixis make clinical or medical necessity judgements?
No. Level of care and continued stay are clinical decisions, made by your clinicians against the payer's criteria. CareVixis works on the revenue consequences: what was authorized, what was billed, what came back, and why.
Keep Kipu. Add Revenue Intelligence.
Keep your platform. Keep your clearinghouse. Change what happens after the data comes back.
Free. No obligation. No email required.
Sources
- Kipu, product overview. Source of the quoted descriptions: "Kipu connects admissions, clinical care, compliance, billing, and business intelligence in one platform"; "From first inquiry to final claim, Kipu supports every step of the journey"; connecting those functions "across every location and level of care"; and keeping "every lead, referral, outreach touchpoint, admissions workflow, and alumni relationship connected". kipuhealth.com. Accessed 18 September 2026. These are Kipu's own published descriptions of its product. CareVixis has not independently tested them and makes no claim about them.
- Centers for Medicare & Medicaid Services, Transactions (HIPAA Administrative Simplification), for the remittance advice standard referenced above. cms.gov. Accessed 18 September 2026.
Kipu publishes customer outcome figures of its own. None is repeated here: CareVixis does not restate another company's marketing figures, and publishes no denial rate, recovery rate or revenue increase figure of its own.
Trademarks and non-affiliation
Kipu® is a trademark of its respective owner and is used here descriptively, to identify software a facility may already use. Quoted product descriptions are Kipu's own words, cited above.
CareVixis is not affiliated with, endorsed by, sponsored by or certified by Kipu. No API integration, native integration, certification or partnership with Kipu is claimed.
Keep the EHR. Add Revenue Visibility Around It.
CareVixis supports practices that want to keep this EHR. VixisIQ™ adds revenue intelligence and VixisTrace™ supports claim root-cause work around the revenue cycle. If a practice later chooses CareVixis-owned technology, the Vixis products can work natively together, but migration is not required.