publicdataau publicdata.au on GitHub
Published by State Revenue Office Victoria under CC BY 4.0 and republished here without change to the content. State Revenue Office Victoria has not endorsed this site.An independent republication of open government data. No government agency has endorsed it. Read more

Unclaimed money claims processed by year, Victoria

live
Publisher State Revenue Office VictoriaUpdated yearlyLicence CC BY 4.0Latest 2026-04-20Rows 21Fields 2

Unclaimed money claims from the State Revenue Office Victoria, one row per financial year from 2004-05 with the number of claims processed. The amounts paid out are in the companion dataset of unclaimed money payments.

Also called: SRO unclaimed money claims, Victorian unclaimed money statistics, Unclaimed moneys claims Victoria.

Part of Unclaimed money held by the State Revenue Office Victoria, 2 tables the publisher releases together: Unclaimed money paid out by year, Victoria.

Before you use it
What does each row hold?
One financial year from 2004-05 and the number of unclaimed money claims the State Revenue Office processed in it.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 2 fields, count and filter across all 21 rows and diff its versions. Every answer names the version and carries SRO's attribution. No key.

Then ask it: What does Unclaimed money claims processed by year, Victoria hold, and what changed in the newest version?

claude mcp add --transport http publicdata https://publicdata.au/mcp

One command. No key, no account, no sign-up.

Download it as Excel, CSV, JSON and 6 more formats

Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version never changes.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version never changes.
https://publicdata.au/d/vic-unclaimed-money-claims/latest/data.xlsx
Download

In your own tools

Use it in Excel, R, Python and more

Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.

The dated URL in the code never changes. https://publicdata.au/d/vic-unclaimed-money-claims/latest/ redirects to the newest version.

https://publicdata.au/d/vic-unclaimed-money-claims/latest/data.csv

In Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.

What is in it

Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised.

FieldTypePublisher's headerNote
financial_yearstringYearThe financial year as the publisher writes it, for example 2024-25.
claims_processedintegerUnclaimed money claims processed

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is financial_year.

The first 10 rows

From the latest version, in the publisher's order, with every field. A blank cell is shown as null.

financial_yearclaims_processed
2024-2516366
2023-2411362
2022-2314273
2021-2219050
2020-2115241
2019-2018094
2018-1918393
2017-1827020
2016-1725330
2015-1626765
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/vic-unclaimed-money-claims/latest/data.json
{
  "financial_year": "2024-25",
  "claims_processed": 16366
}

Query it without downloading

The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

How filters work

Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive except with ilike. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess than or equal to the value.
like.*text*Matches a pattern where * stands for any run of characters. Case-sensitive.
ilike.*text*The same as like, ignoring case.
in.(a,b,c)Equal to any value in the list. A value cannot contain a comma.
is.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.asc or field.desc, comma-separated. The publisher's row order when absent.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers.

Without a version the API answers from the newest loaded version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer that never changes. /api/v1/datasets/<slug>/versions lists the loaded versions. The 1 newest version is loaded; versions lists them.

The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.

https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, or give it to any client that connects to remote MCP servers. Each queryable dataset is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.

What changed

One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal.

versions.json · changes.json · history.tar.zst (3.6 KB, every version's Parquet and manifest)

Questions

How do I download Unclaimed money claims processed by year as a CSV file?

Open https://publicdata.au/d/vic-unclaimed-money-claims/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/vic-unclaimed-money-claims/v/2026-04-20/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.

Can I open Unclaimed money claims processed by year in Excel?

Yes. https://publicdata.au/d/vic-unclaimed-money-claims/v/2026-04-20/data.xlsx is a workbook with the 21 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/vic-unclaimed-money-claims/v/2026-04-20/data.csv.gz is the CSV at about a tenth of the size.

What years does Unclaimed money claims processed by year cover?

The current version covers the years since 2004. Each release from SRO becomes a new dated version here, and earlier versions stay online.

How often is Unclaimed money claims processed by year updated?

SRO releases it yearly. This site checks the portal every week and adds a dated version when the file changes.

Can I use Unclaimed money claims processed by year commercially?

Yes. CC BY 4.0 allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.

Is this the official source for Unclaimed money claims processed by year?

No. The publisher is State Revenue Office Victoria, and its page is https://discover.data.vic.gov.au/dataset/https-www-sro-vic-gov-au-sites-default-files-2025-11-unclaimed-money-claims-2025-csv. This site republishes the publisher's file without changing its content. The original sits beside every version as source.csv with its SHA-256, so the two can be compared.

What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.csv so the change can be checked.

The publisher releases Unclaimed money held by the State Revenue Office Victoria as 2 files at once, so all 2 tables here share a version date.