Billing Report: Batch Report Errors (Post-Transmission) (CMD)

The following errors can be received on the individual batch when transmitting charges to CollaborateMD. These errors appear in the place of the Claim ID and indicate the charge was not transmitted to CMD.

Error Message	Resolution	Error Source
Error: CMD Message - Unable to locate rendering provider.	This happens when the Rendering provider option is chosen and the provider does not exist in CMD.  Validate the Provider was created (added) in CMD before the claim was transmitted.  This can also occur if the konnector is not configured properly.	CMD
No valid charges found for the claim, updated patient	This issue occurs when the CPT code doesn't exist in your CMD customer setup. The CPT code for one or more charges on this claim is missing. As a result, the applicable charge(s) have not been added to this claim. Please confirm this is correct. Steps to Resolve: Add the missing code(s) in CMD: Ensure that the CPT/HCPC codes meet the 10 character limit (including spaces). Example: "H0011 AJ HF" should be "H0011AJ HF." Review codes linked to the LOC or template to confirm that they are unaffected. Update as needed. Delete error claims from the batch: Note: Deleting the batch will remove both successful and unsuccessful claims. Check out this article for instructions. Confirm changes: If the template was billable and ancillary, changes apply moving forward as codes must be selected when added to the facesheet. Click here to learn more about billable and ancillary templates. If the update involves the LOC, allow up to 5 minutes for changes to take effect. Retransmit the updated batch to CMD	CMD
Unable to create claim. The date of service of charge (XXXC-XX-XX) is on or before the hard close date (XXXX-XX-XX).	The client is using CollaborateMD’s Hard Close feature and they are trying to enter a claim that has a date of service that is on or before the Hard Close Date. To fix this issue, the client must disable the feature temporarily or modify the Hard Close Date in CMD to create the claim. Once this is modified in CMD, they should delete the batch in Kipu and transmit the charges to CollaborateMD. Once the charges have been entered, they can reactivate the feature or modify the date to their liking.	CMD
Error: CMD Message - Only 50 charges are supported. The claim will not be created	This occurs due to the limit of 50 charges transmitted from KIPU to CollaborateMD which occurs due to the charge panel set up within CollaborateMD. If the charge panel within CollaborateMD contains 2 or more procedure codes, you can multiply that amount by the total number of entries being transmitted from KIPU. For example: 29 entries transmitted from KIPU multiplied by 2 procedure codes within the charge panel equals 58 total charges which is not allowed. To resolve: Please be mindful when transmitting charges with a charge panel code on KIPU. If that number multiplied by the number of codes within the charge panel exceeds 50, then you will need to scale back from transmitting to make sure the total amount equals 50.	CMD
CollaborateMD Error: Exception Error: undefined method `first' for nil:NilClass	This occurs for a few reasons: Your CMD account is on an older version of the WebAPI. CMD Interface is not set up. Please email [e-mail] to resolve.	CMD
Error: CMD Message - The interface is not turned on for this customer.	This error means the CMD Interface is not active. To resolve the issue, log into CMD and verify that the interface is active by clicking on Interface > Settings > WebAPI > Active. If if it is not, a new Konnector is needed. Please complete the CMD Add Konnector Request form found here. If the Konnector says it is active, please contact support at [e-mail].	CMD
Failed.	A batch can fail for any of the following reasons: The information in the Konnector is incorrect. Please review the data entered on the Konnector to confirm that everything entered is correct. The interface is not activated in CMD. Please email [e-mail] for help resolving this error.	Kipu EMR
Konnector not found.	This generally occurs when the CMD Konnector is not enabled or there is no Konnector that matches the Location and/or Program of the Patient. To resolve: Review the patient facesheet to determine which Konnector being used to transmit the data. This appears in the External App Name field. Locate the Konnector in Settings > Integrations and validate that the configuration is correct. If the configuration is correct, validate that the Konnector is enabled (Use this vendor is checked). If disabled, enable and click Update. If there is no External App Name in the patient facesheet, note the Location and Program. Review each Konnector until the Konnector is found that is configured to match the Location and Program If found, validate that the Konnector is enabled (Use this vendor is checked). If disabled, enable and click Update. If not found, this explains the error, and a new Konnector is needed. Please complete the CMD Add Konnector Request form.	Kipu EMR
Pending: CMD Message - Failed to receive response from CollaborateMD.	This error occurs when Kipu has not received a response from CollaborateMD. Please email [e-mail] to resolve.	CMD
Error: CMD Message - Your credentials do not have access to the requested customer.	This error typically occurs when the WebAPI isn’t selected as Kipu. Validate that the konnector information is an exact match to your CMD account following these instructions. If yes the konnector matches, confirm that the Interface is active in CMD. Navigate to Interface > Settings > Edit. Make sure that the Interface Status drop-down is set to Active. Finally, confirm that Kipu is the vendor associated to this WebAPI interface.  Save your changes. If the vendor is not selected or the interface is inactive please contact Billing Support.	CMD