Product
Overview
The commercial operating system for construction. Capture a commercial event once, every downstream workflow stays connected.
See the whole product →
Contract models
Fixed, cost plus & open book
Claim a fixed sum, reimburse at actual cost, or bill fully open book. ClaimStack handles each, the right way.
See how →
Solutions
Overview
Built for every side of the contract. One commercial record the whole project team can trust, head contract to supplier.
See how it fits your role →
For subcontractors
Free to collaborate
Invited to a project? Submit claims and variations in a format that holds up, free forever.
See the plan →
Resources
Overview
Practical guides on claims, variations and contracts, plus how ClaimStack connects, who's behind it, and how we keep your commercial data safe.
Read the blog →
Get started
See it on your project
A 30-minute walkthrough on your numbers, where the margin usually leaks.
Book a demo →
Pricing
Solutions/Payment claims

Claim with confidence. Get paid on time.

Progress claims and payment schedules are how money actually moves on a job, up to the party above you and down to the subcontractors below. ClaimStack runs the whole cycle on the live contract position, compliant with Security of Payments and cent-perfect, so claims go out on time, assessments hold up, and cashflow stops depending on a spreadsheet rebuilt from memory at month-end.

The commercial OS for payment claims

The most important number on the job, right every time.

Nothing on a project has to be more accurate than a payment claim and the schedule that answers it. ClaimStack turns the monthly cycle into a disciplined routine, the claim built from the live contract position, the schedule built from the claim, claimed and assessed reconciling to the cent, and each claim updating the live cashflow as it goes. Money moves on time, assessments stand up, cashflow tracks what has actually been claimed, and no one starts the month rebuilding numbers in a spreadsheet.

The claim is where cashflow is won or lost.

01 Claims rebuilt in a spreadsheet each month, so numbers drift and the claim goes out late.
02 A claim that does not match the live contract position invites a dispute you then have to argue.
03 Assessments issued without reasons or a compliant schedule leave you exposed under Security of Payments.
04 When a claim is queried, the backing detail is scattered and cashflow stalls while it is sorted out.

From the live position to a compliant schedule, without the spreadsheet.

01 · Prepare

Build the claim from the live position, not from memory.

Apply your cashflow for the period and the claim populates line by line from where the job actually is, contract works and variations together. Your insurances and licences attach automatically from the company library, flagged the moment one is expiring, so the claim goes out complete and on time instead of being rebuilt in a spreadsheet the night before it is due.

PC-0142 · New payment claim
July progress claim
Draft
Apply cashflow4 lines populated for Jul 2026
Preliminaries$42,000
Concrete structure$168,000
Structural steel$96,500
Facade & glazing$74,500
This claim (ex GST)$381,000
Attached from your library
Public Liability Insurance$20,000,000Current
Professional Indemnity$10,000,000Current
Workers CompensationCurrent
Builder's LicenceExpiring · 21d
Insurances & licences attach automaticallyFlagged before they expire
02 · Submit

Lodge once, straight to the other party.

Lodge the claim and its PDF goes direct to whoever it is addressed to, with the line detail and attachments. From that moment both sides hold the same dated record, so there is no re-keying, no separate email, and no argument later about what was claimed or when. The clock on the response runs against a record you both share.

PC-0142 · Submitted
July progress claim
Lodged
PDFPayment claim PC-0142.pdfDelivered
Claiming partyAssessing party
PreparedReconciled and ready28 Jul
LodgedSent to the assessing party31 Jul
ReceivedSame record, both sides31 Jul
Claimed $381,000+ GST $38,100
Claimed this period$419,100
03 · Assess

Respond with a schedule that holds up.

Certify or adjust each line with a reason, then issue a payment schedule that is compliant with Security of Payments in reply. Claimed and assessed reconcile to the cent, GST and retention calculated rather than hand-typed, and every adjustment is on the record. If a claim is ever disputed or adjudicated, the schedule and its reasons already stand behind you.

PC-0142 · Payment schedule
July progress claim
Scheduled
ScopeClaimedAssessed
Preliminaries$42,000$42,000
Concrete structure$168,000$168,000
Structural steelProgress behind claimed percentage$96,500$88,000−$8,500
Facade & glazingUnfixed materials on site excluded$74,500$61,000−$13,500
Subtotal (ex GST)$381,000$359,000
GST (10%)$38,100$35,900
Scheduled (inc GST)$419,100$394,900
Every adjustment carries a reason−$24,200 scheduled vs claimed
Control and compliance

