Appeals

A billing agency’s client audit workflow

A practical workflow for running one payer audit across multiple client practices: authorization, scoped access, intake, QA handoff, and client-safe reporting.

By PayerBeacon · Published · Updated

Written and edited by PayerBeacon. Sources are listed below with the date each link was checked.

How should a billing agency run a payer audit across client practices?

Get written authorization and a BAA in place, scope one payer and one period per client, keep each client’s data separate, and have a second reviewer check the finding before it goes into a client report.

It depends. Some clients can provide a fee schedule and an 835 directly; others need the agency to request the files. The workflow should record who authorized access, which payer and period are in scope, and who reviewed the finding before delivery.

Authorization and access

Start with the paperwork, not the file. Confirm the client relationship, the BAA or other required agreement, and the specific payer and period the client wants reviewed. The agency should not use one client’s files for another client’s report or for a general benchmark without explicit permission.

  • Confirm the client entity, the signer, and the effective date of the BAA or authorization.
  • Confirm which payer and which service period are in scope.
  • Confirm who at the client can answer questions and approve the final report.
  • Grant each reviewer access only to the client practices they work on.
  • Record the date access was granted and the date it should be removed.

Intake for one client

A narrow intake produces a faster, more defensible result. Ask for one payer, one month, a fee schedule with dollar rates, and the matching remittance. If the client cannot provide a dollar rate, say that the line is out of scope rather than guessing.

InputWhat to confirmWhy it matters
Payer and periodOne payer, one service monthKeeps the review reproducible
Fee scheduleDollar rate per code and unit, effective dateProvides the expected amount
Remittance835/ERA or supported export with line detailProvides paid, allowed, and adjustment data
Claim detailCode, modifier, units, date of serviceConfirms the comparison is like-for-like
Client contactNamed reviewer and approval pathPrevents an unreviewed finding from being sent

QA handoff

Separate the person who finds a difference from the person who approves it when the team allows it. The reviewer should be able to see the source rate, the remittance line, the calculation, and the exclusion reason without reconstructing the work.

A review that ends in "not supported" is a useful result. It protects the client relationship and keeps the next finding credible.

  • Second reviewer checks the code, modifier, unit, date, and contract version.
  • Second reviewer re-runs the arithmetic and confirms patient responsibility is not counted as a payer shortfall.
  • Any excluded line is listed with its reason.
  • The client contact approves the final report before it is shared beyond the engagement team.

Client-safe reporting

Report the finding, the evidence, and the limits in the same document. Use "estimated recoverable" or "difference to review," not "recovered," until the payer has paid or accepted the adjustment. Keep each client’s figures separate and do not imply a cross-client benchmark unless the clients have agreed to it.

The report should state the payer, period, number of claims, excluded lines, and the assumptions behind the calculation. If the finding is small, say so. A report that invents urgency is harder to defend than one that is candid about a limited result.

Sources