Errors prevent Charge creation and Create Bills processes from moving on to the next step. Processing errors place the Service in a HOLD status, no charges create, and the Service does not move to a claim file. Create Bills errors place the Charge in a HOLD status and prevent bill creation for that Charge. Corrections are required before for Charge or Bill creation can occur. Use the keyboard combination CTRL-F to search for a specific error within this page.
Code |
Description |
Severity |
Notes |
1001 |
There was an unexpected error processing this service |
ERROR |
|
1002 |
This service is not part of the job |
ERROR |
|
1004 |
State Report Error: |
ERROR |
|
1006 |
AddOn service put on hold due to errors processing its associated parent service. |
ERROR |
Holding the AddOn due to issues with the Parent Service keeps both in sync and prevents the Charge Creation and billing of an AddOn without the required Parent Service. |
1100 |
Charge Strategy cannot be configured with zero minutes per unit |
ERROR |
Verify the Charge Strategy (unit and rate calculations) in Configuration > Services/Payers > Service Definitions > Rates or in Configuration > Services/Payers > Payers > Rates if a Payer Rate override exists. The minutes per unit cannot be zero. |
1101 |
Charge strategy unit ranges do not fit the duration of this service |
ERROR |
The system cannot determine what to charge because the unit ranges do not fit the duration of the Service. Navigate to Configuration > Services/Payers > Service Definitions > Rates to review the unit durations set up for the Service. Also, review Configuration > Services/Payers > Payers > Rates to see if there is an override of the Service Definition default rate for the Payer. Review the Service entry to ensure the duration entered is correct. |
1102 |
No Charge Strategies exist for this Payer |
ERROR |
There is no rate for this Service at the Service Definition or Payer Level. Review Configuration > Services/Payers > Service Definitions > Rates, and review Configuration > Services/Payers > Payers > Rates for the Service provided. If a rate exists, verify that the active dates for the charge strategy encompass the date of Service. |
1107 |
There is no rate that fits this service, payer, and staff |
ERROR |
There is no rate for this Service at the Service Definition or Payer Level that includes the staff member’s credentials. Review the Credential rate settings in Configuration > Services/Payers > Service Definitions > Rates and in Payers > Rates. |
1108 |
No Charge Strategies exist for this Service |
ERROR |
There are no rates for the Service. Navigate to Configuration > Services/Payers > Service Definitions > Rates and ensure the Service has a base rate. Then verify that the Payers > Rates either uses the default Service Definition rate or has rate configured in the Payer rate override for the Service. |
1202 |
Service or bundle on hold due to invalid credentials |
ERROR |
The Service is on hold due to invalid credentials. The staff member does not have the correct credentials to bill this Payer. To view the credentials setup for the Payer, navigate to Configuration > Services/Payers > Payers > Processing, ensure that the staff’s credential is listed, or Bill for Any Staff Credential displays. |
1300 |
No Payers exist for this Client and Service Definition |
ERROR |
Payers either do not exist, or the effective dates do not cover the date of Service. Navigate to Clients > Payers to review. |
1303 |
No Charge could be created for this Client and Service Definition |
ERROR |
This error is most likely due to a configuration or effective date issue. Begin by reviewing the Clients > Payers setup and dates. Then review Configuration > Services/Payers > Service Definitions > Profile, Components, and Rates. Look for discrepancies and date range conflicts. |
1400 |
Unexpected error, no diagnoses were found for this service |
ERROR |
No diagnoses were found and may be due to effective dates or Diagnosis not entered. Review Clients > Diagnosis screen. |
1401 |
Service or bundle on hold due to invalid diagnoses |
ERROR |
The Service or bundle is on hold due to invalid diagnoses. To view diagnosis setup, navigate to Configuration > Services/Payers > Payers > Processing > Diagnosis (either “Bill for Any Diagnosis” or “Do Not Bill for These Diagnosis”). Check for Payer limitations on Diagnosis and compare against the Diagnosis selected for the Service. If the information under Payers is correct, review the setup and effective dates for Diagnosis on the Client Chart by navigating to Clients > Diagnosis. |
1500 |
Service is on hold due to processing issue(s) in the bundle |
ERROR |
The Service is on hold because of issues with the bundle. Navigate to Configuration > Services/Payers > Service Definitions, select the Service Definitions, and then review the Profile tab. This is a generic error and often accompanies code 1502. It can also be caused by a Service Definition being included in more than one bundle. |
1501 |
Service is on hold due to processing issues |
ERROR |
|
1502 |
Services do not meet the minimum requirements to bundle |
ERROR |
Individual Services may have a minimum to bundle requirement. In addition, the bundle may have a minimum number of all aggregated Services requirement. Review the bundle requirements in Configuration > Services/Payers > Service Definitions. |
1504 |
Could not find the billed bundled service |
ERROR |
|
1609 |
Service is on hold for authorization |
ERROR |
View Client Payer authorization information in Clients > Payers. |
1700 |
Service cannot be reprocessed or voided because it is currently in another job that has not been finalized |
ERROR |
This error means the Service is batched in another job and that job must be finalized (or reversed) before proceeding. |
1701 |
Service cannot be reprocessed for last active payer because those charges are not active |
ERROR |
Charge Status must be ACTIVE for the Service to be included in a Reprocess last active payer job. |
2000 |
No charge for payment remittance |
ERROR |
|
2001 |
Remittance is on hold due to processing issues |
ERROR |
|
2002 |
No charge for adjustment remittance |
ERROR |
|
2005 |
Remittance associated with reversed charge |
ERROR |
This error is a result of a Charge being reprocessed before the Remittance associated with that Charge is included in a Process Transactions job. To resolve,
|
3000 |
Missing a non-alias name for client |
ERROR |
The Client is missing a First or Last Name. Review by navigating to Clients > Profile. |
3001 |
Missing a billing address for client |
ERROR |
The Client does not have an address entered in Clients > Contact Info > Edit Client Contact Info with a YES in the Billing column of the address grid. |
3002 |
Missing configuration for payer |
ERROR |
Review in Configuration > Services/Payers > Payers. |
3003 |
Missing organization for charge |
ERROR |
Review in Configuration > Setup > Organizations. |
3004 |
Missing organization NPI |
ERROR |
Review in Configuration > Setup > Organizations. |
3005 |
Missing organization EIN |
ERROR |
Review in Configuration > Setup > Organizations. |
3006 |
Missing organization zip code extension |
ERROR |
Review in Configuration > Setup > Organizations. |
3007 |
Missing payer claim filing indicator |
ERROR |
Review in Configuration > Services/Payers > Payers > Profile 837 Claim Filing Indicator drop-down list. |
3008 |
Missing client payer policy number |
ERROR |
Review in Clients > Profile. |
3009 |
Missing client gender |
ERROR |
Review in Clients > Profile. |
3010 |
Missing payer ID |
ERROR |
Review in Configuration > Services/Payers > Payers > Profile 837 Payer ID field. |
3013 |
Client gender is invalid |
ERROR |
Review in Clients > Profile. |
3014 |
Add-on service charge requires the parent service charge be in the same billing job |
ERROR |
Add-on Services will only create charges if the Parent Service is in the same job. This may require reversing the current job to get the Parent and Add-on in the same job. If the Parent Service was processed through Charge Creation AND finalized, it will need to be reprocessed from the Claims menu to resolve the error. |
3015 |
Missing 837 payer ID for an other payer |
ERROR |
Review in Configuration > Services/Payers > Payers > Profile 837 Payer ID field. |
3016 |
Missing claim filing indicator for an other payer |
ERROR |
Review in Configuration > Services/Payers > Payers > Profile 837 Claim Filing Indicator drop-down list. |
3017 |
Missing subscriber for an other payer |
ERROR |
Review in Clients > Payers. If Client is Policy Holder checkbox is not selected, the Policy Holder section must be completed. |
3018 |
Missing client payer subscriber |
ERROR |
Review in Clients > Payers. If Client is Policy Holder checkbox is not selected, the Policy Holder section must be completed. |
3019 |
Missing subscriber policy number for an other payer |
ERROR |
Review in Clients > Payers. |
4000 |
Missing a non-alias name for client |
ERROR |
Review in Clients > Profile. Either the Client’s First or Last Name is missing. |
4001 |
Missing organization for charge |
ERROR |
Review in Configuration > Setup > Organizations. |
4002 |
Missing client payer policy number |
ERROR |
Review in Clients > Payers. |
4003 |
Missing organization place of service |
ERROR |
Review in Configuration > Setup > Organizations. |
4004 |
Missing organization address |
ERROR |
Review in Configuration > Setup > Organizations. |
4005 |
Missing CMS1500 configuration for payer |
ERROR |
Review in Configuration > Services/Payers > Payers > Billing Methods CMS1500. |
6000 |
Could not locate GL mapping for transaction code |
ERROR |
Review in Configuration > Setup > GL Mapping > Account Code tab. A default mapping is either not configured or active OR a mapping for the Payer is not configured or active. |
6001 |
Could not locate GL mapping for segment one |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 1 tab. A default mapping for Segment 1 is not configured or active OR the Service does not match on the configured Components for an active Segment 1 mapping. |
6002 |
Could not locate GL mapping for segment two |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 2 tab. A default mapping for Segment 2 is not configured or active OR the Service does not match on the configured Components for an active Segment 2 mapping. |
6003 |
Could not locate GL mapping for segment three |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 3 tab. The Segment is enabled and a default mapping for Segment 3 is not configured or active OR the Service does not match on the configured Components for an active Segment 3 mapping. |
6004 |
Found more than one GL mapping for transaction code |
ERROR |
Review in Configuration > Setup > GL Mapping > Account Code tab. |
6005 |
Found more than one GL mapping for segment one |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 1 tab, especially Components list. |
6006 |
Found more than one GL mapping for segment two |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 2 tab, especially Components list. |
6007 |
Found more than one GL mapping for segment three |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 3 tab, especially Components list. |
6008 |
Unable to map this transaction to its GL accounts |
ERROR |
Review in Configuration > Setup > GL Mapping. |
6011 |
Could not locate GL mapping for segment four |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 4 tab. The Segment is enabled and there is no default or active mapping OR the Service does not match on the configured Components for an active Segment 4 mapping. |
6012 |
Found more than one GL mapping for segment four |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 4 tab, especially Components list. |
6014 |
Could not locate GL mapping for client payment default account |
ERROR |
Review in Configuration > Setup > GL Mapping > Segment 1 & Segment 2 tabs. If Client Payments are accepted, the Unapplied Defaults must be configured for Segment 1 and Segment 2. |
6015 |
Found more than one default GL mapping |
ERROR |
Review in Configuration > Setup > GL Mapping. The Account Code has a Default mapping and Segments 1 & 2 have the Unapplied Default mappings. |
6016 |
No active self pay payer found to post the client payment |
ERROR |
This error is the result of a Client Payment being posted in Clients > Account when there is no active Self Pay Payer. Adding a Self Pay Payer or correcting the active dates resolves this error for the GL Posting. In order for the Client Payments to properly be associated with a Charge, the Charge must be reprocessed in the Claims Management menu. A payment may need to be applied to trigger the waterfall to Self Pay. |
7000 |
The 837 Configuration is missing a default bill type |
ERROR |
|
7001 |
Missing address for payer |
ERROR |
Review in Configuration > Services/Payers > Payers > Communications. |
8000 |
Missing a non-alias name for client |
ERROR |
Review in Clients > Profile. |
8001 |
Missing organization for charge |
ERROR |
Review in Configuration > Setup > Organizations. |
8002 |
Missing client payer policy number |
ERROR |
Review in Clients > Payers. |
8003 |
Missing organization address |
ERROR |
Review in Configuration > Setup > Organizations. |
8004 |
Missing UB04 configuration for payer |
ERROR |
Review in Configuration > Services/Payers > Payers > Billing Methods. |
8006 |
Missing client gender |
ERROR |
Review in Clients > Profile. |
8007 |
Missing a billing address for client |
ERROR |
Review in Clients > Contact Info. |
8008 |
Missing revenue code |
ERROR |
Review in Configuration > Services/Payers > Payers or Service Definitions > Rates. The Revenue Code is located beneath the Billing Code drop-down. |