Guide

Statements: cadence, wording, and the day they stop working

Summary

There's no federal statement-frequency mandate — most solo practices bill on a monthly cycle, sending two to four statements before escalating an unpaid balance. Hold the first statement until coordination of benefits has settled the true amount owed, match it to any good-faith estimate you gave a self-pay patient, and keep the wording neutral and factual. Once several statements bring no response, move to a call, a payment plan, or collections instead of repeating the notice.

By Gale Editorial · Updated 2026-07-26. Every figure cited to a dated source. How we write.

How often should you send statements?

There's no federal mandate dictating statement frequency, so this is a practice-management convention rather than a legal requirement: most solo practices send a first statement within about two weeks of the payer's final determination (or immediately for self-pay), then repeat on a 30-day cycle — a second statement, a third, and a final notice — until the balance is paid, arranged, or escalated.

A monthly cadence is the near-universal default because it matches how patients already expect a bill to arrive, and it gives each statement enough time to actually be opened and acted on before the next one lands. The cadence doesn't change for the traveling patient, either — a mailed or portal statement lands the same way regardless of what state they're temporarily in when it's sent. Getting patient billing statements right is mostly about consistency, not cleverness.

What belongs on the statement

A statement earns its keep when a patient can read it and know exactly what to do next: the date of service, the service description in plain language, what insurance paid (if any), the remaining balance, the due date, and one clear way to pay — a phone number for your office, a portal link tied to your payment processing, or a mail-in slip. Skip the CPT and diagnosis codes; they belong on the superbill, not the bill.

Keep the wording plain and neutral — a factual account of the balance, not urgent or threatening language — since sounding like a collection notice too early can make patients disengage from a bill you still expect them to pay through the ordinary statement cycle. Keep the statement separate from any patient communications built for marketing, like the newsletter mailing — bundling a bill with the newsletter mailing muddies the message of both. A statement for a billed e-visit, coded 99421–99423, follows the same format as any other visit — no special telehealth-billing treatment changes how or when you send the bill.

When the balance is still moving

Don't send a statement while a balance is still unsettled between payers — if the patient has coordination-of-benefits between two plans, the true balance isn't known until the secondary payer has run its own adjudication against what the primary already paid 1. A statement that goes out before that finishes usually needs a correction, and a corrected statement right after a first one erodes trust in every statement after it.

Hold the first statement until both payers have posted, even if that means the first bill arrives a few weeks later than your usual cadence — a late but accurate statement collects better than a fast but wrong one.

Statements tied to a good-faith estimate

For a self-pay or uninsured patient who received a good-faith estimate before the visit, the No Surprises Act gives them a formal way to push back if the final bill runs substantially higher than the estimate 2. The regulation sets that threshold at $400 or more above the good-faith estimate — cross it, and the patient can initiate the patient-provider dispute resolution process instead of simply paying the statement 3.

Match your statement's total to the estimate you gave before you send it. If your own records show the bill exceeds that estimate by $400 or more, say so on the statement itself and describe the dispute option, rather than let the patient discover the gap on their own and escalate straight to a complaint.

The line between a statement and a collection letter

A statement you send yourself, under your own practice's name, generally sits outside the Fair Debt Collection Practices Act, because that law governs third-party debt collectors, not a creditor billing its own patient 4. The moment you hand the balance to an outside collection agency, that agency's contact limits, required disclosures, and validation notices are governed by federal debt-collection law — and your own prior statements are not.

That gap is exactly why your own statement wording still matters — write it like a bill, not a warning, and save the harder language for the point where you've actually decided to move the account to collections.

Self-funded plans change what applies

If the patient's coverage comes through a self-funded employer plan, remember that ERISA — not your state's insurance code — governs the claims and appeals framework, and state consumer-protection or prompt-pay statutes that would otherwise shape statement or collection practices often don't reach that plan at all 5. Check whether a plan is self-funded before assuming a state rule applies to how you bill its member.

This rarely changes your statement's cadence, but it can change what disclosures a state might otherwise require you to include — worth a note in your financial policy rather than a surprise mid-dispute.

The day statements stop working

By the third or fourth statement with no payment and no response, a plain statement has stopped doing its job, and repeating it again rarely changes the outcome. That's the point to call the patient directly, offer a payment plan, or move the balance toward collections, rather than mailing another identical notice.

Good dunning etiquette matters across the whole sequence, not just at the end — the tone should escalate gradually from the first notice to the last, so a patient who's about to be sent to collections has actually seen it coming. Before you escalate, make sure the statement history itself would survive a second look — dated correctly, matched to the good-faith estimate if one exists, and free of any balance that coordination of benefits hasn't actually finished settling. Log the date and channel of each statement you send — mailed, emailed, or posted to a portal — so if a dispute ever comes up, you can show the sequence rather than reconstruct it from memory.

Common questions

There's no fixed legal number — most solo practices send two to four statements on a monthly cycle before moving to a phone call, a payment-plan offer, or collections. What matters more than the count is that each statement is accurate and that the patient had a real chance to respond before you escalate.

State the date of service, a plain-language description of what was done, what insurance paid if applicable, the remaining balance, and a clear due date and payment method. Leave off procedure and diagnosis codes — those belong on a superbill for the patient's own insurance filing, not on the bill you send them.

Generally no — the Fair Debt Collection Practices Act governs third-party debt collectors, and a solo practice billing its own patient under its own name usually isn't one. That changes the moment you hand the account to an outside collection agency; that agency's conduct is federally regulated even though your own statements weren't.

It's likely to show a balance that changes once the secondary payer posts, which means you'll send a correction and the patient will see two different numbers in a short window. Hold the first statement until both payers have adjudicated when you know a patient has more than one plan, even if it delays your usual cadence by a few weeks.

Keep it neutral and factual rather than urgent — a statement that reads like a threat before you've actually decided to escalate tends to make patients disengage rather than pay, and it narrows your options later if the account genuinely does need to go to collections. Save firmer language for the point where you mean it.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.Centers for Medicare & Medicaid Services (2026). Coordination of Benefits and Recovery Overview. Centers for Medicare & Medicaid Services (CMS). linkThat coordination of benefits determines primary vs. secondary payer order, which is why a statement sent before both payers finish adjudicating often needs correction.
  2. 2.Centers for Medicare & Medicaid Services (2026). No Surprise Billing. Centers for Medicare & Medicaid Services (CMS). linkThat the No Surprises Act creates a patient-provider dispute resolution process for a self-pay/uninsured patient whose final bill runs substantially above their good-faith estimate.
  3. 3.Office of the Federal Register (2026). 45 CFR Part 149 — Surprise Billing and Transparency Requirements. eCFR. linkThe regulation text setting the $400 threshold above a good-faith estimate that triggers the patient-provider dispute resolution process.
  4. 4.Federal Trade Commission (2026). Fair Debt Collection Practices Act. Federal Trade Commission (FTC). linkThat the FDCPA governs third-party debt collectors, not a practice billing its own patient directly, and starts applying once an account moves to a collection agency.
  5. 5.U.S. Department of Labor (2026). ERISA. U.S. Department of Labor. linkThat self-funded employer plans are governed by ERISA rather than state insurance law, so state prompt-pay or consumer-protection statutes often don't reach how a self-funded plan's member is billed.

https://www.gale.care/for-providers/pp-patient-statements-cadence · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)