The B13 denial code indicates that payment for the claim or service may have been included in an earlier payment. The current remittance may show no new payment. Resolution depends on locating the earlier adjudication and tracing the money through the payer, bank and patient ledger.
Do not automatically rebill or appeal when B13 appears. First determine whether a prior payment was issued, later reversed or recouped, and posted to the correct patient, encounter and service line. A second claim can create more confusion when the original problem is an unmatched ERA, an unapplied deposit or an incorrect posting.
What does the B13 denial code mean?
The CMS standardized Claim Adjustment Reason Code reference defines B13 as: previously paid; payment for the claim or service may have been provided in a previous payment. The word “may” matters. B13 directs the provider to research prior payment history rather than assuming that the current claim is simply unpaid.
B13 is not tied to one CPT or HCPCS code. It may appear on professional, institutional, laboratory, therapy or other claims. The affected service code helps the team match the line to an earlier remittance, but it does not explain why B13 was applied.
Why B13 appears on a remittance
The payer may have paid the same service on an earlier claim, replacement claim or adjustment. The payment may be under a different payer claim-control number, included in a bulk EFT, applied during reprocessing, or offset by a later recoupment. Internally, payment posting and reconciliation can show whether the money posted to another encounter, remained in unapplied cash, or failed to post because the ERA did not match the bank deposit.
A B13 message can also follow a corrected or replacement submission when the payer retained the original payment history. Review the full claim lifecycle, including voids, reversals, takebacks and negative remittances. The latest zero-pay remit is only one event in that history.
B13 is not the same as an exact duplicate denial
CARC 18 identifies a duplicate claim or service. B13 instead points to payment that may already have been included in an earlier remittance. The operational questions overlap, but the response is different: a duplicate review compares submissions, while a B13 review must also prove where the prior payment went and how it was posted.
Do not close the account merely because another claim record exists. Confirm that the earlier payment covers the same patient, payer, date of service, procedure, units, rendering provider and billed line. A payment for a related service or another claim version is not enough.
A worked B13 reconciliation example
Assume a current ERA reports B13 on CPT 99213. The payer portal shows that the same service line was paid under the original claim-control number in an earlier EFT. The ERA trace number matches a bank deposit, but the payment was posted to a different encounter for the same patient. The correct action is to transfer or correct the posting and reconcile the account, not submit another 99213 claim.
If the payer cannot identify the earlier payment, the EFT never reached the provider, the prior payment was fully recouped, or the alleged payment applies to a different service, document that discrepancy and request payer research, reprocessing, reconsideration or appeal under the payer’s process. CPT 99213 is only the service used in this example; B13 can affect many CPT and HCPCS codes.
Evidence to collect before taking action
Build one evidence trail that connects the claim line, remittance and funds. Useful records include:
- The current ERA or EOB showing the group code, B13, any RARC, claim-control number, service line, adjustment and patient responsibility.
- Earlier ERAs, EOBs and payer-portal claim history for the original, corrected, replacement, voided and reprocessed claims.
- EFT trace numbers, check numbers, payment dates, payee details and bank-deposit confirmation.
- Posting batches, patient-ledger transactions, unapplied-cash records and transfer history.
- Recoupment, refund, offset and Provider-Level Balance adjustment records that may have reduced or reversed the earlier payment.
- A concise chronology showing the claim versions, payments, reversals, posting entries and remaining balance.
A practical B13 resolution workflow
1. Read the complete remittance
Capture the group code, B13, any remark codes, affected line, allowed amount, adjustment amount, patient responsibility, payer claim number and payment reference. Determine whether B13 applies to the entire claim or only one service line.
2. Locate the alleged prior payment
Search payer history by patient, member ID, date of service, procedure, billed amount, provider and all known claim-control numbers. Include prior claim versions and adjacent payment cycles rather than limiting the search to the current claim number.
3. Match the ERA to the EFT or check
CMS explains that one ERA or paper remittance may contain decisions for multiple claims and that one EFT or check may represent the benefits for the claims itemized in that remittance. Match the payment trace, total amount, date, payer and payee before concluding that the prior payment was received.
4. Reconcile the posting
The CMS EFT and ERA reassociation guidance explains that matching trace information connects the ERA with its payment so the provider can reconcile the amount, post it to accounts receivable and update patient accounts. Confirm that the deposit and every relevant service line reached the correct ledger location.
5. Check reversals, recoupments and offsets
Review subsequent remittances, refund activity, takebacks and provider-level adjustments. A payment may have been issued and later recovered. Record the original payment and the reversing transaction separately so the payer and internal ledger can be compared accurately.
6. Choose the correct follow-up
If the prior payment is valid and correctly posted, reconcile and close the account. If it is unposted or misposted, correct the ledger. If it was reversed or cannot be substantiated, request payer research or reprocessing. Appeal only when the payer’s determination remains incorrect and the documentation supports the requested action.
What to include in a B13 payer request
State the specific discrepancy and requested outcome. Identify the current claim and line, list all related claim-control numbers, and attach the current and earlier remittances. Include the EFT trace or check information, bank evidence when appropriate, recoupment history and a ledger excerpt showing how the payment was or was not posted.
Use a documented denial management and appeal process when no payment was found. Explain which sources were checked, why the alleged payment does not resolve the balance, and whether the payer should supply a trace, reissue funds, reverse B13 or reprocess the claim. Record the submission confirmation, owner and follow-up date.
Can a B13 balance be billed to the patient?
Not automatically. Review the group code, original adjudication, patient-responsibility amounts, contract terms, benefit rules, required notices and applicable law. A posting or reconciliation problem should not be transferred to the patient merely because the internal ledger still shows a balance.
Prevent repeated B13 reconciliation problems
Use disciplined payment posting and reconciliation to match every ERA to its EFT or check, balance each posting batch and route unmatched items to an exception queue. Monitor unapplied cash, missing remittances, partial postings and deposits that remain unreconciled at day end.
Connect posting exceptions to the denial management workflow so B13 accounts are researched before a rebill or appeal is created. Maintain links among original, corrected, voided and replacement claims, and preserve payer claim numbers and payment traces across every version.
An integrated revenue cycle workflow should also track recoupments, refunds, credit balances and provider-level adjustments. Trend B13 by payer, posting source, location, root cause and dollars so recurring interface or process failures can be corrected.
Frequently asked questions about the B13 denial code
What does B13 mean on a remittance advice?
B13 means the payer indicates that the claim or service was previously paid and that payment may have been included in an earlier payment. Research the earlier adjudication and payment trace before taking action.
Is B13 the same as an exact duplicate denial?
No. An exact duplicate code identifies a duplicated claim or service. B13 points to possible prior payment, so the review must also trace the earlier remittance, funds and posting.
Is B13 connected to one CPT or HCPCS code?
No. B13 can affect many service codes and claim types. Use the actual CPT or HCPCS from the affected remittance when reconciling a specific claim.
Should a B13 claim be rebilled immediately?
No. Rebilling before locating the earlier payment can create another claim record or duplicate activity. Verify the payer history, ERA, EFT or check, recoupments and ledger posting first.
What if the prior payment cannot be found?
Ask the payer to identify the payment date, amount, claim-control number and EFT trace or check number. If the payer cannot substantiate it, request research, reprocessing, reconsideration or appeal with the reconciliation evidence.
What if the payment was received but posted incorrectly?
Correct or transfer the posting under the organization’s approved controls, preserve the audit trail and reconcile the deposit to the ERA. A payer appeal is usually unnecessary when the payer paid correctly and the issue is internal posting.
Reconcile the payment before reopening the claim
B13 resolution requires more than finding an older claim. Trace the prior adjudication to its ERA, match the ERA to the EFT or check, verify recoupments and confirm the ledger posting. Once the complete payment history is clear, the team can reconcile the account, correct posting, request payer research or submit a supported appeal without creating unnecessary duplicate activity.