Statements
Every patient statement for the selected client, above the patient A/R it draws on: what is held, what is ready to send, and what went out this cycle. One statement in full is The Statement Page; the batches that carry them out are Statement Batches.

Who Can See It
Section titled “Who Can See It”User only, when the client is licensed for statements. Administrators and Managers have no access, as with Patients: every row carries a patient name.
The Tiles
Section titled “The Tiles”The tiles count the whole book, never the filtered list, so their totals reconcile against the ledger.
| Tile | What it counts | Selecting it |
|---|---|---|
| Patient A/R | Every open patient balance on the ledger, and how many accounts owe one | Nothing. It is a total, not a filter |
| Held | Statements in Held, with their total | Filters the list to Held |
| Ready to Send | Statements in Ready, with their total | Filters the list to Ready |
| Sent This Cycle | Accounts whose latest statement was sent since the latest finished cycle run started, failed runs included, with their total. A cycle still running does not reset it | Filters the list to Sent |
Selecting a tile again clears its filter. A tile shows a dash rather than a zero when its count could not be read, so a clean day and a failed count never look alike.
Stage Chips and Search
Section titled “Stage Chips and Search”Under the tiles, a Stage chip appears for every rung of the notice ladder that currently holds statements, each with its count. Rungs with none are not shown, so the row fills in as accounts climb the ladder. One stage filters at a time.
Search matches the statement number, the patient’s name and their MRN. What you type in the search box stays out of the page address, so a bookmark or a shared link carries the filters but never the name you searched for. The search is kept while you move around ClaimPod, and cleared when you reload the page or sign out.
The List
Section titled “The List”| Column | What it shows |
|---|---|
| Statement # | The statement number |
| Patient | Name |
| Stage | Where on the notice ladder this statement sits |
| Amount due | What it asks the patient to pay |
| Oldest | Age in days of the oldest open patient balance on the account. Not sortable |
| Status | The status, and for a held statement a short reason: address incomplete, balance changed, settled since, collections clock not started, no guarantor (minor), billing restricted, QMB, do not bill, bankruptcy, deceased, payment plan or secondary pending. A hold raised by a client rule shows its code instead |
| Statement date | When it was generated |
The list sorts by statement date, newest first, and a row opens the statement, by click or with Enter. Each row ends in a download icon that fetches the statement’s PDF; on a held statement it is greyed, and the tooltip says held statements do not have a document yet.
Actions
Section titled “Actions”| Action | What it does | When it is offered but greyed |
|---|---|---|
| Run Statement Cycle | Starts a cycle run now, with the same settings the schedule uses | While a run is starting or already going, when it reads Cycle running… |
A run mints one statement for every account with a patient balance at or above the minimum, not billed within the cadence, and with no statement still Draft, Held or Ready. The defaults are a $5 minimum and 30 days; an Administrator changes them on the schedule. Accounts under the minimum or in credit are counted, never billed. Each new statement is checked as it is made: one that passes is Ready, one that does not is Held and lands on the day’s Statement Review queue, named for the practice day, such as “Statement Review · 09/29/2026”.
Starting a run says Statement cycle started as task # and its number. While
it is going, a banner says when it started, and asking for a second run is
refused until the first finishes. When it finishes, the banner, tiles and list
refresh by themselves. The run’s outcome, as counts of generated, held, under
minimum and credit balances, is recorded on the task in
Tasks. When an account fails, the outcome adds
N failed - see the task log. and the task ends Failed; the statements the
run did generate stay.
Without a schedule, a banner says no statement cycle is scheduled and offers Schedule one. The button still runs a cycle with the defaults, and a single statement can be generated from the patient page.
Statuses
Section titled “Statuses”| Status | What it means |
|---|---|
| Draft | Not yet checked. Generation checks every statement as it makes it, so a statement is Held or Ready by the time it reaches the list |
| Held | The check found a blocking hold, or a deceased or payment plan warning that a reviewer has not released yet. The statement has no document, never batches, and waits on the day’s Statement Review queue |
| Ready | Passed the check, and waits for the next batch |
| Sent | Left in a batch. The document is frozen as the paper that was mailed, and the bill-to is locked |
| Void | Withdrawn. Kept for the audit trail; the balance stays on the account |
Stages
Section titled “Stages”The notice ladder. Two doors open onto it, and both move an account one rung at a time, never further. A cycle run moves an account up only once the cadence has passed since its previous statement. Generate Statement on the patient page moves it up on the same rule, and when the cadence has not passed it bills again at the rung the account already sits on. It is refused while the patient has a statement still Draft, Held or Ready: that one has to be sent in a batch or voided first. Either way, the statement that comes out can be any of the four rungs.
| Stage | Rung |
|---|---|
| Statement | 1 of 4, the first bill |
| Reminder | 2 of 4 |
| Second notice | 3 of 4 |
| Final notice | 4 of 4, and every notice after it |
States
Section titled “States”- Empty - the list says the statement cycle creates statements, or generate one from a patient.
- No statement cycle is scheduled - a banner, with Schedule one linking to Schedules. Not a fault: generating one statement at a time is a legitimate way to work.
- Statement cycle running - a banner with the start time, while the button reads Cycle running….
- A dash on a tile - that count could not be read.
- We couldn’t load statements - with a retry.
- Blocked - without the statements module the screen is not in the sidebar, and a saved link to it says the module is not part of your plan.
Related: The Statement Page · Statement Batches · Bill Patients for What They Owe · Patients · Transactions · Tasks