SAH Pillar · Statements & Claims
How do I produce monthly SAH statements and claim to Services Australia without manual reconciliation?
Support at Home requires a monthly participant statement (what was delivered, what it cost, what contribution was charged, what's left in the budget) and a separate claim against the Aged Care Provider Portal (ACPP) for the government's portion. Both have to reconcile to the same source of truth. Manual production at scale is a guarantee of errors, write-offs, and late submissions.
What the legislation requires
Monthly statements and claims are prescribed outputs of the SAH framework — not optional artefacts.
- A monthly statement must be issued to every participant, itemising services delivered, prices charged, the participant's contribution, the government subsidy, and the remaining quarterly budget position.
- Claims for the government-funded portion are submitted through the Aged Care Provider Portal (ACPP), which is the Department of Health's claiming system for Support at Home.
- Provider records must reconcile against the Services Australia payment records — any discrepancy needs to be investigated, adjusted, and explained.
- The statement format and minimum content are prescribed so participants can understand what they've been charged for and why.
- Disputes raised by participants require a documented response and resolution trail.
Reference: Aged Care Act 2024 Chapter 4 (Support at Home funding and claiming framework); Aged Care Rules 2025 Chapter 4; Support at Home Program Manual — statements and claiming provisions; ACPP claiming guidance (Department of Health).
What providers usually get wrong
The failure modes we see over and over.
- Statements produced by hand from spreadsheet data, with copy-paste errors that erode participant trust and create refund cycles.
- Missing ACPP claim windows because the data wasn't ready in time — a chased claim is worse than a timely claim.
- Reconciliation done quarterly when it should be monthly, leading to a month-three panic when discrepancies compound across three claim cycles.
- No clear audit trail when a participant disputes a charge. The dispute becomes a he-said-she-said conversation because the provider can't produce the evidence for a specific line item.
- Treating statements as a finance-team output at month-end instead of a participant-facing artefact the Care Partner has reviewed. Statement errors reach the participant before the provider knows they exist.
- Not building the statement from the same underlying data as the claim, so the two don't reconcile and the participant sees one figure while the provider claims another.
How Statura handles it
What's in the product today — not on a roadmap.
- Automated monthly statement generation per participant, built from the same service delivery records that feed the claim. Statement and claim are guaranteed to reconcile because they share a source.
- Statement preview and Care Partner approval workflow before send. The Care Partner sees the statement the participant will see, with the ability to hold, adjust, or annotate before it goes out.
- ACPP-format claim file generation with pre-submission validation — rule checks for service category mapping, price caps, participant eligibility, and contribution calculation before the file is produced.
- Reconciliation dashboard showing claimed vs acknowledged vs paid vs disputed, with line-item drill-down when a discrepancy surfaces.
- Dispute and adjustment workflow linking each dispute to the originating statement line, with a resolution record and the correction applied to the next statement.
- Note: Direct live B2G submission to Services Australia is a file-export workflow today, not a live API integration — operators upload the validated claim file into ACPP. Live API submission is on the roadmap and will be released as a drop-in upgrade.
Modules involved
The audit trail
What an ACQSC auditor will actually see.
When an assessor asks for evidence on this obligation, here's what the platform produces on request — date-stamped, user-attributed, and exportable:
- Every monthly statement version per participant, showing what was generated, what was approved, and what was sent.
- Claim file generation log with the underlying service deliveries, the validation rules that ran, any warnings raised, and the file payload.
- ACPP submission log with upload date, reference number, and acknowledgement status.
- Payment reconciliation ledger per claim — claimed, acknowledged, paid, variance, reason for variance.
- Dispute log linked to specific statement line items, with the resolution decision and supporting evidence.
- Adjustment history showing every correction applied to a participant's ledger, the reason, and the approver.
Related SAH pillars
Obligations that sit next to this one.
Participant Contributions
Per-service, means-tested contributions with lifetime caps and hardship provisions.
Read the pillarQuarterly Budgets
Quarterly allocation, real-time burn-rate and unspent funds carry-over with cap enforcement.
Read the pillarService List & Pricing
Three ongoing SAH service categories plus the AT–HM stream, government price caps and your provider price book.
Read the pillarCommon Questions
Frequently asked questions about statements & claims.
Does Statura submit claims directly to Services Australia via API?
Not yet — today the platform generates a validated, ACPP-compliant claim file that operators upload through the Aged Care Provider Portal. The file is built from the same source data as the monthly statement, so they're guaranteed to reconcile. Live API submission is on our roadmap and will be delivered as a drop-in upgrade without changing the claim-preparation workflow.
What validations does the platform run before I submit a claim?
Pre-submission validation catches the common failure modes: services that can't be mapped to a SAH service item, prices above the category cap, contributions calculated against the wrong means-tier, services billed against an inactive or reassessed classification level, and claim periods that overlap with a prior submission. The validator surfaces errors as blockers and warnings as review items before the claim file is produced.
How does the monthly statement stay in sync with the quarterly budget?
Both the statement and the quarterly budget dashboard read from the same service delivery ledger. When a service is logged, adjusted, or reversed, both the statement and the budget update in the same transaction. Participants see consistent numbers whether they check the portal mid-month or read the monthly statement.
What happens when a participant disputes a charge on their statement?
Disputes are raised against the specific statement line — not the whole statement — and flow into a workflow owned by the Care Partner. The line item is flagged, the original service delivery record is linked, the resolution decision is recorded with the Care Partner and date, and any correction is applied to the next statement with a reference back to the disputed line. The participant can see the status of their dispute through the family portal.
Can I review statements before they're sent to participants?
Yes, and that's the default. Every monthly statement enters a review state for the Care Partner before it's sent. The Care Partner sees exactly what the participant will see, can hold the statement if something looks wrong, and signs it off when it's ready. The sign-off is recorded on the statement version.
See how Statura handles statements & claims.
A 30-minute demo, grounded in the legislation and your actual operating model. No generic slide deck.
Free trial includes Compliance Essentials tier (11 modules). No credit card required.
Not sure where to start? Take our free compliance assessment →
