Key date: 12 July 2026. The Services Australia CCS Session Report API v3 becomes effective from this date. Software providers must be using v3 by this date. API v2 end-of-life is 1 October 2026.
What is changing
Services Australia is introducing Version 3 of the CCS Session Report REST API, effective from 12 July 2026. This API is used by child care management software to submit session reports to the Child Care Subsidy System (CCSS) via PRODA B2B.
Session reports are the mechanism by which approved providers report sessions of care to Services Australia. They are used to calculate and process Child Care Subsidy (CCS) payments for families. Providers have a legal responsibility to ensure all session reports are complete, accurate and submitted on time.
API v2 will reach end-of-life on 1 October 2026. Software that continues using v2 after that date will be unable to submit or vary session reports via the B2B gateway.
Key dates
- 12 July 2026: Session Report API v3 effective. Software must be capable of submitting v3 requests from this date.
- 1 October 2026: Session Report API v2 end-of-life. Submissions via v2 will no longer be accepted after this date.
- 3 August 2026: Session report block for the 2025-26 CCS year commences. Reports for weeks in the 2025-26 year cannot be submitted after this date without Department of Education approval.
What changed in v3
The primary change in v3 relates to the reporting of non-prescribed discounts and allowable discount structures. Key technical changes include:
- The
isNonPrescribedAppliedfield type changed from Boolean to String (length 1). Permitted values are now'Y','N'and empty string. Software usingtrueorfalsefor this field must be updated. - Duplicate allowable discount categories for a single session of care are now permitted, as per Department of Education instruction. The previous validation (PMS241) preventing duplicates has been removed.
- Updated cardinality and business rules for the
OtherSubsidiesstructure within session of care submissions. - Additional business clarifications to timeframes for session report submission and allowable discount reporting.
The v3 changes build on discount reporting requirements that came into effect from 7 July 2025, when providers became required to report prescribed discounts when submitting and updating session reports. Non-prescribed discount reporting remains voluntary.
What this means for providers
For most approved providers, the practical impact depends on the child care management software your service uses. Your software provider is responsible for implementing the v3 API changes before the effective date.
If your service uses software that integrates with the CCSS via PRODA B2B, you should confirm with your software provider that:
- Their platform will be updated to API v3 before 12 July 2026
- The update covers the
isNonPrescribedAppliedfield type change - Session report submission will continue without interruption after the effective date
If your software provider cannot confirm readiness, you may need to submit session reports via the Provider Entry Point as a fallback until the issue is resolved. Late or missing session reports can affect families' CCS payments and may result in compliance action against your service.
Session report obligations that do not change
The following core session report obligations are unchanged by the v3 update:
- Session reports must be submitted within 14 days after the end of the week in which care was provided.
- Session reports must be submitted for all enrolled children, including those not eligible for CCS.
- Session reports can be varied or withdrawn up to 28 days after the start of the week to which the report relates, subject to financial year block dates.
- Providers have a legal responsibility to ensure reports are complete, accurate and submitted on time. Inaccurate or late reports may result in families receiving incorrect CCS amounts or CCS debts.
Official sources
- Department of Education, How to manage session reports
- Services Australia, Child Care Subsidy System for software providers
This page provides general information only and is not legal advice. Providers should seek independent advice specific to their service and software environment. The technical API details on this page are drawn from Services Australia specifications and are subject to change. Always refer to the current Services Australia technical specifications for implementation guidance.
How Oiva helps. Oiva is being built with PRODA B2B integration, including session report submission via the v3 API. We are currently in integration testing with Services Australia. Join the founding cohort to receive updates on our CCS readiness as it progresses.