Payment Posting & ERA/EOB Specialist Interview Questions & Answers

The Payment Posting Specialist records payer payments into the billing system: matching ERAs (835 files) or EOBs to claims, posting line-level payments, contractual adjustments and patient responsibility, flagging underpayments and variances, and reconciling deposits. Posting accuracy is the foundation of all downstream A/R โ€” wrong postings corrupt everything after them.

Snapshot$34,000โ€“$46,000 entry; $44,000โ€“$58,000 with 3+ years (US market)

Skills to talk about in the interview

  • ERA (835) auto-posting and manual EOB posting, line-level detail
  • Adjustment groups: CO (contractual), PR (patient responsibility), OA (other)
  • Key CARCs: CO-45, PR-1, PR-2, PR-3, CO-97, CO-50; RARC basics
  • Deposit reconciliation, EFT matching, zero-pay EOBs
  • Variance flags: payment below contract, unexpected denials in remit

Fresher (No Experience)

What they test: Role clarity, EOB reading, accuracy mindset

Q1. What does a payment posting specialist do?

Records what payers actually paid into the billing system: matching each remittance (EOB or ERA) to its claim, posting line-level payments, adjustments and patient responsibility, and flagging anything unusual โ€” underpayments, denials, wrong amounts. Everything downstream (A/R, statements, collections) depends on my postings being right.

Q2. What is an EOB and what information does it contain?

Explanation of Benefits โ€” the payer's processing summary: claim number, DOS, billed amount, allowed amount, what the payer paid, contractual adjustment, patient responsibility, and denial codes/reasons. I read it line by line and translate it into postings.

Q3. What's the difference between billed, allowed and paid amounts?

Billed is what we charged; allowed is what the contract permits; paid is what the payer actually sent; the difference between billed and allowed is the contractual write-off, and allowed minus paid minus patient share is where problems hide. Example: billed $300, allowed $200, paid $160, patient coinsurance $40.

Q4. Why is accuracy critical in payment posting?

Because posting errors compound: wrong patient responsibility creates wrong patient statements and disputes; missed adjustments distort A/R; unnoticed underpayments become silent revenue loss. Fixing posting errors later costs far more than entering them right.

Q5. What would you do if the EOB doesn't match the claim in the system?

Stop and investigate โ€” check payer ID mismatches, duplicate or combined payments, and claim number confusion. Never force-match a remit to the wrong claim; I flag it for the senior/supervisor rather than posting garbage into the A/R.

Q6. How comfortable are you with repetitive numeric work and targets?

Very โ€” I understand posting is high-volume detail work with daily counts, and I'd build accuracy first and speed second. I also know fatigue causes number errors, so micro-breaks and self-checks are part of my method.

TipFresher posting interviews: EOB anatomy, the billed/allowed/paid equation with a worked example, accuracy temperament. Practice reading one sample EOB aloud until fluent.

0โ€“6 Months Experience

What they test: ERA workflow, PR codes, reconciliation basics

Q1. Walk me through posting an ERA (835 file).

Import the 835, review the batch summary (total paid, total adjustments), then review line-level exceptions before finalizing: paid-below-allowed variances, denials I didn't expect, missing write-offs. Post the clean lines automatically, work exceptions manually, and reconcile the batch against the EFT deposit total before closing.

Q2. What's the difference between CO and PR adjustment groups?

CO (contractual obligation) is the provider's write-off โ€” we can't bill the patient for it (CO-45 contractual adjustment). PR (patient responsibility) belongs to the patient โ€” PR-1 deductible, PR-2 coinsurance, PR-3 copay. Confusing them creates wrong patient bills โ€” the most damaging posting error.

Q3. How do you reconcile a payment batch?

Three-way check: ERA total vs system posting total vs EFT bank deposit. Any mismatch gets traced โ€” partial remits, combined check payments, or posting errors โ€” before the batch closes. Reconciliation is what makes posting trustworthy rather than just fast.

Q4. What do you do with a zero-payment EOB (denial in remit)?

Denials arrive in remittances all the time โ€” I post the zero payment with the denial reason, verify the CARC, and route the claim to the denial/follow-up queue with complete notes. Zero-pay EOBs are work items, not dead files.

