Go to top of page



The Data-matching Program is governed by the Data-matching Program (Assistance and Tax) Act 1990 (DMP Act). Under section 12 of the DMP Act, participating agencies are required to table reports in both houses of parliament.

During 2015–16 the department ceased using the Data-matching Program under the DMP Act to detect recipients at risk of overpayment. The department has completed all residual Data-matching Program reviews during 2017–18, and details of these are set out below. As required by the legislation, the costs and benefits of the Data-matching Program are included.

The department continues to act as the Data Matching Agency (DMA) as defined in the legislation. The sole activity of the DMA for 2017–18 was to undertake Data-matching Program activities on behalf of the Department of Veterans’ Affairs (DVA).


In 2016–17 the department undertook enhancements to address compliance risks previously covered by the Data-matching Program. The new approach replaced the department’s component of the activity governed by the DMP Act. The change brought the activity in line with the department’s other data‑matching activity and the Guidelines on data matching in Australian Government administration (voluntary data-matching guidelines) issued by the Office of the Australian Information Commissioner (OAIC).


The department continues to monitor the current operation of the Data‑matching Program. This is predominantly around the activities of the DMA as it completes activities on behalf of DVA. This is undertaken to ensure strict compliance with the legislation.

The statistical details of the results of DMA activities required under guideline 12 of the Schedule to the DMP Act are published in the Department of Veterans’ Affairs annual report 2017–18.

Table 87 below shows the number of residual matches completed for discrepancies identified in previous financial years.

Table 87: Results of discrepancies released for action in 2017–18



Discrepancies which resulted in a notice under section 11 of the Data‑matching Program (Assistance and Tax) Act 1990 being sent(a)


Discrepancies which resulted in action being taken(b)


Cases in which action proceeded despite a dispute about the accuracy of the data(c)


Discrepancies which did not proceed to action after the individual was contacted(d)


Cases where an overpayment was identified(e)


Cases where recovery action was initiated(f)

2 090

Cases where the debt was fully recovered(g)

8 271

(a) Section 11 of the Data-matching Program (Assistance and Tax) Act 1990 requires that people must be given written notice of any proposed action as a result of information gained through the program. People have 28 days to respond.

(b) Following the completion of a cycle, departments undertake further refinements before releasing the discrepancies for follow-up action. These refinements are to reduce the number of unproductive discrepancies that are released.

(c) In any year a small number of people may challenge the accuracy of the information on which the proposed action is based—usually because they do not fully understand conditions of eligibility for payment.

(d) There may be a number of cases where people are sent a notice of proposed action but the action does not proceed. In these cases people or a third party such as an employer are able to provide details to show that the payments received were correct.

(e) The number of overpayment cases identified, including the number of debts waived.

(f) The number of cases where recovery action was commenced on a debt. The department has two ways to recover debts—by withholding part of a customer’s entitlement or by cash repayments.

(g) Recovery of a debt can take place over a number of years and the number and value of debts raised in a year does not necessarily correspond to the number and value of recoveries.


This section sets out the savings and other benefits of the Data-matching Program. It includes details of direct savings in outlays and the actual direct costs of the program. See table 88 below for cost-benefit information.

Direct savings methodology

There are three direct savings components of the program:

  • downward variations in rate or stopping payments
  • raised debts
  • ceasing payments to new recipients for failure to comply with Tax File Number requirements.

The program is also used to match details of former recipients of each assistance agency who owe a debt to the Australian Government. Detection of these recipients means that withholdings can be made from their current entitlement to assist in repaying their debt.

Direct savings achieved

In 2017–18 the Data‑matching Program achieved $14 million in savings.

Direct cost methodology

Administrative costs

Administrative costs included computer and associated costs. The equipment used to run the program cycles has some ongoing administrative costs associated with computer hardware and software maintenance.

Salary costs

The program’s main salary costs were costs associated with:

  • managing and supporting the program within the department
  • the department’s network review activity, including its management and coordination.

Direct cost-benefit summary

When the costs and benefits (direct savings) are compared, the net benefits of the program are significant. In 2017–18 the net benefit of the program was $12.8 million.

Table 88: Direct cost–benefit summary

2017–18 actual


$14 050 800


$1 178 500

Net benefits(b)

$12 872 300

Cost–benefit ratio(c)


(a) Net savings, including the effect of upward variations.

(b) Calculated by subtracting costs from benefits.

(c) Calculated by dividing benefits by costs.


The events listed below include data matching cycles run in accordance with the DMP Act and consultation with the OAIC over the period 2017–18:

  • 24 July 2017 Cycle 3/2017 commenced
  • 18 August 2017 Cycle 3/2017 completed
  • 16 October 2017 Cycle 4/2017 commenced
  • 8 November 2017 Cycle 4/2017 completed
  • 5 February 2018 Cycle 1/2018 commenced
  • 2 March 2018 Cycle 1/2018 completed
  • 30 April 2018 Cycle 2/2018 commenced
  • 28 May 2018 Cycle 2/2018 completed.