What Got Shipped Today - 1/10/26 - Subbie bank details land on the RCTI, draft notices print before they go, and claim approvals take one click

1 October 2026 Thursday, and the money side of the wheel got a serious tune-up. Subcontractor bank details finally have a proper home, draft notices can be checked on paper before they are issued, payment schedules approve in one action, and the client's payment schedule deadline is now on every claim. Features Subcontractor bank details, kept in the Company Directory and printed on RCTIs and BCTIs "When I raise an RCTI on the subbie's behalf, it has to show their account, and I need to know if anyone changes it." Before: There was nowhere in the Deep Space web app to record a subcontractor's bank account. RCTIs and BCTIs printed no payee bank details at all. After: The Company Directory drawer has a new Payment Details tab: account name, BSB and account number (Australian and New Zealand formats), plus optional bank name and SWIFT. Formats are checked as you type. Only roles with Admin edit rights can view the full number or change it, everyone else sees it masked to the last three digits, and portal logins cannot see it at all. Every add, change or removal is logged on the tab with who, when and the masked old and new values, and a change alert email goes to the Remittance Email in Company Settings (or to your admins if that is blank). RCTIs and BCTIs now print the subcontractor's account in a Payment to Subcontractor block, and if the details are missing, generation is stopped with a message pointing you to the tab. Impact: Self-billed tax invoices pay the right account, and a changed bank account, the classic invoice fraud move, never slips through unnoticed. Screenshot: the Payment Details tab in the Company Directory drawer. 1. The new Payment Details tab. 2. Format checks that catch a short BSB before anything is saved. Known limitations: Open Admin, Document Templates once in your workspace so the updated RCTI and BCTI templates load. Templates your team has customised need the payee block added by hand. Export a draft notice as a PDF before you issue it "I want to print it, or send it to our engineer to check, before it goes out under my name." Before: Only issued notices could be downloaded. The only way to see the finished document was to issue it, which took the next number, emailed the recipients and made it part of the contract record. After: The notice composer has an Export PDF button in its footer. It saves your edits, then downloads the draft exactly as it will look once issued (letterhead, type, project, contract, fields, recipients and attachment list), with a DRAFT watermark on every page, no notice number and no issued date. Nothing is numbered, sent or recorded. It works for every notice type, in the Deep Space web app and in the Client Portal. Impact: Notices get reviewed and approved before they leave the building, without a test notice ending up in the contract record. Screenshot: the notice composer on a draft General Correspondence notice. 1. The new Export PDF button in the footer. 2. No notice number until it is issued. Approve all remaining Schedule of Values lines in one action "I have already reviewed the claim. I should not have to click Approve on 80 lines to finish the certification." Before: After reviewing a subcontractor claim, the line items on the payment schedule's Schedule of Values still had to be approved one at a time before the schedule could be submitted. After: The Schedule of Values on a subcontract payment schedule now has Approve all remaining. It approves every line you have not yet decided at its current certified value, shows how many lines and what total before it applies, and leaves lines you have already approved, part-certified or rejected untouched. Each line is still recorded as approved by you, with a time stamp. Impact: Large claims certify in minutes, and every line still carries its own decision for the payment record. Screenshot: the Schedule of Values on a draft subcontract payment schedule. 1. Approve all remaining, with the count of undecided lines. 2. A part-certified line, which is left as is. 3. An undecided line, approved at its certified value. Purchase order lines show what has been invoiced and what is left "Which cost code does the leftover PO balance belong to? I should not have to guess when I close it out." Before: Invoiced to Date and Balance Remaining were only shown for the whole purchase order. Closing out a PO meant adding a negative variation and picking a cost code by hand. After: Each PO line now shows Invoiced and Remaining. A Close out action releases each line's remaining balance back to its own cost code. A PO or line can no longer be reduced below what has already been invoiced against it. Impact: Every dollar of an open commitment sits against the right cost code, and closing out a PO is one action instead of a calculation. Screenshot: a purchase order's line items. 1. Invoiced and Remaining on each line. 2. The Close out action. The client's payment schedule deadline, on every progress claim "If the client misses their payment schedule deadline, I need to know that day, not when I go looking." Before: Head contract progress claims only tracked the payment due date. Nothing showed when the client had to serve its payment schedule, the date that decides what happens if they stay silent. After: Head contracts now have a Payment Schedule Response Period, set in business, working or calendar days. The contract's region suggests a default, and you can override it to match your contract. Every progress claim then gets a Schedule Due date worked out from the claim date, shown in the Progress Claims (to client) register next to Payment Due. Once that date passes with no client payment schedule recorded, the claim shows an overdue warning. Impact: The deadline that protects your claim is visible on every claim, and an overdue client schedule is flagged on the day. Screenshot: the Progress Claims (to client) register. 1. The new Schedule Due column, worked out from each claim date and the head contract's response period. Known limitations: The suggested regional defaults are a starting point only. Always set the period your contract states. Improvements Delay damages rate and cap on the head contract Before: The head contract recorded liquidated damages (what you pay for finishing late) but had nowhere to record delay damages (what the client pays you for each day of compensable delay). After: The head contract now has a Delay damages rate (per day or per week) and a Delay damages cap (a percentage of the contract value or a fixed amount), directly under the liquidated damages pair. Both are optional. Impact: Both entitlements your contract states, in both directions, are on the head contract, ready for your delay and extension of time notices. Screenshot: Notices & Contract Administration on a head contract. 1. The new Delay Damages Rate. 2. The new Delay Damages Cap, directly under the liquidated damages pair. Fixes New Zealand workspaces are no longer asked for a BSB New Zealand banks do not use a BSB, but head contract progress claims and tax invoices on NZ workspaces were blocked until one was entered. NZ workspaces no longer need a BSB, and documents with no BSB to print now leave the empty BSB line off. My Approvals opens invoice and payment schedule records Selecting an invoice or payment schedule approval in My Approvals showed a summary with no way to open the record, and the matched PO appeared as a long system code. Every approval now opens its own record, and the PO shows its readable number. Screenshot: an invoice approval opened from My Approvals. 1. The button that opens the invoice record. 2. The approval summary. Sub Claimed to Date on subcontract payment schedules adds up correctly Sub Claimed to Date on a subcontract payment schedule could overstate what the subcontractor had claimed, and the summary Variance carried the error. It is now previously approved plus this claim. Head contract progress claims count in the right order A claim entered out of order could be counted twice in the running balances on a head contract. Claims are now ordered by their sequence rather than the period typed in, and an already accepted client payment schedule cannot be accepted a second time. Large ITP registers load every page ITP registers showing several form types could return an error and go blank from page three. They now load every page. Got feedback on any of today's updates? Tell us through the feedback portal in the platform. Every note goes straight to the crew building the next release.