What to Prepare Before Requesting a Billing or A/R Assessment

Useful starting information

An initial assessment is more productive when the team can share:

• Specialty and primary service lines.
• Approximate monthly claim volume or high-level A/R aging summary.
• Primary payers and known pain points (denials, aged balances, authorization delays).
• Current billing platform and any access constraints.
• Whether the need is ongoing billing support, a project-style A/R review, or transition help.

What to avoid on the public form

Do not include patient names, insurance IDs, medical records or detailed claim-level PHI. Aggregate summaries and process descriptions are sufficient for the first conversation. Sensitive records move only through an approved secure channel after engagement and authorization.

Expected next step

A scoped discussion clarifies system access, security boundaries, deliverables and reporting before any production work begins. No outcomes are guaranteed.

Contact page with service context: Request an assessment.

A practical initial data packet that does not expose patient records

An initial discovery conversation can begin with an aggregated A/R aging report, approximate monthly claim volume, payer distribution, service mix and a ranked list of operational obstacles. Include system names and constraints on vendor access, without sharing logins, unredacted medical records or patient identifiers.

Distinguish payer rejections, denied adjudications, contractual underpayments, patient-responsibility balances and pending claims. Each requires a different analysis; an undifferentiated “uncollected revenue” total is not a credible recovery forecast.

How to assess proposals objectively

Following discovery, any patient-level review should require an appropriate agreement, access safeguards and explicit authorized scope. Projected recovery figures should be labeled as estimates until source claims have been validated.

A practical example of the first discovery package

A multi-provider practice could begin with a 12-month, aggregated report showing claim submissions and remittances by payer, outstanding A/R by aging bucket, denial categories and a description of its EHR and practice-management setup. Staff should separately list recurring authorization failures, clearinghouse rejections, unexplained contractual payment differences and patient balance complaints. None of this requires uploading identifiable patient records through an open website form.

What information is not necessary for an initial call? Patient names, dates of birth, SSNs, copies of insurance cards, clinical notes, system passwords and raw user-access exports should not be submitted through a general public inquiry channel.

Can an initial assessment estimate recoverability? It can identify questions and broad exposure, but a defensible dollar forecast requires verified claims, expected allowed amounts, appeal status and payer-specific requirements. An old gross-balance total alone is inadequate.

What to expect from a credible review

The team should explain which cohorts need a line-level audit, what access or agreements would be required, the operational cost of remediation and which results remain uncertain. Request a written scope that separates new claim processing, existing A/R, appeals, payer contracting and IT integration responsibilities.

Evidence quality before signing an engagement

Ask for definitions of proposed metrics, a realistic handover period, data-ownership and termination provisions, escalation ownership and security boundaries. The assessment process itself should demonstrate discipline: traceable assumptions, no guaranteed collection percentage without evidence, and a clear distinction between financial operations and legal interpretation.

References

• CMS EDI/remittance guidance
• HHS HIPAA cloud/data guidance

Editorial update: October 11, 2026. Confirm current program, payer and professional guidance before operational use.