Itemized bill requests
How do we deliver an itemized bill to a patient who asks for one, with identity checked and the request logged?
Treat the request as a verified release of the patient's own billing record. When a patient or guarantor asks for an itemized bill, Callvu identifies them with the verification the policy sets for billing information, prefills the accounts and the encounters, confirms which encounter and which format (a detailed statement with the charge descriptions, codes and amounts, the payments and adjustments), chases a missing element (a guarantor's authorization for another adult's bill, an encounter not yet finally billed), generates the itemized bill from the billing system in plain language, delivers it in the chosen form within the policy's period, and logs the request and the delivery on the account.
In scopeSimpleCallvu moves: chase and verify, write back
Last updated November 7, 2026.
The problem today
The itemized bill took three weeks, arrived as a printout of internal codes, and was sent to the patient's ex-spouse who was still the guarantor on file.
An itemized bill is the most common request a billing office receives and the one it handles least well: a form, a fax, a wait for a printout nobody can read, and no check on who is asking. The patient wanted to understand the charges or to submit them to a secondary payer or a health account; what they got was a reason to dispute.
The request is a disclosure of protected health information in the billing record, so the requester's identity and right must be checked (the patient, a guarantor with authority, a personal representative); the state's patient billing laws increasingly require an itemized statement on request, within a period, in plain language with the charge descriptions and codes; and the request and the delivery must be logged. The data is in the billing system; the format and the verification are the work.
A readable itemized bill delivered in days prevents the dispute that a code dump provokes.
How it runs
From the requestto the system of record.
A patient, a guarantor or a personal representative asks for an itemized bill in the portal, on a call, by letter or at a desk. Callvu identifies them and opens the request.
- Patient or guarantor
- Verifies identity, chooses the encounter and the form, and receives the bill.
- Billing
- Decides exceptions in the Decision Desk.
- Callvu
- Verifies, prefills, confirms, chases, generates, delivers and logs.
Verify and prefill
The requester is verified at the level the policy sets for billing information (the portal identity, a one-time code to the contact on file, or a document check), their right to the record is classified (the patient, the guarantor for a minor, a personal representative with documentation), and the accounts and encounters are prefilled from the billing system with their billing status.
Chase and verify what is missing
The requester chooses the encounter and the form (electronic or paper) and the purpose where it changes the format (a secondary payer, a health account, a dispute); a missing element (a personal representative's documentation, an authorization for another adult's bill, an encounter not yet finally billed) is chased through a link or explained with the expected date.
Generate and deliver
The itemized bill is generated from the billing system in plain language: each charge with its description, the service date, the code and the amount, the payments and adjustments by payer and patient, and the balance, with the contact for questions and the dispute and assistance information the state requires; it is delivered in the chosen form within the policy's and the state's period.
Write back
The request, the verification, the delivery with its date and form are logged on the account in the billing system and in the disclosure log where the privacy program requires, and a request that signals a dispute or a hardship opens the dispute or the assistance process.
Where it ends: The right person received a readable itemized bill for the encounter they asked about, within the period, and the billing system holds the request and the delivery. The Decision Trace shows the verification and the right to the record; the Audit Trace shows the request, the generation and the delivery with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The portal, a call, a letter or a desk; the requester verifies and receives on their phone or by mail.
The back office
Billing sees only exceptions; the statement generates itself from the record.
The Decision Desk
- A requester whose authority is unclear, an encounter under dispute or audit, or a format the system cannot produce goes to billing in the Decision Desk with the request and only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
23 hospitals in the Ministry of Health network run on Callvu.
Across Callvu customers
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
Who can ask for an itemized bill?
The patient, the guarantor for a minor, or a personal representative with documentation; the requester is verified and their right to the record classified before anything is sent.
What does it contain?
Each charge with its description, service date, code and amount, the payments and adjustments by payer and patient, the balance, and the contact, dispute and assistance information the state requires, in plain language.
How fast?
Within the state's period where one applies and in any case within the access rule's 30 days; an encounter not yet finally billed is explained with its expected date.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.