8.6 Patient Statements, Payment Collection & Balance Reconciliation
Key Takeaways
- 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.
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.
A front desk specialist collects a $40 copay and, to save time, writes the patient's full credit card number in the appointment comment field to process later. What is wrong with this?
At day's end, the practice management payment report shows $1,240 in card payments, but the terminal batch settles at $1,190. What should the specialist do?
A patient's claim has been submitted but not yet adjudicated. The billing system offers to generate a patient statement. What should happen?