Dext Is More Than Data Capture: 4 Features Practices Overlook

Most practices use Dext for receipt and invoice capture. Fewer use the full range of tools built into the platform for managing expense claims, reconciling supplier statements, and getting a picture of how efficiently the practice is running. Here is a look at what those features do and when they are worth using.

Automating expense claim cycles

Business expense claims in Dext handle out-of-pocket spending: anything an employee has paid for personally and needs to be reimbursed. Employees submit their receipts in the usual ways, via the mobile app, email, or WhatsApp, and those items collect in the expense claims section within the costs workspace.

The part worth configuring is auto expense claims. Rather than having employees manually create a new claim each period, you can set a cadence so that a new expense claim is generated automatically, weekly, fortnightly, or monthly, for each person who submits claims. You choose the users, the frequency, and the closing date, and from that point the system handles the scheduling.

This removes the step where someone has to remember to create the claim before submitting, and it keeps all items for a given period neatly contained. If something is submitted after a claim has closed, it rolls into the next one rather than getting lost.

expense Approvals sit alongside this and are worth setting up for any organisation where someone other than the person submitting needs to sign off before reimbursement. You can configure a basic approval flow where a specific user reviews all claims, or a manager-based flow where the direct manager is notified. Conditions can be layered on top: for example, claims under £500 are approved by a manager, and anything above goes to a named senior approver. Once a claim is submitted for approval, all relevant parties receive a notification and can review and approve directly.

One clarification worth noting: the Dext expense claims workflow does not require the Xero Expenses add-on. The two are separate. Expense claims in Dext can be published to Xero as bills, and once payroll is run, the payment can be matched to the bill in Xero in the normal way.

Supplier statement reconciliation

Supplier statement matching is a feature that sits in its own section within the cost workspace, and it does something that used to require a lot of manual cross-referencing.

When you upload a supplier statement to the Supplier Statements section (rather than the main cost inbox), Dext extracts each line from the statement and performs a three-way match. It checks what invoices appear on the statement, what is already in Dext, and what has been posted to the ledger. The result is a report showing which invoices are present in all three places, which are in Dext but not yet in the ledger, and which might be missing entirely.

In the example of a statement with five invoices, if four are fully matched and one exists only in Dext, that one-item gap is immediately visible and actionable. If an invoice appears on the statement but is absent from Dext altogether, there is a request paperwork function that lets you chase the supplier or the client for the missing document directly from within the interface.

The feature works with Xero and QuickBooks Online integrations. Without a ledger integration, you still get the two-way match between the supplier statement and Dext, which is enough to check that you have a complete set of documents.

One practical tip: clients sometimes upload supplier statements to the main cost inbox by mistake. You can filter the cost inbox by document type to identify any statements sitting there, and move them to the Supplier Statements section with a couple of clicks. From there the matching process kicks off automatically.

Bookkeeping insights across your client portfolio

The Insights section in Dext gives a practice-level view of what is happening across all clients, without having to go into each one individually.

The bookkeeping dashboard shows document submission activity over time, flagging clients whose submission volumes have dropped compared to previous periods. If you are approaching a period-end and a client who normally submits steadily has gone quiet, this is where that becomes visible. You can drill down from the dashboard directly into that client to investigate.

The submission method breakdown is equally useful. It shows, for each client, how they are submitting documents: web app, mobile app, email, and so on. If a client is submitting exclusively via the web app but has the mobile bookkeeping app installed, that is a prompt to check whether they are using it correctly, or whether a quick reminder would help. In the other direction, if a client is consistently submitting via email but could be auto-forwarding from their supplier directly, there is an opportunity to streamline things further.

The insights can be filtered by team or office location within the practice, which makes it easier to see performance at a team level rather than just practice-wide. If different bookkeepers handle different client segments, this lets you assess how each segment is running without manually pulling the information together.

Secure document storage – Dext Vault

Dext Vault fills a gap that the core platform was not designed for: storing and organising non-financial documents.

Receipts, invoices, and bank statements all belong in the cost and sales workspaces. But every client relationship also generates other documents that need to be kept somewhere accessible: lease agreements, loan documents, HR records, company accounts, and similar. Vault provides a dedicated space for these within Dext, rather than having them scattered across email threads or separate file stores.

When a document is uploaded to Vault, Dext uses AI to automatically generate a name, extract a subject, and produce a summary of the document's contents. This means files are searchable and identifiable without any manual tagging. The aim is to make Dext the single place where all contextual information about a business is stored, not just the transaction records.