A single case agreement is the smallest contract most health systems negotiate and one of the most likely to lose money. It covers one patient for one episode, is usually negotiated under clinical time pressure, and sets a rate and a scope that exist nowhere in the standing payer configuration the billing system relies on.
The negotiation itself is generally handled well. Case management or utilisation review establishes the clinical need, secures the authorization and agrees terms with the payer. What follows is the problem. The agreement is a document, frequently a PDF in a case file or an email thread, and the claim that has to match it is produced weeks later by a different team working from the account record and the standing fee schedule.
The result is a denial pattern that is entirely predictable and largely preventable: services outside the authorized list, dates outside the authorized window, missing authorization references, and rates defaulting to a standard out-of-network calculation rather than the negotiated one. This guide covers what the agreement should specify and how to structure tracking so the claim reflects the contract.
What the agreement has to nail down
Because the agreement exists outside any standing configuration, every parameter the claim depends on has to be explicit in it. Ambiguity that would be resolved by a standing contract has nowhere to resolve to here.
- Patient and authorization linkage, the patient identifier, the payer member identifier and the authorization or reference number that the claim must carry to be adjudicated against the agreement.
- Authorized services and limits, the specific services, levels of care or visit counts covered, including anything explicitly excluded, since anything not authorized is generally not payable.
- Effective date range, a defined start and end, with the extension process stated, because care continuing beyond the window is the single most common cause of unpayable claims.
- Rate and methodology, the negotiated amount or the basis of calculation, stated clearly enough that revenue cycle can apply it without interpretation.
- Billing and submission requirements, the submission address or payer identifier, required codes or modifiers, the claims filing window and the appeal process for that agreement.
Each of these is a field, not a paragraph. The practical implication is that a single case agreement should be captured as structured data at the moment it is agreed, linked to the account, rather than filed as a document to be read later by whoever is working the claim. That is the same structural argument that makes standing payer contract terms worth holding as data rather than text.
When a patient remains under care past the authorized end date, clinical continuity carries on automatically and contractual coverage does not. Extension has to be requested and agreed before the window closes. After it closes the provider is negotiating retroactively from a position with no leverage and no obligation on the payer to agree.
Where the money is lost
The losses cluster in a small number of places, all of which sit in the handoff between the team that negotiates and the team that bills.
- Terms living in a document. A PDF in a case file cannot be applied by a claims process. If the rate and scope are not in a field somewhere the account touches, the claim will be produced from the default configuration.
- Expiry unmonitored. Nobody holds the end date, so the extension conversation happens after care has already continued past it, which converts a negotiation into a request for grace.
- Authorization reference dropped. The claim goes out without the reference that links it to the agreement, and adjudication falls back to standard out-of-network handling with a much lower allowed amount.
- Scope creep during the episode. Additional services are delivered clinically and were never authorized, so they are billed and denied, and the appeal is weak because the agreement is explicit about scope.
- Denials worked without the agreement. The denial lands with a revenue cycle team that does not have the agreement terms, so the appeal argues general medical necessity instead of citing the negotiated contract.
Building a workable tracking process
Step 1, Capture terms as structured data at agreement
At the point the terms are agreed, record the rate, authorized services, date range, authorization reference and billing requirements as fields linked to the patient account. This is a two-minute task at negotiation and prevents most of what follows.
Step 2, Make the record visible to revenue cycle
The team producing the claim must be able to see the negotiated terms from the account, without hunting through a case management file. Visibility at the point of billing is the single highest-value change in this whole process.
Step 3, Monitor the end date with clinical lead time
Set escalation far enough before expiry that an extension can be requested with clinical documentation while the window is still open. The lead time should reflect payer turnaround, not administrative convenience.
Step 4, Validate the claim against the agreement
Before submission, check service dates against the authorized range, services against the authorized list, and the presence of the authorization reference. Three checks, all automatable, covering the large majority of denials in this category.
Step 5, Arm the appeal with the contract
When a denial does occur, the appeal should cite the agreement, the authorization and the specific negotiated term. Appeals that argue clinical necessity when a contractual term is the actual answer take longer and succeed less often.
Negotiated terms, visible where the claim is built
See single case agreement terms linked to the account, with expiry escalation and pre-submission validation.
Managing the population, not just the case
Once these agreements are captured as structured records, a portfolio view becomes possible and turns out to be commercially useful. Which payers require single case agreements most often, what rates were agreed by service line, how often extensions were requested and granted, what the denial rate is on these claims compared with standing contracts, and whether a recurring pattern of single case agreements with one payer indicates a network gap worth addressing through a participation agreement instead. That last point is frequently the largest opportunity: a specialty that generates a steady stream of individually negotiated agreements is usually a candidate for a standing arrangement, and the data to make that case only exists if the individual agreements were captured consistently. This is the same aggregation benefit that healthcare obligation management produces across other agreement types.
Denial causes and their prevention
The table maps the recurring denial reasons in this category to the control that prevents each. All five controls are mechanical rather than clinical, which is why this problem responds so well to structured tracking.
| Denial cause | Root problem | Prevention | Owner | Timing |
|---|---|---|---|---|
| Service date outside window | Expiry unmonitored | Escalation before window closes | Case management | Before expiry |
| Service not authorized | Scope change during episode | Scope check at service addition | Utilisation review | During episode |
| Missing authorization reference | Claim built from default config | Pre-submission validation | Revenue cycle | Before submission |
| Rate applied incorrectly | Terms not visible at billing | Structured terms on the account | Revenue cycle | At claim build |
| Weak appeal on denial | Agreement not available to appeals | Agreement linked to the account | Revenue cycle | At denial |
Single case agreements will always be exceptions, negotiated case by case under pressure. What they do not have to be is invisible to the process that bills them. Capturing the terms as data at the moment of agreement, making them visible where the claim is built, and watching the end date converts a reliable source of denials into ordinary, collectable revenue, and it produces the evidence needed to decide which of these exceptions should become standing contracts instead.
For related guidance, see Payer fee schedule audits, finding the loaded rate errors, Value-based care contract administration, simplified and Patient transfer agreements: the paperwork behind continuity.
