What Got Shipped Today - 21/7/26

21 July 2026 Today's launches pull the money side of the build tighter together. Invoices now travel straight into Xero, a matched invoice builds its own claim and payment schedule, approved commercial documents can be reopened cleanly, notices carry their full history with them, and the drawing register finally lets you read what you are registering. Here is what went live. Features Push a head contract invoice straight to Xero "I am the commercial manager. I have just spent the afternoon certifying this month's head contract claim in Deep Space, getting every line, variation and retention right. Then I open Xero and key the whole thing in again by hand, line by line, hoping I do not transpose a figure. When the two do not reconcile at month end, I am the one who has to find out why." Before. A certified head contract invoice lived in the platform and your accounting file lived in Xero, and the only bridge between them was a person retyping numbers. Miss a line, fat-finger a total, and the two ledgers quietly drift apart until someone reconciles them by hand. After. There is now a Push to Xero button on the invoice. One click creates or updates the draft in Xero, carries the certified values and the linked documents across, moves it through to approved, and writes the sync back onto the record, so the claim shows as In Xero with its Xero invoice number right there in Deep Space. If the invoice was never batch-synced before, the platform builds the Xero draft on the spot, so there is no separate Sync Now step to remember first. How this helps. The certified figure in Deep Space and the invoice in Xero are the same number, every time, with no double entry and no transposed digits. Your accounts team sees the bill in Xero the moment it is certified, Deep Space stays the single source of truth, and month-end reconciliation stops being a hunt for where the two systems disagree. Known limitations. Paid status flows back automatically only in the common case. A workspace using the button alone will see a claim marked Paid once the next finance sync runs. The subcontractor claim and payment schedule build themselves "I am a contract administrator. A subbie emails their monthly progress claim, KAI reads it and matches it to their subcontract. Good, but I still have to hand-create the claim record, then build a payment schedule off the back of it, retyping the same line items twice before I can even start assessing what to certify. Now multiply that by forty subcontractors, every single month." Before. When a matched subcontractor invoice was promoted to the register, you still had to create the Subcontractor Claim by hand and then build the Payment Schedule separately, keying the same line items in twice before anyone could review or certify anything. After. When an invoice with a confirmed subcontract match is pushed to the register, the platform automatically creates the linked Subcontractor Claim (as Submitted) and a linked draft Payment Schedule (as Draft) in the same move, carrying the line items straight through. The invoice timeline records every step, so you can see exactly when it arrived, when KAI matched it, and when the claim and schedule were created. Edit the invoice and the claim and schedule update with it. Revise and resubmit, or reject, and they are cleared and rebuilt cleanly. How this helps. The claim-to-payment-schedule chain is built for you the moment an invoice lands, so your CAs go straight to assessing and certifying instead of rekeying. Because the payment schedule exists from day one, the clock on your Security of Payment response timeframes is far easier to hit, and the timeline gives you a clean audit trail of what KAI did and when. Revise and Resubmit: reopen an approved claim without starting over "I am the commercial lead. A claim has been approved but not yet paid, and the subbie flags an error in one of the lines. Today my only options are a messy workaround on a locked record, or voiding the whole thing and re-raising it from scratch, losing all the history in the process." Before. Once a claim or invoice was approved it was effectively frozen. If something needed fixing before payment, the only path was working around a locked record or scrapping it and rebuilding. After. Any unpaid record in the Invoice Register can be moved to a Revise and Resubmit state. The record reopens into a tracked status, the related entry is cleared, and you correct and reissue it cleanly. The action is limited to the Commercial Lead role, so reopening a claim stays a deliberate, controlled step rather than something anyone can do by accident. How this helps. A late change before payment becomes a two-click correction instead of a workaround or a full rebuild, the claim keeps its history, and because every reversal is tracked and role-gated you get the flexibility without losing the audit trail or the control. Revert an approved PO or subcontract back to Draft "I am a project manager. I raised a purchase order, it went through approval, and only then did I spot the cost code is against the wrong trade. Today my only fix is to email Support and ask them to unwind it in the backend, then wait." Before. Once a PO or subcontract was approved, there was no way to send it back to Draft to fix a wrong cost code, supplier or line. The only option was a manual backend revert by our Support team, which is slow and does not scale. After. Approved POs and subcontracts now carry a Revert to Draft action. It is available only while the document is safe to reopen (no invoice, claim, variation, Xero push or in-flight e-signature against it), and only to the person who submitted it for approval or a Highest Authority holder. Reverting collects a mandatory reason, moves the completed approval to a revoked state on the audit trail, and notifies every approver, the drafter and the authority holders by email and in-app. Resubmitting starts a fresh approval. How this helps. PMs and commercial managers can self-serve the fix the moment they catch a mistake, with no Support ticket and no waiting, while the no-invoice guard and the role limit keep it safe once money has actually started moving. Every revert is reasoned, audited and announced, so you never trade control for speed. Notices now carry their whole chain forward "I am a project engineer. I raise a site instruction off the back of a consultant's response to an RFI. The subbie who has to act on it receives a bare instruction with none of the drawings or context that prompted it, so they ring me to ask what it is actually about." Before. When one notice triggered another, the new notice started empty. Attachments, context and the reason it existed were left behind in the previous record, and whoever received it had to go hunting or pick up the phone. After. The chain carries through. When a notice triggers the next one, the relevant attachments, prefilled content and a reference back to where it came from travel with it, so an instruction issued off the back of an RFI and a consultant's response arrives with the supporting material already attached. The builder stays the gatekeeper and decides exactly what carries forward and what the recipient sees, so upstream records are never exposed downstream. How this helps. The person on the receiving end gets a complete, actionable notice the first time, so there are fewer clarifying calls and faster action on site, while the builder keeps full control over what information flows in and out of the chain. Improvements Read the title block before you register a drawing "KAI pulled the drawing number and revision. I just cannot tell if it is right, because I cannot actually read the preview." Before. The drawing preview in the promote-to-register flow was a small, low-resolution thumbnail. Zooming in did not help, so verifying KAI's extracted document number, title and revision meant opening the source file separately, which defeated the point of an inline preview. After. The preview is now a persistent, full-size side pane. As you step through each drawing the title block is legible, so you can confirm what KAI extracted at a glance and promote with confidence. It works for a single drawing and for a bulk promote. How this helps. Registering drawings becomes a quick visual check instead of a leap of faith, and KAI's extraction is easy to trust because you can see the evidence right next to it. Inbound email attachments now land on the notice "The consultant replied to the notice by email and attached the marked-up drawing. Where did it go?" Before. When someone replied to a notice by email, the reply came through but any attachments were silently dropped. The file the consultant sent simply never appeared in the platform. After. Inbound attachments are captured on the reply path and surfaced on the notice activity, alongside the reply itself, with the option to save the attachment straight into your document register. How this helps. The full conversation, files included, lives on the notice, so nothing important is lost in an inbox and the marked-up drawing is one click from your register. GST reads clearly across registers, PDFs and line items "Is that figure GST inclusive or not? The register says one thing and the PDF says another." Before. Amounts were shown without a consistent GST treatment, GST-free lines were still marked up at the company rate, and supplier-facing PDFs could print a total that did not match the work. After. Registers and detail panels clearly separate ex-GST and GST-inclusive figures, each line item carries a plus-GST or GST-free tag, and totals (including on supplier PDFs) are calculated on the taxable lines only. GST-free work is treated as GST-free everywhere it appears, end to end, right through to the Xero push. How this helps. The number you read is the number you can rely on, whether you are looking at a register, a detail drawer or a document you are about to send to a supplier. Fixes GST-free invoices no longer get double-taxed in Xero "This supplier invoice is GST-free, so why did Xero add ten percent on top?" Before. A GST-free supplier invoice pushed to Xero could still be taxed on the Xero side, and a fallback path could tax an amount that already included GST, so the Xero total came out higher than the figure in Deep Space. After. The correct tax treatment flows through per line, GST-free lines stay GST-free in Xero (the right exempt tax code is applied), and the fallback pushes on the right basis so tax is never added twice. The Xero total matches the Deep Space total. How this helps. Your bills land in Xero at the right figure, with no manual correction after the fact. Forwarding a notice now actually sends it "I hit forward, it looked like it went, but nothing ever arrived." Before. The forward action on an issued notice looked complete but was a front-end mock. Nothing was actually sent. After. Forwarding works end to end. Selected recipients receive the notice by email, directory members also get in-app access, and one-off external recipients receive the email only, with a clear note explaining who gets what. How this helps. Forward means forward. The notice reaches the people you send it to. Uploaded invoice documents show without a refresh "I uploaded the file, the list is empty, and now it is asking me if I want to push with no attachments." Before. After uploading a document to an invoice the drawer showed a stale snapshot, so the file did not appear until you refreshed the page, and the same stale view fed the empty-documents warning. After. The uploaded document appears straight away and the attachment check reads the live list. How this helps. What you just uploaded is what you see, with no page refresh and no misleading warning. Spotted something, or want a say in what we build next? Send it to us through the feedback portal inside the Deep Space web app. We read every note, and a lot of what shipped today started as one.