Lock Box Posting

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

Lock Box Posting

NextGen® Enterprise PM supports ERA posting for patient payments using the Lock Box file format. Payments are posted according to the preference setup under Default Transaction Spreading in Practice Preferences > Transactions. By default, the First In / First Out (FIFO) option is selected. For more information on Default Transaction Spreading, refer to the File Maintenance Preferences Guide for NextGen® Enterprise. When the ERA Posting process is run, payments are posted against patient encounters that have a patient balance greater than $0.00. If there are any dollars remaining after the payment is posted, an unapplied payment is automatically posted to the patient’s account. However, if the user does not have the security right to post an unapplied payment, then no payments are posted. In addition, when the ERA Import Posting report is generated, a message displays next to the patient information indicating that the user did not have security to post the unapplied payment for that pa

Help Guide for NextGen® Enterprise PM 8

Practice Preferences for Patient Payments

You can set patient payments that are processed electronically in NextGen® Enterprise PM, similar to an ERA 835 file. The electronic file comes from a bank instead of a payer. You can set this up for your practice through your financial institution. Patients who owe balances would send their payments to the bank instead of to your practice. The bank would then deposit the money into the practice's account and send the practice a file that you can import into NextGen® Enterprise PM, just as an ERA file is imported. A transaction batch is automatically created when the file is imported, and a report similar to the ERA Import Posting report is generated. The table describes the preferences that you can set for patient pay in your practice. Patient Pay Import Description Default Transaction Code You can select the default transaction code to be used during Patient Pay Import. Do not post to encounters in a bad debt status Select this option to stop patient payments from posting automatical

File Maintenance Help for NextGen® Enterprise

Practice Preferences for Patient Payments

You can set patient payments that are processed electronically in NextGen® Enterprise PM, similar to an ERA 835 file. The electronic file comes from a bank instead of a payer. You can set this up for your practice through your financial institution. Patients who owe balances would send their payments to the bank instead of to your practice. The bank would then deposit the money into the practice's account and send the practice a file that you can import into NextGen® Enterprise PM, just as an ERA file is imported. A transaction batch is automatically created when the file is imported, and a report similar to the ERA Import Posting report is generated. The table describes the preferences that you can set for patient pay in your practice. Patient Pay Import Description Default Transaction Code You can select the default transaction code to be used during Patient Pay Import. Do not post to encounters in a bad debt status Select this option to stop patient payments from posting automatical

Help Guide for NextGen® Enterprise PM 8

Posting Transactions

In NextGen® Enterprise PM, a payment is considered posted only if has gone through the posting process. You can add or modify payments for an encounter only until it is posted. The posting process is a way of telling the application that everything has been done correctly and is ready to be committed to the system. Payment posting could be manual in paper format as Explanation of Benefits (EOB) or electronically as Electronic Remittance Advice (ERA). In NextGen® Enterprise PM, there are two sources for transactions, patients or payers. Payments may come from primary, secondary or tertiary payers. Transaction Posting Process You can create a batch to enter relevant information for payments and posting the payments. Viewing Transaction Dates You can view different dates associated with all transactions in the Batch Maintenance window. Recording Transactions to a Batch You can create a transaction batch header to enter payments or transactions. Posting Encounter and Account Level Payments

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

Lock Box Posting

Recommendations

Reading the ERA Import Posting Report

Lock Box Posting

Practice Preferences for Patient Payments

Practice Preferences for Patient Payments

Posting Transactions

Electronic Remittance Advice

Lock Box Posting

Reading the ERA Import Posting Report

Lock Box Posting

Practice Preferences for Patient Payments

Practice Preferences for Patient Payments

Posting Transactions

Electronic Remittance Advice