ERA fatal errors
Path: Transactions>General>ERAs
ERA files can be processed with fatal errors.
- Fatal errors usually mean that the file is corrupted.
- If fatal errors exist in the file, the system rejects the file at the time of processing and shows a message explaining the issues.
- Sometimes, fatal errors can be fixed by deleting the existing ERA file and downloading it from the payer's system again.
- Use this approach when the error message appears with the corresponding request.
Some examples of fatal errors that affect the ERA file are:
- ERA file you are loading is not of the supported format.
- ERA file status is TEST. Only PRODUCTION files can be processed.
- ERA file you are loading is invalid: GS06 and GE02 Functional Group Control Numbers are not equal.
- ERA file you are loading is invalid: ST02 and SE02 Transaction Set Control Numbers are not equal. You cannot post any payments or adjustments in the ERA file with fatal errors.
Associated pages
- About Electronic Remittance Advice (ERA)
- Electronic Remittance Advice (ERA) processing stages
- About Electronic Remittance Advice (ERA) processing logic
- ERA processing logic - claim level
- ERA processing logic - claim details level
- ERA Data tab
- ERA Data tab - Claim level
- ERA Data tab - Service lines
- ERA Data tab - Payments, adjustments, and denial adjustments
- ERA Data tab - Detail errors and warnings
- ERA File tab
- ERA detail errors and warnings
- About applying payments and adjustments in case of levels conflict
- Process ERA file
- ERA Troubleshooting steps
- About Remittance Advice report
- Remittance Advice report details
- Calculation logic for new balance on ERA report
