A patient balance can remain unresolved long after the insurance claim has been paid. The problem is often not the lack of billing activity. It is what happens after the balance becomes the patient’s responsibility.
Are statements reaching patients at the right time? Are staff spending hours reviewing accounts that could move through an automated workflow? And when a balance remains unpaid, does athenaCollector clearly identify when human intervention is needed?
The right patient A/R configuration can help answer those questions. athenaCollector supports patient statements, outstanding-balance visibility, patient account alarms, and payment functionality that can form a structured path from balance creation to resolution.
The goal, however, is not to automate every patient account. It is to automate predictable work, identify exceptions early, and give staff a clear process for accounts that need additional attention.
What Are athenaCollector Patient A/R Rules?
Patient A/R rules are the configuration and workflow controls used to manage amounts that remain the patient’s responsibility after billing activity. They help determine how open balances are communicated, when accounts require follow-up, and when a patient balance should move from an automated workflow to staff review.
athenahealth’s current service documentation lists patient statements, patient account alarms based on client dunning policies, presentation of outstanding balances during scheduling and check-in/check-out, and patient payment processing through the Patient Portal among athenaCollector capabilities.
That means an effective patient A/R workflow should separate routine accounts from exceptions.
How Patient A/R Moves Through athenaCollector
The easiest way to evaluate your configuration is to follow the balance through the revenue cycle, starting before it becomes patient A/R.
1. Address Patient Responsibility at the Front End
Patient collections should not begin only after a statement is mailed.
athenahealth states that athenaCollector can present outstanding patient balances to staff during scheduling and check-in/check-out, including date-of-service and charge-level detail.
That creates an opportunity to address known balances earlier.
Front-office staff should confirm patient and insurance information, review applicable outstanding balances, communicate expected responsibility when appropriate, and collect eligible amounts according to the practice’s policies.
2. Confirm That the Balance Is Ready for Patient Billing
Not every amount displayed on an account should immediately be treated as a final patient responsibility. A balance may still be affected by claim adjudication, payment posting, account corrections, or other billing activity. Before a patient enters a collection workflow, the practice should establish that the amount is valid and ready for communication.
A practical workflow should therefore distinguish between:
| Account condition | Appropriate approach |
| Valid patient balance | Move into the standard billing workflow |
| Claim still under adjudication | Wait until responsibility is established |
| Unposted or unresolved payment | Review before patient communication |
| Billing discrepancy | Route for staff investigation |
| Patient disputes balance | Hold routine collection activity while reviewed |
| Payment-plan situation | Route to the appropriate staff workflow |
The objective is simple: communicate a balance when the practice can clearly explain why the patient owes it.
Automating Patient Statement Workflows
Once a valid patient balance is established, statements can handle much of the routine communication. athenahealth’s current athenaOne service description states that patient statements are sent when patients have open balances. It also documents patient account alarms for dunning-level follow-up and other patient A/R capabilities.
When reviewing statement configuration, focus less on statement volume and more on whether the workflow is moving balances toward resolution. Consider these questions:
| Setting or workflow | What to review |
| Minimum balance | Does the threshold fit the practice’s current configuration and collection policy? |
| Statement frequency | Are communications frequent enough without creating unnecessary volume? |
| Electronic delivery | Are eligible patients receiving available digital communications? |
| Paper statements | Are paper statements still appropriate for patients who need them? |
| Statement holds | Are accounts with unresolved issues prevented from unnecessary repeat billing? |
| Contact information | Are mailing addresses and electronic contact details current? |
| Staff intervention | Is there a defined point where routine automation stops? |
A well-configured statement workflow should make routine accounts easier to manage while directing exceptions toward the right staff member.
Athena Collector Balance Notification Settings: Building a Better Communication Workflow
A statement is only useful if the patient receives it and understands what action to take. The patient communication process should therefore connect the balance, the notification, and the payment option. athenahealth’s patient-facing portal documentation allows patients to access statements and payment information through the Patient Portal.
The objective is not to send the same message through every available channel. It is to give patients a clear and convenient path from balance notification to payment or resolution.
Configure Patient Account Alarms for Exceptions
Automation becomes much more useful when it has a clear escalation point. Athenahealth’s service documentation states that Patient Account Alarms can be configured according to client policy for dunning levels to assist with patient A/R follow-up. The documentation also describes statement-hold functionality associated with account alarms.
For example, a practice may need staff to investigate an account when:
- A balance remains unpaid after the normal communication sequence
- A patient questions the amount due
- A payment arrangement needs to be discussed
- An account contains another billing issue
- A balance is being considered for a different disposition under practice policy
The exact alarm configuration should be reviewed against the practice’s current athenaOne setup. The important principle is that every automated workflow needs a defined exception path.
Build a Patient-Centered Dunning Workflow
Dunning should not simply mean sending more statements. A stronger workflow moves the account through clearly defined stages:
Balance established → Initial communication → Follow-up → Exception review → Staff intervention → Resolution
At the first stage, confirm that the patient responsibility is accurate. The next stage communicates the balance and available payment options. If the account remains unresolved, the system should help identify whether another routine communication is appropriate or whether staff need to step in. The final stage is resolution. Depending on the circumstances and the practice’s policies, that may mean payment, an approved payment arrangement, an account correction, an adjustment, or another appropriate disposition.
This approach keeps automation focused on predictable work while giving staff a clear reason to intervene.
Connect Front-End Collections With Patient A/R
Patient A/R should not be managed as an isolated billing function.
The information collected at registration and scheduling can influence what happens later. Incorrect demographics can interfere with communication. Incomplete insurance information can complicate responsibility determination. Missed opportunities to address known balances can allow avoidable patient A/R to grow.
athenahealth specifically identifies outstanding patient-balance presentation during scheduling and check-in/check-out as part of athenaCollector’s patient A/R capabilities. A connected workflow looks like this:
Registration → Eligibility → Expected responsibility → Point-of-service collection → Claim adjudication → Patient responsibility → Statement → Notification → Payment → A/R follow-up
Each stage affects the next. Improving only the statement process will not fully solve a patient A/R problem if the underlying issue begins with incomplete information or inconsistent front-end collection practices.
Use Exception-Based Follow-Up Instead of Reviewing Every Account
One of the biggest opportunities in patient A/R management is reducing unnecessary manual review. Staff should not have to treat every account as a problem. Routine, valid balances can move through the standard workflow while exceptions are separated for human review. A practical model looks like this:
| Account type | Workflow |
| New valid balance | Standard automated billing |
| Patient has available digital communication | Electronic notification where applicable |
| Repeated unpaid balance | Review or account alarm |
| Patient requests assistance | Staff follow-up |
| Payment-plan situation | Financial discussion according to policy |
| Billing discrepancy | Account investigation |
| Resolved balance | Close the applicable workflow |
| Account requiring another disposition | Follow established practice policy |
This approach can reduce repetitive account checking and give staff more time to resolve the balances that actually require judgment.
Measure Whether Your Patient A/R Rules Are Working
Configuration is only the starting point. Practices also need to measure whether the workflow is producing the intended result. Useful measures include patient A/R aging, collection performance, statement-to-payment conversion, digital payment adoption, unresolved account volume, and staff touches per account.
It is also useful to monitor the time between establishing a patient balance and receiving payment or reaching another final resolution. The purpose of these metrics is not to create more reporting work. They help answer practical questions:
Are patients paying faster?
Are older balances declining?
Are staff spending less time on routine accounts?
Are more accounts reaching resolution without repeated manual intervention?
If the answer is no, changing the rules may be more valuable than simply increasing collection activity.
Common Patient A/R Configuration Problems
Even an automated workflow can perform poorly when the underlying process is not designed correctly.
Statements are sent before responsibility is clear
If the patient’s responsibility is still changing, the communication may create confusion and additional work.
Patient contact information is outdated
A correctly generated statement cannot produce a payment if it does not reach the patient.
The workflow relies too heavily on one communication method
Patients may have different communication preferences and access to electronic channels. Practices should use the communication options available within their configuration appropriately.
There is no clear escalation point
Repeated communication without a defined staff-review stage can increase activity without resolving the underlying problem.
Front-end collection opportunities are missed
Known balances can become more difficult to collect when they are not addressed at appropriate points during the patient journey.
Rules are configured but never evaluated
A workflow can function exactly as configured while still producing poor results. Patient A/R aging, unresolved accounts, statement volume, payment conversion, and staff workload should be reviewed regularly.
A Practical Framework for Optimizing Patient A/R in athenaCollector
If your practice is reviewing its patient A/R configuration, use this five-step framework:
1. Validate
Confirm that the balance is accurate and ready for patient communication.
2. Communicate
Use the appropriate statement and available communication channels.
3. Automate
Allow routine accounts to move through standardized workflows.
4. Escalate
Use account alarms and defined criteria to identify accounts that need human attention.
5. Measure
Track aging, payment conversion, unresolved accounts, and staff workload.
This keeps automation connected to an operational goal. The objective is not to make the system perform more actions. It is to help more patient balances reach resolution with fewer unnecessary touches.
Patient A/R Configuration Checklist
Before changing patient A/R rules, confirm that:
- Patient responsibility is established before routine billing communication
- Statement settings match the practice’s current athenaOne configuration
- Contact information is accurate
- Available electronic communication options are used appropriately
- Patient account alarms have clear escalation criteria
- Front-office staff know when outstanding balances should be addressed
- Exceptions are separated from routine accounts
- Staff understand what happens after the automated workflow ends
- Patient A/R aging is monitored
- Statement-to-payment performance is reviewed
- Unresolved balances have defined next steps
- Configuration changes are tested before broad implementation
Conclusion
Effective patient A/R management is not about sending more statements. It is about moving each balance through the right workflow at the right time.
AthenaCollector provides capabilities that can support patient statements, outstanding-balance visibility, account alarms, and patient payments. The strongest results come when those tools are connected to accurate patient information, clearly established responsibility, front-end collection processes, exception-based follow-up, and regular performance monitoring.
The goal is not more collection activity. It is a clearer path from patient responsibility to resolution.
FAQs
What are patient A/R rules in athenaCollector?
Patient A/R rules are workflow and configuration controls used to manage patient balances, statements, account alarms, and follow-up activity. The available configuration can vary by practice and athenaOne implementation.
Can athenaCollector automate patient statements?
Yes. athenahealth’s current service documentation states that patient statements are sent when patients have open balances. The specific statement workflow and configuration should be verified for the individual practice.
What is a patient account alarm in athenaCollector?
A Patient Account Alarm supports patient A/R follow-up and can be configured according to client policy for dunning levels. It can help identify accounts that have reached a point where additional action may be necessary.
Can patients view their statements online?
Yes. athenahealth’s Patient Portal documentation provides patients with access to billing statements and payment information through the Billing section of the portal.
