The shortest path from an empty account to a served claim runs through five things, in order. Each one exists because the next depends on it.
What to have to hand
- Your ABN or NZBN. The platform looks the rest up from it. If the registry is unavailable, you can enter your legal name yourself.
- A trading address. It appears on the claim as the claimant's address.
- One contract you are about to claim against, with its schedule of items and rates.
- The head contractor's details: their ABN or NZBN, and the person or inbox that receives claims.
The order things happen in
- An organization. The billing boundary, and where members live. It can hold more than one trading entity.
- A company. The trading entity that holds the contract and serves the claim. Most accounts have exactly one.
- A counterparty. Whoever owes you under the contract, usually your head contractor. The registry lookup fills in the rest from the business number.
- The contract. Its items, its retention terms, how often you may claim, and its jurisdiction. The jurisdiction is what every statutory deadline the platform counts is counted against, so it is the field to get right. See timing by jurisdiction.
- The claim. The platform drafts it from the contract; you confirm what was completed in the period, and serve it.
Three things worth knowing before you start
Say where the job is up to first. New contract asks whether the job has been claimed on yet, and if so whether claims go through the head contractor's portal, before you upload anything. The answer decides which documents it looks for: the subcontract alone for a job not claimed yet, and for one already under way the subcontract with every claim you have made on it and the schedules you got back, latest first, or your claims register. Send them all: each claim is then recorded in the contract's claim history. Drop everything you have for the job in one go; each file is sorted onto its line as it uploads.
Say when claims are submitted, then what they cover. The contract form asks on which day each claim is submitted, then whether each claim covers the calendar month or only the work up to the day it is submitted. Most contracts that say "submit by the 25th" still claim the whole month; Queensland and Western Australia start on the second answer, because their acts value only work already carried out. The last day of what a claim covers is its reference date, and reference dates and claim periods explains what it does. If your contract moves the submission day in some months, such as December brought forward for the Christmas shutdown, add each of those months under the first question with its own day; where a claim covers work up to the day it is submitted, that month's claim then covers work up to its own day. Check the preview of your next two claims under the questions, which also shows the next claim in each month with a different day. What a claim covers can't be changed once a claim has been finalised, but the submission day usually can, and so can a month's different day under the calendar month. When a contract starts late in a month, its first claim period can be only a few days long. The form then asks whether you will claim for those days or roll the work into the next month's claim, which is the default: the short period is recorded as no claim, and because claims are cumulative the next claim covers the work from the start date.
You do not have to have served your claims here to track them here. A contract can be set up with the claims you have already served against it, so the retention held and the contract's history are right from the first period you run on the platform. See claim history.