Resolving System-Related ERA Errors

System ERA Error Message	Message Description	How to Resolve
Error occurred during final update to the database. Processing ceased due to inserting duplicate transaction Ids. Error Code = 9.	There was an error during the final update to the database. When you get this message, no information from the ERA 835 file was saved to the database, the ERA Posting process failed.	Always keep a copy of the error message. Follow the instructions in the error message: Wait a few minutes and try processing the file again. If you are unable to complete the ERA Posting process and you get this message again, the error has been written to the ODBC Error Log file. Contact NextGen Healthcare Client Support.
Error occurred during final update to the database. Processing ceased. Error Code = x.	This is a generic system error message. If any problems are encountered when information from the ERA 835 file is being saved to the database, and the error code is other than Error Code = 9, then you get this error. The exact error code displays in the message.	Always keep a copy of the error message. Follow the instructions in the error message: Wait a few minutes and try processing the file again. If you are unable to complete the ERA Posting process and you get this message again, the error has been written to the ODBC Error Log file. Contact NextGen Healthcare Client Support.

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

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

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

Electronic Remittance Advice

Electronic Remittance Advice (ERA) 835 files can be imported from the File > Processes > ERA Posting menu. This process compares transactions in the ERA 835 file for each claim against the charge information in NextGen® Enterprise PM. When ERA transactions match to charges, a transaction batch is automatically created, and the ERA transactions are added to the batch ledger. Transactions in the ERA file that do not match to charges, or do not post for other reasons, display on the ERA Import Posting report as “Not Posted” and are not added to the transaction batch. The ERA Posting process is designed to increase efficiency. Once the original set up for the process is complete, there is minimal effort required to set up additional payers. It is estimated to take about 15 minutes to post an electronic ERA 835 file for a 30-page Explanation of Benefits (EOB) electronically, compared to approximately two hours to post the same 30-page EOB manually. ERA Automatic Adjustments and Library Sett

Help Guide for NextGen® Enterprise PM 8

ERA - 835

This section explains the ERA 835 file. The basic steps in working with the 835 file include: Download the file from the payer or clearing house. Set up an ERA Remittance Profile library. Select File > Process > Import ERA. Print the report. Verify the batches. Post the batches. Reference: For more information on the ERA 837 files, go to the NextGen Healthcare Success Community and download the latest Electronic Remittance Advice (ERA) User Guide for NextGen® Enterprise PM. Parent topic: Coordination of Benefits Electronic and Manual Processing

NextGen® Background Business Processor Help 8

Automated Task for ERA File Posting Using ERA Directory Import

You must create and assign an automated Encounter task in Task Types master file in File Maintenance along with the custom user-defined reason code to track the discrepancy in ERA payment amount and contractual reimbursed amount when you post 835/ERA file in NextGen® Background Business Processor using ERA Directory Import option. Note: If there are more ERA files or each ERA has more than one encounter (claim) and it meets the criteria for payment received but not for the contractual reimbursement amount, then separate tasks must be created for each encounter (claim). When you select the Default for Contract <> ERA Payment Amount check box and configure the patient response (PR) codes in the Reason Code Library Maintenance window in File Maintenance, a task will be generated. This will create the reason code during ERA file import. For more information on creating and assigning the automated task, go to NextGen Healthcare Success Community and download the latest File Maintenance Mast

Resolving System-Related ERA Errors

Recommendations

Resolving Line Item-Related ERA Errors

Resolving Internal System-Related ERA Errors

Reading the ERA Import Posting Report

Electronic Remittance Advice

ERA - 835

Automated Task for ERA File Posting Using ERA Directory Import

Resolving Line Item-Related ERA Errors

Resolving Internal System-Related ERA Errors

Reading the ERA Import Posting Report

Electronic Remittance Advice

ERA - 835

Automated Task for ERA File Posting Using ERA Directory Import