Study guide
8.6 Patient Statements, Payment Collection & Balance Reconciliation
NHA Certified Electronic Health Records Specialist CEHRS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the NHA CEHRS Exam The CEHRS Test Plan & How to Use This Guide
2 Chapter 1: Foundations — Medical Terminology, Health Care Settings & the EHR
1.1 Medical Terminology I: Roots, Prefixes, Suffixes & Combining Forms 1.2 Medical Terminology II: Body Systems, Directional Terms & Clinical Abbreviations 1.3 Health Care Systems, Settings, Personnel & Credentials 1.4 Parts of the EHR & Core Functions of the Electronic Record 1.5 Regulatory Agencies, Professional Standards & Population Health Concepts
3 Chapter 2: Non-Clinical Operations — Patient Registration & Scheduling
2.1 Patient Registration & Intake Workflows 2.2 Master Patient Index (MPI) & Demographic Management 2.3 Appointment Scheduling & Resource Management 2.4 Patient Communication, Portals & Front-Office Operations 2.5 Encounter Documentation: Face Sheets, Labels, Armbands & Check-Out
4 Chapter 3: Non-Clinical Operations — Health Record Administration & Archiving
3.1 Health Record Types, Hybrid Systems & Data Conversion 3.2 Record Retention, Storage & Archival Policies 3.3 Release of Information (ROI) & Authorization Procedures 3.4 Auditing, Chart Maintenance & Record Integrity
5 Chapter 4: Non-Clinical Operations — Data Sources, Devices & EHR User Support
4.1 Retrieving Patient Data from Internal Databases (Provider, Payer & Financial) 4.2 Acquiring Patient Data from External Sources 4.3 Importing from Integrated Devices & Managing EHR Hardware Inventory 4.4 Identifying, Reporting & Reconciling Data Discrepancies 4.5 End-User EHR Training, Competency & Training Documentation 4.6 Communicating Software Updates, IT Troubleshooting & Escalation
6 Chapter 5: Clinical Operations — Clinical Intake, Point-of-Care & Vitals
5.1 Clinical Intake, Rooming & Vital Signs Documentation 5.2 Chief Complaint, History of Present Illness (HPI) & ROS 5.3 Physical Exam Documentation & Clinical Notes Formatting (SOAP) 5.4 Allergy Documentation, Adverse Reaction Logging & Safety Alerts 5.5 Problem Lists, Medical History & Immunization Tracking 5.6 Patient Education Materials in the EHR & Scope of Practice
7 Chapter 6: Clinical Operations — Templates, Documentation Review & Data Retrieval
6.1 Developing Clinical Templates for Data Capture 6.2 Reviewing Clinical Documentation for Completeness & Accuracy 6.3 Point-of-Care EHR Support & Telehealth Workflows 6.4 Navigating the EHR to Retrieve Requested Patient Data 6.5 Securely Transmitting & Exchanging Patient Data
8 Chapter 7: Clinical Operations — CPOE, Orders & Decision Support
7.1 Computerized Provider Order Entry (CPOE) Fundamentals 7.2 Laboratory & Diagnostic Test Order Entry and Results Tracking 7.3 Medication Reconciliation, e-Prescribing & Formulary Checks 7.4 Clinical Decision Support Systems (CDSS) & Practice Guidelines 7.5 Clinical Care Coordination, Referrals & Discharge Planning
9 Chapter 8: Revenue Cycle & Financial Management
8.1 Insurance Verification, Eligibility (EDI 270/271) & Prior Authorization 8.2 Superbills, Charge Capture & Encounter Form Management 8.3 Coding Fundamentals for EHR: ICD-10-CM, CPT & HCPCS Level II 8.4 Claim Submission (EDI 837), Remittance (EDI 835) & Revenue Cycle 8.5 Providing Estimated Patient Costs & Good Faith Estimates 8.6 Patient Statements, Payment Collection & Balance Reconciliation
10 Chapter 9: Regulatory Compliance, HIPAA & Security
9.1 HIPAA Privacy Rule & Protected Health Information (PHI) 9.2 Minimum Necessary Rule, Permitted Uses & Patient Rights 9.3 HIPAA Security Rule: Administrative, Physical & Technical Safeguards 9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs) 9.5 Information Blocking Rules, 21st Century Cures Act & Compliance Audits 9.6 Allocating & Verifying EHR Access Controls and Role-Based Privileges 9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation 9.8 Abbreviation Policies, Professional Standards & EHR Downtime Procedures
11 Chapter 10: Data Management, Reporting & Health IT Standards
10.1 Health IT Interoperability: HL7, FHIR & Health Information Exchanges (HIE) 10.2 Standardized & Ad Hoc Financial Reports 10.3 Standardized & Ad Hoc Clinical Reports 10.4 Verifying Report Accuracy & Avoiding Common Reporting Errors 10.5 Quality Reporting, MIPS, Promoting Interoperability & Clinical Dashboards 10.6 Data Abstraction, Quality Improvement Studies & EHR System Security Management
8.6 Patient Statements, Payment Collection & Balance Reconciliation
Key Takeaways Explain This Topic AI
A patient statement is produced only after insurance has adjudicated and contractual adjustments have posted, so the balance shown is true patient responsibility.
Payments are posted to the correct patient, account, encounter, and line item, and every payment generates a receipt.
Card data is handled through PCI-compliant terminals or gateways and never stored in free-text EHR fields.
Daily balance reconciliation compares system-posted payments against the cash drawer, terminal batch settlement, and deposit, and any variance is investigated before the day closes.
Non-payment is documented as thoroughly as payment, including refusals, financial hardship screening, and payment plan arrangements.
Last updated: August 2026
Two test plan tasks close the revenue cycle at the patient level: task 3.H (navigate the EHR to provide patient statements) and task 3.I (collect and post payments to a patient's account). The supporting knowledge statements cover payment methods and credit card charging procedures (3.K18, 1.K12), balance reconciliation between the EHR and receipts (3.K19), and documentation for both payment and non-payment (3.K20).
Generating a Patient Statement
A statement should never be produced until the account is ready. The sequence is fixed:
Charges are captured and the encounter is closed (Section 8.2).
The claim is submitted and adjudicated (Section 8.4).
The remittance is posted — payment, contractual adjustment, and any denial reason codes.
Secondary insurance is billed and adjudicated if it exists.
Only the balance remaining after all payer activity is billed to the patient.
Sending a statement before adjudication bills the patient for amounts the payer will cover and produces exactly the phone call the front office least wants.
What a compliant statement contains
- Element Detail
- Patient and guarantor Name, account number, statement date
- Service lines Date of service, provider, plain-language description of each service
Financial detail per line Charge, insurance payment, contractual adjustment, patient responsibility split into copay, deductible, and coinsurance
- Account summary Prior balance, activity, current balance, aging buckets
- Payment instructions Due date, portal link, remittance address, phone number, accepted methods
Assistance information Financial assistance policy, payment plan availability, and the number to call with questions
Statements go to the guarantor — the party financially responsible — which is not always the patient. Statements are also delivered through the patient portal where the patient has opted in.
Collecting and Posting Payments
Payments arrive as copays at check-in, balance payments at check-out, mailed checks, portal payments, and payer electronic funds transfers. Regardless of source, posting follows the same discipline:
Right patient, right account, right encounter, right line. A payment posted to the wrong encounter creates a false open balance on one visit and a false credit on another.
Post at the time of collection. A payment collected but not posted until the next day means the statement that runs overnight bills the patient for money already paid.
Issue a receipt every time , printed or electronic, showing date, amount, method, last four digits of the card if applicable, and what it was applied to.
Apply payments correctly. Copays post to the encounter that generated them; a payment on an old balance posts to the oldest open item unless the patient directs otherwise. Do not silently apply a copay to an unrelated aged balance.
Handle credits properly. An overpayment is a credit balance, and credit balances must be worked and refunded on a defined cycle — retaining an overpayment on a federal program account is a compliance exposure.
Card handling and PCI
Rule Reason
Process cards through the PCI-compliant terminal or payment gateway only Keeps the practice out of scope for storing card data
Never type a full card number into an EHR note, comment, or scheduling field Free-text card data is unencrypted, unsearchable for deletion, and an immediate PCI violation
- Store only the last four digits and authorization code Sufficient to reconcile without holding sensitive data
- Do not email or fax card numbers, and shred any paper form containing them Same reason
- Follow policy for card-on-file consent Requires written patient authorization defining what may be charged
- Daily Balance Reconciliation
Knowledge statement 3.K19 covers reconciliation between the EHR and receipts. At the close of each day:
Run the payment posting report from the practice management system for the date, by user and by payment method.
Settle the card terminal batch and compare the terminal total to the posted card total.
Count cash and checks against the posted cash and check totals and the receipts issued.
Investigate every variance before closing. Common causes: a payment collected but not posted, a payment posted twice, a refund not recorded, a card transaction voided at the terminal but left posted, or a payment posted to the wrong account.
Prepare the deposit so that the deposit total equals the reconciled posted total.
Document the reconciliation with the totals, any variance, the explanation, and who reconciled and reviewed it.
Segregation of duties is the control that makes this meaningful: ideally the person who collects payments is not the only person who reconciles and deposits them.
Documenting Non-Payment
Knowledge statement 3.K20 makes documentation for both payment and non-payment explicit. Record:
A patient's inability or refusal to pay a copay at the time of service, and that services were provided anyway where policy requires it
- Financial hardship screening offered or completed, and the outcome
- Payment plan terms agreed to — amount, frequency, start date, and the patient's acknowledgment
- Charity care or financial assistance applications submitted, approved, or denied
- Bad-debt or collection referrals, with the date and the approval authority
- Any dispute the patient raises about a charge, and how it was routed
Two boundaries close this out. Emergency care is never withheld for inability to pay — federal law and organizational policy both control here. And collection activity must follow the organization's policy and applicable law; a front-office specialist informs and documents, but does not improvise collection tactics.