Posting Capitation Payments

The reason a claim remittance can be posted almost mechanically is that it arrives against the claims it decided. The remittance advice — electronically, the 835 — names each claim and line and states the allowed amount, the adjustment, and the patient's share. A capitation payment carries none of that, because it is not paying for any particular service. It is a fixed amount paid for each member enrolled for the period, to cover a defined scope of care, and it is paid whether or not that member is ever seen.

That single fact — paid regardless of whether the member receives services — is what separates the two tasks. A claim payment answers the question, what did the payer decide about this claim? A capitation payment has no such question to answer, because it was not decided about a claim; it was decided about a population and a period. So a poster who approaches it the way they approach a remittance — hunting for the claims to apply it to — finds nothing to apply it to. That is not a defect in the file. It is the nature of the payment.

Every payment a practice receives has to be proven right against something. For a claim payment, that something is the claim — the allowed amount against the contract, the payment against the allowed amount. For a capitation payment the charges are the wrong reference, because the payment was never a function of what was billed. It is a function of who was enrolled. The amount should equal the members the payment covers for the period, each at the agreed per-member rate. What that rate was agreed to cover, and what happens when utilization runs past it, are terms of the arrangement rather than of the payment — Capitation Contract Basics covers the agreement this payment comes out of.

So the reconciliation is to eligibility. The roster the payer paid on is compared against the members the practice believes are enrolled, and the two are made to agree. The characteristic error here is not a wrong figure dropped in the wrong bucket; it is an unreconciled roster — being paid for members who have terminated, or not being paid for members who enrolled. It does not surface as a cash difference the way a short claim payment does, because there is no expected claim amount for it to fall short of.

Membership is not static, and its corrections reach backward. A member can be added or terminated with an effective date inside a period already paid, so a capitation payment routinely carries retroactive adjustments to prior periods — a member restored for a month already closed, or removed from one already settled. Posting has to attach each adjustment to the period it corrects rather than the period it arrived in; do it by arrival date and the reconciliation for both periods quietly drifts out of agreement.

Being paid by capitation does not mean the work goes unrecorded. The services the capitation covers are still submitted — as encounters — and they still adjudicate. What comes back is not a payment but an adjustment: the covered service is shown and its charge is reduced to nothing under a contractual-obligation reason that marks it as covered by the capitation arrangement, with no separate amount paid. The money for that service already arrived, prospectively, in the capitation payment.

This produces two flows that must not be confused. There is the money flow — the periodic capitation, reconciled to the roster — and the encounter flow — the services recorded, adjudicating at zero pay. They live in different places and mean different things, and the danger is treating a line from one as though it belonged to the other.

The encounter is not busywork either. It is how the payer measures what its capitation bought — the utilization, the risk of the population, the quality of the care — and under managed-care rules the entity paying capitation is required to collect it, including from the providers it pays by capitation. A dropped encounter, on the reasoning that it pays nothing, erases the record of care actually delivered; and because future capitation rates are built on that data, a practice that stops submitting encounters under capitation is degrading the very record its next rate depends on.

A capitation payment does not attach to the moment a service is delivered. The practice is paid to stand ready to serve the population for the period, so the payment covers that whole period, whether or not it is drawn on — attributed to the period the members were entitled to care, not to the month they happen to use it. A capitation payment for a month belongs to that month even if no member was seen; it is not a windfall in a quiet month or a shortfall in a busy one. The gap between the fixed payment and the cost of the care actually used is the risk the practice accepted, not a posting exception to be chased.

A capitation contract also frequently pays less than the headline rate up front. A portion may be withheld — retained by the payer, held against the practice's performance and the results of a shared risk pool, and returned in whole, in part, or not at all after the period closes. The base per-member payment, the amount withheld, and any later settlement of the pool are three different events, and posting them as one misstates every period they touch.

For all that it differs, a capitation payment is still a deposit, and every deposit has to tie out. The completeness discipline is the same one Payment Reconciliation applies to every channel — the money that arrived is accounted for and posted. What changes is only the thing it is proven against: a membership roster instead of a batch of claims. A capitation payment that cannot be tied to a contract, a period, and a roster has nowhere to land, and like any unplaceable receipt it sits as unapplied cash until it is reconciled — never resolved by writing it off.

And because the practice's reported figures are built from what posting recorded, a capitation payment mishandled distorts them quietly. Forced against open claims, it closes balances that were never going to be paid per service and leaves the encounters looking settled by cash they had nothing to do with. Posted as ordinary accounts receivable, capitated accounts make the A/R read like charges awaiting payment when the payment already came a different way. The net collection rate and the receivable that feeds it describe a fee-for-service world; capitation is not in that world, and posting is where the two are kept from contaminating each other.