Where to start

Wondering where to start?

If its a claim rejection on a response report
try our Claim Rejections Page.

If it is an error in the InterfaceEDI program itself
try our InterfaceEDI Errors page.

Other useful information (Some other stuff)

Recent site activity

Home‎ > ‎

InterfaceEDI Errors and Messages


ERA 835 Payment Application



Host Not Found
while sending Claims or downloading reports, usually this is caused by a firewall, the firewall may be on the computer you are using or it may be a separate device on your network. Usually a personal firewall or security suite will have a list of programs that contains rules to apply to those program when they run. Look for InterfaceEDI and see if the program has a status of "Deny" or "Block".
It may also be caused by an error in the network or the clearinghouse ftp server didn't respond. If this is the case then try again.

EADSDatabaseError qryInsurance: Error 7200:  AQE Error:  State = S0000;   NativeError = 2124;  [Extended Systems][Advantage SQL Engine]Invalid operand for operator: >= [Invalid DATE] go to Control Panel, click on Regional and Language Options,  verify the Short Date is in the MM/dd/yyyy format, if not click on Customize, then go to the date tab, then change the short date format to MM/dd/yyyy

tblMEVerifyRec: Error 5004: Either ACE could not find specified file, or you do not have sufficient rights every time InterfaceEDI creates a claim file it creates a set of temporary tables. This error usually means that the create of those tables failed. First thing to look for is to see if somebody else is sending claims from another computer or remote session. It is possible that somebody has left a copy of InterfaceEDI open and viewing the EMC Verification Report. Another option is that the user doesn't have permission to create the tables in the data directory.

Invalid User ID or Password Reported By

if you are on Medisoft Version 14sp1, make sure you have the latest InterfaceEDI update. Changes were made in Medisoft that affect whether a claim is sent in Test or Production Mode.

CareVu Users : if this is a new user setup, contact CareVu to see if they have your account setup to submit claims using Secure FTP. Then check the Connection Type in InterfaceEDI. It should be FTP with SSH unless FTP with SSH is not available.

Availity Users : if this is a new setup, make sure the EDI Receiver setting for Transmission Mode is Active or Production.


The current socket connection has been reset- files not sent

The connection to the clearinghouse was broken while you were sending claims. Our program can't tell if the claims were sent so it did not mark the claims as sent.

to avoid possibly sending the claims multiple times,

go in to the interfaceedi to Reports, then download reports, see if you have a report for the claims you tried to send.

If you don't have a report after 6 hours, send the claims again, if you get a report, then the claims were sent.

Use claim management to mark the claims you sent to paper, then choose to print them to paper, but export them to a file instead of printing them to a printer. This will mark the claims as sent and set the billing dates for those claims.

Service not available, closing control connection
 
On the ftp screen behind the error, the last command will appear as LIST -al.
 
Go to Connection Type, try turning the Use Active Mode FTP on if it is off or off if it is on.

Missing 835 Reports
go in to View Previous Reports, look for the first report, is it on or about the same day as the first 835 in the 835 viewer?
if so, click on Add/Remove at the top then on Recover Files Removed From Index
if that adds reports, exit from there
go to 835 Remittance, click on Tools, Conversion, Convert All 835s, choose to not overwrite the files