Verify customers' concession entitlements with Services Australia through the CCeS batch enquiry service

Overview

The CCeS integration verifies that customers hold the concession or pension entitlement they claimed (Pensioner Concession Card, Health Care Card, DVA Gold Card, War Widow(er) card) against Services Australia’s Centrelink Confirmation eServices (CCeS).

It works as a batch file exchange with the CCeS Batch Enquiry portal - you download a request file from Dataforce ASAP, lodge it on the portal, then upload the response file back into Dataforce ASAP:

  1. Dataforce ASAP builds a request file from the customer details and mapped question answers (CRN, date of birth, claimed priority group, consent)
  2. You lodge the file on the CCeS Batch Enquiry portal
  3. The portal’s response file is uploaded back into Dataforce ASAP, and each appointment’s verification status updates - Verified, Unmatched, Failed or Rejected

Enabling and configuring

Enable CCeS under Config Integrations Integration Settings.

Setting Purpose
Sender Organisation CRN The organisation CRN issued by Services Australia - included in every request file.
CRN Question The question(s) holding the customer’s Centrelink CRN or DVA file number.
Date of Birth Question The question(s) holding the customer’s date of birth.
Priority Group Type Question The question(s) recording which card or entitlement the customer claims.
Customer Consent Question The question(s) recording customer consent. Appointments without consent cannot be exported.
Confirmation Date Source Activity Date, or Question (a Confirmation Date Question field appears when Question is chosen).
Include Address Whether to include the property address in Customer Detail and DVA requests.

Each question mapping accepts multiple questions - only one is expected to be answered per appointment.

The CCeS Verification Export screen

Open Admin Import/Export CCeS Verification Export (global administrators only).

  1. Choose a Search Type - by submission Export Batch, or by Submission Eligibility Date range.
  2. Choose the Request Type - Status Request (Centrelink), Customer Detail Request (Centrelink), or External Department / DVA. The customer list is filtered so the CRN format matches the request type.
  3. Click Search. The grid shows each appointment’s customer, CRN, consent, and current Verification Status (Not Submitted, Pending, Verified, Unmatched, Failed, Rejected). Appointments without recorded consent are greyed out and cannot be selected; already-verified rows are deselected automatically.
  4. Select the rows to verify and click Download XML. You are asked for your CCeS portal User ID (your Services Australia portal login, not your Dataforce ASAP username). Dataforce ASAP produces a zip containing the request file and marks the selected appointments Pending.
  5. Lodge the file on the CCeS Batch Enquiry portal, and when the response is ready, click Upload Response and upload the response or rejection file (zip or xml). The grid refreshes with the updated statuses, and the Match Code Definition column translates each response code to plain English.

Where verification status is visible

  • Submission Centre - when CCeS is enabled, batches show a CCeS column with Pending / Verified / Unverified counts. The Pending and Unverified pills deep-link straight into the CCeS Verification Export screen, pre-filtered to that batch.

Automatic re-verification on customer changes

If a customer’s name or property address changes, any existing verification results for their appointments are cleared automatically (pending requests are left alone) so the entitlement is re-verified against the updated details. These clears are recorded in the audit log.