Patient statement workflows in medical billing software determine which balances become statements, when those statements leave the system, and what happens when payment does not arrive. The documented controls differ meaningfully across platforms: Tebra offers automated digital-first or paper-plus-digital delivery schedules with a specified 60-day or 180-day cadence [1]. athenahealth generates statements at the patient account level, not the claim level, with the billing cycle date set when the first claim balance drops to the patient [2][7]. The platform states that statements are generated only for outstanding balances that exceed $9.99, that a typical billing cycle is 35 days, and that progressively severe dunning messages appear on subsequent statements [3]. These are not cosmetic variations. A practice that relies on a four-week paper reminder cycle will see different recovery behavior than one using weekly texts followed by mailed statements on Day 30 and Day 60 [1]. The practical work is therefore to map existing collection procedures onto what each system can actually enforce, and to identify where a platform forces a change rather than accommodates it [4][5].
Delivery cadence and channel sequencing
Tebra's Automated Patient Billing documentation describes two recommended delivery schedules with distinct channel logic. The Weekly (Digital-First) schedule, available to practices with Tebra Payments or Patient Collect (Stripe) activated, sends text and email communications weekly beginning on Day 1 and Day 8, then mails paper statements on Day 30 and Day 60 within a 60-day cycle [1]. A separate Monthly (Paper + Digital) option is described as a 180-day schedule that sends an email, text, and paper statement on each scheduled day in the cycle [1][6]. The 90-day schedule that sends email, text, or paper depending on the specific day is the Accelerated (Paper + Digital) option [1][6]. The Monthly (Paper Only) schedule, available to Billing subscribers, sends a paper statement every 30 days across a 180-day cycle, but QR code and online payment options appear only for practices with the supported payments products activated [6].
athenahealth organizes statements around a patient account-level cycle rather than a fixed marketing-style cadence. Documentation states that statements are generated at the patient account level, not the claim level, and that the billing cycle date is set when the first claim balance drops to the patient [2][7]. A typical cycle is described as 35 days, with roughly one quarter of currently responsible patients receiving a statement in any given week [3][7]. If an additional claim drops to the patient between cycles, such as on Day 15, it remains in drop status until the next statement generation [2]. This comparison shows a core decision point: Tebra's pre-set schedules emphasize channel sequencing and a finite cycle window, while athenahealth's workflow anchors statement timing to an account-level cycle that can absorb later claim drops without immediate output [2][6].
Minimum balance logic and statement suppression
Both platforms enforce a minimum balance threshold, but the documented values and editorial controls differ. Tebra requires users to enter a minimum patient balance amount before enabling Automated Patient Billing, and the minimum is presented as a required configuration field rather than a fixed figure [1][6]. athenahealth, by contrast, states in documentation that athenaOne generates and sends patient statements only for outstanding balances that exceed $9.99, with a note that the minimum statement balance does not apply to practices and departments in New Mexico [3]. This distinction matters for practices with high volumes of small balances: a fixed platform floor may suppress a larger share of statements than an operator-set threshold would, but it also removes the need to monitor whether staff entered an appropriate value.
Statement suppression extends well beyond the dollar threshold. athenahealth lists several factors that can prevent generation, including a hold statement reason set on the patient account, a future next statement date, and an unapplied amount that exceeds the outstanding amount [3]. Patient account alarms can also hold statements, and family billing logic holds all statements in a family account if one patient in that account is on hold [2][3]. Tebra's automated workflow excludes patients selected by name and patients whose collection category record has "Send Statement?" disabled [6]. The practical consequence is that a statement queue rarely reflects every outstanding balance; operators must distinguish intentional holds from configuration errors. athenahealth directs users to the Workflow Dashboard to access held accounts, while RXNT provides a Statement Queue with Pending and other tabs for reviewing statement status [3][5].
A concrete evaluation walkthrough
Consider a suggested evaluation for a 12-provider specialty practice with a $25 current statement threshold and a preference for paper only. The practice would first inventory its true balance profile: if a large share of patient balances falls below $9.99, athenahealth's documented platform minimum would alter its existing threshold without any setting change [3]. It should then test schedule fit. Tebra's Monthly (Paper Only) schedule mails every 30 days over 180 days, but online payment links on statements are limited to practices with supported payments products activated [6]. If the practice cannot or will not activate those products, the paper statements lose the documented online-payment affordance in that schedule [6]. Finally, the practice should review hold behavior: athenahealth's family billing logic holds all statements for a family account when one member is on hold, which could delay collections for accounts that would otherwise be ready [2]. This walkthrough does not identify a winner; it defines which documented constraints would force workflow changes in either direction [2][3][6].
Dunning escalation and statement content
Dunning behavior is documented most explicitly in athenahealth's materials. The platform describes progressively severe dunning messages appearing on each subsequent statement when charges go unpaid within the statement cycle [3]. The standard paper statement includes a payment due amount and date, charge details with insurance payments or adjustments, and a remaining patient balance associated with a transfer reason such as copay, deductible, coinsurance, or Misc [2]. A simplified statement variant is generated for organizations using the Online Statement-based Experience when the patient has five or fewer charges and all charges are of the same type, with columns for service date, provider, charges, payments/credits, and patient balance [2][7]. This conditional formatting is a workflow decision: it determines whether a patient sees a compact summary or a fuller charge-by-charge ledger.
Tebra's dunning escalation is embedded in the delivery schedule rather than presented as a separate message-intensification setting. The Weekly (Digital-First) schedule sends repeated text and email reminders weekly before paper statements appear on Day 30 and Day 60, effectively escalating from digital only to mailed output within a single cycle [1][6]. RXNT documentation describes a Statement Queue where warning icons remain visible until associated issues are resolved, and statements that error while sending move back to a Pending tab, though no escalation message wording is specified [5]. The evidentiary gap is notable: dunning message text is documented for athenahealth, while Tebra's automated schedule implies escalation through channel changes but does not publish the reminder copy in the retrieved materials [2][3][6].
Operator control versus platform-managed automation
Manual workflow tools remain present even where automation is enabled. Tebra allows practices to exclude patients on Automated Patient Billing when sending statements through the Desktop Application, so a staff-run batch does not duplicate an automated send [4]. Users can also save an XML file for a third-party vendor to process patient statements, an integration path that shifts printing and mailing outside the platform [4]. athenahealth similarly supports printing a summary of patient balances from the Quickview page when a statement is held for an unresolved account number issue, and it mails statements every day of the week to the guarantor on file [3]. These manual paths matter because automation is rarely comprehensive; the documentation assumes staff will intervene for exclusions, address corrections, and vendor handoffs.
RXNT and AMKAI illustrate the continuum toward operator-initiated workflow. RXNT's Statement Queue supports generating statements on statement cycle dates or manually with a Generate Statement button, and statements that error while sending return to the Pending tab [5]. Print batches are limited to 100 statements, and users must mark statements as printed after PDFs are generated [5]. AMKAI's RCM ledger requires operators to define groups by primary provider, patient classification, or insurance classification, then choose billing options such as dunning messages and file layout before creating statements [8]. These workflows transfer more sequencing responsibility to the practice: the system generates what is selected, but does not impose a pre-set digital-then-paper cadence comparable to Tebra's [1][5][8]. A useful control question is whether staff will reliably initiate each batch, since RXNT's pending statements are generated automatically from the statement cycle or manually, while AMKAI's workflow requires operators to define groups and choose billing options before creating statements [5][8].
Sources & references
- Automated Patient Billing Settings - Tebra Help Center · helpme.tebra.com
- User Guide — Patient Statement Samples · help.athenahealth.com
- User Guide — Patient Statements · help.athenahealth.com
- Send Patient Statements · helpme.tebra.com
- The Billing Statements Queue – RXNT Help Center · help.rxnt.com
- Automated Patient Billing Settings · helpme.tebra.com
- User Guide — Patient Statement Samples · help.athenahealth.com
- Generating Patient Statements · officehelp.amkaicloud.com