Revenue cycle outsourcing is one of the larger discretionary spends a health system makes, and one of the least examined contractually. The business case is usually built on a contingency rate compared against internal cost per dollar collected, the agreement is drafted around that rate, and the terms that determine whether the arrangement actually works get comparatively little attention.
That is unfortunate because the arrangement has an unusual shape. The vendor touches patients directly, holds protected health information, controls the data needed to measure its own performance, and is paid in a way that rewards collection rather than collection quality. Each of those features needs a contractual answer, and none of them is addressed by negotiating the percentage.
This guide works through the five areas a revenue cycle agreement has to settle, and the recurring duties each one creates. The framing is deliberately operational, because most of what goes wrong in these relationships is visible in monthly reporting long before it becomes a contract dispute.
Five areas the agreement has to settle
These are the terms that determine how the relationship behaves in month eighteen rather than month one. Each creates both a drafting question and an ongoing monitoring duty.
- Fee basis and commissionable receipts, gross or net, treatment of direct patient payments, recoupments, refunds, prior-vendor accounts, write-offs and charity determinations.
- Performance measures, outcome measures with defined baselines and calculation methods, reporting frequency, and consequences for sustained underperformance.
- Patient-facing conduct, contact methods and frequency, tone and script standards, routing of hardship and financial assistance enquiries, and complaint escalation with response times.
- Data rights and use limitations, business associate relationship with subcontractor flow-down, segregation, a use limitation for the vendor’s own purposes, and access during and after the term.
- Exit and transition, account return format and timing, work in progress treatment, run-off fee entitlement and data return format with a deadline.
A health system that settles all five has an arrangement it can manage and leave. One that settles only the first has an arrangement whose performance it cannot verify and whose data it cannot retrieve, which is a weak position long before anyone decides to change vendor. The ordering also matters: fee basis and performance measures are easiest to negotiate before the vendor has the work, while conduct standards and data use limitations can usually be added later without much resistance.
Most monthly fee disputes come from one ambiguity: which receipts the contingency rate applies to. Name the treatment of direct patient payments, payer recoupments and refunds, accounts previously worked by another vendor or internal team, and amounts resolved by write-off or charity determination. Four sentences at drafting replace a recurring reconciliation argument, and they also make the vendor’s own forecasting more honest.
The duties that run every month
Five recurring duties keep the arrangement honest. All of them depend on the health system holding the measures and definitions independently of the vendor’s reporting, because a measure that only the vendor can calculate is not a control. None of them require more than a few hours a month once the definitions are fixed.
- Monthly performance reporting against measures. Reported on the contractual basis with the calculation method fixed, so a change in the vendor’s methodology is visible rather than absorbed
- Fee reconciliation against the commissionable definition. A periodic check of invoiced fees against the contractual base, sampling the categories most likely to be misapplied
- Complaint review with root cause. Volume, category and resolution reviewed quarterly, because patient complaint patterns are the earliest signal that conduct standards are slipping
- Attestation refresh for subcontractors. Business associate and subcontractor arrangements confirmed annually, treated as expiring documents with renewal dates rather than standing assurances
- Exit readiness confirmation. An annual check that account return and data return could actually be performed in the agreed format and window, documented before it is needed
A five-step roadmap for tightening a revenue cycle arrangement
Step 1, extract the fee definition and test it
Read the commissionable base definition and test it against a month of actual receipts, category by category. This exercise almost always finds at least one category being treated differently from the contract, in one direction or the other, and it quantifies the issue immediately.
Step 2, replace activity measures with outcome measures
Review the performance schedule and identify measures that reward motion. Propose outcome substitutes with defined baselines at the next commercial moment, which is usually a term extension or a rate negotiation where the vendor has something to gain.
Step 3, write the patient conduct standards down
Where conduct is governed by vendor policy rather than contract, bring the essential standards into the agreement: contact limits, routing of financial assistance enquiries, complaint escalation and response times. Vendors with good practice will agree readily, which is itself informative.
Step 4, close the data use gap
Add or tighten a use limitation preventing the vendor from using health system data for its own analytics, benchmarking or product purposes without consent, and confirm subcontractor flow-down. This term has grown considerably more important as vendors commercialise data assets.
Step 5, negotiate the exit while you are happy
Agree account return, work in progress treatment, run-off entitlement and data return format and deadline now, while there is no transition under way. An exit clause negotiated during a transition is negotiated against a counterparty holding the data, which is the worst possible moment.
Measure the vendor against the contract
Aavenir holds fee definitions, performance measures, conduct standards and exit duties on the vendor agreement, with monthly reporting and reconciliation as tracked obligations.
Why accountability does not transfer
Patients do not distinguish between a health system and its collection vendor, and neither, in substance, do regulators or the press. A call made in the wrong tone, at the wrong hour, to a patient who had already qualified for financial assistance becomes the health system’s problem whatever the agreement says about independent contractor status. That asymmetry is the argument for contracting conduct standards rather than relying on vendor policy, and for reviewing complaint patterns as a leading indicator rather than as a service issue. The same logic applies to data: the business associate agreement is a contractual control over an exposure that remains the provider’s regardless of who processes the information.
Area, drafting question and ongoing duty
The table pairs each area with the question to settle at drafting and the duty it creates afterwards. The duty column is what belongs in the obligation register with an owner and a cadence.
| Area | Drafting question | Ongoing duty | Evidence |
|---|---|---|---|
| Fee basis | Which receipts are commissionable | Periodic fee reconciliation | Reconciliation worksheet with findings |
| Performance | Which outcome measures and baselines | Monthly reporting on fixed method | Report with calculation inputs |
| Patient conduct | What standards and escalation times | Quarterly complaint review | Complaint log with root cause |
| Data rights | What use limitation and flow-down | Annual attestation refresh | Current attestations with dates |
| Exit | Return format, timing, run-off fees | Annual exit readiness check | Readiness note and format confirmation |
The percentage is the easiest term to negotiate and the least predictive of how the arrangement performs. What determines that is whether the commissionable base is defined precisely, whether performance is measured on outcomes the health system can verify independently, whether patient conduct is contracted rather than assumed, whether the data can be used only for the health system’s purposes, and whether leaving is possible on known terms. All five are drafting decisions with monitoring consequences, and all five are cheaper to settle before the relationship starts. Health systems running structured obligation management for healthcare already have the register these duties belong in.
For related guidance, see Business associate agreement obligations at a glance, Physician and provider agreement tracking for health systems and Staffing agency contract control for health systems.
