What Got Shipped Today - 28/10/26 - Bank detail checks on every invoice, side by side drawing compare, Final Accounts signed in the platform, duplicate programme tasks and subcontract recall

28 October 2026 Features Every supplier invoice is checked against the bank details you hold "As an Accounts lead, I need to know the moment a supplier's bank account on an invoice doesn't match what we have on file, before anyone approves a payment to a scammer." Before: KAI read the ABN off an invoice, but bank details landed as loose text in Payment Terms and nothing compared them with the Company Directory. A fake "our bank details have changed" invoice could potentially be approved and paid like any other, and one person could change a supplier's bank account on their own. After: KAI now reads the bank details on every supplier invoice and runs a Supplier identity check against the Directory: does the ABN or NZBN belong to this supplier, does the bank account match the one on file, and is that account used by any other company. A changed account turns red with the masked numbers and a reminder to call the supplier on the Directory number, not the one on the invoice. While a red flag is open, Send for Authorisation and KAI auto-progress are blocked. An Admin can override, but only with a written reason that goes on the Timeline. Changing a supplier's bank details now needs a second Admin to approve, and the Directory warns you if an account is already used by another company. Approvers see the warnings at every approval step, and the Invoice Register has an Identity issues tab and badge. An unknown ABN can be turned into a new company straight from the invoice. The same check covers subcontractor claims, payment schedules and RCTI/BCTI. Impact: The most common construction payment fraud, a changed bank account on a real-looking invoice, gets stopped at the first step instead of discovered after the money has gone. (1) KAI's identity check on the invoice: the ABN matches, but the bank account on the invoice doesn't match the one on file, so it's flagged red with a prompt to call the supplier. (1) Send for Authorisation is blocked until the check passes. (2) An Admin can override, but only with a reason that is recorded on the invoice Timeline. Compare drawing revisions and KAI writes out every change for you "As a Site Manager, when a new revision lands I want to know exactly what changed, in plain words, without hunting for clouds or squinting at an overlay." Before: Compare from the Document Register only offered an overlay, labelled by file name or v1/v2. You had to spot the differences yourself, and a reworded note or a changed spec is almost impossible to see in an overlay. The KAI change list ran from scratch every time you opened it and took 20 seconds or more. In the viewer, nothing on screen told you clearly you were looking at an old revision. After: KAI reads both revisions and writes out every change as a numbered list in the Changes panel, starting with a one-line summary of how big the revision is. Each change is tagged (Added, Detail, Note changed, Title block), explained in plain English with the old and new values, and pinned to where it sits on the sheet. Rebar changed from N16-4 to N16-400, a level annotation from 139.6.20 to 139.660, a referenced drawing number from ST-1431A to ST-1440, a grout note reworded: the text changes an overlay can't show you are spelled out line by line. KAI works out the list in the background as soon as a revision is registered, so it's ready the moment you open the compare. Compare also opens straight to the previous and current revision, labelled by Rev and date. Choose Overlay, Side by side or Swipe. In Side by side, Link zoom keeps both drawings at the same zoom and position as you pan, and Swipe lets you drag a split line across the sheet. Your last mode is remembered. In the viewer, a revision timeline lets you click between revisions (or use the [ and ] keys), an old revision shows a Superseded banner and watermark with a one-click jump to current, and the drawing strip shows document number and Rev instead of file names. Impact: You read what changed instead of hunting for it, so a one-character spec change doesn't slip through to site, and nobody builds off a superseded drawing by mistake. (1) Swipe between Rev A and Rev E (or pick Overlay or Side by side). (2) Drag the split line across the sheet. (3) KAI's change list opens with a one-line summary of the revision, ready the moment you open it. (4) Detail changes spelled out, down to the rebar, bolt and plate specs. (5) Text changes with the old and new values, and where they sit on the sheet. (1) Pick Overlay, Side by side or Swipe, with Link zoom keeping both sheets in step. (2) The older revision is labelled Rev A, Superseded. (3) The newer one is labelled Rev E, Current. Final Account statements, generated and signed in the platform "As a Commercial Manager, when a subcontract is finished I want the Final Account statement built from the real numbers and signed by both sides, without retyping it in Word." Before: There was no Final Account in Deep Space. Commercial teams typed the statement up in Word, chased signatures by email and filed it somewhere outside the project. After: Executed subcontracts have a new Final Account tab. It shows the six statement figures live from the subcontract (original sum, approved variations, final sum, certified to date, balance owing and retention held), using the same numbers as the Overview. Readiness checks stop you generating it while variations are open, a claim is waiting on a payment schedule, or a balance is still owing. Missing producer statements, O&M or warranties give a warning you can override with a reason. Pick the signatories, download a watermarked draft, then send it: you sign first, then the subcontractor. The fully signed PDF is filed to Project Documents > Commercial > Final Accounts, the subcontract moves to Final Account Agreed, and the Timeline records who signed and when. Impact: Close-out happens in the same place as the rest of the subcontract, with figures nobody can mistype and a signed record ready for the retention release. (1) The new Final Account tab with its four steps, from Readiness to Final Account Agreed. (2) The six statement figures, pulled live from the subcontract. (3) Readiness checks that must pass before the statement can be generated. The Final Account Statement PDF. (1) Contract, head contractor, subcontractor and trade, filled in from the subcontract. (2) The six figures, pulled live, with the final sum and semi-final balance underlined. (3) Signature blocks for both parties, head contractor first. (4) The retention advice. The DRAFT watermark only appears on the downloaded draft. Duplicate a programme task for every trade "As a Construction Manager, when three trades do the same activity I want to copy the task once per subcontractor, links and all, instead of rebuilding it three times." Before: A programme task holds one subcontractor. For a multi-trade activity you had to add a new task, retype the name, duration and dates, re-enter every predecessor by hand and set the subcontractor, once per trade. After: Click Duplicate next to the task name on any row of the Construction Program (hover the row to see it), or at the bottom of Task Details. Choose up to 10 copies and give each its own subcontractor and cost code. Each copy keeps the name, dates, duration, WBS group and predecessors (same link types and lags), sits directly below the original, and can also be linked to the same successors. Bookings, progress, change requests and SoV links are never copied. On the live programme you're asked once, for the whole batch, whether to notify the subcontractors now. Drafts notify at publish as usual. Impact: Multi-trade activities take one step instead of several, with no missed links, so every trade gets its own booking and the critical path stays honest. (1) In the Construction Program, hover any task row and click the Duplicate icon next to the task name. (2) Or open the task and click Duplicate at the bottom of Task Details. (1) Set how many copies you need and give each its own subcontractor and cost code. (2) Copies can also link to the same successors as the original. Recall a subcontract after it's been sent for signature "As a Contract Administrator, if the subcontractor won't sign until we change something, I need to pull the agreement back, fix it and reissue it, not delete it and start again." Before: Once a subcontract was Sent for Execution it was locked. The only options were to resend the link or upload an executed copy, so a simple change like removing retention meant deleting the subcontract and recreating it. After: The Agreement tab now has Recall to Draft while you're waiting for the subcontractor's signature or your own countersignature. You give a reason, the outstanding signing link is voided (anyone opening it is told the agreement has been withdrawn), and the subcontract goes back to Draft as a new version (v2, v3 and so on). Make your changes, approve and send it again through the usual flow. Every recall is logged on the Timeline with who, when and why. Once a subcontract is executed it stays locked, and later changes go through variations. Impact: A negotiation on one clause no longer costs you the whole subcontract record and its history. Known limitations: The subcontractor can't yet reject the agreement with a comment from the portal. That's next. (1) Recall to Draft sits on the Agreement tab while the subcontract is waiting to be signed. Improvements Programme PDFs carry your logo and the project name "As a Project Manager, the programme I send to my client should look like it came from us." Before: Export PDF printed "Construction Programme" and the date. No logo, no project number or name. After: Programme PDFs (Export PDF and Save to Project Documents in the ... menu on the Construction Program, plus Publish) now print your company logo from Company Settings on the left, the project name under the title, and a small "Powered by Deep Space" in the footer. If a logo is missing it is left out cleanly, never an empty box. Impact: The programme you send out is branded and clearly tied to the right job. (1) In the Construction Program, open the ... menu. (2) Click Export PDF. Save to Project Documents and Publish use the same branded layout. The exported programme (A3 landscape). (1) Your company logo from Company Settings. (2) The project name under the Construction Programme title. (3) A small Powered by Deep Space in the footer. Known limitations: Coming next: the project number in the title, and your client's logo on the right ("Prepared for"), uploaded once on the client in Company Directory and reused on every project for that client. Dollar-band sliding retention on head contracts "As a Commercial Manager in New Zealand, our head contracts hold retention by value band, and I need the platform to calculate it the same way." Before: Head contract sliding retention only supported milestone and cap rules, unless the contract used the NZS 3910 profile. Dollar bands were only available on subcontracts. After: Head contracts now have the Claimed Contract Value trigger, the same as subcontracts. Set ordered dollar bands with a rate for each, plus an optional overall cap. Each rate applies only to its own slice of the cumulative certified value, and the include or exclude variations setting applies to the band base. Impact: Retention on progress claims to your client matches the contract, with no side spreadsheet. Search and filter Expiring Documents "As an HSEQ Manager, I need to find which insurance certificates or worker licences are about to expire without scrolling the whole list." Before: The Expiring Documents list had no search and no type or scope filters, unlike the old All Documents page. After: Search across document, company, category, type and worker. Filter by Company or Worker documents and by Document type, which narrows to the category you picked. Clear filters resets everything in one click. Old worker links now open the worker in User Directory > Inductions. Impact: Chasing renewals takes a search, not a scroll. Fixes An invoice can't be quietly matched to another supplier's PO Change match now lists only the invoice supplier's purchase orders. Admins can show other suppliers' POs, but picking one shows a red Supplier mismatch naming both suppliers, and it can't be saved without a written reason that goes on the Timeline. The Invoice Register shows a badge on any mismatched invoice. This closes a gap where one invoice could be paid twice through two POs. KAI explains fully claimed purchase orders instead of calling them missing KAI now sees the printed PO on the invoice even when its lines are already fully claimed. It says the PO is fully claimed rather than claiming it doesn't exist in the workspace, and it no longer auto-matches to it. New purchase orders default to NZD in New Zealand workspaces A new PO's currency now follows the project's location, then your Company Settings country. NZ workspaces no longer see new POs default to AUD while everything around them shows NZD. Adding a programme link no longer pulls a task too early When you add a predecessor link, the programme now respects every predecessor the task already has, so the task and its chain don't jump earlier than their other links allow. HSEQ and Delivery Custom Forms register scrolls again Long Custom Forms registers in HSEQ and Delivery scroll all the way to the bottom again. Got feedback or an idea? Tell us through the feedback portal in the Deep Space web app. We read every one.