Every claim, reconciled.
Drop your billing export. ClaimBook reads each line, calls the right government endpoint, and returns a settled ledger — same working day.
Integrated with the government payors that matter in India
A claim filed isn't a claim paid.
Most mid-size hospitals lose 3–7% of their government claims revenue to mismatches no one had time to chase. ClaimBook exists to close that gap.
Average days to settle a single government claim.
From the moment a claim is filed to the day it lands as reconciled cash, your finance team is running blind.
Claims are rejected, re-filed, or written off entirely.
Most denials are clerical — a code, a line item, a date mismatch. Few hospitals have the time to find out which.
Number of audit trails most billing teams keep on rejections.
When a denial comes in three weeks later, no one remembers which line of which Excel it came from. The trail is cold.
Three steps. Same day.
No new software for your staff to learn. They keep working in Excel and the billing system they already use — ClaimBook reads what they already produce.
Drop the file.
Excel, CSV, or the PDF your TPA emailed at midnight. ClaimBook reads the claim format you already export — no remapping, no IT project.
AI parses each line.
Our model reads patient IDs, procedure codes, dates and amounts — even when your file's column order changes week to week. Every parse is shown back for review.
Reconcile with the payor.
We call NHCX, RGHS or CGHS for each claim and return a ledger — what matched, what didn't, and the exact source row behind every number.
Built for the people on the desk.
Every feature exists because a billing manager or CFO told us they needed it. No reporting dashboards for the sake of dashboards.
Any format, any export.
Excel, CSV, PDF — even the messy ones with merged cells and a header three rows down.
AI that shows its work.
Every parsed field links back to the exact cell, page and column it came from. Reviewable, auditable, defensible.
Direct to NHCX, RGHS, CGHS.
No middleware. We call the government API for each claim and return what they said, in writing.
Session-only by design.
Your files live in memory for one session. When you close the browser, the data is gone — by architecture, not by promise.
An audit trail per line.
Every claim carries its full history — file, parse, call, response. When a denial comes in three weeks later, the trail is warm.
Same-day settlements.
Most reconciliation runs finish in under five minutes. Your team starts the day with a ledger, not an inbox.
We don't keep your data.
Most platforms ask for trust. ClaimBook removes the need for it — your claims data never leaves your session. There is nothing to leak because there is nothing stored.
- No-Storage Session-only architecture. Uploaded files are decrypted in memory for the length of one reconciliation run, then irrecoverably purged.
- Encrypted TLS 1.3 in transit, AES-256 in memory. Every call to NHCX, RGHS and CGHS rides the government's signed channel. No proxies.
- Compliant DPDP Act 2023 by construction. We don't process patient PII — only line-level claim data, which is purged on session close.
- Audit Every line, signed. Each reconciled row carries a cryptographic hash of its source — verifiable months after the fact.
A typical reconciliation run.
What the log looks like from your browser's perspective. Nothing leaves except claim lines on a signed channel — and nothing remains afterward.
What changes in the first quarter.
Numbers from our Rajasthan pilot cohort. We expect the next set of hospitals to see similar shifts — but every quarter starts with a baseline you'll own end-to-end.
A product in active construction.
We don’t hide where ClaimBook is — this page is the honest snapshot. Sign up for the pilot and you’ll be among the first hospitals to use the “Now building” column the day it ships.
Live in pilot
- Excel, CSV and PDF claim upload
- NHCX, RGHS, CGHS reconciliation
- Per-line audit trail with source hash
- Session-only architecture
- TLS 1.3 in transit, AES-256 in memory
Now building
- TPA & PSU custom payor integrations
- Multi-user roles for billing teams
- Hindi / Devanagari interface
- Scheduled reconciliation runs
- Webhook export to HIS / ERP
On the roadmap
- General availability — Q3 2026
- Pan-India rollout after Rajasthan pilot
- Private insurer (Star, HDFC Ergo, etc.) reconciliation
- Denial-management workflow
- SOC 2 Type II audit
“For the first time, my Monday meeting starts with a number, not a question. ClaimBook gives the desk what every CFO has been asking for — a claim is either settled, or it tells me why not.”
Answers to the questions hospitals ask first.
If you’re evaluating ClaimBook for your hospital, start here. Anything missing? Write to hello@claimbook.in and we’ll add it.
What is ClaimBook?
Which insurance schemes does ClaimBook reconcile against?
Is ClaimBook safe to use with patient and claim data?
How long does a reconciliation run take?
Who is ClaimBook built for?
Does ClaimBook replace our existing billing software?
Is ClaimBook generally available?
Who builds ClaimBook?
Where is ClaimBook available?
How do I request a demo?
See ClaimBook on your own claims.
30 minutes. A real reconciliation run on a sample export from your hospital. No data leaves your session.