CAQH Document Expiration: Prevent a Complete Profile From Becoming Unusable
Prevent a CAQH profile from becoming unusable because a license, malpractice certificate, DEA record, or other supporting document expired while the narrative profile stayed accurate.
CAQH maintenance often fails in the document layer, not the data-entry layer. A clinician’s name, work history, locations, and specialty can remain perfectly accurate while a required license or malpractice document expires. When that happens, an authorized payer looking for a current credentialing record may encounter an incomplete or stale file even though staff believe “CAQH is done.” Treat every uploaded document as a dated asset with an owner, effective date, expiration date, replacement lead time, and verification status. The maintenance calendar should generate work before expiration, and the coordinator should confirm the replacement is actually accepted in the profile. Re-attestation and document renewal are related but not identical clocks; a document can expire between attestation dates.
Inventory CAQH documents by expiration date instead of by filename alone
CAQH profiles rely on supporting documents whose effective and expiration dates can differ from the attestation cycle.
A profile can require document replacement even when no demographic field changed.
Document quality matters: the uploaded file should be current, legible, and clearly tied to the provider.
Build a document table with provider, document type, issuing jurisdiction or carrier, issue/effective date, expiration date, current filename, CAQH status, and internal owner. Common entries can include professional licenses, malpractice coverage, DEA or controlled-substance credentials where applicable, certifications, W-9/authorization forms when requested, and other documents shown as required in the provider profile. Avoid a shared drive containing “license.pdf” with no date context. A reviewer should be able to tell which version is current without opening five scans. Include a link to the authoritative source or internal renewal record when useful.
Order replacement work by lead time and credentialing impact
Updating the document and then completing the required attestation step helps ensure changes are reflected in the credentialing record.
Payers may still request additional primary-source evidence outside CAQH.
A credentialing profile is a set of claims supported by evidence. Monitor the evidence expiration dates, not only the portal’s attestation countdown.
Not every document needs the same lead time. A malpractice certificate may arrive automatically at renewal, while a professional license or controlled-substance credential can require earlier action. Add a preparation date based on real renewal behavior. Flag documents that will expire during an active payer credentialing case; a payer may ask for the renewed version before final review. If the issuing authority is delayed, record the renewal submission or other allowed evidence but do not invent validity beyond the official expiration. Escalate clinical-operational risks, such as a license nearing expiration, outside the credentialing calendar as appropriate.
Upload the renewed document and verify its platform status
After renewal, upload the replacement and check that CAQH recognizes it correctly. A successful browser upload is not the same as a document being processed and available as intended. Verify the profile’s document status and associate the correct dates. If the file is unreadable, cropped, password-protected, or assigned to the wrong category, replace it promptly. Save the renewed document in the internal source packet first so the practice retains a copy even if access to the portal changes later. Update the maintenance table with the upload and verification date.
Re-attest when profile changes require authorized organizations to see the update
Treating “attested” as meaning every document is current. When this happens, correct the source record first and then update the downstream copies that are actually affected.
Uploading a new certificate but leaving the old policy dates in the profile. Do not bury this under a generic “pending” label. Name the blocker, the owner, and the next action.
Storing documents with unclear filenames and no expiration metadata. A copied prior application is especially risky here because an old file can be internally consistent and still be wrong for the current facts.
Waiting for a payer deficiency letter instead of monitoring expirations. The safe response is to stop the handoff until the source evidence and submitted answer tell the same story.
If renewing the document required changing profile data—such as a license number, state, coverage details, or other substantive field—complete the appropriate review and re-attestation so authorized organizations can receive the updated profile information under CAQH workflow. Do not wait for the next routine attestation when a material change needs to be visible sooner. Conversely, do not click attestation as a substitute for uploading the renewed evidence. The data and document layers both need to be current. Keep the attestation history and the document history as related but distinct records.
Keep old versions for historical claims and credentialing questions
Document register: Tie the document to the specific field or decision it supports.
Current uploaded file: Record where it came from and when someone verified it.
Profile field/date: Preserve the prior version when an effective-date sequence could matter in a later review.
Attestation confirmation: Keep the current version and enough history to show when it changed.
Prior-version archive: Use a filename that includes the provider or entity, document type, and the date that matters.
Retain prior versions internally with their valid periods. Historical payer reviews, claims, audits, or malpractice questions may concern a date when the previous license or policy was the correct evidence. Replacing the current file should not erase that history. Use a naming convention such as document type plus effective/expiration date and move superseded files to an archive folder rather than deleting them. This also helps explain apparent differences in old submitted payer packets: the office can show that the attachment was current on the submission date even though a newer document exists today.
Use document maintenance to trigger payer-specific updates when needed
Some document renewals trigger more than a CAQH upload. A new malpractice carrier, changed DEA address, updated license status, or specialty certification may need direct notification to certain payers, Medicare, or internal billing/compliance systems. The maintenance record should therefore include a “downstream actions” field. When the replacement arrives, the coordinator checks the payer-specific SOPs and opens the necessary changes. CAQH remains a shared source, but the office should not assume every authorized organization automatically consumes every update on the timetable the practice needs.
Operational checklist
- Create a document register with issue date, expiration date, and profile field supported.
- Set reminders ahead of high-risk expirations such as licenses and liability coverage.
- Replace the document and update associated profile dates together.
- Re-attest when required so the revised information is finalized.
- Confirm the new file is visible in the portal.
- Keep the prior version in the internal archive with clear effective dates.
Frequently asked questions
Can a CAQH profile become a problem even if all the entered data is accurate?
Yes. Required supporting documents can expire or be rejected while narrative data remains correct. Track document status and expiration separately from profile data accuracy.
Should document renewals wait for the next CAQH re-attestation?
No. Replace expiring documents when they renew and update any related profile data promptly. Complete re-attestation as required so authorized organizations can see relevant updated information.
Should old licenses or malpractice certificates be deleted after renewal?
Keep prior versions in the internal archive with their valid periods. They can be important for proving what was current on a historical application or date of service, even though CAQH should display the current evidence.