How payment posting works, and where money hides

Payment posting is treated as the clerical end of the revenue cycle, and it decides what every other part of it believes. The ageing report, the denial queue, the patient statement run and the month-end revenue figure are all downstream of decisions somebody made while posting a remittance.

Which means posting done quickly and carelessly does not simply produce a small error. It produces a practice that is confidently wrong about its own accounts receivable.

Every line is a decision

A remittance line does not just say how much was paid. It says how much was allowed, how much was adjusted and why, what the patient owes, and whether anything was refused. Posting it means deciding, for the remaining balance, where it goes next: to a secondary payer, to the patient, to a contractual adjustment, or to a queue for somebody to look at.

Get that wrong in the generous direction and the practice writes off money it was owed. Get it wrong in the other direction and patients receive statements for amounts a contract says they do not owe, which is both a service failure and, depending on the contract, a compliance problem.

The distinction that matters most

A contractual adjustment and a denial can look almost identical on a remittance and mean opposite things. One is the difference between what was billed and what the contract allows — normal, expected, nothing to do. The other is the payer refusing to pay something it may owe.

When both are posted as adjustments, the claim closes and the denial vanishes. It does not appear on the denial report, nobody appeals it, and the ageing report looks healthier than the practice is. This single habit is responsible for more invisible loss than most practices realize, and it is entirely a posting-side problem.

So the rule is: post the denial as a denial, with its reason and remark codes attached, and let the denial queue decide what happens next. Posting is not the place where a refusal gets resolved, but it is the place where a refusal gets recorded.

Reconcile to the deposit

The check on all of this is simple and is skipped constantly: what was posted today should equal what was received today. Bank deposits, card settlements, payer electronic funds transfers and patient payments, against posted totals.

When those two numbers do not agree, something specific is wrong — a batch posted twice, a batch not posted at all, a takeback applied as a payment, a payment belonging to a different tax identification number. Each of those is findable on the day and close to unfindable three months later.

A daily reconciliation with a written explanation for any variance is the single most valuable control in this function.

Where money hides

• Unposted batches. Received, not applied. They should be counted every day and aged, with a reason attached to anything older than a couple of days.
• Partially posted batches. More dangerous than unposted ones, because they look finished.
• Takebacks and recoupments. A payer reclaiming a previous payment on a current remittance. Posted incorrectly, it either doubles the loss or hides it.
• Refunds and credit balances. A credit that sits on an account is often somebody else’s money and needs a defined process rather than a periodic clean-up.
• Interest and penalty payments. Small amounts that post oddly and quietly break reconciliation.
• Payments received for an entity that is not you. Rare and worth having a rule for before it happens.

What to set up before handing it over

The posting rules

Which adjustment codes map to which categories, what triggers a balance transfer to a secondary payer, when a balance becomes patient responsibility, and what the threshold is for a small-balance write-off. If these live only in one person’s head, they are not rules, they are habits.

The exception rule

What the seat does with anything that does not fit: post to a holding location, flag, and report. The wrong answer is to guess, and the second wrong answer is to leave the batch untouched with no note.

Autopost configuration

Electronic remittances can post automatically, and should — but the rules behind autoposting need review, because a badly mapped adjustment code applied automatically produces the denial-hiding problem above at scale and at speed.

The daily close

What must be true before the day is closed: everything received is posted or explained, the reconciliation balances, and the unposted count is recorded.

Access and separation

Posting access is financial access. Named accounts, not shared logins, so every posted line is attributable — which matters for both audit and for finding the source of a mistake.

How to assess it

• Does posted cash reconcile to received cash daily, and are variances explained in writing?
• What is the unposted balance right now, and how old is the oldest item?
• Are denials being posted with reason codes and reaching the denial queue?
• How many accounts required correction after posting, and what caused them?
• Are balance transfers to secondary payers happening promptly, or is the secondary ageing?
• Are credit balances being identified and cleared under a defined process?

When outsourcing makes sense

Payment posting is well suited to a dedicated seat because the rules can be written down completely and the work can be checked against an external fact — the deposit. That is a rarer combination than it sounds, and it is why this function is often the first one a practice hands over successfully.

It is worth considering when posting is running behind, when the ageing report is not trusted, when denials seem lower than the practice’s experience suggests, or when the person posting is also the person doing three other things and posting is what slips.

Questions for a provider:

• Will the seat post inside your system, under a named account?
• Who reconciles to the deposit, and what will you receive daily?
• How are denials posted, and do they reach your denial queue automatically?
• What happens to a line the seat cannot post confidently?
• Is it a dedicated full-time seat or shared capacity?
• How is month-end handled, and what does the close look like?

How Soft Home Global staffs this

Soft Home Global provides trained full-time back-office seats from Rawalpindi, Pakistan. Payment posting is published at $1,500 per seat per month, billed per seat with a one month minimum.

The seat posts inside your system on US hours, to your posting rules and your adjustment map: electronic remittances and manual explanations of benefits, adjustments recorded by category, denials posted with their reason codes so they reach the denial queue rather than closing silently, balances transferred to the next responsible party, and a daily reconciliation against what was received.

Anything that does not fit the rules is flagged rather than guessed, and reported the same day. Where a posted denial needs working, it moves to the AR and denials queue — a seat Soft Home Global also staffs, which is what turns the handoff into a queue rather than a message.

The test to run this week

Take one day. Add up everything received — payer transfers, card settlements, cheques, patient payments — and compare it with everything posted for that day. Then look at the denials posted: do they carry reason codes, and did they appear in the denial worklist?

If the first number does not match and the second answer is no, the practice’s reports are describing a business that does not exist, and every decision made from them is being made on fiction.