Accurate Payment Posting & ERA Reconciliation

Why Precise Payment Posting Matters

Inaccurate payment posting creates a cascade of downstream problems: incorrect patient balances, false AR aging reports, missed underpayment disputes, and compliance risks. Many practices underestimate how errors in this seemingly administrative step can distort the entire financial picture of a practice.

BlueBird Medserv treats payment posting as a critical quality-control checkpoint. We don't just record payments — we verify them against contracted rates, reconcile them against submitted charges, and immediately escalate any variance for investigation.

Our Payment Posting Services Include

• Electronic Remittance Advice (ERA) auto-posting with exception management
• Manual EOB posting for payers without ERA capability
• Patient payment posting from checks, credit cards, and online portals
• Insurance payment vs. contract rate variance detection
• Automated underpayment flagging and dispute initiation
• Contractual adjustment and write-off management
• Secondary claim generation after primary payer adjudication
• Daily cash reconciliation and deposit verification

Key Benefits

The Hidden Revenue in Underpayments

One of the most overlooked sources of revenue loss in medical billing is insurance underpayments — situations where the payer processes and pays a claim, but pays less than the contracted rate. Unlike denials, which generate a clear rejection notice, underpayments often pass unnoticed because the claim was technically paid. Without an automated comparison against your fee schedules and payer contracts, underpayments accumulate silently, costing practices thousands to tens of thousands of dollars annually.

BlueBird Medserv's payment posting process includes automated fee schedule verification for every payment received. Our system compares each posted amount against your specific contracted rate with that payer, flags any discrepancy above a defined threshold, and initiates the dispute or reconsideration process immediately. This proactive approach recovers underpayment revenue that most practices never realize they are owed.

ERA vs. EOB: How We Handle Both

Modern medical billing involves two primary formats for payment and remittance information. Electronic Remittance Advice (ERA), transmitted as an 835 transaction file, allows for high-volume automated posting with minimal manual intervention. Explanation of Benefits (EOB) documents, received by mail or through payer portals, require manual entry but carry the same contractual and audit significance as electronic remittances.

BlueBird Medserv handles both formats with equal precision. Our ERA auto-posting process handles the majority of payments electronically, with intelligent exception handling that identifies and routes unusual adjustments for human review. For EOBs, our payment posting specialists enter each remittance manually, verifying every line-item adjustment code, and flagging any contractual adjustment that appears inconsistent with your current payer agreements.

Payment Posting as a Quality Control Checkpoint

Beyond simply recording payments, our payment posting function serves as an active quality control checkpoint in your revenue cycle. Every payment we post is an opportunity to catch payer errors, identify claim-level issues that may indicate a systemic billing problem, and verify that your accounts receivable data reflects reality. When the payment posting function is performed accurately and promptly, every downstream metric — AR aging, collection rate, days in AR — becomes meaningfully more reliable and actionable for your practice leadership.

BlueBird Medserv's payment posting team operates with a zero-tolerance approach to posting errors. Every entry is reviewed for accuracy before being finalized, and our daily quality control process reconciles all posted payments against bank deposit records — ensuring that every dollar received is accounted for and every discrepancy is identified and investigated before month-end close. This discipline protects your practice from the financial reporting errors that compound when inaccurate payment data flows downstream into AR analytics, patient statements, and provider productivity reports.

Inside an 835: What Posting Staff Actually Read

The 835 (ASC X12 005010X221A1) is the HIPAA standard electronic remittance advice. Posting is not just matching a check amount to a patient; each loop carries information that drives the next billing action:

• BPR and TRN segments carry the payment amount, method (ACH/EFT, check or virtual card) and the trace number used to match the remittance to the deposit.
• CLP (claim payment) segments show the patient control number, claim status code (processed as primary, secondary or tertiary, denied, reversal), total charge, total paid and patient responsibility.
• SVC (service line) segments show each procedure, billed amount, paid amount and units, so line-level partial payments and denials are visible.
• CAS (claim adjustment) segments carry the group code, CARC and amount for each adjustment, and the LQ segment carries the RARC.
• PLB (provider level balance) segments show adjustments not tied to a claim, such as overpayment recoveries, forwarding balances and interest.

Paper EOBs hold the same information in a different layout, and they are keyed manually. Because the hand-keyed version is more error-prone, the same CARC, group code and amount rules are applied to both, and paper payers are periodically reviewed for electronic enrollment. ERA enrollment is by payer and by tax ID and NPI, and the ERA should be paired with EFT where possible so that the remittance and the money can be matched to each other.

