Payment claims and schedules under the NSW Security of Payment Act
Palydin counts the payment schedule window for NSW contracts in business days, skipping weekends and NSW public holidays, and prints the Act's wording on every payment claim and payment schedule it issues. The claim, the assessment, and the reasons stay on one record.
01The problem
The NSW clock starts when the claim is submitted
When a claim is submitted on a NSW contract, Palydin records the response due date ten business days later and shows it on the claim, so the assessor works to the date rather than finding it.
Without a shared record
- The ten business days are counted by hand, and a public holiday is missed.
- A claim goes out without stating it is made under the Act.
- The payment schedule is a spreadsheet export with reasons in an email.
- Nobody can show when the claim was received or the schedule issued.
- Supporting documents are collected after the claim has already gone.
With Palydin
- Response due date counted in NSW business days from submission.
- Every claim and schedule states it is made under the NSW Act.
- Reasons recorded on each line the assessor reduces.
- Sign-off before a schedule issues, when your organisation needs it.
02How it works
From contract to audit, step by step.
- 01
Set the contract to NSW
Choose NSW as the contract's jurisdiction. Deadlines, dates, and the wording on issued documents follow it.
- 02
The claim starts the clock
On submission Palydin records the response due date ten business days later, skipping weekends and NSW public holidays.
- 03
Assess with reasons
Reduce lines with a reason on each, so the schedule explains the difference between the claimed and scheduled amounts.
- 04
Issue the payment schedule
The schedule's cover letter gives the scheduled amount, points to the reasons, and states it is provided under the NSW Act.
Every step writes to the same record
Nothing is re-keyed between stages, so the audit trail is a by-product of doing the work.
- Contract (NSW)
- Payment claim
- Response due
- Assessment reasons
- Payment schedule
- Audit
03Who it's for
Useful from either side of the contract.
- Subcontractors
- Issue claims that state the Act and see the response due date as soon as you submit.
- Head contractors
- Assess subcontractor claims to the NSW deadline and issue a schedule with reasons.
- Principals
- See every NSW claim's response date across your contracts.
04Built for Australia
Built around the records commercial teams argue over.
Palydin speaks Australian construction: progress claims, retention, GST, payment schedules and the claimant–assessor relationship between subcontractors, head contractors and principals.
Australian contract language
- Progress claims
- Claim periods, claimed-to-date values, prior assessments, supporting documents and submitted status stay together.
- GST and retention
- GST, retention deductions, held amounts and release context stay visible inside the claim workflow.
- SOPA payment schedules
- Payment schedule dates sit beside the claim, the assessment reasons, the contract terms and the audit history.
- Both sides of the contract
- Subcontractors prepare the record. Head contractors and principals assess from the same file.
Controls both sides can trust
- Audit trail
- Claim changes, assessment reasons, variation decisions and retention activity stay attached to the record.
- Access controls
- Role-based permissions keep claimant, assessor, admin, commercial and viewer work separated.
- Counterparty scoping
- External parties only see the contracts they are connected to, never the rest of the portfolio.
- Contract-cited AI
- Answers point back to the contract material, so the team can check the source before acting.
05Questions
Common questions
Which NSW Act does Palydin work with?
The Building and Construction Industry Security of Payment Act 1999 (NSW). Contracts set to NSW count deadlines in NSW business days and print the Act's name on issued claims and schedules.
How long does a respondent have to give a payment schedule in NSW?
Under the NSW Act it is ten business days after the payment claim is served, or earlier if the contract requires it. Palydin counts the ten business days from submission. If your contract sets a shorter time, work to that.
Does Palydin prepare the NSW supporting statement?
No. A head contractor's claim to the principal needs a supporting statement. Prepare and sign it as you do now, and keep it with the claim's documents in Palydin.
Is this legal advice?
No. Palydin tracks dates, wording, and records. How the Act applies to your contract is a question for your team and advisers.
Put your next claim on the record.
Book a 30-minute walkthrough on one of your contracts. When it fits, we set up a project pilot on a live contract and your team judges Palydin on its own numbers.