Konetic One Australian Community Services Management Platform Logo
Funding and reporting

DSS Data Exchange reporting for settlement and multicultural providers

The DSS Data Exchange is the reporting backbone for most Commonwealth community services funding, including SETS. Providers that treat DEX as a monthly export exercise spend days reconciling client counts against session logs. Providers that build it into the case record spend minutes.

What is the DSS Data Exchange and what does DEX reporting require?

The DSS Data Exchange, known as DEX, is the data collection and reporting system the Department of Social Services uses across most of its community grants programs, including SETS. Providers report client details, service contacts called sessions, and for some programs a partnership approach outcomes tool called SCORE. Reports are due on a quarterly cycle through the DEX portal or via a compatible upload. Konetic One builds the session and client records DEX requires as case managers work, then produces a submission ready extract.

Quarterly
Standard DEX reporting cycle for most community grants programs
0
Manual re-keying between the case record and the DEX extract
Pre-flight
Validation against DEX field rules before submission

What providers tell us

The problems this has to solve.

01

Session data entered twice

A case manager logs a contact in the case file, then someone else re-enters the same contact into a DEX upload spreadsheet weeks later, often losing detail in translation.

02

SCORE not embedded in practice

The SCORE outcomes tool is meant to be completed with the client during service delivery. When it is bolted on as a separate survey, completion rates collapse and the outcome story disappears.

03

Consent for data exchange unclear

DEX requires client consent to be recorded correctly, including for unidentified data pathways where a client does not want identified information shared. Getting this wrong risks non compliant submissions.

04

Multiple programs, one DEX ID

A provider running SETS alongside other DSS grants has to report each program correctly under the same organisation identifiers, and mixing them up produces reporting that misrepresents delivery against each contract.

Session and client data collected as the work happens

Every case contact, whether a full case management session, a brief phone check in, or a group activity attendance, is captured in the format DEX expects, with service type, delivery mode and duration recorded at the point of contact rather than reconstructed afterwards.

Client demographic fields required by DEX, country of birth, main language, visa pathway, Indigenous status, are captured once at intake and reused across every program the client touches, rather than asked again for each funding stream.

  • Session records map directly to DEX service type and delivery mode fields
  • Client demographic fields captured once, reused across every DSS funded program
  • Consent for identified, unidentified or use only data pathways recorded per client
  • Group and community activities logged as DEX compliant sessions with attendee counts

SCORE embedded in the case conversation

For programs using the partnership approach, the SCORE outcomes tool is presented inside the case management workflow at the points DEX expects it, typically at commencement and at exit or review, so the case manager and client complete it as part of the conversation about progress rather than as an administrative add on.

Because SCORE responses sit against the same goal plan the case manager is already using, the outcome data reflects the actual work rather than a best guess filled in under deadline pressure.

Where SCORE sits in the case management cycle
Point in the caseSCORE activityWho completes it
CommencementBaseline domain scores against presenting circumstancesClient with case manager
ReviewOptional interim score where the case is long runningClient with case manager
ExitFinal domain scores, closure reasonClient with case manager
Where SCORE sits in the case management cycle

A clean extract, and a place to defend it

The DEX extract generated from Konetic One is validated against current DEX field rules before it leaves the building, and the exact file submitted is retained. If a program review or an audit asks why a figure looks a certain way, the underlying case record is one click away, not a forensic exercise in an old spreadsheet.

Multi program organisations can generate DEX extracts per organisation identifier and per program without cross contaminating activity from a neighbouring contract.

  • Pre-flight validation against DEX field and code set rules
  • Retained copy of every extract submitted, matched to the reporting period
  • Program level separation for organisations holding multiple DSS grants
  • Audit trail on every reportable field change

Questions

DEX reporting, answered.

Sign in Book demo