Contractual vs. Patient Responsibility: The Posting Order

Each dollar on a remittance has to land in exactly one place: payer payment, contractual write-off, patient responsibility, denial or other adjustment. The group code is what decides it. An illustrative example for an in-network claim:

The check is simple arithmetic: billed minus contractual minus patient responsibility equals the payment. Whenever the payer's math does not tie, the claim is flagged. Related rules that posting staff apply:

• PR amounts can transfer to the patient or secondary insurance, but CO amounts cannot be balance-billed when the provider is contracted.
• Secondary and tertiary claims are generated from the primary 835 with the primary payment and adjustments reported on the 837 (CAS and AMT segments), or via payer crossover where it is available.
• Denied lines are not written off during posting. They are routed to the denial queue with the CARC/RARC attached.
• Payments applied to the wrong patient, date of service or line are corrected by reversing and reposting, never by editing a balance to make it agree.

Underpayment Detection Against the Contract

A payment can be "correct" on its face and still be short. Detection requires the expected reimbursement for every CPT/HCPCS code, modifier and place of service to be stored in a contract model and compared to the allowed amount at posting.

1. Load the expected rateContracted fee schedules, percentage-of-Medicare formulas and carve-outs are loaded for each payer and plan, with effective dates, so the expected allowed amount can be calculated per line.
2. Compare at postingThe allowed amount on each service line is compared to the expected amount. Differences above a set tolerance are flagged. Multiple procedure reductions, modifier pricing (such as 50, 51, 62, 80) and sequestration or other known adjustments are accounted for before a variance is called an underpayment.
3. Validate before disputingThe analyst confirms the contract version, the date of service, the plan and any payer policy that would legitimately reduce payment. A false underpayment dispute wastes payer goodwill.
4. File the disputeThe reprocessing request, payer dispute form or contract-based appeal is submitted with the 835 line, the contract excerpt and the expected calculation. Dispute windows are often shorter than people expect, so variance items are dated at posting.
5. Track to recoveryOpen variances stay on a log until the payer reprocesses, the dispute is lost with a documented reason, or the item is closed. Patterns by payer feed contract review and rate renegotiation.

Reconciling Postings to Bank Deposits

Posted payments must equal money received. A practical daily reconciliation compares three views of the same cash:

1. Batch totalsEach payment batch posted in the practice management system is totaled by source (ERA/EFT, lockbox checks, patient payments, merchant processor).
2. Remittance to depositFor EFT, the TRN trace number and amount on the 835 are matched to the ACH credit on the bank statement. For checks, the check number and amount are matched to the lockbox or deposit record. Virtual card payments are matched to the processor settlement, which may be net of card fees.
3. Resolve breaksCommon causes of mismatches are an 835 received without a deposit, a deposit with no 835, a PLB recoupment netted from a payment, a batch posted to the wrong date, and duplicate postings. Each break is logged with an owner and an age.
4. Close the periodUnapplied cash, suspense balances and unreconciled items are reviewed before month-end close and cleared or documented.

Refunds, Overpayments and Recoupments

Posting also surfaces money that belongs to someone else. Overpayments arise from duplicate payments, payment after a primary and secondary mix-up, payments for services later adjusted, and payer errors. A good process is:

• Identify: credit balances are reviewed regularly by payer and by patient, and each is classified as a true overpayment, a misposted payment or a timing difference before any refund is issued.
• Refund or reapply: payer overpayments are returned by check or refund request form with the claim reference; patient credits are applied to other open balances first, then refunded according to policy and state unclaimed-property rules.
• Respect deadlines: federal rules for Medicare and Medicaid generally require identified overpayments to be reported and returned within 60 days of identification, and many commercial contracts and state laws set their own refund and recoupment windows. Process timing should follow the applicable contract and counsel's guidance.
• Handle takebacks: payer recoupments appear as negative PLB entries (for example overpayment recovery, forwarding balance or interest codes) or as reversal claim statuses on the 835. Each recoupment is matched to its original claim, checked for validity and disputed where the payer's basis is wrong.

The Daily Posting Workflow and Exception Queues

Auto-posting handles clean, expected remittances. Everything else is routed to an exception queue instead of being forced through:

• Unmatched claims: an 835 line that cannot be matched to a patient control number or account.
• Variance items: allowed amounts that differ from the contract model.
• Denials and zero-pay lines: forwarded to the denial or AR queue with codes attached.
• Reversals and corrections: reverse-and-rebill sequences from the payer, which must net out correctly.
• Unusual adjustments: uncommon CARCs, large write-offs and credit balances needing review before approval.