Q5. What common posting errors have you seen (or made)?

Real ones: posting PR amounts as CO (wrong patient bill), missing secondary-payer sequences, auto-accepting variances without review, and misposting a combined EOB across the wrong claims. I keep a personal error log โ€” knowing my own error patterns is how I fixed them.

Q6. How do you handle payments that arrive without any EOB or ERA?

Unapplied or unmatched cash: I don't guess-post. Log the deposit, attempt matching by amount/date/payer, and escalate unmatched funds to the senior with documentation. Posting money to random claims corrupts the A/R and creates refund liabilities.

TipCO vs PR discipline and the three-way reconciliation are the 6-month signatures. Have a real error log story โ€” self-awareness sells here.

1 Year Experience

What they test: Variance analysis, secondary posting, underpayment flags

Q1. How do you detect and handle underpayments during posting?

Compare paid amount against the contracted allowed per payer/CPT. Below contract: flag the variance with the EOB line and contract reference, route to the underpayment queue for reconsideration, and never close the claim as fully paid. Recurring short-pays on one payer become an escalation case.

Q2. How does secondary insurance posting work?

After primary posts: send or verify the secondary claim with the primary EOB attached, then post the secondary's payment with its own adjustments, and confirm the total across payers plus patient share equals the allowed. Sequence errors (billings out of order, COB wrong) surface here โ€” I flag them for COB fixes.

Q3. What is balance billing and when is it a problem?

Billing the patient for amounts the payer should have covered โ€” beyond PR amounts on in-network claims. It's usually a posting or contract error, not a collections strategy. When I spot PR + CO confusion creating balance-bill exposure, I flag it immediately before statements go out.

Q4. How do you handle interest or incentive payments on remits?

Some payers pay interest on late claims or prompt-pay incentives โ€” these post separately from claim payment, flagged in the system so they don't distort the claim's paid amount or create refund math errors later. Special-payment types get documented, not blended.

Q5. What posting KPIs did you own?

Claims/EOBs posted per day, posting accuracy from QA sampling, batch reconciliation exceptions resolved same-day, and variance flags raised (count and dollars). The variance dollars I flagged often mattered more to leadership than my posting count.

Q6. How do you handle takebacks or refund requests found during posting?

Payer takebacks (recoupments) post as negative adjustments with the original claim reference and reason โ€” never silently netted against unrelated claims. Refund requests route to the refund process with documentation. Recoupments are audit-relevant; I keep their trail clean.

TipUnderpayment detection and secondary/COB posting fluency mark the one-year poster. Takeback/refund handling shows audit-awareness beyond routine posting.

1โ€“2 Years Experience

What they test: Posting ops, QA contribution, exception queues

Q1. How have you improved a posting process?

One with numbers: e.g., standardized exception-review checklists by payer (top variance patterns), which cut misposted variances and shortened batch close time. Or: built a payer cheat-sheet mapping their remit quirks so exceptions resolve first-pass.

Q2. How do you QA other posters' work?

Sample posted batches against source ERAs/EOBs โ€” check payment amounts, adjustment coding (CO vs PR), patient responsibility accuracy, and variance flagging. Trend errors by poster and payer, coach privately, and fix systemic issues in checklists or system settings.

Q3. How do you manage the exception queue without it becoming a dumping ground?

Defined exception categories (variance, denial-in-remit, unmatched payment, takeback), owners per category, aging visibility, and a daily review cadence. Exceptions are where the real money decisions live โ€” unmanaged queues hide underpayments and denials.

Q4. What's your approach when posting reveals a payer's systematic error?

Document the pattern with claim samples and dollar impact, escalate via the variance/underpayment process with a specific ask (reprocessing, corrective action), and post affected claims accurately in the meantime. Evidence converts frustration into recovery.

Q5. How do you handle posting during system conversions or new payer onboarding?

Parallel-run posting where possible, validate converted open balances against real remits, build payer-specific exception checklists, and monitor the first month's posting QA at 100%. Conversions are where posting discipline proves or breaks itself.

Q6. Describe a reconciliation nightmare you resolved.

Real story structure: the mismatch (deposit vs posting totals), the tracing method (claim by claim, payer by payer), what it turned out to be (combined checks, misapplied funds), and the fix โ€” plus the control you added so it can't repeat.

