Billing operations guide

Design a payment posting close checklist for the billing desk

A daily close checklist that ties deposits to remittance batches, surfaces exceptions in a fixed order, and leaves a reviewable packet.

Published 6 min read
On this page

Set the daily close boundary

A payment posting close needs a clear cutoff because payments that arrive after the cutoff belong to the next business day. Record the cutoff time, the time zone, and the systems included in the close. List the team members who posted during the day and the person who will review the result. Without that boundary, two shifts can count the same payment or leave a late batch in neither day.

The close should cover electronic remittance, paper checks, card payments, and any manual adjustment that changes cash. Attach the bank or processor deposit report to the remittance summary before posting is considered finished. Note any deposit that lacks a matching remittance and any remittance that lacks a deposit. Those two exceptions tell the reviewer where to look first.

Match deposits to remittance batches

Match each deposit to a remittance batch using the trace number, batch total, and posting date when those fields exist. Compare the total before and after posting rather than checking only individual claims. A batch can appear balanced at the claim level while the deposit remains unmatched at the bank level. Keep the batch identifier in the close file so a later reviewer can reproduce the match.

When a deposit includes multiple remittances, split the match without losing the link to the original deposit. When a remittance includes a deduction that does not belong to the batch, record it as an exception instead of forcing the total. Do not edit the source file to make the numbers agree. The close file should show the source amount, the posted amount, and the reason for any difference.

Review exceptions in a fixed order

Review unapplied cash first, then partial payments, overpayments, reversals, and unidentified deposits. That order protects the largest and most reversible risks before the team spends time on small variances. Give each exception a type, a source reference, an owner, and a next action date. A reviewer should be able to read the exception list without opening every claim.

A reversal needs the original payment reference and the reason for the reversal, not just the new balance. An overpayment needs a decision about refund, credit, or transfer, and that decision belongs to the approved owner. A partial payment needs a note on whether the remaining balance is patient responsibility, a payer issue, or an unresolved adjustment. The close is complete only when each exception has a next step.

Keep unapplied cash visible

Unapplied cash is a temporary holding state, and it should never become a quiet place to park difficult work. Set an age threshold for unapplied items and report the count and value at every close. Assign the oldest item to a named person before the shift ends. If the team cannot identify the source, document the search rather than guessing a patient or claim.

A useful unapplied cash note includes the deposit date, amount, trace or check number, remittance reference, candidate matches considered, and the reason each candidate was rejected. That note lets the next reviewer continue without restarting the search. It also shows whether the problem is a missing remittance, a posting error, or a payer reference that does not exist in the system. Keep the note with the case so a later reviewer does not have to rebuild the search from scratch.

Prove the close with a short packet

The close packet should contain the cutoff note, deposit report, remittance totals, exception list, unapplied cash list, and the preparer and reviewer names. Keep it short enough that a manager can read it in a few minutes. Add the reconciliation difference and an explanation when the posted total does not equal the deposit total. If the explanation is unknown, label it unknown and assign the investigation.

Retain the packet with the accounting period so a later audit can connect the posting to the bank record. Store supporting exports in the approved system rather than a personal drive. Use the packet to answer questions about a specific transaction without reconstructing the day from memory. The same evidence supports payment posting and collections follow-up when a balance remains open.

Hand off the next morning cleanly

End the close with a short handoff that names what is still open, who owns it, and when it will be reviewed. Separate items that need a payer response from items that need an internal decision. Flag any exception that could affect the next day's deposit or a patient statement. The next shift should not have to infer priorities from a long queue.

Close the loop with accounting

The posting close and the accounting close should agree on the cash and adjustment totals for the day. Send the close packet to accounting with the reconciliation difference and the exception list. If accounting records a deposit that the billing team has not posted, treat it as an open item rather than a timing difference to ignore. Agree on the cutoff and the contact for a late entry.

Reconcile the day's adjustments to the approved reason codes and the source remittance. A large adjustment without a clear reason should stay in the exception list until an owner explains it. Do not let the accounting team see only the net result when the gross activity contains a reversible error. The two views should tell the same story.

Review the close packet at the next morning's handoff and again at month end. At month end, compare the daily packets to the monthly control account and explain any gap. A daily close that never reconciles to the monthly total is not a reliable control, even if each packet looks complete. The connection between the two cycles is where many posting errors surface.

Authoritative references

  1. CMS Medicare Remittance Advice
  2. CMS Medicare Overpayments
  3. HHS HIPAA Privacy Rule
  4. NIST Cybersecurity Framework
  5. GAO Green Book

Philippines staffing intake

Define the role before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us