Start from the remittance and the payment evidence
CMS explains that a remittance can contain decisions about multiple claims and adjustments at different levels. Preserve the original ERA or paper remittance and the available payment reference. The posting team needs enough context to connect the explanation with the correct entity, deposit and accounts.
Do not begin with a bank total and distribute it across claims merely to make the batch balance. The payer’s explanation may include items that need separate handling. Record what has been matched and what remains an exception. Restrict patient and financial details to the authorized billing and accounting systems used for this work.
Define practical exception categories
Create categories such as missing remittance, unidentified deposit, unmatched claim, duplicate file, unexplained adjustment and payer response needing interpretation. Keep categories specific enough to route the work. A single bucket called posting issue makes it difficult to see whether staff need a file, a system correction or a qualified review.
For each item, capture the payer, relevant date, available references, reason for the hold, owner and next action. Avoid duplicating detailed patient data in a general task board. Our payment posting support can help organize this workflow within the practice’s approved systems and responsibilities.
Read adjustments at the correct level
CMS describes claim adjustment group codes, reason codes and remark codes, along with provider-level balance adjustments. Those elements help explain why a payment differs from a submitted amount. Staff should preserve the full combination and context instead of reducing it to a generic denial label.
Route interpretation questions to a qualified billing reviewer. A provider-level item may require a reconciliation task that differs from a claim-specific follow-up. Do not force it onto an unrelated patient account. Keep the original file available so another reviewer can reproduce the reasoning and identify whether the action taken matches the payer’s actual explanation.
Review responsibility before moving balances
A remaining balance needs a supported disposition. Check the remittance, contract information and applicable billing requirements before assigning an adjustment or patient balance. If the evidence is incomplete, keep the item in a documented review state with an owner rather than using a default write-off or patient transfer.
Define who can approve contractual adjustments, refunds, corrections and other account changes. Separate routine entry permissions from decisions that need supervisory review. The practice’s policy should explain how staff obtain that review and retain the rationale. Accurate posting is a control over the account record, not simply a measure of how quickly a batch is closed.
Reconcile batches without hiding differences
Compare the remittance amounts, deposit information and posting totals through the practice’s reconciliation method. Identify any difference explicitly and determine whether it results from timing, a missing file, provider-level activity or another documented cause. Do not silently carry an unexplained amount forward as if it were resolved.
Keep exceptions connected to the batch so the accounting and billing teams can see the same status. Establish an internal review cadence and escalation rule based on volume and risk. Where an issue needs payer assistance, preserve the question and response reference. This makes follow-up more precise than repeatedly reporting that the account does not balance.
Use recurring exceptions to improve the source workflow
Review repeated patterns with the team that can address their cause. A wrong provider association may belong with enrollment. A missing ERA may belong with the electronic transactions owner. An unclear adjustment policy may require billing management or compliance review. Assigning the right owner reduces unnecessary handoffs even when the payer decision itself cannot be changed.
Document the change and check a later batch for the same pattern. Keep the focus on accurate records and resolved evidence. Niyutsa can coordinate accounts receivable follow-up when a posted item needs further work, with approvals and payer decisions retained by the responsible parties.
Close a partial payment exception with a traceable record
A remittance covers several claims and the deposit agrees with the payer’s total, but one claim has an unexpected adjustment. First confirm the deposit, remittance and batch separately. Review the affected claim at the applicable claim or service-line level and compare the coded reason with the payer policy or contract where relevant.
Keep the adjustment in the appropriate exception queue until its owner determines the next action. A posting lead may handle a matching issue, a denial reviewer may need the affected claim documentation and an underpayment reviewer may need the applicable fee schedule. Avoid changing patient responsibility just to reconcile the deposit total.
At closeout, note the account, reason, decision, evidence and reviewer. If a category recurs, collect several examples and look for a common source such as one payer product, mapping rule or recurring contractual discrepancy. Then assign follow-up to the process owner who can address that source.
- Payment match. Tie deposit and remittance to the same payer and receiving entity.
- Claim exception. Record reason and the level of the affected adjustment.
- Resolution. Document who owns the issue and which evidence supports the next action.
What if the bank total matches but individual balances look wrong?
Close the financial reconciliation where supported and keep the claim-level exceptions open. Review each affected balance using the remittance, claim record and applicable contract or policy.
Tag a repeated exception with the source
When the same mismatch returns, label the payer product, the actual system or workflow involved and the person investigating the pattern. This keeps successive reviewers from opening duplicate work items and gives finance a clear record of outstanding exceptions.
Common questions
Is every adjustment a denial?
No. Read the complete remittance context. Adjustments can occur at different levels and may require different accounting or billing actions.
Should an unexplained difference be written off to close a batch?
Use the practice’s authorized review process. Preserve the difference as an assigned exception until there is a supported disposition.
Who should own a missing ERA?
Assign a specific electronic transactions or payer-contact owner, while keeping the posting team informed of the retrieval status.
Sources and further reading
Put this guide to work
Use the current program or payer instructions to confirm the steps for your own organization. Niyutsa Technologies can help scope application preparation, tracking and the handoff to billing.

