Processing Claims for Candid
Last updated: March 4, 2026
Canvas and Candid are building a streamlined API integration to replace the previous nightly CSV file process — moving from a 24-hour data exchange to real-time claim and payment sharing. This article covers how the integration works, how to move claims through the Submission Queue, and when to collect copayments.
Keep in mind: This integration has no impact on appointment creation, note creation, or locking a note. It only applies to claim processing after a claim moves from the Coding Queue to the Submission Queue.
What you'll learn:
What the Candid API integration includes
How to prepare a claim before moving it to the Submission Queue
How to move individual and batch claims
What automatic queue movement looks like after submission
How Canvas updates claims after Candid adjudicates
When to collect copayments in relation to Candid processing
Before You Begin
Make sure the following are in place before submitting claims to Candid
All organization, practice location, and provider addresses use a 9-digit zip+4 format — for example, 12345-6789
Each practice location has a Tax ID and billing address configured, or Bill Through Organization is enabled with a Tax ID at the organization level
Hold any claims you want to process through the Candid integration in the Coding Queue until the transition date
What's Included in This Integration
This integration focuses on real-time claim submission and payment sharing between Canvas and Candid. The goals are to enable Candid to file claims faster, provide real-time claim status updates within Canvas, and improve the overall flow of data between platforms.
The integration includes
Real-time claim submission: When a claim is moved to the Submission Queue, Canvas automatically sends it to Candid via API 60 seconds after the move. The 60-second delay gives users time to undo the action if it was accidental
Automatic queue movement: Candid moves the claim in Canvas to the appropriate queue based on whether the submission was successful or requires changes
Real-time claim status updates: Once Candid receives a claim, users can monitor its status directly in Canvas without needing to log into Candid
Finalized claim updates: When Candid finalizes a claim, Canvas retrieves the relevant changes and updates the claim to reflect its finalized state
Payment sharing: When a patient payment is collected in Canvas, that information is sent to Candid via API
Moving Claims to the Submission Queue
Before moving a claim, make sure all three of the following are true
The encounter has been completed
The note has been signed or locked
The claim has been reviewed in the Coding Queue to confirm all required information is included
If a claim has any claim checks, resolve those before moving it to the Submission Queue whenever possible.
Moving an individual claim
Navigate to the claim
In the upper right of the claim heading, locate the claim's current queue
Click the queue name to open the dropdown of all revenue queues
Select Submission Queue to complete the transfer
Batch moving claims
Navigate to the Coding Queue in the Revenue view
Apply any necessary filters to target specific claims — for example, claims for a specific provider
In the upper right, click Batch Actions to open the dropdown
Click Move claims to queue
Select Submission Queue — the claims will transfer immediately
Accidentally moved a claim? No worries — you have 60 seconds to undo it. An option to revert the move will appear immediately after moving a claim or batch of claims. Once that window closes, the claim will need to be worked from whichever queue it landed in.
What Happens After a Claim Reaches the Submission Queue
60 seconds after a claim lands in the Submission Queue, Canvas sends it to Candid via API. Candid then automatically moves the claim to one of two places
Filed Queue — Candid received all required information and has created an encounter. Claims here are actively being worked by Candid
Coding Queue — Candid was unable to process the claim due to missing or incorrect information. A comment will be added to the claim activity explaining what's needed, and a task may be created in Canvas to notify your team. Make the necessary changes and move the claim back to the Submission Queue when ready
The goal is for your Submission Queue to be at zero at the end of every day — giving your team a clear picture of what Candid is working on and what still needs attention.
Making changes to a filed claim
If a filed claim is returned to the Submission Queue after adjustments, Candid will return a 422 EncounterExternalIdUniquenessError. This happens because Candid already has the claim on file and can't accept a duplicate submission.
If changes are needed after a claim has been filed, make them directly with Candid. You can still update the claim in Canvas to keep your records aligned — just don't send it back through the Submission Queue.
How Canvas updates claims after Candid adjudicates
When Candid finalizes a claim, Canvas automatically retrieves the relevant changes from Candid and updates the claim to reflect its finalized state, including the claim queue.
Collecting Payments with Candid
Canvas supports both general payments and copayment collection through the Payment Collection workflow. When a payment is collected in Canvas, that information is automatically sent to Candid via API.
Collecting copayments for Candid? Wait until the claim has successfully landed in the Filed Queue before collecting. Collecting a copayment before that point may prevent it from linking to the correct Candid encounter.
General payments don't carry the same timing requirement, but following the same order is good practice. For step-by-step payment collection instructions, see Collect Patient Payments.
Next Steps
Confirm all organization, practice location, and provider addresses use a 9-digit zip+4 format before submitting claims to Candid
Monitor your Submission Queue daily and aim to end each day at zero
For any claims that return to the Coding Queue, review the claim activity for Candid's comments and resolve before resubmitting
Once claims reach the Filed Queue, Candid takes over — no action needed until they move to the Adjudicated Queue
Frequently Asked Questions
Understanding the integration
Q: Does the Candid integration change how I create appointments or document notes?
A: No. The Candid integration has no effect on appointment creation, note creation, or locking a note. Your clinical workflows are unchanged — this integration only applies after a claim moves to the Submission Queue.
Q: How is this different from the previous Candid process?
A: Previously, Canvas sent a nightly CSV file to Candid once every 24 hours. This integration replaces that process with a real-time API connection, enabling faster claim filing, real-time status updates in Canvas, and automatic payment sharing.
Q: Why does the Submission Queue need to be at zero at the end of the day?
A: The Submission Queue is a transit point, not a holding area. A claim sitting there means Candid hasn't confirmed it one way or the other. Keeping it at zero gives you a clear signal about where every claim stands.
Before you submit
Q: What zip code format is required for Candid submissions?
A: All addresses for your organization, practice locations, and providers must use a 9-digit zip+4 format — for example, 12345-6789. Claims with standard 5-digit zip codes may fail to submit to Candid.
Moving claims
Q: Can I move claims individually and in bulk?
A: Yes — both options are available. Individual claims can be moved from within the claim view, and multiple claims can be batch moved from the Revenue view in the Coding Queue.
Q: What should I do if I moved a claim to the Submission Queue by mistake?
A: You have 60 seconds to revert the move. Look for the undo option immediately after moving the claim. Once that window closes, address the claim from the queue it landed in.
Q: Should I resolve check notifications before moving a claim?
A: Yes, whenever possible. Resolving them before submission reduces the chance of a claim being returned to the Coding Queue. If you can't resolve a notification, you can still move the claim — just monitor the outcome closely.
After submission
Q: How do I know if a claim submitted to Candid successfully?
A: Within 60 seconds, Canvas sends the claim to Candid and the claim will automatically move to either the Filed Queue (success) or back to the Coding Queue (error). If it returns to Coding, check the claim activity for Candid's comments on what needs to be corrected.
Q: What is a 422 EncounterExternalIdUniquenessError and why am I seeing it?
A: This error appears when a claim that was already filed with Candid gets sent back through the Submission Queue after adjustments. Since Candid already has the claim on file, resubmitting it causes a conflict. Once a claim reaches the filed queue, it should not be removed. If changes are needed after a claim has been filed, make them directly with Candid. You can update the claim in Canvas to keep your records aligned — just avoid sending it back to submission.
Q: When does Canvas update a claim with Candid's data?
A: When Candid finalizes a claim, Canvas automatically retrieves the relevant changes and updates the claim — including the claim queue — to reflect its finalized state.
Collecting payments
Q: Can I collect a copayment before the claim reaches the Filed Queue?
A: It's not recommended if you want the copayment linked to the correct Candid encounter. Wait until the claim has successfully landed in the Filed Queue before collecting copayments.
Q: Does the timing recommendation apply to general payments too?
A: The requirement is specific to copayments that need to link to a Candid encounter. General payments don't carry the same dependency, though following the same order is good practice.
Related Articles
Keywords: Candid claim processing, Submission Queue, Canvas billing workflow, Candid API integration, filed queue, claim queue movement, copayment timing, zip+4
Categories: Revenue Cycle Management, Claims Management, Candid Integration
Roles: Billing Staff, Practice Managers, Revenue Cycle Teams