TipProcess improvement with numbers, QA rubrics, and exception-queue management define this level. The reconciliation story proves real competence under pressure.

2โ€“3 Years Experience

What they test: Team management, posting strategy, integration with A/R

Q1. How do you manage a posting team's production and quality?

Daily volume dashboards with QA accuracy sampling, workload balancing by payer complexity, exception-queue ownership per team member, and weekly error-trend reviews. My policy: accuracy gates batch closure; speed targets follow skill โ€” the same discipline I ran as a poster.

Q2. How do you connect posting accuracy to downstream A/R health?

Posting errors become downstream chaos: wrong PR creates patient disputes, missed variances lose revenue silently, misposted denials age incorrectly. I feed posting-error patterns into A/R training and keep a monthly joint review with the A/R lead โ€” posting is A/R's foundation, and both teams should see it that way.

Q3. What's your strategy for auto-posting vs manual posting?

Auto-post clean 835 lines (high-volume routine payers), manual for exceptions, variances and complex payers. I monitor the auto-post exception rate monthly โ€” when payer behavior shifts, auto-posting silently misposts unless someone watches. Trust automation with measurement.

Q4. How do you handle credit balances discovered in posting?

They're refund obligations, not windfalls: identify the source (overpayment, duplicate payment, misposting), document, and route to the refund process with the compliance clock in mind (payer-specific refund timelines). Sitting on credits is a compliance risk, not a convenience.

Q5. How do you set up posting for a new payer onboarding?

Get their remit samples first (ERA or EOB format), map their adjustment quirks and special codes, build the exception checklist, define auto-post rules, and run the first month at heightened QA. Payer remits differ more than people expect โ€” onboarding is where misposting is born.

Q6. What posting metrics matter to leadership, and how do you report them?

Posting accuracy (QA), timeliness (days from remit to posted), variance dollars flagged, exception queue aging, and unapplied cash aging. I report weekly in a one-pager: trend, exceptions, actions. Leadership cares about cash integrity, not line counts.

TipTeam production management, auto-post governance, credit-balance compliance, and the posting-to-A/R connection define the 2โ€“3 year poster-lead.

3+ Years Experience

What they test: Posting program design, revenue integrity, audits

Q1. How do you design the posting function for a growing organization?

Segmented by payer complexity (routine auto-post payers vs complex manual payers), a dedicated exceptions/variance desk, reconciliation controls owned separately from posting (segregation of duties), and dashboards covering accuracy, timeliness and variance dollars. Growth breaks posting when reconciliation and posting live in the same unreviewed hands.

Q2. How do you contribute to revenue integrity programs from posting?

Posting is where payer behavior becomes visible data: underpayment variance by payer/CPT, denial-in-remit patterns, recoupment trends. I feed this monthly to contracting and denial teams with dollar figures โ€” posting data is the cheapest revenue-intelligence source in the cycle.

Q3. How do you handle posting compliance (audit trails, refund regulations)?

Complete posting audit trails (who posted what, when, from which source), documented recoupment and refund processes with regulatory clocks, segregation between posting and reconciliation duties, and periodic internal audits. Posting is a compliance surface โ€” regulators and payers both audit it.

Q4. Describe designing a variance management program.

Structure: variance definition per payer contract, detection at posting (automated comparison vs fee schedule), a variance queue with owner and aging, escalation thresholds by dollar, and monthly recovery reporting with payer-level trends. Underpayment recovery starts with detection discipline at posting.

Q5. How do you manage posting through payer system changes (new remit formats)?

Test remits before go-live, map new adjustment codes against our posting logic, update auto-post rules and exception checklists, train the team with before/after examples, and monitor the first weeks' QA at elevated sampling. Format changes are where silent misposting happens.

Q6. What's your framework when posting accuracy degrades across the team?

System-first diagnosis: a payer format change, an auto-post rule error, a system update, staffing strain. Team-wide simultaneous drops are rarely five people failing at once โ€” find the change, fix it, retrain the delta, and only then look at individual performance.

TipProgram-design level: segregation of duties, variance programs, compliance audit trails, system-first diagnosis. One variance-recovery result with dollars is your proof.

