Some HCBS costs should not be hidden inside a broad rate. A pass-through cost may be clearer when the expense is specific, variable, and directly evidenced.
Strong rate-setting mechanics define when pass-through treatment is appropriate. This matters when funding and payment models need flexibility without losing financial control.
Across the Commissioning, Funding & System Design Knowledge Hub, pass-through cost controls help show which expenses are reimbursed separately and why.
When pass-through rules are unclear, transparency becomes a payment risk.
Why pass-through costs need tight definition
Pass-through costs can support fair funding where expenses vary by participant, geography, supplier, or service condition. They can also create disputes if the rules are vague.
If commissioners do not define eligible cost types, providers may claim expenses that should sit inside the base rate. If the rules are too narrow, providers may carry costs that the model was never designed to absorb.
A practical framework for pass-through cost control
A controlled pass-through model defines eligibility, evidence, approval, payment, and reconciliation. It should explain which costs are separate and which are already included in the unit rate.
The process should protect flexibility while keeping reimbursement evidence clear and auditable.
Operational Example 1: Defining eligible pass-through cost types
Step 1: The commissioning finance lead lists proposed pass-through cost types and records eligibility rules in the pass-through definition schedule.
Step 2: The provider finance representative reviews the schedule for delivery practicality and records any disputed cost type in the provider feedback log.
Step 3: The contract manager checks whether each cost is excluded from the base rate and stores the finding in the contract pricing file.
Step 4: The commissioner approval panel confirms eligible cost types and records the decision in governance minutes.
Required fields must include:
Cost type, eligibility rule, base rate treatment, approval status.
Cannot proceed without:
A defined pass-through schedule showing which expenses can be claimed separately.
Auditable validation must confirm:
Eligible costs are not already funded through the base HCBS rate.
This process prevents double funding and underfunding. Without it, providers and commissioners may disagree about whether an expense is claimable. Early warning signs include repeated clarification questions or inconsistent approvals. Escalation starts with the contract manager when eligibility cannot be applied consistently.
Governance audits the definition schedule, feedback log, pricing file, and approval decision. The approval panel reviews before implementation. Action is triggered by unclear eligibility or overlap with the base rate. Evidence includes rate files, contract schedules, provider feedback, finance notes, and governance records.
Operational Example 2: Approving pass-through claims during delivery
Step 1: The provider submits a pass-through claim and records cost type, participant link, invoice reference, and service period in the claims portal.
Step 2: The contract officer checks claim completeness and records acceptance, rejection, or clarification need in the pass-through intake log.
Step 3: The finance analyst verifies the invoice against eligibility rules and stores the review result in the payment evidence folder.
Step 4: The contract manager authorizes payment or rejection and records the decision in the claims decision register.
Step 5: The provider receives the decision notice and stores payment outcome evidence in the finance record system.
Required fields must include:
Cost type, invoice reference, service period, decision outcome.
Cannot proceed without:
Invoice evidence and a clear link between the cost and eligible service delivery.
Auditable validation must confirm:
The claim meets eligibility rules and is supported by source evidence.
This control keeps reimbursement decisions consistent. Without it, pass-through payments may depend on individual judgement rather than rules. Early signs include rejected claims, incomplete invoices, or disputed eligibility. Escalation moves to the contract manager when the claim is high value, repeated, or unclear.
Governance reviews claim logs, invoice checks, decision registers, and payment records. The contract officer reviews each claim on receipt. Action is triggered by missing evidence, disputed eligibility, or repeated claim issues. Evidence includes invoices, portal records, payment files, provider correspondence, and audit notes.
Operational Example 3: Reconciling pass-through costs at review points
Step 1: The finance lead extracts paid pass-through claims and records total paid value, cost type, and provider pattern in the reconciliation worksheet.
Step 2: The contract analyst compares paid claims with expected use and records variance in the pass-through review dashboard.
Step 3: The commissioning manager reviews whether repeated claims indicate base rate weakness or legitimate variable cost and records findings in the rate learning file.
Step 4: The review panel decides whether to maintain, narrow, expand, or redesign pass-through rules and records the decision in governance minutes.
Required fields must include:
Paid value, cost pattern, variance status, rule decision.
Cannot proceed without:
Reconciliation evidence showing how pass-through costs are being used over time.
Auditable validation must confirm:
Pass-through rules remain appropriate and do not mask base rate failure.
This process turns payment evidence into rate learning. Without it, repeated pass-through use may hide a cost that should be built into the rate. Early warning signs include rising claims in one category or provider-specific patterns. Escalation moves to the review panel when use becomes structural rather than exceptional.
Governance audits reconciliation worksheets, dashboards, rate learning files, and panel decisions. The finance lead reviews quarterly. Action is triggered by repeated high-value claims or unexpected cost patterns. Evidence includes paid claims, invoices, provider records, finance analysis, and governance minutes.
System and funder expectation
Federal, state, and Medicaid-aligned funders expect separately reimbursed costs to be transparent and controlled. Pass-through payments must show why the expense is separate, how it is evidenced, and how it is reconciled.
This supports HCBS rate-setting mechanics for defensible unit rates and service packages, because clear cost treatment strengthens pricing, payment, and audit logic.
Regulator expectation
Regulators expect payment arrangements to support safe delivery without creating weak accountability. If a cost is reimbursed separately, the audit trail should show eligibility, approval, payment, and review.
The evidence should connect the cost to service delivery and show that duplicate funding has been avoided.
Pass-through cost controls protect flexibility and transparency
Pass-through cost controls allow HCBS rate models to handle specific variable expenses without weakening financial discipline. They make clear which costs sit outside the base rate and how reimbursement is governed.
Outcomes are evidenced through eligibility schedules, claims records, invoice checks, reconciliation worksheets, and governance decisions. These records show whether pass-through payments are justified and controlled.
Consistency is maintained when rules are defined before implementation, applied during claims review, and tested through reconciliation. This protects providers, commissioners, and funders from unclear cost treatment and supports defensible HCBS rate design.