Same Meal. Four Payment Rules.

Before you configure billing, define what the payer is actually buying.

A payer offers $100 for a healthy food service. That sounds simple until you ask: “What exactly does the $100 buy?”

It could mean one delivered box, one week of support, actual food costs reimbursed up to a monthly limit, or a defined contract package. The amount may be identical while the payment rule is completely different.

Those rules create different revenue cycles. Per unit payment makes each delivery the billable event. A weekly or monthly bundle makes the service period matter. Cost-based reimbursement requires the provider to track actual costs and the remaining benefit cap. A defined contract package follows the unit, documentation and payment trigger negotiated with the payer.

The rate is not the payment rule. First define what the payer considers billable.

A useful way to think about the same Food is Medicine (FIM) service is through four common payment rules. Each changes what a community-based organization (CBO) must track, what it submits for payment, and when revenue is earned.

These are practical operating patterns, not formal regulatory categories. A payer can combine them, add authorization limits, or define a different unit entirely. The exact rules still depend on the program, payer and contract.

1 - Per Unit

Per-unit payment is the most intuitive model: one completed service equals one reimbursable unit. The unit might be a meal, a food box or another discrete service. The rate tells you what one unit pays, but the operational question is whether the organization can prove that each unit actually occurred.

Current Food is Medicine programs use this structure in several ways. Michigan's nutrition-focused In Lieu of Services (ILOS) policy defines medically tailored and healthy home-delivered meals on a per meal basis. North Carolina's Healthy Opportunities Pilot fee schedule defines healthy food boxes as one food box and several meal services as one meal. The service unit is therefore tied to the completed delivery, not simply to the member's enrollment in the program.

This model makes delivery data part of the revenue cycle. A missed delivery, duplicate delivery, wrong member, incorrect service date or missing proof can change the number of billable units. The payer may also define whether preparation, delivery, nutrition assessment or other costs are already included in the unit rate. In Michigan, for example, meal preparation and delivery are included in the meal unit cost, and delivery may be included in the weekly food pack unit when appropriate.

What this means for the CBO: If every delivery is a unit, the billing system needs one defensible record for every unit. At minimum, that usually means the member, service, service date, quantity, authorization context, proof of delivery and any exception that prevented the service from being completed.

When payment is per unit, every unit has to be independently defensible.

2 - Per Weekly or Monthly Bundle

A bundled unit changes the focus from each individual item to a defined period of support. Instead of asking how many meals or grocery items were delivered, the payer defines a week, month or other period as the reimbursable unit.

Michigan provides a clear example. Its Healthy Food Pack is defined as one weekly food pack, while the Produce Prescription is defined as one weekly voucher. The food pack can represent a meaningful amount of food support, but for billing purposes the unit is still the weekly pack. In other arrangements, a payer may negotiate a monthly program rate or another time-based package.

Once time becomes part of the unit, calendar logic becomes billing logic. A CBO needs to know what happens when a member starts midweek, pauses services during a hospitalization, changes plans, loses eligibility or stops before the end of the billing period. Whether a partial week or month can be billed, prorated or not billed at all depends on the payer's rules or contract.

Fee treatment matters here too. Michigan's policy says delivery is included in the Healthy Food Pack unit cost when appropriate, and its optional pricing guidance models administrative expenses and delivery costs as components of the weekly rate. Another payer could choose to separate those costs instead. The organization cannot assume the service period and the fee structure work the same way across contracts.

What this means for the CBO: A time-based unit requires a service period ledger, not just a delivery log. Track the authorized start and end dates, each period billed, pauses or gaps, partial period rules, proration logic and the documentation that proves the required support was delivered during that period.

When time is the unit, calendar logic becomes billing logic.

3 - Cost-Based Up to a Cap

Cost-based reimbursement up to a cap is fundamentally different from a fixed rate. The payer reimburses actual eligible costs, but only until the member reaches a defined dollar ceiling for the benefit period. The cap is the maximum available benefit, not an automatic payment amount.

North Carolina's Healthy Opportunities Pilot illustrates this structure for Fruit and Vegetable Prescription services. The state's published fee schedule treats the service as cost-based reimbursement up to a monthly cap. It also provides a separate monthly coordination payment to the organization that coordinates the service. That distinction is useful because it shows why administrative fees cannot simply be assumed to sit inside the food benefit.

Consider a hypothetical $100 monthly cap. If the member receives $72 of eligible food, the reimbursable service cost may be $72 rather than $100. If eligible costs reach $118, the benefit may still stop at $100 unless the program separately allows another fee. Whether delivery, administration, coordination or other costs count against the cap, sit outside it, or are bundled into the food cost is a program specific rule.

