Section 1: Portal Setup & User Management
Most Availity problems start at setup. Incorrect registrations, misassigned roles, and orphaned user accounts create downstream issues that look like payer problems but are actually configuration problems. Get this right first.
Organization Registration Checklist
- Verify NPI and Tax ID accuracy: Availity validates against NPPES. If your NPI or Tax ID doesn't match what's on file, payer connections will fail silently. Verify both at npiregistry.cms.hhs.gov before registering.
- Register one organization per Tax ID: Multi-location practices should register the parent organization, then add service locations underneath — not separate organizations for each location. Duplicate registrations cause claim routing issues.
- Designate at least 2 administrators: If your sole admin leaves, you're locked out of user management. Always have a backup admin with full access.
- Enable multi-factor authentication (MFA): Required for HIPAA compliance and increasingly required by payers for portal access. Set it up at registration, not after a security incident.
- Complete payer enrollment for every active payer: Registration alone doesn't connect you to payers. You must complete the EDI enrollment process for each payer you want to transact with. This is the step most new users miss.
Role-Based Access Best Practices
Availity uses role-based access control. Assign roles intentionally — not everyone needs admin access, and front-desk staff don't need claims management tools.
| Role | Suggested Users | Access Level |
|---|---|---|
| Administrator | Office manager, billing manager | Full access: user management, payer enrollment, all transactions |
| Claims User | Billers, coders | Claim submission, claim status, remittance viewing |
| Eligibility User | Front desk, patient access | Eligibility verification, coverage detection, member ID lookup |
| Auth User | Auth coordinators, clinical staff | Prior authorization submission, status tracking, auth dashboard |
Run a user access audit every quarter. Deactivate accounts for staff who have left. Verify role assignments match current job functions. Orphaned admin accounts are a HIPAA risk and a security vulnerability.
Section 2: Eligibility Verification Workflow
Eligibility is the highest-volume transaction on Availity and the one with the biggest downstream impact. A missed coverage detail at check-in becomes a denial 30 days later. Here's how to build an eligibility workflow that catches problems before they become claims issues.
Standard Eligibility Check Protocol
- Run eligibility 48 hours before the appointment. Not at check-in — 48 hours before. This gives you time to resolve coverage issues, obtain prior auths, and contact the patient about financial responsibility. Check-in eligibility checks catch problems too late to fix them.
- Verify all active coverages, not just primary. Availity's Coverage Locator can identify coverages the patient may not have disclosed. Run it for every patient, every visit — coverage changes more frequently than patients report.
- Check specific benefits for the scheduled service. "Active coverage" doesn't mean "covered for this service." Drill into the benefit detail for the specific CPT codes you're planning to bill. Look for: copay/coinsurance amounts, deductible status, out-of-pocket max progress, and any service-specific limitations.
- Document the eligibility response. Save or print the eligibility response and attach it to the patient account. If a payer later denies for eligibility, your documented verification is your appeal evidence.
- Flag patients with coverage changes. Create a workflow to flag accounts where coverage has changed since the last visit — new plan, new group number, new effective date. These accounts need manual review before the claim goes out.
Availity shows "Active" coverage but doesn't always surface benefit exclusions or service-specific limitations in the summary view. You must click into the detail response to see plan-specific restrictions. "Active" ≠ "Covered for your service." Train staff to always check the benefit detail, not just the coverage status.
Self-Pay Eligibility Screening
For patients presenting as self-pay, run Availity's self-pay eligibility check before accepting the self-pay classification. The tool searches across payers for active coverage the patient may not have disclosed. This recovers billable coverage in an estimated 5-15% of self-pay encounters — revenue that would otherwise be written off or sent to a lower reimbursement rate.
Section 3: Claim Status Automation
Manually checking claim status is the biggest time waste in most billing offices. Here's how to minimize it.
Auto-Status Configuration
If you're on Essentials Pro, configure automated claim status checks. The system will pull status updates on a scheduled basis and flag claims that need attention — adjudicated, denied, pending, or in review. This eliminates the "log in and check each claim" workflow that consumes hours of staff time daily.
Claim Status Escalation Protocol
| Days Since Submission | Status | Action |
|---|---|---|
| 0-14 days | Pending / In Process | No action. Normal processing timeframe for most payers. |
| 15-21 days | No status update | Run manual claim status check in Availity. Verify claim was received (check for submission errors). If no record at payer, resubmit. |
| 22-30 days | Still pending | Check for payer-specific processing delays. Document status check. Set follow-up reminder for day 35. |
| 30+ days | No adjudication | Escalate. Call payer directly. Document call reference number in Availity notes. Start timely filing protection documentation. |
| Approaching timely filing limit | Any non-final status | URGENT: Resubmit claim with proof of original timely submission. File appeal preemptively if nearing deadline. |
Every claim status check in Availity is timestamped and logged. Use these logs as evidence of timely filing if a payer claims late submission. Screenshot or export status check results for claims approaching filing deadlines. This is your insurance policy against "we never received it" denials.
Section 4: Prior Authorization Optimization
Prior auth is where the most staff time gets burned. These tactics reduce turnaround time and approval rates.
Before You Submit: Auth Requirement Check
Don't assume auth is required — verify first. Availity's portal lets you check whether a specific payer requires prior authorization for a given procedure. Running this check before submitting saves time on unnecessary auth requests and prevents delays when auth IS required but you assumed it wasn't.
Submission Best Practices
- Submit electronically through Availity whenever possible. Electronic submissions are tracked, timestamped, and visible in the auth dashboard. Fax submissions create black holes — no status tracking, no timestamp proof, no audit trail.
- Attach clinical documentation at submission. Don't wait for a payer request. Proactively include: relevant clinical notes, diagnostic results, treatment history, and medical necessity justification. Claims with complete clinical documentation at initial submission get approved 2-3× faster than those requiring additional information requests.
- Use the auth dashboard daily. Check pending authorizations every morning. Payers may request additional info and set short response deadlines (often 5-7 business days). Missing a request window means starting over.
- Track auth numbers religiously. When an auth is approved, document the auth number, effective dates, approved units/visits, and any conditions. Map auth numbers to scheduled services in your PM system. An approved auth with the wrong number on the claim is the same as no auth.
Prior authorizations have expiration dates. A 90-day auth approved in January expires in April. If the service gets rescheduled past the expiration date, the auth is void. Build an auth expiration tracking workflow — check all outstanding auths weekly and flag any expiring within 14 days.
Section 5: Common Availity Errors & Resolution
These are the 12 errors that generate the most support calls and the most wasted staff time. Know the fix before you hit the wall.
| # | Error / Issue | Root Cause | Resolution |
|---|---|---|---|
| 1 | Payer not found in eligibility | Payer not enrolled in your Availity organization, or using wrong payer ID | Check payer enrollment status. Complete EDI enrollment if missing. Verify payer ID matches Availity's payer list. |
| 2 | Patient not found / no match | Subscriber ID, DOB, or name doesn't match payer records | Verify member ID from insurance card. Try searching by SSN if available. Check for name spelling variations (maiden name, hyphenated). |
| 3 | Claim rejected — invalid NPI | Billing or rendering NPI not enrolled with payer | Verify NPI enrollment status with the specific payer. Different from Availity enrollment — payer must recognize the NPI independently. |
| 4 | Claim rejected — invalid taxonomy code | Provider taxonomy on claim doesn't match payer's credentialed taxonomy | Verify taxonomy code in NPPES matches what the payer has on file. Update in Availity claim template if needed. |
| 5 | ERA/835 not posting | Remittance enrollment incomplete or EFT/ERA not linked | Verify ERA enrollment for each payer. Ensure EFT and ERA are linked (some payers require separate enrollment for each). |
| 6 | "AAA" rejection on eligibility | Payer system returned an error — could be system outage, invalid request format, or payer downtime | Wait 15 minutes and retry. If persistent, check Availity's system status page. Contact payer directly if the issue is payer-side. |
| 7 | Claim shows "Accepted" but no adjudication | Claim accepted by clearinghouse but not yet processed by payer | "Accepted" means Availity received it. Check claim status after 7-10 business days to verify payer receipt and processing. |
| 8 | Prior auth submission fails | Payer doesn't accept electronic auth through Availity, or missing required fields | Verify payer supports electronic auth via Availity. Check all required fields — diagnosis codes, procedure codes, place of service, requesting provider NPI. |
| 9 | Duplicate claim rejection | Claim with same patient/DOS/CPT already on file at payer | Check claim status on original submission. If original was denied, correct and resubmit with frequency code 7 (replacement) or 8 (void). |
| 10 | User locked out | Too many failed login attempts or MFA issues | Organization admin can unlock the account. If admin is locked out, contact Availity support. Prevent with password manager adoption. |
| 11 | Secondary claim rejected | Primary payer EOB data not correctly attached to secondary submission | Attach the primary 835/EOB to the secondary claim. Ensure coordination of benefits fields are correctly populated. |
| 12 | Claim attachment not received by payer | Attachment submitted but not linked to claim, or wrong attachment type | Verify attachment was linked to correct claim number. Check payer's accepted attachment types (PDF, TIFF, etc.). Resubmit with correct reference number. |
Weekly Availity Optimization Checklist
Run through this every Monday morning. It takes 20 minutes and prevents 80% of the week's avoidable issues.
- Check Availity system status: Any payer connections down? Scheduled maintenance windows this week?
- Review pending prior authorizations: Any expiring this week? Any requiring additional documentation?
- Audit unpaid claims 30+ days: Run claim status on all unpaid claims over 30 days. Flag for escalation.
- Check for unworked claim rejections: Any rejected claims from last week that haven't been corrected and resubmitted?
- Verify ERA/835 processing: Are all expected remittance files posting? Any missing ERAs from last week's payments?
- Review eligibility check failures: Any patients scheduled this week with failed eligibility checks? Resolve before the appointment.
- Check user access: Any new hires needing Availity access? Any departures needing account deactivation?
- Review denial trends: Are you seeing increased denials from any specific payer this week? Flag for root cause analysis.