Posting Patient Payments
Posting a payment from a patient is not the same task as posting a payer's remittance. A payer's payment is accompanied by a remittance advice that names the claim, the line, and the share it assigned to the member, so posting it is mostly transcription. A patient's payment arrives with a name and an amount. Which balance it settles is a decision the practice makes — and that decision is the whole job.
Updated 10 min read
On this page
Key takeaways
- A payer payment is transcription — the remittance says where it goes. A patient payment is an application decision, because nothing that arrives with it says where it goes.
- A payment taken before the claim is adjudicated is applied against an estimate. Until the plan decides, what the patient actually owes is not known, so that payment has to be reconciled to the amount the remittance later assigns.
- A patient payment that cannot be matched to a balance is unapplied cash; one that exceeds what the patient owes is a credit balance. Both arise here for the same reason — no remittance directed the money.
- Applying a payment to the wrong account balances the cash and corrupts the ledger — the same trap as posting a payer lump sum: the deposit ties out while the account describes something that did not happen.
A patient payment has no remittance behind it
The reason posting a payer's payment can be made mechanical is that the payer sends instructions. The remittance advice — the electronic version is the 835 transaction — arrives against the specific claims it paid and states, line by line, the allowed amount, the adjustment, and the amount assigned as patient responsibility. A poster reads it and records it. The instructions are in the box.
A patient's payment has no such document behind it. The 835 is a payer-to-provider standard; there is no equivalent transaction that a patient sends with a check or a card. What arrives is money and, at best, a name and a statement number. Nothing in it decides which of the patient's open balances it settles — so posting a patient payment is not transcription of an instruction that already exists. It is the making of that instruction.
The task changes, so the error changes
When the payment arrives decides what it means
A patient can pay at two very different moments, and the difference is not a matter of convenience — it changes what the payment is.
After the claim is adjudicated, the remittance has already assigned the patient's share. The patient is paying a known balance, and applying the money is a matter of putting it against the balance the remittance created. Before the claim is adjudicated — a payment taken at or around the visit — the plan has not yet decided anything. What the patient owes is determined when the claim is processed and reported on the remittance, so a payment taken first is applied against an estimate, not against a settled amount.
An estimate is not the bill, and posting can quietly treat it as one
There is an accounting name for this that is worth knowing because it states the operational fact precisely. Money a practice receives before it has done the work it is paid for is not revenue — it is a liability, an obligation to deliver a service or return the money. In the accounting standard it is a contract liability. And once the claim adjudicates, any amount the patient paid above what the plan assigned is money the practice expects to give back — a refund liability — rather than income it gets to keep. Neither is a bookkeeping nicety: both say that a patient payment taken early is held, watched, and trued up, not banked and forgotten.
How and when to collect from a patient — at the desk, on a statement, from a card on file — is a separate question with its own rules, and this article does not take it up. The point here is narrower and only about the money once it is in hand: a payment that arrived before the payer decided cannot be posted as final, because the number it is measured against does not exist yet.
Applying it to the right balance
A patient is rarely a single balance. There may be several dates of service, more than one open statement, and a guarantor account that carries balances for more than one patient. A payment has to land on a specific one of these. If it does not, it does not disappear — it sits as money received against no particular charge, which is the definition of the suspense state posting is supposed to avoid.
Where the patient has directed the payment — paying a specific statement, or naming the visit — that direction governs, and posting simply follows it. Where they have not, the practice's own consistent, written application rule is what keeps the money attributable later: applied the same way every time, a payment can be traced back to a decision, and a review can tell whether that decision was right. Applied ad hoc, the same dollar becomes impossible to account for a month on, when the balance it settled and the balance it should have settled are both long closed.
| Dimension | Payer remittance | Patient payment |
|---|---|---|
| What directs the money | The remittance. It names the claim and line and states the share it assigned. | Nothing arrives that names a balance. The practice decides where it applies. |
| The core task | Transcription — record what the remittance already decided. | Application — decide which balance the payment settles. |
| The characteristic error | Mistranscription — the right figure in the wrong bucket. | Misapplication — the right money against the wrong balance. |
| When the owed amount is known | Already — the remittance reports it. | Only after the claim adjudicates, if the payment came first. Until then it is an estimate. |
| Where it goes to hide | A partial denial buried inside a lump-sum-posted claim. | Unapplied cash, or a credit balance the account carries as though it were settled. |
The two failure modes share a property that makes both dangerous: the cash reconciles in every case. Nothing that checks the money will catch either one — only something that checks the detail will.
Applying a payment to the wrong encounter is the patient-side version of the lump-sum trap that How Payment Posting Works describes for payer money. The deposit is right, the total is right, and one account now shows a balance paid that is not paid while another shows a balance owed that is not owed. It is invisible to every control that watches cash and visible only to one that reads the ledger.
The two places a patient payment goes to hide
Because nothing directs a patient payment to a balance, two exception states are specific to this work, and both are liabilities the practice is holding rather than money it has earned.
- It cannot be matched to a balance
- A payment with no identifiable account, or one that arrives before the charge it is meant to pay, has nowhere to land. It becomes unapplied cash — held in suspense until it can be applied, and cleared by application rather than written off. On the patient side this is common precisely because the payer's control numbers, which resolve so many payer payments automatically, do not exist for money a patient hands over.
- It exceeds what the patient owes
- When the adjudicated share turns out lower than what the patient paid — often because a pre-visit estimate was high, or because the patient and a secondary plan both paid — the excess is a credit balance that has to be confirmed and refunded to the party it belongs to. It is not the practice's to keep; in accounting terms it is a refund liability, and a credit balance sitting unresolved is money owed back that the books are quietly carrying as though it were not.
This is why patient A/R is reported net of these
It still has to reconcile, whatever the method
Cash, a check, or a card changes the mechanics of receiving a patient payment and none of the posting obligation. Whichever way it arrives, it is part of a deposit that has to tie out, and its application has to be provable against that deposit — the same completeness discipline Payment Reconciliation applies to every channel the money comes through. The method is where a patient payment differs from a payer's; the requirement that the record account for the money is where it is exactly the same.
Because so many downstream figures are built from what posting recorded, patient payments posted loosely distort more than one account. The practice's collection performance — the net collection rate and the balances that feed it — is computed from posted data, and money sitting in suspense or misapplied to the wrong account is money the metric cannot see where it actually is.
Common questions
Why is posting a patient payment harder than posting an insurance payment?
Because the insurance payment comes with instructions and the patient payment does not. A payer sends a remittance that names the claim, the line, and the share it assigned, so posting it is largely transcription. A patient's check or card arrives with a name and an amount and nothing that decides which of the patient's open balances it settles — so posting it means making that decision. The characteristic insurance error is recording the right figure in the wrong bucket; the characteristic patient error is applying the right money to the wrong balance. In both, the cash still reconciles, which is why neither is caught by anything that only checks the money.
How should a payment collected before the claim is processed be posted?
As a payment against an estimate, not against a settled balance — because until the plan adjudicates the claim, what the patient owes is not yet known. Money received before the work it pays for is done is a liability the practice is holding, not revenue, and once the claim processes the amount paid has to be reconciled to the share the remittance assigns. If the patient paid more than the plan assigned, the difference is a credit balance to be refunded; if less, there is a remaining balance to bill. The payment does not close the account; it opens an obligation to true it up.
A patient paid but we cannot tell which balance it belongs to. What happens to it?
It is posted to unapplied cash — a holding state for money received but not yet applied to a specific charge — and cleared by applying it once the correct balance is identified, never by writing it off. This happens more with patient money than payer money because the control numbers that let software match a payer's payment to a claim do not exist for a payment a patient hands over. The risk is that it sits: unapplied cash is a liability the practice is holding, and while it sits, the balance it should have settled still shows as open and may be followed up or sent to the patient a second time.
Can we keep a patient's overpayment against their next visit?
That is a decision governed by the practice's policy and the rules that apply to refunds, not by posting — and this article does not give legal guidance on it. What posting is responsible for is recognizing the overpayment for what it is: an amount the practice expects to return, a refund liability rather than income. A credit balance left unresolved on a patient account is money owed back that the books carry as though it were the practice's. Confirming and resolving it is covered in the credit balance article.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next.
How Payment Posting Works
Posting the payer's side — and the lump-sum trap the patient side repeats.
Patient Responsibility
What the patient actually owes — the balance a patient payment is applied against.
Unapplied Cash
Where a payment that cannot be matched to a balance waits.
Credit Balance Refund
Resolving the excess when a patient has paid more than they owe.
Authoritative sources
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Publishes the remittance-advice and cost-sharing rules: the amount a patient owes is set when the claim is adjudicated and reported to the provider on the remittance.
- X12 — EDI standards (opens in a new tab)
Maintains the 835 payer-to-provider remittance that makes posting an insurance payment mechanical; there is no adopted equivalent transaction for a patient's payment.
- FASB Accounting Standards Codification (opens in a new tab)
Topic 606: consideration received before a performance obligation is satisfied is a contract liability, and an amount expected to be refunded is a refund liability — not revenue.
- Healthcare Financial Management Association (HFMA) (opens in a new tab)
Publishes guidance on classifying patient accounts receivable net of applied and unapplied payments and of credit balances.