Error Report Cheat Sheet (Release ERA page)

Let's review the errors you'll encounter when working your Release ERA page, and what steps you’ll need to take to resolve them. 

  1. Error reports appear once you've released ERA's using the Release ERA process. Scroll down to the bottom of the page to view associated errors. 
  2. Click on the blue link in the last column to open a detailed Error Report view. This report will open a pop-up window.
  3. This report includes a list of errors or exceptions (in the Error Desc column) that you’ll need to review, as an action may be required. 
  4. The table below is a list of the most common error descriptions and the recommended action for each error. 
  5. Once you finish working an error report and balance the EOB, click the Close checkbox on the left side of the page and then click Update at the bottom of the page. You can close multiple error reports at the same time. After you close an error report, it no longer displays on this page.

Important: We recommend you work your Error Report within 48 hours from the time the ERA was auto-posted to ensure proper accounting and balancing. Always verify the total amount posted matches the EOB paid amount. Error Reports do not alert you if the total amount posted does not match the paid amount of the EOB.  So, it is imperative that you balance the amount auto-posted by running one of the Payment Balancing Reports.

For some of the listed actions below, you will need to access Standard Payments, found by selecting Payment > Batch Payments, and/or Error Corrections, which is also found under the Payment menu. 

Errors: Action Required

Error Description Action
Account has a payment sticky note(s) Payment did not post during Release Process. Post payment manually and follow instructions detailed on Sticky Note.
Account, Date of Service, CPT code, and units combination was not found
Post payment manually after determining where the payment should be applied. Payment may need to be posted to the insurance over-line if the Date of Service or CPT code was billed out of RevFlow and is now inactive. Payment may need to be applied to the previous billing software.
Patient account was not found
Post payment manually. The patient account number does not match a RevFlow account number. Search by patient name. If not found, check inactive patients and/or previous billing system. Payment may need to be applied to the previous billing software.
Matching Inbound Payer ID not found Verify the payer released is the same payer listed on the patient's account. If payer matches, send check information revequip@webpt.com to request inbound payer id to be added to the payer record.
Charge left with a credit balance Correct account using Error Corrections. EOB auto-posted and left a credit on the CPT code listed on the Error Report.  Determine if credit is correct or if an action needs to be taken.
(Reason Code) adjustment excluded The adjustment did not apply to the CPT code listed on the Error Report. Determine if this is a denial. If it is a denial, no action needed. This denial will be listed on the Zero Pay Report for the Billing Staff to work. If an adjustment needs to post during the auto-posting, email revequip@webpt.com requesting adjustment reason code to be added to the release process. Include the clinic code, check number and reason code that you would like added. If an adjustment is posting during the release process that should not adjust, email revequip@webpt.com requesting the adjustment reason code to be excluded during the release process. Include the clinic code, check number and reason code you would like excluded.
Units do not match The units billed do not match the units paid on the CPT code listed on the Error Report. Check account in Error Corrections selecting inactives to see if the units were updated. Post the payment appropriately. This error is often listed for all CPT codes where a payer reimburses a flat, contracted rate and does not pay per billed unit. You’ll need to determine which payers you can ignore this error for.
Negative Adjustment Posted The CPT code listed on the Error Report included a negative adjustment on the electronic EOB listed in the adjustment column. It is important to check these accounts using Error Corrections to make sure an incorrect balance has not moved out to the patient or secondary. Some payers that post the entire payment to one CPT code will use negative adjustments to apply a balance to the next available payer or patient. You will need to determine which payers you do not need to verify accounts are correct.
Charge already posted Open EOB and make sure in Error Corrections that payment has posted (usually payment is posted).
Missing a CPT Code Correct posting in Error Corrections.
OA-23 adjustment excluded Verify if an adjustment is needed.
PR-96 adjustment excluded Make sure charge should not be adjusted. If for a penny charge, no action needed.
CO-B7 adjustment excluded Make sure charge should not be adjusted.
CO-B13 adjustment excluded Use Error Corrections to see if charge should be adjusted off.
CO-22 adjustment excluded Make sure charge line is correct in Error Corrections.
CO-97 adjustment excluded Make sure charge should not be adjusted. This is normally used for 97010 and should be manually adjusted off.

Errors: No Action Required

Error Description Action
No Error No action needed. EOB released with no errors.
Secondary or Tertiary Insurance No action taken
OA-18 adjustment excluded No action taken
OA with any adjustment code Most OA qualifiers are for secondary payers. These codes are excluded and normally no action is required
PR-119 adjustment excluded No action needed
CO-21 adjustment excluded No action needed
CO-18 adjustment excluded No action needed
CO-29 adjustment excluded No action needed
CO-24 adjustment excluded No action needed
CO-170 adjustment excluded No action needed
CO-151 adjustment excluded No action needed
CO-22 adjustment excluded No action needed
CO-165 adjustment excluded No action needed
PR-16 adjustment excluded No action needed

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.