A Guide to Downloading 837p Files in CR Essentials

Efficiently generating an 837p file in CR Essentials is a crucial step in the claim submission process. It is imperative to follow a systematic approach to facilitate this, ensuring accurate input of essential details. The steps outlined below guide users through the process.


Step 1: Configure Payers in CR Essentials

A. In CR Essentials, go to the Settings section from the main menu, then click on Financial Settings.


B. Access the Payer List

  • On the Financial Settings page, select Payers to view a list of all configured payers.


C. Edit Payer Settings

  • Click Edit next to each payer you want to connect through Availity.


D. Update Claim Settings

  • Scroll to the Claim Settings section. In the "Connection" dropdown menu, select Availity.


Step 2: Configure Advanced Claim Settings

After selecting Availity as the connection, click on the Advanced Claim Settings button. This will allow you to fine-tune the payer configuration for compatibility with Availity.


Step 3: Enter Required Payer Settings

Within the Advanced Claim Settings window, ensure the following fields are filled in. These numbers depend on what clearinghouse you want to submit the claims to. These numbers you should get from the clearinghouse and the ones on the image below are for Availity only.

  • Interchange Sender ID (ISA06):
  • Interchange ID Qualifier (ISA07):
  • Application Sender’s Code (GS02):
  • Application Receiver’s Code (GS03):

Once complete, click Save to apply your changes.



Step 4: Enter client's information.

Go to the client's profile and click on the edit button on the top right corner and make sure the following fields are filled out:

  • First Name and Last Name
  • Gender
  • Address
  • DOB
  • Primary Payer
  • Insurance ID
  • Diagnosis

Step 5: Go to billing summary, click on the claims tab, and then clic on the claim ID.


Step 6. Go to the CMS 1500 form and click on the "Download 837p file" button.


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

Still need help? Contact Us Contact Us