How do I price accommodation, publish it transparently, and manage RAD/DAP options without tripping disclosure rules?

• Providers must publish their accommodation prices so that prospective residents and families can compare before making an admission decision. Prices must be published on MyAgedCare and on the provider's website where one exists.
• Accommodation prices are capped at a maximum derived from the Maximum Permissible Interest Rate (MPIR), published and maintained by the Department of Health. Providers can charge at or below the cap, but not above.
• Residents must be offered the choice between paying a Refundable Accommodation Deposit (RAD), a Daily Accommodation Payment (DAP), or a combination. Providers cannot require a specific payment type.
• The relationship between the RAD amount and the equivalent DAP is set by a formula based on the MPIR — providers cannot set their own conversion rate.
• Resident agreements must include prescribed content about accommodation payment options, refund conditions, and the resident's rights.
• RAD refunds must be paid within the statutory refund period when a resident leaves the service (by departure, transfer, or death). Late refunds attract penalties and interest.
• Means-tested residents may qualify for full or partial government-funded accommodation support, in which case the provider is paid by the Department rather than the resident.

Reference: Aged Care Act 2024 Chapter 4 (accommodation payments); Aged Care Rules 2025 Chapter 4; Maximum Permissible Interest Rate notices published by the Department of Health; MyAgedCare accommodation pricing publication framework; Department guidance on resident agreements.

• Not publishing prices on MyAgedCare. This is a hard disclosure obligation — not a marketing choice — and missing it is a finding at the next assessment contact.
• Prices above the MPIR-derived cap. Providers occasionally charge above the published cap because the internal pricing didn't update when the MPIR changed. Every day of above-cap pricing is an overcharge.
• Pressuring residents toward a specific payment type. The resident's right to choose RAD, DAP, or a combination is legal — steering them is not. A provider that 'prefers RAD for cash flow reasons' and communicates that preference to prospective residents is on dangerous ground.
• Incorrect RAD-to-DAP conversion. Providers apply their own conversion rate (or guess) instead of the MPIR-based formula, which overcharges residents choosing DAP.
• Resident agreements missing prescribed content. The agreement is used as the resident's contract — missing clauses aren't just a legal risk, they're a compliance finding.
• Late RAD refunds. The statutory refund period is clear, and a RAD refund that misses the deadline attracts penalties and interest automatically. Providers that don't have a workflow for refund deadlines often learn about late refunds from a complaint, not from their own system.
• Treating accommodation pricing as a finance-team activity separate from the admissions process. The resident's choice of payment option needs to be captured at admission, in the agreement, and flow into billing — a disconnected process creates mismatches that surface at refund time.

• Room-level pricing with the MPIR-derived cap enforced. Operators cannot save a price above the cap — the system refuses it.
• Automatic MPIR-based RAD-to-DAP conversion so the DAP equivalent of a RAD is always calculated correctly and updates when the MPIR changes.
• Published pricing export for MyAgedCare and the provider website — the published prices are generated from the same source as the pricing applied at admission, so MyAgedCare and internal records are guaranteed to match.
• Admission workflow capturing the resident's payment choice (RAD/DAP/combination) with the supporting agreement, the prescribed content, and the signed copy.
• RAD refund workflow with the statutory refund deadline tracked per resident departure. Alerts fire in advance of the deadline so refunds are completed on time.
• Resident agreement template with all prescribed content — operators can customise provider-specific sections but cannot remove the mandatory clauses.
• Means-tested accommodation support workflow — where a resident qualifies for government-funded support, the claim flows through the AN-ACC claiming channel and is reconciled against the Department payments.
• Pricing history per room so operators can reconstruct what price applied at any historical date — important when an accommodation payment dispute arises months after admission.

When an assessor asks for evidence on this obligation, here's what the platform produces on request — date-stamped, user-attributed, and exportable:

• Room pricing history — every price change, the effective date, the MPIR cap at the time, and the operator who made the change.
• Published pricing record — what was published to MyAgedCare on which date, with the file or submission reference.
• Resident agreement versions per resident — the signed copy, the payment choice, and any variations.
• RAD deposit and refund log per resident — deposit amount, date received, refund amount, refund due date, refund actual date, and any interest or penalty paid.
• MPIR history — the published rate changes, the effective dates, and the corresponding cap adjustments.
• Pricing disclosure record per incoming resident — what was disclosed at admission, on what date, in what form.