Troubleshooting 837 EDI Batch Billing

Last updated
Save as PDF

Overview

Troubleshoot issues with batch billing for an 837 EDI file.

Details

Issue: My 837 EDI file status is not what I'm expecting it to be.

Solution: Use the following table to aid in troubleshooting possible solutions.

Possible Cause	Possible Solution
The Billing file is showing as 'Released', not 'Processed'.	Check for possible errors in Corepoint. Reach out to your TIER/SQL/Corepoint Administrator to check the connection state and/or Logs for Errored Messages in the Corepoint Admin Console. For example: The error states ‘Unable to convert value for database parameter ‘PayorKey’ to type Int32’. This usually means that the PayorKey is NULL. You can review in SQL to validate: Select payorKey,* from bil_batches where batchkey = 45976
After the user released an 837 EDI batch, they cannot find the output file.	The user just needs to know where to pick up the file so that it may be placed with the respective clearinghouse or payor. Look in SQL for this information. The BIL_Payors table holds the location of where the 837 files are created. Select FileOutput_837I, FileOutput_837P, * From BIL_Payors In some systems the Payor form shows this as well. There is a Configuration tab for 837P and one for 837I, as in the following example.

Possible Cause

Possible Solution

The Billing file is showing as 'Released', not 'Processed'.

Check for possible errors in Corepoint.

Reach out to your TIER/SQL/Corepoint Administrator to check the connection state and/or Logs for Errored Messages in the Corepoint Admin Console.

For example: The error states ‘Unable to convert value for database parameter ‘PayorKey’ to type Int32’. This usually means that the PayorKey is NULL. You can review in SQL to validate:

Select payorKey,*
from bil_batches where batchkey = 45976

After the user released an 837 EDI batch, they cannot find the output file.

The user just needs to know where to pick up the file so that it may be placed with the respective clearinghouse or payor.

Look in SQL for this information. The BIL_Payors table holds the location of where the 837 files are created.

Select FileOutput_837I, FileOutput_837P, *
From BIL_Payors

In some systems the Payor form shows this as well. There is a Configuration tab for 837P and one for 837I, as in the following example.

Refer to your Agency’s Billing Setup process as needed. If, after following the troubleshooting steps, the issue still occurs, please contact your TIER System Administrator so they can contact NetsmartCares Support for assistance.