Reading the ERA Import Posting Report

Help Guide for NextGen® Enterprise PM 8

Reading the ERA Import Posting Report

After you have completed the ERA Posting process, the ERA Import Posting report generates. Overall, the report is a complete audit of the ERA 835 file and is grouped by unsuccessful and successful entries. NextGen® Enterprise PM does not, however, report provider level adjustments. The report is sorted by practice with the ERA payments that did not post successfully listed first, followed by all the ERA payments that posted successfully. An ERA message displays in the Description column of the report next to each line item as an indicator for why the ERA claim payment did or did not post against the encounter information. Each of these messages applies to ANSI file formats. The transaction level Reason Codes that are distributed to service lines display on the report, along with their descriptions. Note: The ERA Import Posting report detects and rejects an ERA transaction with a denial reason code and total transaction amount that is not $0.00. Resolving Encounter-Related ERA Errors On

Help Guide for NextGen® Enterprise PM 8

Resolving Line Item-Related ERA Errors

The ERA messages outlined below are related to those line items listed on the encounter that the ERA payment is posting against. There are two types of line item related ERA messages: The primary error ERA message This type of message indicates the exact line item on the encounter that caused the ERA posting process for the encounter to be unsuccessful. The secondary ERA message This type of message displays for any line item following the primary error. Because the ERA posting process was stopped due to the primary error, these line items are not processed. Note: Once the line item payments post, a "Line Item successfully posted" message displays. If NextGen® Enterprise PM finds any existing payments for a payer, this message indicates that secondary payments were also found during posting. The following table outlines each of the primary error ERA messages and the associated secondary ERA messages, a description of why the primary and secondary ERA message may have occurred, and the

Help Guide for NextGen® Enterprise PM 8

Posting an Electronic Remittance

This section provides information about the process of posting an electronic remittance. When posting the ERA, the system compares the ERA payment information for each claim in the file against the encounter information in your system that the claim was originally created for. In order for the ERA payments for each claim to post successfully, the ERA payment information for a claim must match the encounter information the ERA is posting against. If there is a discrepancy between the ERA information and the encounter information, the ERA payment for that claim does not post and an error message displays on the ERA Import Posting report. In addition, if an ERA payment is posting against multiple line items in an encounter, all the line items must be error-free for the ERA payment to post successfully. The ERA process only calculates and posts adjustments for encounter primary and secondary payers. If the primary ERA pays a charge off, it is settled to the secondary and is included on the

Help Guide for NextGen® Enterprise PM 8

Resolving Internal System-Related ERA Errors

The ERA messages outlined here are related to internal system errors. These ERA messages are also considered primary and secondary. The primary error ERA message This type of ERA message indicates the exact line item in the encounter that caused the ERA posting process for the encounter to be unsuccessful. The secondary ERA message This type of message displays for any line item following the primary error. Because the ERA posting process was stopped due to the primary error, these line items are not processed. The following table outlines each of the primary error ERA messages and the associated secondary ERA messages, a description of why the primary and secondary ERA message may have occurred, and the possible resolution to the primary error message. Primary Error ERA Message Message Description How to Resolve Insurance not found for this encounter. The ERA file information for the insurance associated with this encounter does not match the insurance associated with the encounter in

Help Guide for NextGen® Enterprise PM 8

Bundled Payments

For bundled payments, the ERA Import Posting report functions as described below: If an Encounter Level Payment Distribution method is not selected in the Remittance Profile library, the ERA Import Posting report displays the following message: "Bundled payment was not posted because Encounter Level Distribution method was not enabled in the Remittance Profile". Note: The ERA Posting process cannot post bundled payments unless an Encounter Level Payment Distribution method has been selected in the Remittance Profile. If the claim is UB/837I and no claim was found for the encounter of the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no claim was identified for this encounter". If the claim is UB/837I and no match was found for the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no charge match was found for this revenue code". If the clai

Help Guide for NextGen® Enterprise PM 8

Auto Balanced Batch Column on the ERA Import Posting Report

If you set the Automatically balance batch when an ERA is imported with no errors option in the Remittance Profile Library to either Auto Balance or Auto Balance and flag for BBP, then the Auto Balanced Batch column on the ERA Import Posting report displays one of the following: Y indicates no errors were encountered during the import and the batch was auto-balanced. N indicates errors were encountered during the import and the batch was not auto-balanced. If the option is not enabled or is blank (default), then the column displays N/A on the report for all batches. Some clearinghouses may use the same ERA payer number for all payers. In this case, if an 835 ERA file contains a single check with multiple payers and some payers use a Remittance Profile library with the Automatically balance batch when an ERA is imported with no errors option enabled and other payers use a profile with the option disabled, then the Auto Balanced Batch column on the ERA Import Posting report will display

Reading the ERA Import Posting Report

Recommendations

Reading the ERA Import Posting Report

Resolving Line Item-Related ERA Errors

Posting an Electronic Remittance

Resolving Internal System-Related ERA Errors

Bundled Payments

Auto Balanced Batch Column on the ERA Import Posting Report

Reading the ERA Import Posting Report

Reading the ERA Import Posting Report

Resolving Line Item-Related ERA Errors

Posting an Electronic Remittance

Resolving Internal System-Related ERA Errors

Bundled Payments

Auto Balanced Batch Column on the ERA Import Posting Report