4+ Years Experience

What they test: Leadership, automation governance, cross-functional ops

Q1. How have you led automation in posting operations?

835 auto-posting with exception queues, automated fee-schedule comparison for variance detection, and dashboards for batch reconciliation. My governance: every automated path has a validation sample, an exception-rate monitor, and a human sign-off on batch closure. Automation drafts; the team certifies.

Q2. How do you structure posting within a full RCM operation?

Integrated with A/R and denials: posting feeds variance queues and denial queues directly with clean notes; A/R aging depends on posting timeliness; and the whole pipeline shares one dashboard (remit-to-post lag, exception aging, variance recovery). Siloed posting creates the handoff gaps where revenue dies.

Q3. How do you manage client-facing posting issues (BPO context)?

Honest monthly reporting: posting accuracy, variance dollars identified, recovery status, and โ€” where relevant โ€” telling the client their fee-schedule data or payer mix is driving variances, with evidence. Client trust in posting comes from transparent reconciliation, not from quiet claim counts.

Q4. What's your playbook for a major payer remit disruption (format change, system outage)?

Contain (hold auto-posting for affected payer), assess (sample remits, map changes), adapt (update rules/checklists, train), and recover (rework affected batches with reconciliation). Document everything โ€” remit disruptions create both misposting risk and reconciliation gaps that auditors ask about later.

Q5. How do you develop posting leads and supervisors?

Ownership with guardrails: each lead owns a metric and a payer segment, runs the daily exception huddle, and brings data-backed solutions to reviews. I coach their coaching initially, then step back. Leads grow by running real things with real stakes.

Q6. What would you do in your first 90 days leading our posting function?

Baseline: accuracy (QA sample), remit-to-post lag, variance recovery status, exception aging, unapplied cash. Quick wins: the top two error sources and the worst aging queue. Structural: auto-post governance review, variance program check, and a reconciliation control audit. Baseline dashboard published by week two.

TipLeadership interviews: automation governance, integrated pipeline design, client transparency, crisis playbooks, 90-day plans. Quantify every claim.

5+ Years Experience

What they test: Strategy, cash-integrity economics, industry direction

Q1. How do you frame posting strategy at the executive level?

Posting is cash integrity: it determines whether reported A/R is real, whether patient bills are correct, and whether payer underpayment gets caught or silently absorbed. I present posting in three currencies โ€” A/R accuracy, variance dollars recovered, and compliance risk managed. Functions that frame themselves in cash language get funded; ones that frame themselves as data entry get cut.

Q2. What structural improvements have produced lasting posting quality?

Segregation of posting and reconciliation duties, automated variance detection against contracts, exception queues with owners and aging, and the posting-to-A/R data feedback loop. Structure beats heroics โ€” quality that depends on individual vigilance doesn't scale.

Q3. Where is payment posting heading as an industry?

Toward real-time remittance (payer APIs, faster ERA cycles), richer auto-posting logic, and AI-assisted variance detection. The human role shifts to exception judgment, payer relationships and revenue-integrity analysis. Teams should build data literacy now โ€” poster roles are becoming analyst roles.

Q4. How do you quantify the cost of poor posting quality?

Four buckets: misdirected patient bills (disputes, churn), silent underpayment (uncollected forever), corrupted A/R (wrong priorities, wasted work), and compliance exposure (refund clocks, audit findings). I've built this math for business cases โ€” poor posting is far more expensive than the headcount to do it right.

Q5. What's the most significant posting transformation you've led, with numbers?

Flagship: scope, the mess (misposting patterns, aged exceptions), the redesign (controls, automation with governance, exception program), and measured outcomes (accuracy up, variance recovery up, lag down). Rehearse it โ€” this is your executive proof.

Q6. Why you, and what do you need from this organization?

Full arc: posted, QA'd, built variance programs, led automation with governance, and framed posting in executive language. What I need: contract/fee-schedule data access, sponsorship for detection tooling, and a culture that treats variances as revenue, not noise. With those, cash integrity improves measurably in two quarters.

TipExecutive interviews: cash-integrity framing, cost-of-poor-quality math, structural playbooks, industry trajectory. Close with the rehearsed flagship transformation.