Letter of agreement

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

An LOA usually has a narrow scope

An LOA may support a single case, episode, service, location, or temporary out-of-network arrangement. Some payers use similar labels for broader documents. Read the actual terms.

Do not treat one member’s LOA as a network contract or a rule for other members. Its authority ends where its defined scope ends.

Identify the parties and precedence

Confirm the payer legal entity, provider legal entity, tax identifier, member, product, and authorized signers. Determine whether an existing participation agreement, provider manual, authorization, or plan document also applies.

The LOA should explain which document controls if terms conflict. Counsel should resolve silence or ambiguity before the practice relies on a rate, notice, dispute, or termination provision.

Capture the operational terms

A build-ready abstract records:

• member and product identifiers
• billing and rendering providers
• approved locations, settings, and modalities
• service codes, modifiers, units, and provider types
• rates or payment methodology
• authorization number, limits, and period
• claim form, submission route, filing rule, and attachments
• member-cost and balance-billing terms when addressed
• start, expiration, renewal, and termination events
• contact, escalation, reconsideration, and dispute paths

Record absent fields as unresolved. Avoid filling gaps from another payer’s LOA.

Authorization and agreement remain separate

An authorization may approve a service under a benefit and clinical-review process. An LOA establishes commercial or operational terms for its defined scope. Either document may refer to the other.

Verify both when both apply. Neither one guarantees claim payment. The service still needs qualified clinical direction, consent, documentation, accurate coding, eligibility, and every applicable claim requirement.

A fictional LOA release

Pine Harbor, a fictional ABA practice, receives an LOA for one member’s assessment and initial treatment period. The agreement lists two services, two provider types, one home location, and a 90-day term. The practice creates eight release combinations.

Six combinations have matching service, provider, location, rate, authorization, claim route, and date evidence. Readiness is 6 of 8, or 75%. One is held because the provider type is absent from the rate paragraph. One is held because the authorization ends before the LOA.

Both holds stay visible. The practice seeks written clarification and does not use the closest rate or longest date.

Release scheduling and claims with evidence

Before promising a payer-covered start, confirm the member, benefit path, clinical prerequisites, signed LOA, authorization when required, provider, location, staff, supervision, and safe setting. Before claim release, recheck the service date, code, units, rendering provider, location, authorization balance, LOA version, and timely-filing path.

Store the signed document with restricted access. Link the approved abstract to scheduling and billing controls rather than copying sensitive member details into broad operational fields.

Negotiate terms that can be operated

Before signing, test whether the proposed language can be implemented. A rate without a unit definition, a service without an eligible provider type, or an authorization period without an aligned agreement date will create avoidable holds. Ask for the payer’s claim route, control-number expectations for corrections, records process, and named escalation contact.

Model the expected service pattern using the exact codes, units, rates, travel, supervision, administrative work, payment timing, and possible member responsibility. Keep the model fictional or de-identified during negotiation unless sharing member information is authorized and necessary. A favorable headline rate can still produce an unsustainable arrangement when unpaid duties or slow payment dominate.

Document rejected language and the final compromise. Later reviewers should be able to see why a term changed and which operational control was designed around it.

Plan for expiration and continuity

Create reminders before unit, date, or episode limits. Assign renewal, transition, records, family communication, schedule, and claim owners. An expiring LOA may affect funding while clinical transition and continuity duties follow their own authorities.

If renewal remains uncertain near expiration, identify the last safely schedulable date, open authorizations, outstanding claims, appeal options, and alternative funding routes. Communicate verified facts early enough for an orderly decision. Do not represent a pending extension as approved.

Preserve the expired version for outstanding claims and appeals. Record any extension with its source and effective date.

Measure the complete case pathway

Useful measures include LOAs received with all required terms, release combinations cleared, unresolved terms by age, renewal decisions before expiration, claims accepted for adjudication, and mature payment variances. Keep coverage, authorization, claim status, and payment measures separate.

The NAIC state insurance department directory can help locate a regulator. It does not interpret an LOA or establish jurisdiction over a particular plan.