What Got Shipped - 21/9/26 - New Zealand buyer-created tax invoices, and the Project Inbox learns to search

Published 21 September 2026 Features BCTI: raise a New Zealand buyer-created tax invoice off a certified payment schedule User Story As a commercial manager on a New Zealand job, I was raising buyer-created tax invoices outside Deep Space because the platform only understood the Australian RCTI, so I can now set a subcontract to BCTI and generate the correct New Zealand document straight off the certified payment schedule. Before BCTI is the New Zealand equivalent of the Australian RCTI, the same arrangement where the head contractor raises the tax invoice on the subcontractor's behalf, under NZ GST rules and NZ wording. Deep Space had one tax mode for that arrangement and it was Australian. A New Zealand builder either issued an RCTI-worded document that named the wrong revenue authority, or left the platform and raised it by hand. After BCTI is now a tax mode of its own on a subcontract, alongside Invoice, Claim = Invoice and RCTI. Set it at contract creation and the payment schedule carries a Tax: BCTI badge through its life. On the Documents tab of a certified schedule, a published Subcontractor BCTI template sits ready to generate, next to the New Zealand payment schedule document, with its own variable set and its own letterhead rather than the Australian body text with the labels swapped. The template seeds itself into existing New Zealand workspaces, so you do not need to build it, and the GST Number line prints as a GST number rather than as the name of the variable that holds it. Impact A New Zealand builder can now run the whole subcontractor payment cycle inside the platform: certify the claim, issue the schedule under the Construction Contracts Act, then raise the BCTI off that same certified figure. The tax document and the schedule agree by construction, because they are generated from one record rather than reconciled afterwards. Project Inbox: search every piece of correspondence in the workspace User Story As a contract administrator, finding the email that settled a scope argument meant remembering which project it was filed under and then scrolling, so I can now search the whole workspace's correspondence and refine the results down to the thread I want. Before The Project Inbox rail was a design surface. Filtering happened in the browser, over whatever had already been loaded, which meant it could only ever narrow the current page and not reach the correspondence sitting behind it. Anything older than the loaded window was invisible to it. After Search now runs on the server, across the workspace rather than inside a single project, over a purpose-built index of every piece of correspondence. The Refine rail is wired to it: narrow by the facets you actually think in, and the counts reflect the full corpus rather than the page in front of you. The results grid also gets its width back, so the scope selector no longer squeezes the search box out of shape.Impact Correspondence stops being something you file and starts being something you can interrogate. The question "when did we first tell them the slab was delayed" becomes one search rather than an archaeology exercise across projects, and the answer arrives with the thread attached. Notices: attach documents straight from the Document Register User Story As a contract administrator raising a notice, the only place I could attach from was the Explorer, so I can now pull the controlled, current revision out of the Document Register instead of hunting for a copy of it in a folder. Before The notice composer's attach modal offered one source: the CDE Explorer. The Document Register, which holds the revision-controlled, registered version of every drawing and document, was not reachable from the composer. So the drawing that went out on a notice was whatever copy someone found in a folder, not necessarily the registered revision. After The Document Register is now a source in the attach modal, sitting alongside the Explorer. Pick a registered document and the notice carries a snapshot of its register metadata, so the record shows which document number and which revision actually went out, not just a filename.Impact What you sent and what the register says you sent stop being two separate questions. On a claim or a dispute months later, the notice itself evidences the revision, which is the thing that usually cannot be proven after the fact. Submittals: files outside the register are handled to the same standard as everything else User Story As a document controller, files attached under "files not in the register" were treated as a lesser class than everything else in the CDE, so I can now trust that they land in the same place, under the same rules, with their origin recorded. Before "Files not in the register" predated the current registration work and had fallen behind it in three ways: it accepted file types the register cannot control, it did not file them anywhere predictable, and close-out reported something different from what it had actually written. After The register takes PDFs only, so what enters revision control is something that can be revised and compared. Files land in Unsorted where a document controller expects to find and place them, and the submittal pack they arrived on is recorded as the source. Close-out now reports what it wrote. Impact One registration standard across the CDE instead of two. A drawing that arrives on a submittal is handled exactly like one that arrives on a transmittal, which is what makes the register worth trusting as the single record. The RCTI document is reachable from the payment schedule that certified it User Story As a commercial manager on an RCTI subcontract, my workspace had a published RCTI template that no screen would offer me, so I can now generate it from the certified payment schedule where it belongs. Before On a subcontract set to RCTI, the Documents tab of an accepted payment schedule offered only the payment schedule template. The RCTI template could be published, assigned and correctly configured in Admin and still never appear, because the picker never asked for it. There was no route from a certified schedule to the tax document it should produce. After The picker reads the subcontract's tax mode. On an RCTI or BCTI contract it offers the RCTI or BCTI document and defaults to it, while keeping the payment schedule template selectable on the same record. Both documents are issued on these contracts, the schedule for security of payment and the tax invoice for GST, so this is an addition rather than a swap. Invoice and Claim = Invoice contracts are unchanged. Impact The document that the tax office expects now comes out of the record that certified the amount. No parallel spreadsheet, no re-keying the certified figure into a template outside the platform, and no chance of the two disagreeing. Improvements Reopen a rejected subcontract variation without starting again User Story As a contract administrator, rejecting a subcontractor variation was a one-way door, so I can now reopen it to Pending Approval when the subcontractor comes back with what was missing. Before A rejected variation was terminal. When the subcontractor supplied the backup you had asked for, the only way forward was a new variation, which meant re-keying the scope and losing the thread between the claim, the rejection and the resolution. After A Reopen to Pending Approval control on a rejected variation puts it back into the normal approval flow, with a confirmation step. The provisional schedule of values re-syncs so the line is claimable again, and approval then follows the path it always would. Impact The register tells the truth about what happened. One variation, one history, showing that it was rejected, reopened and then approved, instead of a dead record and a mystery duplicate sitting next to it. Delete a head contract created by mistake User Story As a commercial manager, a head contract created in error sat on the register forever, so I can now delete it as long as nothing has been raised against it. Before Head contracts could be created but never removed. A duplicate or a wrong-project entry stayed on the register permanently, and every report and selector carried it. After A delete control sits beside Edit on the register row and in the contract detail drawer, behind a confirmation. It refuses if anything is linked to the contract, so a live contract with claims, variations or a schedule of values against it cannot be removed by accident. Impact The register reflects the job. Mistakes made in the first ten minutes of setting up a project no longer follow it to practical completion. The revised contract sum now states its tax basis User Story As a project manager reading a subcontract, the revised contract sum gave me a number with no way to tell whether GST was in it, so I can now read the basis off the tile rather than working it out. Before The View subcontract dialog showed a revised contract sum with no tax basis stated. Every subcontract figure in Deep Space is exclusive of GST, but nothing on screen said so, and the figure people quote to a subcontractor is usually the inclusive one. After The tile labels the figure ex GST and quotes the inc GST amount underneath it. Impact One fewer place where two people in the same meeting are looking at the same number and meaning different things. Fixes Document Register filters show what they filter Before The five filter dropdowns on the Document Register toolbar truncated to "All c...", "All s...", "All s...", "All a..." and "All t...". Two of them truncated to the same string, so nothing on screen told you which was discipline and which was status. After Each dropdown shows its full label: All disciplines, All statuses, All sets, All approvals, All types. Impact The toolbar is usable without opening each dropdown to find out what it does. The Document Register toolbar, with each filter now showing its full label instead of truncating to an unreadable stub. The contact details card is legible again Before The contact details card in the Company Directory printed an internal identifier next to the email, clipped long email addresses mid-string with no wrap and no tooltip, scattered the default-contact checkboxes across different positions so the labels read against the wrong boxes, and overflowed its own width. The row action menu beside it was clipped by the table and shifted the table when you opened it. After The identifier is gone, emails wrap or truncate with a tooltip, the checkboxes sit on one axis with their labels beside them, and the card fits its own width. The row action menu now floats clear of the table and opens without moving anything. Impact The screen where you tell Deep Space who should receive what is now a screen you can read. Budget Register actuals pair each claim to its own certified amount Before Where several claim rows sat against a single subcontract schedule of values line, the Budget Register actuals and the cost code breakdown repeated one certified figure across all of them instead of reading each row's own amount. The line total was wrong, and so was every report drawing on it. After Claim rows are paired to their schedule rows, so each certified amount lands against the line it belongs to. Impact Actuals on a subcontract with a busy claim history can be relied on again. This was the kind of error that only shows up when someone adds the register up by hand and finds the cost report disagrees with the claims. Have something you want to see in Deep Space? Tell us through the feedback portal in the platform. We read every submission and a good number of the entries above started there.The Documents tab of a certified payment schedule on a BCTI subcontract, with the Subcontractor BCTI template published and ready to generate alongside the New Zealand payment schedule.