Kipu holds the chart. Your biller works from a spreadsheet.
Custom reporting and billing census automation for Kipu operators, built to work alongside Kipu's own analytics and integrations.
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. Independent: not affiliated with Kipu.
The gap
Three places the week lives, and a person in the middle.
Nothing checks the 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.
Five checks on every line
Record numbers do the matching, never names. The five billing checks, in detail.
Reads Kipu's API directly, read-only. At the network below, every center's census comes straight from Kipu's API. Where an account does not have the API switched on, the exports your team already pulls keep working.
Never bills, never touches a claim. Nothing reaches your biller until someone approves it. How the billing census automation works.
Alongside Kipu
Keep Kipu. Check the part that lives outside it.
Kipu already does
- The chart and documentation
- Its own analytics and a billing audit tool
- AI note tools and integrations
- Kipu RCM, if you use it
or the exports you already pull
We add
- The billing census outside Kipu, in your biller's format
- Reconciliation against each site's own attendance log
- A roll-up across several Kipu instances
- Five checks before the week leaves the building
Already on Kipu
Built at a five-facility network that runs Kipu.
The full case study, including what I will not claim · How Kipu API access works
Kipu questions
What Kipu operators ask first.
Doesn't Kipu already have reporting?
Yes. Kipu has its own analytics, a billing audit tool and integrations, and you should use them. Custom work adds value where the billing census lives outside Kipu, in a spreadsheet your biller works from, and has to be reconciled against each site's own attendance log and rolled up across several Kipu instances. That reconciliation is the part we build.
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 switched on per account, and once it is, we read the census directly, read-only. That is how the network above runs today.
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. Where the tooling runs and who can access the data is agreed in writing before any patient data is touched. 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.
Does it work for IOP and PHP programs?
Yes. It was built at a network running IOP and PHP on Kipu. Each program's hours rules and each site's log format go into the configuration, so a short IOP day or a PHP day under its hours is flagged before the week is billed.
Can it catch level-of-care and authorization problems?
It compares the level of care in Kipu with each site's attendance log, client by client and day by day, and flags where they differ. Authorization dates and units are not in the check yet. The full workflow is in the level-of-care guide.
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.