This model requires a different kind of controls. The provider needs to know the cap amount, when it resets, which expenses are allowable, how much has already been used, whether unspent dollars carry forward and how separately reimbursable fees are handled. A simple count of boxes or meals is not enough.

What this means for the CBO: Build a benefit ledger that separates actual service cost from any administrative or delivery fee, applies the correct cap and reset period, and prevents billing beyond the remaining balance. The organization also needs documentation that supports the underlying cost, not only proof that the service occurred.

A cap is a ceiling, not a rate.

4 - Defined Contract Package

The fourth model is the most contract driven. Instead of a state fee schedule fully defining the unit of service, the payer and provider negotiate what the package includes, how it is priced and what has to happen before payment is earned. The package could be a monthly program rate, a per-member arrangement, a defined set of deliveries or another structure.

California Community Supports is a useful example of why contract terms matter. The California Department of Health Care Services does not set provider rates for Community Supports. Rates and payment arrangements are negotiated between managed care plans and Community Supports providers and should be reflected in the network agreement. California also publishes a non-binding pricing resource to inform contracting rather than dictate the final rate.

Contract defined economics do not necessarily mean the provider avoids healthcare billing. California requires contracted Community Supports providers to submit claims using standard specifications and code sets, while the negotiated agreement determines the payment arrangement. The same concept can appear in commercial, Medicare Advantage or health system contracts: a healthcare transaction may still be required, but the contract defines what the payer is buying.

That makes contract interpretation a revenue cycle management (RCM) function, not simply a legal one. Eligibility, authorization, service duration, rate, administrative and delivery fee treatment, data requirements, invoice or claim expectations, payment timing and reconciliation rules all have to be translated into operational logic.

What this means for the CBO: Do not operationalize the rate in isolation. Convert the contract into a billing specification that clearly defines the billable package, member eligibility, authorization, required deliverables, fee treatment, transaction method, payment trigger and reconciliation process.

When the contract defines the package, the contract becomes part of the billing logic.

Same $100. Four Different Rules.

At $100 per box, the delivery itself creates the billable unit. At $100 per week, the provider has to satisfy the payer's definition of a completed service period. Under a $100 monthly cap, actual eligible costs draw down the balance and may never reach the full $100. Under a $100 contract package, the provider gets paid only after satisfying the deliverables and transaction requirements defined in the agreement.

That is why the question “What is the rate?” is usually too early. The rate only becomes useful after the provider knows what the payer considers billable, what period the payment covers, what limits apply, how fees are treated, what proof is required and what event actually triggers payment.

Before you price the service, define the payment rule.

Food is Medicine programs often look straightforward at the point of service. A member receives meals, groceries, a food box or a voucher. But the payment model determines whether the provider is managing units, periods, costs, contract deliverables or some combination of all four.

For CBOs entering healthcare reimbursement, that distinction is not accounting trivia. It determines what data has to exist before a claim or invoice can be generated, how revenue is forecast, which exceptions need human review and where payment leakage is most likely to occur.

The Six Questions to Answer Before you Configure Billing

These questions turn the payer's payment rule into an operating specification. Answer them before building the claim, invoice or reconciliation workflow.

The Payment Rule is the Operating Model

Once those six answers are answered, the rest of the revenue cycle becomes much more concrete. Coding can be mapped to the correct unit. Invoice templates can be built around the required period or cap. Proof of service can be collected at the right moment. Reconciliation can compare what the organization delivered against what the payer says it paid for.

The scalable capability is not memorizing one state's rate sheet. It is translating each payer's payment rule into data, workflow and controls that the organization can repeat. The food may look the same. The operating model does not.

Sources and Further Reading

Michigan MDHHS: In Lieu of Services Policy Guide

Current Michigan ILOS billing and service unit rules, including per-meal, weekly food pack and weekly voucher units along with guidance on how delivery costs are treated.

Michigan MDHHS: Optional ILOS Pricing Guidance

Illustrates how Michigan modeled food, labor, administrative expenses and delivery costs when developing non-binding midpoint rates for nutrition focused ILOS.

North Carolina DHHS: Healthy Opportunities Pilot Fee Schedule

Defines per-meal and per food box payment units and a cost-based Fruit and Vegetable Prescription benefit with a monthly cap and separate coordination payment.

California DHCS: Community Supports Policy Guide

Explains that Community Supports provider rates and payment arrangements are negotiated between managed care plans and providers and reflected in the network agreement.

California DHCS: Community Supports Pricing Resource

Non-binding pricing benchmarks and cost driver assumptions, including food, delivery and administrative cost considerations for medically supportive food services.