Kipu holds the chart. Your biller works from a spreadsheet.
Between the two, someone carries the week across by hand. That is where the money leaks: attendance never entered, days billed above the note, a level-of-care change the authorization never caught up with. We check that week against the chart before it leaves the building.
Nothing replaces Kipu or your billing company. BAA signed first. A person approves every line.
The gap
Three places the week lives, and a person in the middle.
Nothing checks that census against the chart before claims go out, except the person who typed it. When it is wrong, you hear about it at denial time, or as a takeback later.
What it does
It reads what Kipu already holds and checks the week.
Drafts the census in your biller's format
From the Kipu exports your team already pulls, such as chart summaries and attendance, plus each site's own log, in each site's own spreadsheet habits.
Checks every line five ways
Unbilled attendance, billing above documentation, threshold days, level-of-care conflicts and identity mismatches. Record numbers do the matching, never names. The five leaks, in detail.
Holds every disagreement for a person
Nothing reaches your biller until someone approves it. The engine never bills and never touches a claim.
Moves to the API when you are ready
Where your Kipu account has its API switched on, that can replace the exports. Where it does not, the exports keep working.
Already on Kipu
Built at a five-facility network that runs Kipu.
- Four separate Kipu instances across five facilities, and every site with its own spreadsheet habits. The engine learned each one before anyone talked about standardising.
- 637 entries in the first real run, zero conflicts against the operations lead's own manual work.
- A parallel week, run by the operations lead against the manual census, signed off with three notes. All three were in the engine the same day.
- Running now on three of the four outpatient sites. The fourth is moving onto the shared census template first.
Kipu questions
What Kipu operators ask first.
Does this replace Kipu, Kipu RCM or our billing company?
No. Keep all three. Between the chart and the file your biller reads, a person still carries the week across by hand. This checks that week before it leaves the building.
We already use Kipu's AI note tools.
Good. We do not write notes. The notes are the input: the engine checks that what gets billed is supported by what was documented.
Does Kipu need to approve anything?
Not to start. The audit works from exports your team can already pull. Kipu's API is an option later, if your account has it switched on.
What about 42 CFR Part 2?
Substance use records carry a second federal rule on top of HIPAA, and the updated Part 2 rule has been in force since February 2026. The tooling runs in your environment, on your own files, and only counts travel. A BAA is signed first, plus a qualified service organization agreement where Part 2 applies. No patient data goes to an ad platform. Your privacy lead decides what the agreements must cover. This is not legal advice.
What does it cost?
The audit is quoted flat before you commit, on the free call. The engine is a flat build, quoted after the audit, and the audit is credited toward it. If the audit finds nothing much, you keep the SOP and buy nothing.
Bring one completed month.
A free call. Walk me through how a session in Kipu becomes a paid claim at one facility, and I will tell you where I would look first. If you are not a fit, I will say so on that call.