CHSP DEX Reporting: Provider Data and Reconciliation Checklist

DEX reporting is the end of an operational chain: an approved service, a provider's funded activity, actual delivery and the records used to prepare the submission. A technically accepted file is not, by itself, proof that every reported service is appropriate. The CHSP DEX Guide effective 1 July 2026 expressly distinguishes the system's general functions from CHSP program requirements.

This is Statura Care's suggested provider review checklist, not a replacement for your grant agreement, current DEX guidance or reporting officer's review. Sources checked 6 September 2026.

Keep a controlled mapping of the provider's funded activities to the relevant DEX structure. Check the organisation, outlet, program activity, case and service definitions used by your system. Do not let a convenient software category become the reporting authority.

Ask who owns changes to the mapping and how their effective dates are recorded. A changed service label should not silently rewrite an earlier reporting period. In a software demonstration, inspect one reported row and trace it back to the source service and mapping version.

Check My Aged Care identifiers in the appropriate program-specific fields. The CHSP guide warns against using identifiable information in client, case and session identifiers. Treat information needed for service delivery separately from what is required or permitted in an external report.

Your internal checklist should identify missing identifiers, duplicate records and unresolved reporting-permission questions. Give each exception an owner. Avoid fixing an identifier by guessing, copying another person's value or substituting a dummy number.

Use synthetic data for vendor demonstrations. A reporting example does not need real client names, addresses or health information.

Groups, meals, transport and individual visits need different questions at the point of capture. Review actual attendance, delivery dates, cancellations, output units and applicable service-specific fields. Avoid treating a rostered booking as evidence of completed delivery.

A practical test is to start with a fictional group of six attendees, correct one attendance record and inspect every downstream total. This is a software test scenario, not a universal DEX calculation. The expected outputs must follow the current definition for the particular activity.

Keep contribution amounts, outputs and provider costs distinguishable. A dollar collected from a client and an hour of service are not interchangeable reporting measures.

Use the current DEX bulk-upload technical specification and relevant reference data to validate file structure and handle errors. Technical validation and the provider's substantive review serve different purposes.

Before release, your review record should identify the reporting period, source records included, unresolved exceptions, preparer and reviewer. Record the file version and when it was produced. Give the team a reproducible way to explain why a source record was included or excluded.

If a vendor describes its reporting as automated, ask which steps are automated: preparation, validation, download, upload or receipt reconciliation. Ask to see the actual supported route.

Track prepared, reviewed, exported, submitted and accepted as different states. A download should not mark a submission accepted. Record the external result and preserve enough detail to distinguish accepted rows from exceptions needing attention.

Test a rejected row followed by a correction. The system should make it possible to identify the original source record, the reason for rejection, the correction and the replacement reporting outcome. Ask how it avoids resubmitting accepted work unnecessarily.

Keep a separate reporting calendar based on the current CHSP obligations and your grant. Do not assume the generic DEX collection window defines every CHSP deadline.

Ask the supplier to demonstrate the whole chain using your service mix: client approval, funded activity, delivery, contributions, file preparation and external-result reconciliation. A screen labelled DEX or a downloadable XML file does not establish the full workflow.

Review Statura Care's CHSP software with your reporting and operations teams. This page does not claim a live direct DEX integration. Our CHSP software planning guide provides a broader buying brief, including migration and mixed-program scenarios.