Manage the risk, in real time.

A payment claim is a legal instrument with deadlines attached, so the risk is not only getting the number right, it is getting it out on time, in the right form, with the right sign-off. ClaimStack runs all of it on the live position instead of a spreadsheet, so claiming and assessing stays controlled, consistent and on the clock, every month.

Consistent format

Every claim and schedule goes to the client in the same professional, compliant format, so nothing is reformatted per client and nothing looks ad hoc.

Deadlines monitored

The statutory Security of Payments dates are tracked and flagged ahead of time, so the dates that put payment, or your position, at risk are in front of you while there is still room to act on them.

Approvals attached

Claims and schedules run through their approval workflow before they leave, so nothing is issued without the right sign-off behind it.

Off the spreadsheet

The whole cycle runs on the live commercial position in real time, not a workbook rebuilt at month-end, so the risk is managed as it happens.

However you bill

Claim up. Assess down.

Apply for your money from the party above you, and assess the claims that come from below, both on the same disciplined process. Each contract bills the way it runs, a direct invoice or a full payment application.

Direct invoice

Send an invoice with all of its backing detail attached, for contracts that do not run a formal assessment.

Full payment application

Run the whole cycle: the claim, a line-by-line assessment and a payment schedule compliant with Security of Payments.

What the business gets

Better outcomes, every claim run.

Claims out on time, every month
Cashflow updated from every claim
Cent-perfect, claimed to assessed
Compliant schedules, issued by default
A dispute answered from the record
No claim rebuilt from a spreadsheet
Both
Claim up, assess down
0
Spreadsheets at month-end
Cent
Perfect, claimed to assessed
SOP
Compliant by default
Time back

One claim run a month, not a week of rebuilding.

The claim is built from the live position and the schedule from the claim, so the monthly cycle is a routine, not a reconstruction. No collating backup by hand, no re-keying the assessment, no chasing which version is current; the time goes into the numbers, not the paperwork.

PreparationNo claim rebuilt in a spreadsheet each period.
AssessmentNo schedule retyped line by line by hand.
BackupInsurances, licences and detail attached, not chased.

Frequently asked

How is a payment claim built each month?

You apply your cashflow for the period and the claim populates line by line from the live contract position, contract works and variations together, rather than being rebuilt in a spreadsheet. Your company insurances and licences attach automatically from the library and are flagged before they expire, so the claim goes out complete and on time.

What makes the assessment hold up under Security of Payments?

Each line is certified in full or adjusted with a reason, and the response is issued as a compliant payment schedule. Claimed and assessed reconcile to the cent, GST and retention are calculated rather than hand-typed, and every adjustment, reason and delivery record is retained. If a claim is ever adjudicated, the schedule and its trail already stand behind you.

How do we make sure nothing misses a Security of Payments deadline?

The statutory dates on every claim and schedule are tracked and flagged before they fall due, so responses go out inside the window rather than a day late. Because a missed date under Security of Payments can cost you the right to withhold, or the right to be paid, taking the timing off a manual calendar and onto the live record removes one of the biggest risks in the whole cycle.

Why does a consistent claim format matter?

Every claim and schedule leaves in the same professional, compliant format, so there is nothing to reformat per client and nothing that looks ad hoc or invites a query on presentation alone. A claim that is clear and consistent is quicker to assess, harder to dispute, and reflects well on the business every time it lands in a client inbox.

Can we both claim and assess on the same platform?

Yes. You apply for payment from the party above you and assess the claims that come from below, both on the same disciplined process. Each contract bills the way it runs, a direct invoice with its backing attached, or a full payment application with a line-by-line assessment and a compliant schedule.

How does this protect cashflow?

Every claim updates the live cashflow, so your expected position reflects what has actually been claimed and assessed rather than a guess. And because the claim is built from the live position and lodged on time, and the assessment is a routine rather than a rebuild, money moves on schedule instead of stalling while numbers are argued or backup is collated. Both sides work from one dated, cent-perfect record, so there is less to dispute and less that holds a payment up.

The claim is how you get paid.
Make it airtight.