A payment schedule is your answer to a claim served on you. What the law requires of it, and what happens if you do not serve one in time, is in responding to a payment claim. This page covers doing it here.
Issuing a schedule serves it. When you issue, the platform generates the schedule document and emails it to the subcontractor in the same step. There is no separate send.
Starting a schedule
From the Schedule queue, choose Prepare on the claim, or open the claim and choose Prepare the payment schedule. The claim you are answering has to be recorded first. The page shows how long is left before the deadline.
Assessing each line
The schedule is a grid of the lines they claimed, with these columns:
| Column | What it holds |
|---|---|
| Claimed this period, Claimed retention | What they claimed on the line, as recorded. |
| % of claim | A way of typing the accepted figure: the share of what the line claims this period that you accept. 80% against a line claiming $3,000 accepts $2,400. It is not progress against the whole item. |
| Accepted this period | What you accept for the line. |
| Retention withheld | The retention you withhold from what you accepted. It starts at what the contract's retention terms give, and you can change it. |
| Reason | Why, wherever the line is not accepted as claimed. A line you do not accept at all is a line accepted at nil, with its reason. |
A reason is required on any line that is:
- accepted at nil, which is how a line is rejected;
- accepted at anything other than the amount claimed; or
- withholding different retention from what the claim shows.
Retention withheld can never exceed the accepted value on its line.
Each line starts accepted as claimed, with the retention worked out from the contract's retention terms, up to its limit. The claimed retention stays in its own column so you can see where the two differ. Where the contract's figure is the only difference, the line arrives with the reason "Retention withheld at the rate in the contract.", which you can edit. If you change the accepted value the retention follows it, until you type a retention figure of your own.
A request for retention back
If the claim asks for retention to be released, the request has a section of its own, Retention release, with the line named Retention release request. The section's heading shows the release requested, the retention you hold on the subcontract, and the contract's release trigger: the percentage of the contract that has to be certified before retention comes back, and whether it is reached, counting the work you accept on this schedule. A final claim often carries the last of the work and the release request together, and it is this schedule that reaches the trigger.
The heading also shows how much retention is available to release with this schedule. That is the share of the retention held that the contract lets you release once the trigger is met, counting the retention this schedule withholds, and all of it once the defects period has ended. While the trigger is not met, nothing is available.
The request starts at the amount requested, or at the amount available if that is less, so it starts at nil while the trigger is not met. Starting below the request needs your reason before you can review, because you are accepting less than was asked for. You cannot review a release above the amount available. If you reduce the work so that the trigger is no longer met, the request keeps its figure, and you are asked to set it to nil before you can review.
Beneath the grid are the totals: Accepted this period, Retention withheld and the Scheduled amount (excl. GST), which is what you propose to pay. There is also an optional Reasons summary for anything that belongs to the schedule as a whole rather than to one line.
Shortcuts
Above the grid are three shortcuts. Each one sets a starting point, and you can still change any line afterwards. None of them saves anything until you save or review.
- Accept all as claimed sets every line to the amount claimed and the retention the claim shows, and clears every reason, since no line then differs from the claim. A retention release request is accepted only up to the amount available to release, so it stays at nil if the release trigger would still not be met. It keeps any reason you gave it, and the page says so beside the button.
- Accept a percentage of each line sets every work line to a percentage of the amount claimed. Type the share you are accepting, such as 90 to take 10% off; a minus sign is not accepted. It gives the same figure as typing 90 into each line's % of claim. Before you apply it, the page shows the accepted total and the scheduled amount it would leave. You give one reason, and it goes on every adjusted line that does not already have a reason of its own. Retention is worked out again from the contract's terms on the new figures. One-off charges are left as they are. A work line you had set to nil takes the percentage like any other, so set it to nil again afterwards. The platform records the percentage you applied with the schedule. The subcontractor does not see it.
- Copy from the last schedule you issued on the same subcontract repeats how you treated each item then. A line you accepted at nil is accepted at nil again, with the same reason. A line you accepted at part of its claim is accepted at the same proportion of this claim, with the same reason. A line you accepted as claimed is accepted as claimed. Items that are new on this claim are left as they are. The button only shows once you have issued a schedule on the subcontract.
Draft, review, issue
- Save draft keeps your work without checking reasons. The schedule shows as Draft.
- Review checks every line that needs a reason has one, moves the schedule to Awaiting issue, and opens Ready to issue.
- Back to draft, on Ready to issue, returns you to editing.
- Issue schedule, at the bottom of Ready to issue, issues and serves it.
- Discard draft, on either page once a draft is saved, throws the schedule away after you confirm. The claim then offers Prepare the payment schedule again. An issued schedule cannot be discarded.
⚠️ A draft does not answer the claim. The claim stays in the schedule queue and the deadline keeps running until the schedule is issued.
Ready to issue
Before anything is sent, Ready to issue shows you what is about to go out:
- the scheduled amount, with what you accepted, the retention you withheld and what was claimed;
- the claim it answers, and how it will be served;
- the issue date it will carry if you issue it today, which is the day it is served;
- when the schedule is due, and when payment falls due under the subcontract;
- a preview of the schedule document, marked DRAFT. The copy that is sent has no watermark;
- who it goes to: the To and CC lines with each contact's roles, the addresses your company copies, where replies will go, and any of the subcontractor's contacts it will not reach, with the reason and where to fix it.
The list of recipients is the same list the email is sent to. If something is wrong, fix the contacts or your settings, then come back to this page.
If the deadline has passed, the page says first what that means under the act, and Issue schedule stays disabled until you tick the box that says you are issuing it late. The preparation page states the same consequence above the grid while you prepare it.
What issuing does
- The schedule document is generated from your figures and reasons. It states the figures excluding GST, and lists the elements the act requires of a payment schedule. It does not certify that your schedule meets them: the content is yours.
- It is emailed to the subcontractor, as a PDF attachment, from your company's name. It goes to the contacts on the contract who hold the Claims role, or to every active contact on their side if none does. Their Project Manager and Accounts contacts are copied, and so are the addresses your company copies on everything it serves (Settings → Copy your team on claims and schedules). The email states the claimed, accepted and retention figures, and the scheduled amount, all excluding GST. A reply goes to your company's reply-to address. If your company has none set, it goes to whoever issued the schedule, so that person's email address is visible to the subcontractor.
- The schedule is Issued, and the claim leaves the schedule queue. An issued schedule cannot be edited.
The claim then shows who prepared the schedule and who issued it. Prepared by is whoever last saved its figures, with Save draft or Review, and Issued by is whoever pressed Issue schedule. Neither name appears on the document or the email the subcontractor receives.
Beneath those names, the claim shows who the email went to and what became of it: queued, sent, delivered, bounced or failed, with the time. A bounced or failed email is shown in red, with the reason it was given.
If the email bounced or failed, re-send it. The delivery line then has a Re-send email button. It sends the same schedule document to the same recipients again, and the claim shows the new email as queued. It does not change the date the schedule was issued, and it is offered only while the latest email has bounced or failed, never once one is queued, sent or delivered. A re-send goes to the recipients the schedule was first sent to, so if the address itself was wrong, serve the schedule another way.
Check the recipients on Ready to issue before you issue. The platform sends to whoever is recorded on the contract, and it cannot tell whether that person is the right one to serve.
When the platform will not issue
- The contract is set to manual service. Issuing is refused if the contract's email service setting is off, exactly as serving a claim is, and Ready to issue says so in place of the Issue schedule button. Either set Serve payment schedules by email? to Yes in the contract's terms, if the contract allows service by email, or serve the schedule outside the platform and record it here. The preview is still there, so you can check the document you serve.
- The subcontractor has no active contact on the contract. Ready to issue says so and keeps Issue schedule disabled. Add one, then issue.
- The contract is not under the Western Australian act. Issuing is available for Western Australian contracts only for now, because the document states what the act requires and that has been settled only for Western Australia. The schedule queue, the claim, the preparation form and Ready to issue all say so, and offer no Issue schedule button. You can still record the claim and prepare the figures, then serve the schedule outside the platform and record it here, which starts from your draft.
- The head contractor features have been switched off for your organization. Nothing already recorded is lost, but a new schedule cannot be issued.
In every one of these cases the deadline still runs. Serve the schedule another way rather than waiting.
What the platform does not do yet
- Your company's reply-to address cannot be changed in settings yet. It can only be given when you first sign up, for your first company. Until you can set one, replies go to whoever issued the schedule.
Until those arrive, keep your own evidence of service. Asking the subcontractor to confirm receipt is the simplest way.
Recording a schedule you served yourself
If you served a payment schedule outside the platform, record it so the claim stops showing as unanswered. This is the usual case for claims you received before you started using the platform, and for any schedule the platform would not issue for you.
Open the claim and choose Record a schedule issued outside the platform. Where the platform can issue the schedule for you, the link follows Already sent it?. The page opens on a place to drop the schedule you sent. Drop it there and it is read: your reference, the date you issued it, and what it said for each line it mentions are filled in for you and marked Read, so you can see which figures came from your document. A line your schedule does not mention keeps what it started at. Check what was read against your copy and correct anything that is wrong; a figure you change is marked as edited. The file stays on the claim as your record of the schedule.
If you would rather enter it by hand, choose Type it in instead. You still attach the schedule you sent, but it is not read unless you ask for it to be. Either way, the page asks for:
- the date you issued it, which cannot be before the claim was served on you or after today;
- how you served it: email, post, personal delivery or lodgment;
- your reference for it, if it had one; and
- what it said for each line, in the same grid as above. Each line starts at what was claimed, or at your draft if you had started preparing a schedule on the claim, so change the figures to match your schedule. When you change the amount accepted on a line, its retention is worked out again at your contract's terms, as it is when you prepare a schedule here, unless the retention was read from your schedule or you typed a different figure, in which case it is kept. No reason is required, because you are recording a schedule that has already gone out as it was.
Recording does not send anything. No document is generated and nothing is emailed to the subcontractor. The claim leaves the schedule queue and its reminders, and the figures you enter count towards what you have certified and the retention you hold. The claim shows the schedule as issued outside the platform, and who recorded it.
A recorded schedule cannot be edited, just like one issued here, so check the figures and the date against your copy before you record it. If you had already started preparing a schedule on the claim, the form starts from that draft's figures, reasons and summary, and recording replaces the draft with what you record. If you record the draft exactly as it was saved, the claim still names whoever prepared it beside whoever recorded it.
Recording many schedules from a register
If you served schedules on a subcontract's claims before you joined, you can record them all at once from a register instead of one claim at a time. On the subcontract's claims, choose Record schedules already sent. The option shows while any claim on the subcontract is still waiting for a schedule.
The register is a CSV file with one row per schedule and these columns:
- Claim: the claim's reference, as it is recorded here;
- Issued: the date you issued the schedule, as 2026-03-06 or 6/3/2026 (day first);
- Served by: Email, Post, Personal delivery or Lodgment;
- Certified ex GST: the total your schedule certified;
- Document: the file name of the schedule you sent;
- Reference: your own number for the schedule, if it had one; and
- Paid on and Amount paid: if you have already paid the claim, the date you paid it and the amount, including GST. Fill in both or neither.
Download a register to fill in gives you a file already listing the subcontract's claims that are waiting for a schedule. If you keep your register in a spreadsheet, save it as CSV. Upload the register together with the schedule documents it names.
Before anything is recorded, every row is shown with what will happen to it. A row whose certified total is the claim's total records each line as claimed.
A row whose certified total is less than the claim's is recorded by spreading that total across the claim's lines pro rata: each line is certified the same share of what it claimed, to the cent, and withholds the retention your contract takes on that figure. Because the register gives only a total, the platform chose those line figures, not your schedule, so the claim and the Register export say Certified total spread pro rata beside them. If your schedule certified the lines differently, record it from the claim instead, where you can set each line.
Some rows are skipped and have to be recorded from the claim:
- a row certified for more than the claim's total;
- a row certified short on a claim that asks for retention back; and
- a row certified short on a claim that includes a one-off charge.
A row is also skipped if no claim has its reference, if two claims or two rows match it, if the claim already has a schedule, if its document was not uploaded or another row names the same document, or if its date, method or figure cannot be read. The reason is shown on the row.
Recording from a register works exactly like recording one schedule: nothing is sent, nothing is generated, and each claim leaves the schedule queue. Each row is recorded on its own, so one row that cannot be recorded does not stop the others. When it finishes, you see which rows were recorded and why any others were not.
A row with Paid on and Amount paid also records that payment against the claim, after its schedule, as if you had recorded it on the claim's Payment card. A claim you paid in full is then not shown as owing on Due to pay. If the payment cannot be recorded, for example because it is more than the schedule made payable, the claim's payments are recorded in Xero, or a payment is already recorded against the claim, the schedule is still recorded, and the row says why the payment was not, with a link to the claim's payments.
Sending the bill to Xero
If your company is connected to Xero, you can record what an issued schedule certified as a bill from the subcontractor in your own Xero, so the payable is in your books without typing it in again.
First, set up bills once for the company under Settings → Xero setup → Bills for payment schedules you issue: the account subcontract work is a cost in, the liability account for retention you hold, and the GST rate for each tax treatment. Then open the claim. Once its schedule is issued, the Bill in Xero panel offers Send bill to Xero, which shows the lines, the account each one goes to, the totals and the due date before anything is sent.
- The figures are what you certified. Work and charges are at the amounts on your schedule, and retention you withheld comes off, so the bill falls due at what you owe now. They match the subcontractor's own tax invoice for the claim.
- The bill is dated the day you issued the schedule. You can choose another date, for example to keep it out of a period you have closed in Xero.
- The reference is the subcontractor's claim number and the job, so the bill and their invoice read the same.
- The bill is approved in Xero, with nothing attached, and nothing is sent to the subcontractor. Sending the bill is not serving the schedule, and it is not paying it.
- A schedule has one bill. If one was sent wrongly, void it in Xero; the platform notices and lets you send it again. A bill is never corrected from here, because an issued schedule never changes.
The platform will not send a bill for a schedule you recorded as issued outside the platform, because it is very likely in your Xero already. It also says what to fix when the bills setup is incomplete, an account has gone from your Xero, or the subcontractor is not linked to a Xero contact for your company.
Sending the bill to MYOB
A company connected to MYOB rather than Xero records the bill in its MYOB company file the same way, from the claim's Bill in MYOB panel. A schedule has one bill, in one of the two. Bills for payment schedules you issue covers the setup and what the bill looks like in MYOB.
Paying the claim
Once the schedule is issued, record what you pay against the claim in its Payment panel, or choose Mark as paid to record the whole balance at once. Recording payments against a claim has the detail, and the Due to pay tile on your overview adds up what is still to pay across your subcontracts.
Who can do this
Owners, admins and members can prepare and issue a schedule, record one served outside the platform, and send its bill to Xero or MYOB. Only owners and admins can set up bills in the Xero or MYOB settings. paymentclaims.ai staff cannot do any of these on your behalf, including when they are helping set your account up.