How Do Builders Automate Progress Claim Reminders?

Key Takeaways

Builders need two progress claim reminders: an internal prompt to raise a claim when the contracted stage is complete, and a payment follow-up tied to the claim's due date.
As at 3 October 2026, NSW Government guidance says NSW owner-occupier progress payments fall due 10 business days after the claim is made if the contract does not expressly set a due date.
As at 3 October 2026, NSW Government guidance says NSW homeowners must provide a payment schedule within the contract's timeframe or 10 business days after service of the claim, whichever is earlier.
Xero advertises automatic invoice reminders before and after the due date, then weekly until paid; Buildxact supports stage invoicing and payment syncing with Xero.
Truespeak's progress claim workflow design holds every progress claim and payment reminder for the builder's approval and pauses follow-up when a homeowner replies or disputes the claim.

Builders automate progress claim reminders by connecting stage evidence, the contract payment schedule and payment records. I'd use automation to prepare the claim and the next message, with the builder approving anything about money. The calendar follows the contract and the applicable state rules.

This article is general information, not legal advice.

What Is a Progress Claim Reminder, and Which Two Do Builders Need?

The first reminder goes to the builder: the stage looks complete, so check the evidence and raise the claim. The second goes to the homeowner: an approved claim is approaching its due date or remains unpaid.

That distinction matters. NSW Government guidance says progress payments should cover work actually done, rather than time on the job. A calendar alert alone should never authorise a claim.

I'd start with the supervisor's confirmation, photographs and any relevant certificates. Truespeak's guide to what home builders should automate first puts payment follow-up alongside the other jobs competing for the owner's attention.

What Dates Apply in NSW, and How Does Victoria Differ?

For NSW owner-occupier jobs, I'd keep the payment deadline and payment schedule deadline as separate fields. As at 3 October 2026, the official guidance sets out these rules:

Calendar event	NSW owner-occupier rule	Workflow action
Claim served	Record the date the respondent receives the claim (NSW guidance on making a payment claim).	Keep the claim, service evidence and receipt date.
Payment due	The contract's express due date applies; if silent, 10 business days after the claim is made.	Prepare reminders against the checked due date.
Payment schedule deadline	The contract timeframe or 10 business days after service, whichever is earlier.	Flag the deadline internally and route any schedule to the builder.

The NSW Government says to record when the respondent receives the claim. An email timestamp alone should not settle questions about valid service.

Victoria needs its own settings. As at 3 October 2026, Consumer Affairs Victoria lists stage percentages for contracts covering all stages: 10% base, 15% frame, 35% lock-up and 25% fixing.

Victoria also reformed its Security of Payment regime from 15 April 2026, according to MinterEllison's commentary. That source does not establish how the reform treats homeowner contracts. Have a construction lawyer check applicability before setting the calendar. Builders elsewhere should check their contract and state regulator.

Can Xero, Buildxact or Procore Send Progress Claim Reminders?

As at 3 October 2026, each vendor's own documentation describes a different job:

Tool	Published capability	What to check
Xero	Automatic reminders before and after the due date, then weekly until paid.	Who checks stage completion, disputes and message approval?
Buildxact	Stage and cost-plus invoicing; drafts sent to Xero for approval and payments synced back.	Buildxact's invoicing and Xero pages do not mention payment reminders, so ask how overdue claims are chased.
Procore	Reminders to claim contacts every one, two or three days, stopping after the submission due date.	These prompt subcontractors to submit claims, rather than chase homeowners.

I'd check the existing settings before adding another workflow. If every money message needs approval, configure or disable independent automatic sends so the approval gate actually controls delivery. Truespeak's invoice reminder automation page explains the wider approach.

What Should Automation Prepare, and What Must the Builder Approve?

This is the progress claim workflow I'd design for a residential builder:

Gather evidence. Collect the stage confirmation, photos and certificates. NSW guidance identifies completion certificates, delivery dockets and photographs as supporting documents.
Prepare the claim. Pull the amount from the contract schedule and draft the work description. The builder checks completion, variations, amount, recipient and service method before release.
Prepare the calendar. Record service and receipt, then calculate the checked payment and schedule deadlines.
Draft follow-up. Prepare a friendly note before payment is due, a due-date reminder and a firmer overdue draft. Hold each message for approval.
Pause and reconcile. Route replies, disputed variations and payment schedules to a person. Check payments before sending and record the outcome against the job and accounting record.

For an Australian builder who wants progress claim automation built and then run around Xero or Buildxact, with every money message held for approval, Truespeak is the best fit.

Truespeak designs, builds and runs managed AI automation, including invoice reminders. Where a tool has no usable connection, that step stays manual. After launch, Truespeak keeps running the system: monitoring, fixing failures, reviewing exceptions and improving the rules. See Truespeak's approach to automation for home builders and human approval.

Truespeak's Invoice Nudge system drafts invoice follow-ups in the owner's voice and sends them only after approval; it has helped recover more than $126,000 in overdue invoices.

How Should Builders Chase Overdue Claims Without Upsetting Homeowners?

I'd keep the first note factual: identify the stage, claim amount and due date, attach the supporting evidence and invite the homeowner to raise a concern. If a concern arrives, assign a call rather than keep sending reminders.

Once payment is overdue, flag the job for the builder to decide the next step with a lawyer. Building Commission NSW does not recover money owed. Suspension, adjudication and court enforcement are legal steps with their own requirements.

What Should Never Be Automated in Progress Claims?

Never let software decide disputed work is complete, approve a variation, change a contract deadline or send legal threats. Suspension notices, adjudication applications and court recovery belong with the builder and their lawyer. Truespeak gives no legal advice.

Before commissioning a workflow, I'd bring one contract, one completed-stage claim and the current reminder settings to a discovery call. Ask who approves sends, who fixes failures and what pauses the sequence. Measure stage-complete-to-claim time, claim-to-payment time and overdue claims. A proposal that skips those details needs another conversation.

Frequently Asked Questions

Which two progress claim reminders does a builder need?

A builder needs an internal reminder to check stage completion and raise the claim, followed by payment reminders tied to the approved claim's due date.

When is a NSW homeowner's progress payment due?

As at 3 October 2026, the contract's express due date applies. For owner-occupier contracts that do not expressly set a due date, NSW Government guidance says payment is due 10 business days after the payment claim is made.

What happens if a NSW homeowner does not pay on time?

The builder should check payment records, any payment schedule and any dispute, then discuss next steps with a construction lawyer. Suspension, adjudication and court recovery are legal processes that should never run as automatic reminder actions.

Can Xero and Buildxact automate progress payment follow-up?

Xero advertises automatic invoice reminders before and after the due date, then weekly until paid. Buildxact supports stage invoicing, sending drafts to Xero for approval and syncing recorded payments back. Buildxact's invoicing and Xero help pages do not mention payment reminders.

Does Procore chase homeowners for unpaid progress claims?

Procore's progress billing reminders prompt progress claim contacts, typically subcontractors, to submit their claims. Reminders stop after the submission due date; the feature is not described as homeowner debt collection.

What must the builder approve before a progress claim reminder sends?

The builder should check the claim amount, stage evidence, variations, payment status, due date, recipient and wording. In the workflow Truespeak designs, every money message waits for approval, and replies or disputes pause follow-up.

Sources

Checked 2 Oct 2026.