A remittance moves from a payer's adjudication file to your bank deposit on its own schedule — and the two halves rarely arrive together. Here is how the lane actually runs, where it drifts, and what keeps reconciliation clean across every payer you bill.
Intake
A claim and the payment that answers it are two documents that should tell the same story. In a clean operation they do. In a real one, the claim says one thing, the remittance says something slightly different, and a person decides which is right.
Intake
An encounter becomes a coded record, is scrubbed for edits, and leaves through the clearinghouse.
Same day
Route
The payer adjudicates the claim and returns a decision with whatever payment is attached to it.
Days
Reconcile
Posting, appeal, patient billing — all of it depends on the return trip being legible.
Weekly
Release
The matched amount posts, the exception queue clears, and the deposit is released against the record.
Weekly
Most teams are strong on the outbound half and weaker on the inbound half. That is the sentence to sit with — the part of the lane you don't control is the part you have to learn to read.
Route
Every payment that leaves a payer arrives on one of three rails. They are not interchangeable, they carry different amounts of remittance detail, and each needs its own handling rule before the deposit arrives.
Rail one
A check arrives with a paper advice stapled to it, and the advice is often the only place the adjustment detail exists. Someone opens it, reads the line items, and types the numbers into the posting screen. The rail is slow, but the remittance is right there in the envelope.
Carries
Full line-level detail, transcribed by hand
Rail two
The deposit lands in the operating account on the payer's cycle; the 835 file lands whenever the payer produces it. When the two are electrically enrolled, matching is quiet. When they are not, the deposit posts against nothing and waits in an exception queue.
Carries
Electronic remittance, when enrolled per payer
Rail three
The payment arrives on a card number the payer issues for one claim batch. The card network is not a remittance carrier, so no advice travels with it. The deposit is visible, the explanation is not — which is exactly where an unmatched pile starts.
Carries
Payment without accompanying remittance advice
The point of putting them on one bench is comparison. A practice that takes all three rails needs three handling rules — and one person who watches that all three rules hold.
Shift change
Back office · handover
The room keeps running. Someone leaves, someone arrives, and the queue has to be exactly where it was left — which is why one person clears it to zero every week and no one logs into a payer portal to find out.
Reconciliation slip
Remittance advice
835 electronic remittance, line by line
Payment advice
Deposit matched to the advice that explains it
Exception queue
Cleared to zero every week, one owner
Operator notes
Once the payer's adjustment codes are mapped to your posting rules, alignment stops being a technical problem. What remains is discipline — and the notes below are what the discipline looks like on a real desk.
Electronically enroll
Enroll for electronic remittance with each high-volume payer.
Per payer
RCM
Until the enrollments exist, every remittance arrives as a download or a printout and every line is a transcription. Converting the top twenty payers by volume first means the queue shrinks fastest at the payers you see most often.
Keep the enrollment dates in one place. When a payer moves you onto a new portal version, the enrollment is the first thing to check before you assume the file stopped coming on its own.
Field note — where a Zelis portal login exists per payer, consolidation is what removes the logins.
Map adjustment codes
Map each payer's adjustment codes to your posting rules once.
Once
RCM
Every 835 carries the payer's reasoning in adjustment codes — contractual obligation, patient responsibility, denial reason. The mapping translates those codes into the actions your system takes, and once it is written the posting becomes a rule instead of a decision.
Review the mapping when a payer changes their code set. That change is usually the reason a payment that once posted cleanly has started landing in the exception queue.
Field note — the mapping is what makes reconciliation quiet instead of manual.
Route exceptions
Send unmatched deposits to a visible exception queue, not a personal inbox.
Weekly
RCM
An unmatched payment in an inbox is invisible the moment the person who owns that inbox is on vacation. A shared queue keeps the count on the wall where the team can see it — and a visible count is the only pressure that actually clears it.
Field note — a queue with one owner beats a queue nobody owns.
Own the clear
Give one person the job of clearing that queue to zero every week.
Weekly
RCM
Teams that do not clear the queue weekly will have the same backlog in January that they had in September. The count is the metric that matters, because it is the one that compounds.
Field note — weekly is not a slogan here; it is the cadence that holds.
On the provider side
Payment integrity is the discipline of making sure a claim is paid correctly — not overpaid, not underpaid, and not denied for a reason that does not hold. It runs on the payer side as edit rules and audits; on your side it runs as a review of what came back.
Check first
Denial reasons — read the code the payer actually sent, not the category your system guessed at.
Check second
Adjustment codes — contractual, patient responsibility, or an edit your own mapping needs to update for.
Check third
The right to appeal — if the reason does not hold, the appeal is the correction, and it is on you to file it.
Never assume
That a paid claim was paid correctly. Underpayments slip through quietly, which is why the review runs on a cycle.
Adding a payer
Before adding a payer to an automated lane, confirm three things. The first thirty payments are where the surprises live, and having one person watch them end-to-end is cheaper than a clean-up six months later.
Question one
Do they send electronic remittance at all, or is the advice a portal download you will transcribe?
Question two
Does their payment rail match something your system posts natively, or does it need a new handling rule?
Question three
Who owns the first thirty payments end-to-end, and where is that ownership written down?
Avaneer Health and Change Healthcare both operate in the payer-provider connectivity space. Their existence is a reminder that routing infrastructure is its own specialty; your job is making sure the last mile into your own system is clean.
Where to go next
If the drift is on the remittance side, portal guidance is where the work gets documented per payer. If the drift is on the mapping side, the playbook is where the enrollment, mapping and queue routines live. Zeils Agent keeps both on the same shelf so the operators walking the lane do not have to be the ones who remember it.
