ACT payments
Invoices of A$25,000 or more paid by ACT Government entities — what the register is, and what it is not.
Payments are a different kind of record from everything else in this product, and reading them as awards will get you the wrong answer about every supplier in them. The page says so at the top for that reason, and so does this one.
Where you read them
The ACT's payments are a list of their own: ACT payments, under Awards in the sidebar, which the ACT payments chip at the end of the jurisdiction row on Contracts also opens. The ACT's contracts are on Contracts with the other states' awards, and its payments are never mixed into them. They are labelled payments, filtered and exported as payments, and they enter no award count and no award total. A supplier's ACT payments also appear on the supplier page, as a tile of their own beside the award figures and never inside them.
What the register is
Alongside its contracts and tenders, the Australian Capital Territory publishes the Notifiable Invoices Register: every invoice of A$25,000 or more that an ACT Government entity has paid, added monthly, under CC BY 4.0. It runs from December 2005 to the present. Each row names the entity that paid, the supplier that was paid, one line describing what for, the amount, the date the invoice was received and the date it was paid — and, on about half the rows since 2025 and almost none before, the entity's own contract number.
What it is not
A payment is not a contract award. It carries no contract value, no start or end date, no procurement method and no category, because the register publishes none of those things. One contract produces many payments, so a supplier paid monthly under an arrangement won years ago appears many times over; counting those rows as wins would inflate their record by an order of magnitude. Nothing in this product ever adds a payment to an award total, an award figure in a report, an Explore figure, a supplier's win record or a CSV of awards — payments have their own list, their own record page, their own supplier tile and their own export, and that separation is the point of them.
It is also not the whole of what the ACT spends. Anything under the threshold never enters the register at all, so a total here is a total of large invoices and not of a budget. And it says nothing about what is still to be paid: an arrangement half delivered looks exactly like one finished.
Reading the figures
Two numbers travel together wherever payments are counted, and they are deliberately not derivable from each other:
- The count is of payments, including the ones whose amount the register withheld.
- The total is of the amounts that were published. A withheld amount is ignored rather than read as zero, so a count of fifty can be a total over forty-seven.
The register also publishes credit notes — negative amounts, money that came back to the entity. They keep their sign and are netted off a total, and a single credit reads as, for example, -$12,000 (credit) rather than as a figure that looks like a loading error. Where an amount was not published at all, the row reads Amount not published, which is not the same as nothing having been paid.
Entity names are shown exactly as the register writes them. Some are titles and some are the
register's own short codes — iCBR, CED-C, HCS-Housing — and the filter matches either, exactly,
because the codes are short enough that a partial match would merge two of them.
On a record
A payment's page shows the two sets it belongs to, where the register gave the keys for them: everything else that entity paid against the same contract number, and everything that supplier was paid in the twelve months to this payment. Either block is absent rather than zero when its key is missing — a payment with no contract number has no siblings to have none of. Each links to the same list, filtered the same way, so the figure and the rows agree.
There is no AI summary on a payment and there will not be one: the register publishes one line about each, and that line is the title. In search, payments appear grouped — one result per supplier and paying entity, under the ACT payments tab, headed by what was paid for — and each opens this list filtered to that pair. They cannot be added to a pipeline — a payment is money already gone, not an opportunity to bid for.
Licence and coverage
Every payment row and every figure over payments carries the publisher's attribution line, rendered exactly as the ACT wrote it. ACT payments are included from Launch Plus up, and in the trial, along with every other state and territory record. On the Market report, ACT payments is its own choice in the Jurisdiction control and is never added to an award figure. What is loaded for each jurisdiction is listed on Jurisdictions, and an empty payments list can mean the filter matched nothing or that the register is not switched on for this deployment yet — the page says both rather than claiming either.