Partner onboarding
Getting Started
With an IDR Partner
Before the first claim changes hands, decide who sends the records, who acts on them, and how updates reach your billing team. This checklist covers the practical questions to work through with an IDR partner.
Decide who does what
Your billing team knows the provider and its claims. When you bring in independent dispute resolution (IDR) support, put the division of work in writing. Name the provider decision-maker, billing contact, dispute contact, and a backup for each.
Specify who can authorize work, communicate with payers, approve an offer or settlement, and receive notices. Settle the service scope and applicable agreements before sharing patient information. Clearest’s HIPAA notice explains the role of its business associate agreements; executed agreements govern the specific relationship.
Use these steps to prepare for a partnership discussion. The transfer method, responsibilities, and reporting arrangements will depend on your organization.
Work out how records will move
List the records your team can supply: claim details, complete explanations of benefits, payment or denial notices, relevant plan information, and prior correspondence. Identify where each record lives and who can retrieve it.
- Choose the approved secure channel and name the people permitted to use it.
- Set file types, naming conventions, and a stable claim reference.
- Specify how corrections replace earlier versions without losing the history.
- Decide how receipt is acknowledged, missing files are requested, access is removed, and records are retained.
A discussion about onboarding does not require patient records. Use the contact form to arrange a conversation, then establish the secure channel before transferring claim information. Do not assume an API or an automatic connection to your billing system is available.
Try the handoff with a small sample
- Prepare: collect the agreed records and match them to claim lines.
- Review: check completeness, permission, and the applicable dispute route.
- Resolve: return missing information to a named owner.
- Acknowledge: record which items were accepted for further work.
Choose a limited sample that exposes the variations your team actually sees, such as multiple service lines, corrected remittances, or records spread across systems. Do not delay time-sensitive cases while waiting for a sample exercise. A file arriving successfully does not establish IDR eligibility or mean a dispute has been filed.
Walk through our invented handoff example with a corrected remittance and missing plan information. Use the blank document inventory to track versions, missing records, and owners in your own approved system.
Agree what each handoff status means
These suggested labels separate transfer, review, and filing. Agree on your own definitions and supporting records before using them in reports. They are not Clearest product statuses or commitments.
| Label | What it records | Supporting record |
|---|---|---|
| Received | The agreed destination has received the files. | Transfer acknowledgment and document inventory. |
| Awaiting information | A named question or missing record remains open. | Exception, affected reference, owner, and next action. |
| Accepted for review | The receiving team has agreed to undertake the defined review. Eligibility and filing remain separate. | Reviewer’s acknowledgment and scope of acceptance. |
| Filed or submitted | A filing has actually been submitted through the applicable process. It is not a determination or payment. | Submission confirmation and reference, retained by the filing owner. |
Give every exception an owner
When information is missing, note what is needed, who will retrieve it, and when it is due. Distinguish an internal response target from a regulatory deadline. A handoff between teams does not itself extend the time available.
Assign someone to verify the governing dates and monitor notices. The CMS process overview describes the federal sequence and extensions; your team must assess the applicable route and current requirements for each dispute.
What if a corrected record arrives after handoff?
Send the affected internal reference, the new version reference, and an explanation of what changed through the agreed channel. Keep the earlier version available. Ask the receiving reviewer to acknowledge the correction and identify any payment, eligibility, or filing work that needs rechecking.
What if an urgent notice arrives while a record is incomplete?
Notify the person responsible for the dispute dates and the agreed backup through the urgent-notice channel. Identify the actual notice and unresolved record separately. That person must assess the required action using the applicable instructions; an internal “awaiting information” status does not grant more time.
Handoff examples and status questions added . CMS document and communication guidance checked for these additions on that date.
Plan for status updates and payments
| Decision | What to decide |
|---|---|
| Status | Definitions for received, awaiting information, filed, determined, and paid. |
| Cadence | When updates arrive and how urgent notices reach a backup contact. |
| Payment posting | Who matches funds and remittances to the provider’s ledger. |
| Costs | Who funds fees, receives refunds, and reconciles service invoices. |
Check that both teams can keep it running
Before making the handoff routine, walk through a complete record, an incomplete one, an urgent notice, and a payment with both teams. Write down the contacts, update schedule, and escalation path. Test what happens when the usual person is away.
For the broader service scope, see IDR support for billing and RCM companies. A partnership discussion can establish which parts of this checklist fit your current systems and client agreements.
YOUR NEXT STEP
Need IDR support
for your clients?
Talk through your clients, billing workflow, and partnership requirements.
Discuss an IDR partnershipContent and sources reviewed .
