> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.staple.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.staple.ai/_mcp/server.

# Product Enhancements

Stay up to date with everything new in Staple AI — new features, enhancements, and fixes shipped each month. Subscribe via [RSS](./changelog.rss) to get release notes as they go out.

## September '26

September builds on last month's foundations. Singapore e-invoicing now runs end to end in both directions with credit notes, you can choose exactly which fields and table columns each queue shows and exports, Reconciliation 2.0 lets you decide how linked documents are compared, and email files can be uploaded straight into Staple.

## **1. Singapore e-Invoicing: Receiving, Sending and Credit Notes**

Last month, Singapore customers gained self-onboarding for InvoiceNow and IRAS tax submission. This release completes the day-to-day flows on top of it: receiving supplier e-invoices, sending your own, and handling credit notes in both directions.

![](/_fern-img/4d4b96dcc792da5dc7129bb9a6453aee3f0416e35763678392a95e0c511a0217.webp)

#### **What's in it**

* **Receive (AP):** supplier invoices and credit notes sent over Peppol arrive in Staple automatically, routed to the queue assigned to the receiving company, with the Peppol status shown on every document
* **Send (AR):** send an invoice over Peppol, to IRAS, or to both, from a single API call. The destination follows your onboarding configuration, and Peppol and IRAS statuses are tracked separately so a partial failure is easy to spot
* **Credit notes:** issue credit notes that reference the original invoice, for Peppol with IRAS, sales reported to IRAS and purchases reported to IRAS. Received credit notes land in the same queue as invoices
* **Status API:** check the Staple, Peppol and IRAS status of up to 100 documents in one call

#### **Benefit**

Singapore customers can now run their full e-invoicing cycle through Staple: receive from suppliers, send to customers, correct with credit notes, and report to IRAS, all tracked in one place.

## **2. Show or Hide Fields and Table Columns**

Every queue can now decide exactly which fields and table columns appear on the Edit Document page. Hide what your team does not need, and it is left out of exports and downloads too.

![](/_fern-img/86e997c8d21c019a046e4b01647a9c41b21c26741f41def21c75006c8f3c9a6a.webp)

#### **How it works**

* Open a document and select the filter icon next to the **Fields** and **Tables** tabs
* On **Fields**, tick the fields to show and untick the ones to hide, then **Save**
* On **Tables**, each table category lists its columns. Untick columns to hide them, or untick every column to hide the whole table
* Use search, **Select all** and **Clear all** to move quickly
* The filter follows the model automatically: new fields appear already ticked and deleted fields disappear
* When a document no longer matches its model, the rescan icon shows a badge. Open it to see which items are missing or no longer defined, and rescan the document in one click

#### **Benefit**

Reviewers see only the data that matters to them, and exports and downloads carry exactly the same set, through both the interface and the API. Hidden values are not deleted and remain available to Reconciliation.

## **3. New updates in Reconciliation 2.0**

Two updates to Reconciliation 2.0 this month: you now decide how numbers are compared across linked documents, and filters show which document every field belongs to.

### **3.1 Individual and Aggregate Comparison**

When one anchor document is linked to several others, the same comparison can mean two very different things. A PO billed across several invoices should match the invoices added together. A unit price agreed on a PO should appear unchanged on every invoice line. Until now there was no way to say which one you meant, so the engine had to guess, and whichever way it guessed was wrong for half of the use cases.

Comparison Rules now has an **Individual | Aggregate** toggle on every numeric comparison, so you state the intent and the engine follows it.

#### **Individual: each linked document is checked on its own**

Individual compares the anchor value against each linked document separately, and every one of them has to pass.

**Example:** the unit price is 50 on the invoice, and the invoice is linked to four POs that each carry a unit price of 50. The values are not added up. Staple checks 50 against 50, then 50, then 50, then 50, and the row reconciles only when all four match.

![](/_fern-img/212777d3eb6d2d880bbd658bd00e5333ee8c68b413853edb49398e55355af742.webp)

#### **Aggregate: linked documents are added up and compared as a total**

Aggregate adds up the values from all linked documents and compares the total against the anchor.

**Example:** a PO is raised for 100 units and billed across three invoices of 40, 30 and 30 units. Staple adds the invoices together, 40 + 30 + 30 = 100, compares the total against the PO quantity of 100, and the row reconciles.

![](/_fern-img/bba5654390989e6284864ee2d91a59157745c19acf6e1cfcfef854c58dd6df52.webp)

#### **How it works**

* In **Edit Linking Set**, go to **Comparison Rules** and pick the fields to compare
* When both sides are numeric, the **Individual | Aggregate** toggle appears on the row. Select the info icon beside it for a quick definition of each mode
* Tolerance follows the mode you pick: in Aggregate it applies to the total, in Individual it applies to each linked document

#### **Benefit**

The engine no longer guesses. Split billing, repeated deliveries and fixed unit prices each reconcile the way your business actually works.

### **3.2 Group Name Beside Every Filter Field**

In a linking set, the same field often exists on more than one document type: Vendor Name appears on the invoice, the PO and the delivery order, and PO Number appears on both the invoice and the PO. In the Document Set List filter, those fields used to look identical, so it was hard to tell which one you were filtering on.

Every field in the filter list now carries the name of its group beside it, such as **Invoice**, **Purchase Order** or **Delivery Order**. Search for a field and you see every version of it, clearly labelled, and you pick exactly the one you need.

![](/_fern-img/6de9704989daebd80e3c4ac8dbb0e47c1c75b8c1386704637f36b874bcb93216.webp)

#### **Benefit**

Filters return the document sets you actually meant, without trial and error.

## **4. Upload Email Files (.eml and .msg)**

Saved emails can now be uploaded straight into Staple. Previously a downloaded `.eml` or `.msg` file was blocked, so teams had to open it, pull out the attachments and upload them again. That step is gone.

![](/_fern-img/702edbf1732e908ea30b91a9e34f5db6ebefa4262edb0f267d9d0df218ddc153.webp)

#### **How it works**

Email files are handled through manual upload, API upload, forwarding and connected inboxes. Five settings in **Edit Queue**, **Automation** control what Staple creates from each email:

* **Extract attachments as documents:** each attachment becomes its own document. On by default
* **Create a PDF of the email itself:** a document showing From, To, Cc, Subject and Date above the message body
* **Combine attachments into a single document:** everything the email produces becomes one document, in the order it appears
* **Handle nested .eml/.msg files:** extract attachments from an email attached inside an email, one level deep
* **Use email metadata from the connected or forwarded email:** documents take the metadata of the email they arrived in

#### **Benefit**

Emails go into Staple exactly as they were received, with no manual unpacking, and each queue decides how their contents become documents.

## **5. Refreshed Document Editor**

The Document Editor has a cleaner look and fewer clicks. The folder tree has new icons and shows how many uploaded documents each queue holds, and the toolbar icons are updated. In Intelligent Split, the first split instruction opens by default and a new **Apply This Split** button applies it.

![](/_fern-img/d358d3dacee6f1a37b7ab8b09aaf04cef6b5e62801cd066842bb5d9f8a7ad0c1.webp)

## **6. Translate API**

Supporting documents in any language can now be translated into English through the API. The translated document keeps the layout of the original, and it is stored alongside the original as a supporting document, so teams get an English copy they can read and archive without any manual translation.

## Enhancements

* **Export remembers your last format.** The Export dialog now opens on the format you last used in that queue, so a repeat export is one click shorter.
* **Knowledge Base columns use the same data types as model fields.** Choose from ten types when uploading a sheet. String is now called Text, and the previous Text type is now Text (Embeddings). Enrichment rules show an error when a field and a column are not compatible.
* **New rejection reason: PO number missing or invalid.** A tenth reason has been added to the Reject document menu.
* **Teammate upload notifications only for the queue you are viewing,** instead of on every screen for every shared queue.
* **Confidence scores in downloads.** Download data extracted can include confidence scores in JSON and XML, in the interface and through the Download Data API.

## Bug Fixes

* **Complex tables:** extraction of complex tables is more consistent, with fewer tables detected with headers but no rows.
* **Reconciliation filters:** filter fields picked from more than one data type are all kept.
* **Data Enrichment:** table enrichment now writes the mapped value when the knowledge base column is a Number.
* **Export:** exporting with exactly one document selected from the action bar works again.
* **Scanning:** the file size message now shows the current page limit of 400.

## August '26

August is the biggest release of the year so far. Reconciliation 2.0 goes live as a configurable matching engine, Singapore customers can self-register for InvoiceNow and activate IRAS tax submission without operator help, and Data Enrichment now shows reviewers every candidate match instead of a single silent pick.

## **1. Reconciliation 2.0**

A completely rebuilt reconciliation engine, live on production. Rather than a fixed invoice-matching tool, it is a configurable engine you set up once for your own use case. It is designed and architected to fit invoice matching, KYC verification, AML and more, so it drops into very different business problems without being rebuilt each time.

![](/_fern-img/f24ab47f1359ceb9362afebc4b3fe69dd49b4bcd9c3e3bd8ab188daf40d8ee46.webp)

#### **What's in it**

* **Guided three step setup,** with a built-in Staple Guide walking you through every field
* **Relationship Tree** giving you a visual picture of the whole setup as you build it
* **Any field to any field:** header to header, header to line, line to header, line to line
* **Fully user configurable comparison rules and tabs,** with tolerance so small variances still pass
* **Fulfilment tracking:** what is covered, what is still open
* **User defined labels:** name outcomes in your own terms, like Missing PO or Over-billed Quantity
* **Reconcile Details** with an issues-only view, and the original scan alongside the extracted data
* **Custom columns, saved filters and search** across your Linking Sets

#### **Benefit**

One engine adapts across use cases instead of a rebuild each time. Teams configure their own matching logic rather than commissioning a custom build, and reviewers see exactly which values disagree instead of hunting through documents. The setup is self-serve, guided at every step.

## **2. Singapore e-Invoicing: InvoiceNow Self-Onboarding and IRAS Submission**

Singapore is mandating e-invoicing through InvoiceNow, the national network run on Peppol by IMDA. Staple is an IMDA-accredited Peppol Access Point, and this release delivers two things: customers can now register their own Singapore companies end to end, and they can activate IRAS tax submission on top of it.

![](/_fern-img/e590cfc3226917aae1c886f1adcb9eaf28c7af351ca1c790c17b670387d9013c.webp)

#### **Self-onboarding**

* **Register from the UI:** add a Singapore company, provide the required details, and authorise Staple through CorpPass. A Letter of Authorization covers exception cases
* **One registration covers both directions.** A company is registered once as a single Peppol participant that both receives (AP) and sends (AR) e-invoices
* **Registration state is visible** at every step, so you can see which companies are Registered and which are still Processing, with localised UEN validation on entry
* **Assign receiving queues:** each registered company maps to one or more Staple queues, so incoming e-invoices land in the right place
* **Outbound e-invoice generation:** send invoice data to Staple and Staple produces a compliant PINT-SG e-invoice and delivers it over Peppol. Invoices and credit notes are supported document types

#### **IRAS tax submission**

IRAS submission is a separate, optional activation with its own CorpPass approval, tracked independently of registration as Not active, Processing or Active. Turning it on requires a GST registration number, and it is a single switch covering both directions.

* **Submitted alongside a Peppol exchange:** on a sale, once the invoice is sent successfully over Peppol, a copy is submitted to IRAS. On a purchase received over Peppol, the received document is submitted automatically
* **Submitted to the tax authority only:** transactions that never travelled over Peppol can still be reported to IRAS as tax data. This covers sales and purchases made outside the network, aggregated point-of-sale and simplified tax invoices, and aggregated petty cash

#### **Benefit**

Customers meet the Singapore mandate on their own timeline, in one place, without an operator driving registration on their behalf. Multi-entity groups can onboard every company themselves, and GST-registered businesses get tax submission handled automatically once activated.

## **3. Data Enrichment: Multi-Match Picker and Matching Rows**

When Data Enrichment filled a field, a reviewer could see the value but not why it won. If the lookup hit several rows, a twelve-way match looked identical to a clean single match, and correcting a wrong pick meant retyping by hand. Now every candidate is visible and selectable.

![](/_fern-img/1ac0d5d11c5107e66242a00df4a7e8081dd2d533f54dc4ba0e07cc11b1b39568.webp)

#### **How it works**

* **See every match in one click.** Each enriched field carries a single data enrichment icon, shown by default. Clicking it lists the matched values directly under a "Matched values" header with the count, so there is no menu to step through
* **The winner is marked** as the best match, and the field's current value is marked as selected. The list scrolls and pages in more candidates for a long match set
* **Pick a value to correct the field.** Selecting a candidate replaces the value and is recorded as a user edit, so it overrides enrichment and survives re-evaluation. The field also stays free-text editable when no candidate fits
* **View the source rows in the dataset.** A control at the bottom of the list opens the read-only knowledge base panel, which now offers an "All records" and "Matched records" switch below the pinned selected row. The matched view shows just the candidates with the winning row highlighted, and filters apply to whichever view you are on
* **Works the same** on sidebar fields and complex-table cells. When nothing matched, the icon still opens and reads "No matched values"

#### **Benefit**

Reviewers can tell a clean single match from a multi-match at a glance, understand why a value was chosen, and fix a wrong pick by selecting the right row instead of retyping it.

## Enhancements

### Scanning

#### **Bulk label management**

![](/_fern-img/879fcc1258fbc5347fa2b10c0a73a3e085641c8338013127fb097fa13d1c8540.webp)

The Label documents action now has Tag and Untag modes in one dialog. In Untag mode the picker lists only the labels currently applied to your selected documents, each with a count of how many of them carry it, and confirming removes that label from every selected document that has it. This makes reassignment practical at volume: when someone goes on leave, you can untag them and tag a replacement across a hundred documents at once.

Separately, tagging or untagging a label on a single document now only requires access to the document itself. The add, edit and delete labels permission is still required for label administration and bulk label management.

#### **New rejection reason: Wrong billing name**

![](/_fern-img/879d66766e9aca758e1ee7eb793481741fae106432dcdc5343ad7b5be11f33f7.webp)

A ninth reason has been added to the reject document menu, available to all customers. The existing reasons are unchanged.

#### **Bulk rescan raised from 10 to 100 documents**

Bulk rescan now handles up to 100 documents in one action, across both the interface and the processing behind it.

### Data Enrichment

* **Overwrite policy now checks the current value, not the extracted value.** Where two rules depend on each other, the second rule previously only ever looked at the originally extracted value. Now, whenever a value changes, whether a user edited it or another rule wrote it, the dependent rule is re-applied against the current value.
* **Data Enrichment and Set Value now run on documents created from structured files.** Documents that arrive as XML or JSON and are converted into a readable document, e-invoices being the common case, previously could not use these rules because both only ran after a scan. Now the queue's Set Value and Data Enrichment rules fire at creation with no extra configuration, on both header fields and line-item columns. Values resolve in the standard order of Set Value, then Data Enrichment, then user edit, and AI refresh re-runs enrichment on demand.

### API

* **Confidence scores are now available in downloads and through the API.** Until now the score only existed in the review screen, so anyone processing documents programmatically received extracted data with no signal of which values were reliable. In the interface, Download data extracted has a new "Include confidence scores" checkbox. Through the API, the Download Data endpoint takes a new optional `includeConfidence` parameter. Each document gains a single `Confidence` block carrying the combined score plus its OCR and extraction parts, for header fields and for table headers, columns and rows. Existing integrations are unaffected because the parameter defaults to off. Available for JSON and XML on custom model queues using complex tables. [API reference](https://docs.staple.ai/api-reference/v2/documents/download-multiple-documents-data)

### Export

* **Email columns moved to the end of the CSV.** Spreadsheet tools cap a single cell at 32,767 characters, so a long email body would overflow into the next row and push the remaining records out of alignment, making the file hard to read and filter. All email columns now sit at the end of the CSV, so the rest of the record stays intact. This applies to Export data, Download data, and Global Search bulk download, and no columns were removed.

## Bug Fixes

* **Intelligent feedback:** deleting a template no longer leaves the document attached to it, so the document stops appearing trained and the control behaves correctly. Matching also no longer uses a loose threshold without document type guards, which had produced false-positive matches against completely unrelated documents.
* **Model fields:** deleting an optional field no longer leaves the remaining fields in the wrong order.
* **Global Search:** Invoice model document types stay available in search after model members are removed.

## July '26

July's release focuses on trust and verifiability, a faster scanning experience, and cleaner data by design. Reviewers can now see how confident the AI is in every field, filter large queues down to exactly what they need, verify the integrity of any export, and give every line item column a data type.

## **1. Search and Filter in the Scanning Table**

A major upgrade to the scanning table. Each reviewer can now narrow a shared queue down to just the documents they care about, searching and filtering across every field Staple captured, even hidden ones, with the view persisting between sessions.

![](/_fern-img/422e7788e70b98b8e2359aeab6e191b2b6eeb03691859c0f2be530ff2684f2cb.webp)

#### **How it works**

* Filter on any captured field, enriched field (such as a vendor code looked up from a vendor name), document detail (file name, doc ID, upload or completion or export or rejection dates), email detail (sender, subject, body), label, or status detail (scan outcome, match status, rejection reason, export failure reason)
* Field appropriate operators: numbers (equals, greater or less than, between), text (contains, starts with, equals), dates (on, before, after, between, plus presets like last 7, 30, 90 days), currency, yes/no, and people
* Combine multiple conditions, each shown as a removable tag above the table
* Case insensitive keyword search across all captured fields, working together with filters
* The filter persists per reviewer per queue across tab switches, logout, and other devices, without affecting teammates' views

#### **Benefit**

Reviewers jump straight to their slice of a large shared queue instead of scrolling and paging, reducing missed or double handled documents.

## **2. Confidence Score in the Review Screen**

Every field and table extracted by a custom model now shows a "how sure am I?" signal, so reviewers can spend their time on the fields that actually need a look instead of checking everything.

![](/_fern-img/8b162360a54094e06437c4f335df5744f94bf31eb08d84ef76948b193233f963.webp)

#### **How it works**

* A dark tick marks high confidence, meaning a score of 0.90 and above. An orange warning marks low confidence, a score below 0.90
* Hover any icon to see the exact score and status message
* Appears on sidebar fields, table column headers, and individual table cells
* When you edit the value of a low confidence field, the orange warning updates to a dark tick
* Queue admins can toggle it off in Queue Settings, then Preferences

## **3. Mexico CFDI E-Invoice Validation and XML Import Framework**

A new end to end capability to validate Mexican CFDI e-invoices inside Staple. CFDI XML files are imported, converted into a stored document and PDF, and validated against Mexican tax authority (SAT) requirements, with results exposed through APIs and a complete audit trail.

#### **How it works**

* **Import:** a CFDI XML is imported, mapped to the queue's model (custom models and complex tables supported), and turned into a stored document record with a generated PDF
* **Three step validation, run in order:**
  * **Schema validation** confirms the invoice matches the official SAT CFDI 4.0 structure and version
  * **SAT status validation** calls SAT's service to confirm the invoice is genuinely active, so a cancelled or unknown invoice fails, with automatic retries
  * **RFC validation** confirms the receiver's tax ID on the invoice matches the configured recipient, proving the invoice is actually addressed to you
* **Structured results via API,** retrievable by document ID or CFDI UUID
* **Full audit trail** records every step and the final outcome as the authoritative compliance record

#### **Benefit**

Automatically confirms each CFDI is genuine, currently valid, and correctly addressed before it is trusted or reimbursed, removing slow manual verification and reducing audit exposure.

## **4. Data Type Selection for Line Item Table Headers**

Line item table columns can now carry a data type, so Staple knows what each column represents. Amounts stay amounts, dates stay dates, and the whole product now speaks one consistent data language.

![](/_fern-img/a6a07c754ee3a027602a8537393be014080ef5664a97094341ca2ea223e64a5c.webp)

#### **How it works**

* Assign a data type to each line item column, drawn from the same 14 data types used for document level fields, with identical behavior across the product
* Cleaner captured data at scanning time, with better accuracy and fewer manual corrections
* Built for global invoicing: credit note negatives like (\$2,690.57) become -2690.57, European amount formats are supported, and Asian dates are converted
* Consistent, comparable data unlocks reconciliation across purchase orders, goods receipts, and invoices

#### **Benefit**

Line item data is clean by design, with no downstream cleanup. Existing table headers default to Text and deprecated field types are migrated automatically, so no action is needed.

## **5. Audit Verification**

Staple now has an Audit Verification screen that confirms whether a document is a genuine, unaltered Staple output. Drop a file into the screen and Staple reads the cryptographically signed record embedded in it and tells you instantly whether the signature is valid.

![](/_fern-img/71491ff9dedf4b55c99903a4256e05d5a11c82ab36a9975f5db1ae6a974667cc.webp)

#### **How it works**

* Open the Audit Verification screen and drop in a file, or click to browse. It supports PDF, PNG, JPG, DOCX, XLSX, PPTX, and JSON exports
* For a genuine Staple processed document, it shows a green "Valid Signature" along with the audit data: document ID and name, status, queue, who uploaded and completed it, the timestamps, time to complete, and the behavior history
* For a tampered or non-Staple file, it shows a red "Invalid Signature" with "No valid signature or metadata found"
* Verification reads the signed record embedded at export, so anyone can confirm a document's integrity independently

#### **Benefit**

Customers, auditors, and regulators can confirm in seconds whether a document genuinely came from Staple and has not been altered, without contacting Staple.

## **6. Editable Table Line Items in Documents Created from XML and JSON**

Some documents arrive as structured files rather than scans. E-invoices from government portals and networks, for example, come as XML or JSON. Staple converts these into a readable document in the UI, with header fields and a line item table, and this release lets you edit the table line items in them.

#### **How it works**

* Table rows can now be edited, added, and corrected directly in the document view, just like a scanned document
* Each line item keeps a stable identifier through ingestion, enrichment, and export, so your edits flow cleanly to downstream systems
* Set Value rules and Data Enrichment now also run on these documents

#### **Benefit**

Structured file documents, including government and network e-invoices, are no longer read only at the line item level, so reviewers can correct and complete them in place before export.

## Enhancements

### E-Invoice

* **Inbound for Germany and France:** inbound e-invoices for Germany and France are pulled into Staple automatically and created as documents in the right queues, ready for the usual review and export. Duplicate deliveries are de-duplicated and failed deliveries are retried.

### Data Enrichment

* **Smarter fuzzy matching:** vendor name matching now handles spacing differences, for example "MHBland" versus "MH Bland," and produces fewer false matches from generic shared words like "Ship Suppliers" or "Trading."
* **Master data sync with Concur:** the master data (knowledge base) used for enrichment and validation can now be kept in sync with the connected finance system.

### Reconciliation

* **Force match a single linked document:** you can now force match when only one document is linked to the anchor document, which was previously blocked.

### Webhook

* **Move document to another queue:** a new webhook fires whenever a document is moved from one queue to another, so downstream systems are notified in real time instead of polling. Subscribe to it as "Document Moved Into Queue" in Webhook Setup.

### Scanning

* **Default "Latest First" ordering:** every scanning tab now opens newest first on its most relevant timestamp, and that order is preserved as you page through documents, including with custom columns. The Rejected tab flipped from oldest first to newest first.
* **File size as a custom column:** add a File Size column to the scanning list view to spot oversized, at risk files before you export.
* **Unlimited custom columns:** the previous cap of 10 custom columns has been removed, so teams can tailor the list view to exactly how they work.
* **Asian date normalisation:** dates written in Asian scripts and non-Gregorian calendars now normalise correctly, including CJK year, month, day formats, Japanese eras, Taiwan ROC years, and Thai Buddhist dates.

### Export

* **Export status in the Progress Panel:** the Progress Panel now shows export and exported status alongside upload and scan status, including failed exports.
* **Export from the "Failed to Export" screen:** export is now available directly from a failed to export document, so you can re-trigger it after fixing the issue.
* **Concur export, automatic compression over 10MB:** a new queue setting compresses oversized PDFs automatically so documents above Concur's 10MB limit export successfully, with the compressed file size visible in the Progress Panel.

## June '26

June's release focuses on upload visibility, e-invoicing self-service, translation control, and model configuration. These updates give users real-time insight into document processing, let customers onboard their own subsidiaries for e-invoicing compliance, and make models easier to maintain.

## **1. Progress Panel: Live Upload Visibility**

Uploading through the UI used to come with a blind spot: once you hit upload, you had no idea what was happening to your document. Slow scans looked like lost documents, and the only option was to refresh and hope.

The new Progress Panel gives you live, end-to-end visibility into every upload.

![](/_fern-img/e2ff2a5298fd04a65360814f2781faf7ca45ef9aafcc8030bcd89e6d481392d3.webp)

#### **How it works**

A floating panel appears on the queue list page, similar to a cloud drive upload tray. Kick off an upload, carry on with your work, and revisit anytime to check progress. The panel expands and collapses without blocking anything else you are doing.

Each document moves through clear states, so you always know exactly where it is:

* Uploading
* Uploaded
* Moving to Scanned
* Scanning
* Scanned
* Upload Failed, Scan Failed, or Duplicate when something goes wrong

#### **What's included**

* Upload up to 100 documents at once, up from the previous limit of 10
* Per-document progress bars covering both upload and scan stages
* Retry button for failed uploads, directly from the panel
* Filter entries by status, time period, or document name
* Covers uploads from the UI, API, and email, scoped to your own documents

#### **Benefits**

* No more guessing whether an upload went through
* Failed documents are surfaced explicitly instead of silently disappearing
* Bulk uploads scale without losing track of individual files

## **2. Global E-Invoice Onboarding: Germany and France**

Receiving e-invoices in Germany and France requires registering each legal entity on the Peppol network. Previously, onboarding a new subsidiary took days of manual back-and-forth setup.

Customers can now self-register their subsidiaries directly inside Staple, in a fully guided flow.

![](/_fern-img/eb3404f6ccbacd4a9f8538d7f5aab9422cc51c12d8266ae63630e86d7f174808.webp)

#### **How it works**

* Open the onboarding flow inside Staple and register a subsidiary for Germany or France
* The guided UI collects the required company details and handles Peppol registration
* Once registered, the entity can receive e-invoices directly into Staple queues

#### **Benefits**

* Self-service setup: no back-and-forth with support to onboard an entity
* Compliance handled: meets e-invoicing mandates in Germany and France
* Scales for multi-entity customers: parent companies can onboard all their subsidiaries themselves
* One consistent Staple experience end to end

More countries are on the way, with Poland and Singapore in progress. Reach out to [hello@staple.ai](mailto:hello@staple.ai) to get started.

## **3. Field-Level Translation Control**

Document translation translates every field in a document. But some values mean the same thing in any language and should never be translated: bank codes (BIC/SWIFT), currency codes, flight numbers, names. A SWIFT code like CHASAU2X translated into another language becomes meaningless.

You can now turn translation off for individual fields while the rest of the document stays translated. Supported translation languages are English, Simplified Chinese, and Japanese.

#### **How it works**

Each header field has a **Translate field** toggle in the model sidebar.

![](/_fern-img/6346935fad29c41aa365577dea075b3bc5f80de35967b9294d1140cd33248c2a.webp)

Each table column has a **Field translation** toggle in its column header edit.

![](/_fern-img/86bc3b149499bae4de1f7385a1ecf74066ae1fc0dfb2cbc9ee1babb73795cdfc.webp)

Turn a field off and it keeps its original extracted value, even in the translated view. The setting is stored on the model, so it applies to every document scanned with it.

#### **What's included**

* Works on both header (sidebar) fields and table columns
* A column setting applies to every row in that column
* Exports, downloads, data mapper lookups, and reconciliation all respect the per-field setting
* Existing models are unchanged by default: all fields stay translated until you switch specific ones off

## **4. Sidebar Fields Move from Template to Model Level**

Deleting a field from a template did not delete it everywhere. Sidebar fields lived at the template level, so removing a field from one template left it alive in others, and it would still show up in the queue. Truly removing a field meant deleting it template by template.

Sidebar fields now live at the model level: a single source of truth.

#### **What changed**

* Removing a field from a template now removes it across all templates in the model
* Data area and keywords are now optional, so you can save templates without them

![](/_fern-img/e53e2c9ee29d99261a1a96102d05dfc54d76d1b2eabdbb9237c36b8d8bed9677.webp)

For template-specific tagging, you no longer delete the field. Simply leave it untagged on templates that don't need it, and the system knows not to extract it there.

#### **Benefits**

* One place to maintain sidebar fields
* No more orphaned fields living on in queues after deletion
* Faster template setup when data area and keywords aren't needed

## **5. Data Enrichment Refinements**

Data Enrichment shipped in May. June sharpens it.

#### **What's included**

* No-match policy improvements: fallback behavior when no matching record is found is now clearer and more predictable

![](/_fern-img/113753f4917364ec6871a71a6cee76a53140a24032b11e29c1d9e9d77e27a947.webp)

## **6. Set Value Conditions**

Set Value rules previously applied to every document in the queue. They can now apply conditionally: the value is set only when the document meets the conditions you define.

#### **How it works**

* Add up to 5 conditions to any SET rule. All conditions must be true for the value to apply (combined with AND)
* Each condition has three parts: a field, an operator, and a value
* Operators adapt to the field type. Number and date fields support `=`, `!=`, `<`, `>`, `<=`, `>=`. Text and true/false fields support `=` and `!=`
* Works on both custom-model and predefined-model queues
* Runs before Data Enrichment, so enrichment lookups use the corrected values

#### **Example**

![](/_fern-img/a430a79eadd177a90abba14faffc2bb3f5c25ea903c628e05d0c01a8d701ff0d.webp)

A travel expense queue has a field called "Is total more than X". A rule is set: if Total > 500, force fill the field as "Yes". A ticket with a total of 903.50 comes in, the condition matches, and the field is set to "Yes" automatically at scan time.

## Minor Enhancements

### **1. Set Value Rule Limit Increased from 10 to 50**

![](/_fern-img/03dd0a66ac772c220262eac5a0990e35912a31fce50600b4d290304dae8b5002.webp)

Advanced queue setups now have more room for business-specific automation. Larger rule sets no longer need to be split across multiple queues.

### **2. Custom Model Support in Staple Chat**

Staple Chat previously only supported queues running predefined models. Chat now works with custom models too, so queues built on custom models get the same chat experience as everything else.

### **3. .txt File Upload**

The UI now supports uploading .txt files directly. Text-based inputs follow the same document intake flow as every other supported format, with no workaround needed.

### **4. Document Labels Included in All Export Formats**

Applied document labels are now carried across all supported export formats. Reporting and downstream systems receive the same label information you see in the product.

### **5. Clearer Queue Name Validation**

When a queue name exceeds the character limit, you now get a clear, specific message instead of an opaque validation error.

### **6. Failed Document Lifecycle Fix**

Failed documents could previously be moved to Completed from the edit page and exported unexpectedly. The edit-page state flow has been tightened so failed documents follow the expected lifecycle.

## May '26

May's release focuses on **data enrichment, bulk export, duplicate detection improvements, and queue management enhancements**. These updates give teams more control over data quality, large-scale operations, and document workflows.

## **1. Data Enrichment**

Documents arrive with gaps: missing vendor codes, supplier names that don't match your master list, typos in line items. Data Enrichment fills these automatically using your own reference data.

#### **How it works**

* Upload your reference data (vendor master, SKU list, customer master) as a knowledge base
* Create enrichment rules that define what to look up and which document field to populate
* Rules run automatically on every document processed by the queue

**Matching types**

* **Exact** — for codes and IDs
* **Fuzzy** — for name variations and typos
* **Semantic** — for meaning-based matches across inconsistent terminology

**You control the outcome**

* No match found: leave as-is, blank the field, or set a default value
* Multiple matches: use first result, best-scoring result, or a default
* Existing extracted value: overwrite it or keep it

What gets enriched: header fields and table columns. Every enriched cell is visually marked and logged in the audit trail.

#### **Also shipping: Set Value Conditions**

SET rules now support IF conditions — a value only applies when the document meets your criteria.

* Supports numeric thresholds, date comparisons, boolean checks, and string equality
* Up to 5 conditions per rule, combined with AND

## **2. Bulk Download**

If you need to extract a large volume of documents and their data for audits, reporting, or migrations, the old approach was to download them one at a time.

This release introduces **Bulk Download**.

![](/_fern-img/68f2834756a010f167c348eb82da19064fb5d1409cd0164f5687f024183f7705.webp)

#### **How it works**

From the Global Search page, filter the documents you need and trigger a bulk download job. The export runs in the background. You receive two emails — one confirming the job started, and one with the download links when it is ready.

* Choose from CSV, XML, JSON, or TXT
* Optionally include the original source files alongside the extracted data
* Supports up to 200,000 documents per batch
* Role-based access control: only authorised users can trigger bulk downloads
* A status screen in the product lets you track active and completed jobs

**What's next:** Bulk Download from Global Search is the first phase. The same capability for the Scanning view page is coming next.

#### **Benefits**

* No more one-by-one downloads for large datasets
* Usable for audits, reporting, migrations, and custom dashboards
* Background processing means you can continue working while the job runs

## **3. Duplicate Detection for Removed Documents**

Duplicate checking previously did not account for documents that had been removed from the system. If a document was deleted and someone re-uploaded the same file, it would pass through without being flagged.

This is now fixed.

![](/_fern-img/ab79d11e4a1bce6b17b111acc31fa324ac930c7fa70a5e288f1615b1513274b1.webp)

Duplicate checks now run against removed documents too. If a re-uploaded file matches a document that was previously removed, it is flagged as a duplicate.

This also applies to documents produced by Intelligent Splitting. If a parent document was split and some pages were removed, a re-upload of the same source file will still be caught.

## Minor enhancements

### **1. Queue Rule Limit Increased from 5 to 10**

You can now add up to 10 rules per queue, up from the previous limit of 5. A guardrail ensures only one "compare against previous documents" rule is allowed per model, so the higher limit does not affect performance.

### **2. File Size Warning Before Export**

When exporting documents to integrations that have file size limits (such as SAP Concur's 10 MB cap), Staple now shows a warning on the export screen if the file is likely to exceed the limit. Previously, oversized files would fail silently or return a vague error. You now see the issue before triggering the export.

### **3. "Not Found" Label in Reconciliation**

When a reconciliation rule applies a label based on a match outcome, the "Not Found" label is now visible across all reconciliation views and included in export APIs. This makes it easier to identify line items or headers where no matching record was found, without having to dig into individual documents.

### **4. Query Performance**

Document count queries load faster. Queue-level counts and reporting views respond more quickly.

## April '26

April's release brings a major capability in intelligent document handling, Malaysia e-invoice compliance for AR teams, deeper audit trails for field edits, and several workflow and integration improvements.

## **1. Intelligent Splitting**

Multi-type documents are common in logistics, finance, and operations. A single uploaded file might contain purchase orders, delivery orders, and invoices bundled together. Splitting them manually before processing is slow and error-prone.

This release introduces **Intelligent Splitting**, which removes that step entirely.

#### **How it works**

Define splitting instructions once, in plain language, the same way you would prompt an LLM. Every bundled document uploaded to the queue gets split into its individual components automatically, before processing begins.

* Supports any document mix — invoices, POs, delivery orders, KYC packets, medical files, and more
* Up to 2,000 characters of instruction, so you can be as specific as the document requires
* Map one instruction set to multiple queues
* Splitting happens within seconds, even on large multi-page files

**Example:** A 14-page file containing purchase orders, delivery orders, and invoices was uploaded. Intelligent Splitting produced 11 separate documents — 8 purchase orders, 2 delivery orders, and 1 four-page invoice — all ready for processing.

After splitting: Use Labels and Rules to auto-route each document type to its correct queue. Full documentation and walkthrough video at [docs.staple.ai](https://docs.staple.ai).

#### **Benefits**

* No manual sorting before upload
* Works across industries where composite documents are the norm
* Scales to high-volume document intake without added effort

## **2. Malaysia E-Invoice: Accounts Receivable**

Malaysian businesses are legally required to submit invoices to the government tax portal (MyInvois, run by LHDN) for verification before sharing them with buyers. Without automation, this means manual data entry for every invoice, strict formatting requirements, and no reliable audit trail.

Staple now handles the entire submission process on your behalf, from the moment an invoice is issued to the point it is verified by the government and ready to share with your buyer.

#### **How it works**

There are four things you can do:

**Submit an invoice** — Send your invoice data to Staple via API. Staple converts it into the government-required format, validates the details, and submits it to MyInvois. You get an instant confirmation with a tracking reference. You do not need to wait for the government to finish processing before continuing your workflow.

**Check the status** — Use the tracking reference to see where your invoice stands. The government returns one of five statuses: Valid, Invalid, Cancelled, Submitted (still processing), or Duplicate. If the invoice is rejected, Staple tells you exactly which fields need to be corrected before resubmitting.

**Retrieve the official copy** — Once an invoice is validated, the government issues an official verified copy. You or your buyer can retrieve this using the reference on the invoice. Useful for verifying invoices you receive from suppliers before approving payment.

**Cancel an invoice** — If an invoice was submitted by mistake, it can be cancelled within 72 hours of government validation. After that window, a Credit Note is required instead.

#### **Benefits**

* No manual submissions to the MyInvois portal
* Your ERP or finance system stays in the loop without human intervention
* Every mapping, submission, and cancellation is logged for audit
* Errors are surfaced with specific field-level details, not vague rejection messages

Reach out to [hello@staple.io](mailto:hello@staple.io) to get this enabled for your organisation.

## **3. Data Edit Audit**

When a user changes a field value during document review, there was no structured record of what changed, when, or by whom. For compliance-heavy workflows, that gap matters.

This release introduces **Data Edit Audit** for sidebar fields.

![](/_fern-img/7760047635b3aa69c9d9c66e27ce3a83a96933a611e36b496a5c92017e5d1a04.webp)

#### **How it works**

Every change a user makes to a sidebar field during scanning is now detected, captured, and written to the audit record. The edit event includes what was changed and a log entry that surfaces cleanly in the UI and in audit downloads.

#### **What's included**

* Full edit detection for sidebar fields
* Audit events created on save
* Edit metadata visible in the UI and downloadable

#### **Benefits**

* Know exactly what was changed after extraction
* Demonstrate data integrity to auditors and downstream systems
* Supports compliance requirements in regulated industries

## Minor enhancements

### **1. Uploaded Tab Enabled by Default / "Received" Renamed to "Scanned"**

![](/_fern-img/936583be67548a7df92af1e115257a3ac6bdca211244e71deb5f5c61ab4a15bc.webp)

Two UI changes shipped together to make the document intake workflow clearer.

The Uploaded tab is now enabled by default on all new queues. Documents still move automatically to the processing queue unless you change the default intake settings. Existing workflows are unaffected.

The "Received" state has been renamed "Scanned" across the UI. A "Previously called 'Received'" hint is displayed for continuity. The underlying backend state is unchanged, so no integrations break.

### **2. Search Improvements**

Search V2 is faster and more relevant. Content search now returns results ordered by relevance, with the most relevant matches at the top. Page load times for search results are reduced. The advanced search pagination UI has also been simplified, removing the page input and total page count display to reduce visual noise.

### **3. SAP Concur: USD Currency Conversion**

For customers using the Concur integration, Staple can now convert invoice amounts to USD at the current day's exchange rate before export. If an invoice arrives in EUR (or any non-USD currency), the conversion happens automatically during the Concur export flow. Reach out to [support@staple.ai](mailto:support@staple.ai) to enable this for your organisation.

### **4. PDF Generation: Updated Visual Standard**

Generated PDFs now reflect updated header styling, sidebar colouring, and form layout. The header limit has been increased from 5 to 25, and multi-page table support has been added so large tables are no longer cut off across pages. One standard format applies across all customers for consistency.

### **5. Email Integration: Logos and Inline Images Excluded by Default**

When using the email integration, Staple previously ingested inline comment images and logos alongside document attachments. These are now excluded by default. Only actual document attachments are scanned. The email integration sync has also been fixed to use the current mapping date rather than the first mapping date, preventing duplicate scans when re-syncing.

## March '26

March’s release focuses on improving **scanning performance, global usability, model configuration efficiency, integration flexibility, and data accessibility**. These updates reduce manual effort, improve reliability, and make the platform more scalable for enterprise workflows.

## **1. Scanning Performance and Reliability Improvements**

Document scanning has been enhanced to improve both **processing speed and reliability**, especially for large and complex documents.

#### **How it works**

* Processing has moved from **sequential to concurrent execution**, allowing documents to be broken down and processed in parallel
* Improves performance for large documents (e.g., multi-page files)
* Introduces a **self-healing mechanism** for handling failures
* If a specific step (e.g., table detection) fails, only that step is retried instead of reprocessing the entire document
* Retry attempts are controlled with a maximum limit to prevent infinite loops

#### **Benefits**

* Faster processing of large documents
* Improved system throughput
* Reduced failure rates
* No need for manual retries

## **2. Copy and Paste Fields in Model Builder (Sidebar Fields)**

Creating similar templates previously required manually re-tagging fields, even when configurations were identical.

This release introduces **copy and paste functionality for sidebar fields in Model Builder**.

![](/_fern-img/e22d8a701e937f409833a3133677160b4150fef162df1376c1e083b728037cdf.webp)

#### **How it works**

* Copy field configurations from one template
* Paste them into another template
* Uses browser clipboard for transferring field configurations

#### **Benefits**

* Faster template creation
* Eliminates repetitive field tagging
* Useful for creating similar template variants

## **3. Localisation Expansion (Chinese & Japanese)**

Localisation support has been expanded further across the platform to improve usability for international teams.

![](/_fern-img/2e5cf7795f709a9ea9ca19f494cedfd96b341a63ffa0f3e0fd2af1b90b16bb5c.webp)

#### **What’s included**

Localisation now covers:

* Profile page
* Role management
* Analytics
* Advanced search
* Queue list
* Model builder
* Scanning tabs
* Hover messages
* Email templates
* Label actions

Supported languages:

* Chinese
* Japanese

#### **Benefits**

* More complete localisation across workflows
* Improved usability for global teams
* Better adoption in regional markets

## **4. Webhook Workflow Enhancement (Manual Trigger Support)**

Webhook creation previously required selecting an event, which prevented manual or ad-hoc workflows.

This release introduces support for **event-optional webhook configuration**.

![](/_fern-img/3a92c310e313837b8aeffb601b6c74c8f0d22c722477e53b3b084daba81ea033.webp)

#### **How it works**

* Event selection is now optional
* Webhooks can be created without selecting any system event
* Enables manual triggering of webhooks

#### **Benefits**

* Supports ad-hoc integrations
* Enables manual workflows
* Allows reuse of webhook endpoints

## Minor enhancements

### **1. Include Email Metadata in Export and Download**

Email metadata was previously available in the system but not included in exported or downloaded data.

This release enables **email metadata to be included in all exports and downloads**.

#### **How it works**

Included metadata fields:

* From
* CCs
* Date & Time
* Subject
* Email body

Available in:

* UI downloads and exports (single and bulk)
* API downloads and exports

#### **Benefits**

* Improved downstream data processing
* Better traceability of document origin
* Eliminates dependency on Concur-specific exports

### **2. Role-Based Access for Multiple Export and Document Actions**

Document actions were previously not controlled at a granular level based on user roles.

This release introduces **role-based access control for export and document actions**.

#### **What’s included**

* Multiple export (re-export) restricted based on user roles

* Role-based control for:

* Removing documents

* Removing exported documents

#### **Benefits**

* Better governance and control
* Prevents unintended actions
* Aligns actions with user permissions

### **3. TypeORM Upgrade**

The backend ORM layer has been upgraded to improve system stability and maintainability.

#### **What’s included**

* Upgrade to latest TypeORM version
* Replacement of deprecated query methods
* Migration to updated architecture patterns

#### **Benefits**

* Improved stability
* Reduced technical debt
* Better long-term maintainability

## February '26

February’s release focuses on improving **navigation, reconciliation flexibility, localisation, and document processing accuracy**. These updates make it easier to manage large numbers of queues and models, add greater control to reconciliation workflows, and improve the platform experience for international teams.

## **1. Search and Sorting for Queues and Models**

Managing a large number of Queue Groups, Queues, and Models can make navigation difficult. Previously, users relied on browser search to locate items, which did not preserve queue hierarchy and made it harder to understand context.

This release introduces **native search and sorting capabilities** to improve discoverability and help users prioritize their work more efficiently.

![search and sorting queues and models](/_fern-img/98ad44f4e4e7d2af37adab6e6b5d996826a088c50d0c5a986e8678ebdf7f651a.webp)

#### How it works

**Search**

Users can now search for Queue Groups and Queues directly from the **Queues page**.

* Search results update automatically as users type.
* Results **preserve the queue hierarchy**, showing the Queue Group and its associated queues.
* If a Queue Group matches the search, all its child queues are displayed.
* If a Queue matches the search, the system displays the queue together with its parent Queue Group.

Users can also search **Models by name** from the Models page.

**Sorting**

Queues can now be sorted using multiple criteria:

* Name (A–Z / Z–A)
* Created Date (Newest First / Oldest First)
* Latest Document Uploaded
* Pending Documents (Uploaded + Received)

Models can also be sorted alphabetically:

* Name (A–Z)
* Name (Z–A)

#### Benefits

* Faster navigation across Queue Groups, Queues, and Models
* Improved discoverability in environments with many queues
* Ability to prioritize queues with recent activity or higher workload
* Reduced reliance on browser search workarounds

## **2. Label Support for Reconciliation**

Reconciliation previously relied only on system-generated statuses such as **Fully Reconciled, Partially Reconciled, Not Reconciled, and Error**. These statuses were sometimes insufficient to represent business-specific reconciliation scenarios.

This release introduces **custom labels for reconciliation**, allowing users to classify reconciliation results based on configurable business rules.

![](/_fern-img/cf7bb592efed8573e6456b16a6c490ed230aa644d7854c7292464668d10cd199.webp)

#### How it works

Users can now create reconciliation rules using field comparisons: When the rule condition is satisfied, a **user-defined label** is automatically applied to the reconciliation.

Example:

* If **Invoice Amount > Purchase Order Amount**, the reconciliation can be labeled**Overcharged**.
* If **Delivery Order Amount \< Purchase Order Amount**, the reconciliation can be labeled**Not Fully Delivered**.

Custom labels work alongside the existing reconciliation statuses without changing current workflows.

#### Benefits

* Greater flexibility in representing reconciliation outcomes
* Ability to implement business-specific reconciliation logic
* Improved visibility when reviewing reconciliation results

## **3. Configurable Document Display Name in Reconciliation**

Previously, the system used **file name** as the primary identifier for documents in reconciliation views. File names are often auto-generated and not meaningful for users.

This release allows customers to configure a **business-relevant field** to display as the document identifier.

#### How it works

A new configuration allows users to define a **display\_name\_field** for each document type.

Examples of display fields:

* Invoice Number
* Purchase Order Number

When configured, the selected field appears as the **primary document identifier** in reconciliation lists and document links.

If no display field is configured, the system continues to display the **file name**.

#### Benefits

* Improves readability in document lists and reconciliation views
* Aligns document identification with real business identifiers
* Makes reconciliation workflows easier to interpret

## **4. Dashboard Localisation (Chinese and Japanese)**

Staple now supports localisation for **Chinese and Japanese** users across the main dashboards.

This enhancement allows users to interact with the platform in their preferred language, improving usability for international teams.

#### What’s included

Chinese localisation is now available for:

* Staple Dashboard
* Reconciliation Dashboard
* Document Editor Dashboard

![dashboard localisation](/_fern-img/af59959ed5e6772aba70337efd5af88ced8914f174514b85560e871dc7a661d9.webp)

The platform interface, including buttons, labels, notifications, and messages, is translated to support Chinese-speaking users.

Japanese localisation support has also been extended to improve accessibility for teams operating in Japan.

#### Benefits

* Better usability for Chinese and Japanese users
* Improved accessibility for global teams
* Supports adoption of Staple AI in international markets

## **5. Complex Table Type Consolidation**

Some documents contain multiple tables of the **same category** on a single page. Previously, these tables were processed separately, which could create duplicate table structures.

This release introduces **automatic consolidation of tables with the same category**.

![](/_fern-img/d9f583d6521dca69f8f349d59fc5d18b28cc8bd6759540a2ad68b23d14855b26.webp)

#### How it works

* Tables with the same category on the same page are **automatically merged**.
* During annotation, the UI enforces a rule allowing **only one table instance per category per page**.

#### Benefits

* Cleaner document structure
* Easier review of extracted data
* Reduced duplication in table extraction

## Minor enhancements

#### **1. Complex Table Translation Workflow Improvements**

Previously, complex table extraction always triggered translation requests to the translation service, even when translation was disabled or unnecessary. This caused unnecessary processing overhead.

This release improves the **translation workflow for complex table extraction**.

##### Benefits

* Reduced processing time for English documents
* Improved extraction accuracy
* Lower load on translation services
* Consistent translation behavior across scanning and Smart Fill workflows

#### **2. Removal of Predefined Model and Smart Table UI Options**

To simplify the product interface and align with the current architecture, several legacy options have been removed from the UI.

##### Changes

* Predefined model creation options removed from **Queue Settings**
* Smart Table and Feedback configuration options removed from **Preferences**
* Models now use **Complex Tables only**

This simplifies the configuration experience and removes outdated UI elements.

#### **3. GraphQL Security and Dependency Improvements**

This release includes backend improvements to improve security and maintainability of the GraphQL service.

##### Updates

* Express upgraded to a **security-patched version**

* Legacy **MySQL-related code removed**

* Critical dependencies upgraded:

* cookie

* jsonwebtoken

* qs

##### Benefits

* Improved platform security
* Reduced technical debt
* Better long-term maintainability of the GraphQL service

## January '26

New yer and powerful new releases.

January’s release focuses on improving **reconciliation clarity**,**model flexibility**,**document navigation**,**export reliability**, and**global readiness**. These updates reduce manual work, remove workflow friction, and give users more control over how documents are viewed, edited, reconciled, and exported.

## **Scanned Document View in Reconciliation**

![](/_fern-img/93fb7f2e97e4378ab1482c037dae559b86ecd5ea4f60f5c4b1b68111ae3d83ce.webp)

During reconciliation, users had limited visibility into the original source documents and their related matches. Verifying values often required navigating away or manually locating documents, slowing down reconciliation and increasing error risk. To eliminate this, we've launched scanned document view in Reconciliation.

**How it works**

* A new **“eye” icon**is available under**Actions** in:

* Matches view

* Matches list

* Reconciled view

* Clicking the icon opens the **scanned document view**, showing:

* The anchor document (for example, Invoice)

* All related matching documents (for example, Purchase Orders, Delivery Orders)

* Supports:

* Zoom

* Edit

* Redirection to the specific document

* Multiple matching types are supported:

* Type 1: doc1, doc2, doc3 (thumbnail view)

* Type 2: doc1, doc2, doc3 (thumbnail view)

* Type 3 and beyond — up to **10 document types**

**Example:**
In a three-way match scenario (Invoice, Purchase Order, Delivery Order), users can view the invoice alongside all its matching POs and delivery orders in one place.

**Benefits**

* Faster reconciliation decisions
* Reduced context switching
* Easier validation of extracted and matched values

## **Sidebar Field Reordering in Custom Models**

Users previously had to rely on numbering field names to maintain sidebar order, making models harder to manage as they evolved. A new **reorder icon**is available in the sidebar field list for**custom models**

**Users can:**

* Open the sidebar field list popup
* Rearrange fields
* Save changes by clicking **Complete**

**Benefits**

* Sidebar order can evolve as models grow
* No need to rename or renumber fields
* Better usability during document editing

**Applicable Use Cases**

* Custom models with frequently changing fields
* Large models where field order impacts productivity

## Germany E-Invoice Support (Peppol integration)

In Germany and parts of Europe, invoices cannot be reliably ingested via email forwarding due to regulatory and technical constraints. Hence, Germany launched e-invoicing via PEPPOL. Staple AI quickly integrated with Peppol to help transfer the documents and stay compliant.

**How it works**

* Staple integrates with Peppol
* Invoices are received via the **Peppol network in XML**
* PO invoices, Non-PO invoices, credit notes and problematic invoices are then auto classified by Staple AI
* Traditional and hybrid invoices (PDF invoices with XML version attached) can be ingested by Staple AI through any channel and processed
* Acts as a compliant ingestion path for Germany e-invoices

**Benefits**

* Regulatory-compliant e-invoice ingestion
* Eliminates reliance on email forwarding
* Enables expansion across EU markets
* Completely cuts down data entry and classification efforts.

## **Edit Document Page Layout Preference**

![](/_fern-img/81a2d8d307c4653870caeba3427d8fe117f34e63acd05f630853a67d9b723385.webp)

Users working with complex tables had to repeatedly close or switch panels to reach their preferred view, slowing down document editing. A new **queue-level preference** allows users to define how the Edit Document page opens:

**Options:**

* Show sidebar panel first
* Show table panel first
* Show both sidebar and table panel

Configured via:
**Queue Settings → Preferences → Edit Document Page Layout**

**Benefits**

* Faster access to the most relevant panel
* Reduced repetitive UI actions
* Improved editing experience for complex documents

## **Product Localisation**

Global teams were forced to use the platform in English, limiting adoption and usability in non-English regions. Henceforth, they can use Staple AI in their native language.

**How it works**

* Full frontend migration to an i18n framework

* Supported languages:

* English (US/UK)

* Simplified Chinese (zh-CN)

* Japanese (ja-JP)

* All UI text replaced with translation keys

* Locale-specific date and time formatting

**Benefits**

* Users work in their preferred language
* Better usability for international teams
* Supports expansion in China and Japan

**Applicable Use Cases**

* Multi-country finance and operations teams
* AP teams operating in local languages

## **Move Documents Between Received and Uploaded States**

![](/_fern-img/d07b4e96f11938b8f1e63c98a862458cea47c9ef8738a8fdbb42924c9ab484c1.webp)

Document intake states were rigid, limiting flexibility when users needed to correct where documents sat in the workflow.

**How it works**

* New option to **set default intake state to “Received”**

* Users can:

* Move documents from **Received → Uploaded**

* Move documents from **Uploaded → Received**

* Documents in the Uploaded tab can now be **deleted**

**Benefits**

* More control over document intake flow
* Easier correction of ingestion mistakes
* Cleaner queue management

## Minor enhancements

#### **Automatic Export for Manually Completed Documents**

**Automatic export previously:**

* Did not trigger for documents manually moved to Completed
* Required a confusing completeness ≥100% check

This caused operational friction and manual exports.

**How it works now:**

* Documents moved to **Completed** (manually or automatically) are now eligible for auto-export
* Completeness checks are removed
* Export triggers when Auto-export is enabled

#### **QR Code Scanning (Size-Agnostic)**

![](/_fern-img/f27e807555516fa64470904d567f2c30aef1f0b751e5b98449ecebc74b5529fa.webp)

Small or irregularly sized QR codes were not reliably scanned. QR codes are now scanned **regardless of size**

* Improved data capture accuracy
* Better support for logistics and shipping documents

## December '25

**December’s release focuses on speed, accuracy, and control across the document lifecycle.** This update makes it easier to find documents instantly, gives teams more flexibility when working with complex data and mappings, and ensures that user edits are consistently respected across scanning, reconciliation, search, and downstream systems. Together, these enhancements reduce manual effort, improve traceability, and help teams move through reconciliation with greater confidence.

## Search by Document ID

Finding a specific document just got faster.

![](/_fern-img/cd5e0c41e55cfa98090d57f68db4606d8b7e4eed9f1c03181707c5016a278bfd.webp)

You can now search using **Document ID**(a system-generated unique identifier) in both the**Scanning page**and the**Advanced Search page**. This is especially useful when you already have a document ID from an API, email, support ticket, or audit trail.

**What’s included**

* **Scanning page search bar** now supports Document ID, alongside file name and company name.
* **Advanced Search** includes a new *Document ID* field that works across queues.
* Supports **partial and case‑insensitive search**.
* If the ID is unique, only the matching document is returned.
* Search works seamlessly with existing filters and fields.

**Why it matters**

* Quickly locate a document without scrolling or guessing filters.
* Reduce back‑and‑forth with support when customers share document IDs.
* Easier audits and investigations using a single, reliable identifier.

*Note:* For now, Document ID is not added as a visible column on the scanning table, and search behavior remains within the selected tab (Received, Completed, etc.).

## User Edit Management & Order of Precedence

We’ve introduced a robust way to **track and prioritize user edits** made on the scanning screen, especially for documents processed using the data mapper.

When users edit extracted or mapped values, those edits are now treated as the **single source of truth** across the product.

**Order of precedence**
When displaying or exporting data, the system now follows this order:

1. Rescan (resets every data captured)
2. User edits (Data manually entered and saved by the user)
3. Set values (In queue automations, we can set constant values for required fields)
4. Data mapper values (data fetched from the master data)
5. IF values (data derived using the Intelligent feedback provided by user during scanning)
6. Extracted values (data captured by Staple AI during scanning)

**What’s included**

* User edits are clearly identified and tracked for data‑mapper‑related fields. Therefore,

* Changes made during data extraction automatically reflect in the matching and reconciliation screens.

* Regardless of whether the extracted data is in English or in the document’s original language, user edits are reflected consistently across both versions.

* Display, exports and APIs all reflect user‑edited values consistently.

* In the queue search as well as advanced search, users can search using the edited value.

* Assuming, a field during scanning has multiple matches from the master data, the user can always pick the right match from the dropdown for each field.

* Edited values always override extracted, matched, or system‑generated values.

* Edits are saved only when the user clicks **Complete**.

* Unsaved edits are discarded on refresh, rescan, logout, or tab close.

**Why it matters**

* Users stay in control and system logic never silently overwrites their changes.
* Data mapper logic can safely re‑run using user‑provided corrections.
* Consistent values across UI, exports, downloads, and downstream systems.
* Easier debugging when investigating document changes.

## Direct document access from the Reconciliation screen

* A new **Document** link is available on the Matches page, allowing users to open the source document directly.
* This removes the need to copy the file name and search manually.

![](/_fern-img/9b084f0bc9fba9869d1b405741093cdad89630f3030e91efba8f54dcd28ec424.webp)

## Other product enhancements

### **Reconciliation supports all complex table types**

Reconciliation now handles all complex table types. Previously, only select table structures were supported; all table variants are now fully supported in Recon.

### **Mapped data flows into Reconciliation**

* Mapped values, including **user-edited values**, now flow into the Reconciliation page. Earlier, edits didn't flow into Recon.
* Any edits made during scanning are reflected consistently in Recon.

### **Last reconciled date**

* A new field shows **when a document was last reconciled**, making it easier to track reconciliation activity.

![](/_fern-img/389effd2f84e79f2a6af60992699a05a3cb240520bfd8f2cff5711dd531798dc.webp)

### Data Mapper Rule Limit Increased

We’ve increased the **data mapper rule limit per queue from 7 to 15**.

This change is driven by e‑invoicing and complex document scenarios where more fields need to be mapped reliably.

**What’s included**

* Each queue can now support up to **15 data mapper rules**.
* No changes required to existing rules, current setups continue to work as before.

**Why it matters**

* Greater flexibility for complex invoice formats.
* Better coverage for country‑specific and regulatory data requirements.
* Fewer workarounds when mapping large or detailed documents.

As always, these updates are live for all customers. If you have feedback or want to see related enhancements next, please eor your Staple AI contact.

## November '25

### What's new this month?

This month’s updates focus on giving you more control, accuracy, and security across your reconciliation workflows. From multi-key document matching to force-unmatch capabilities and expanded reporting categories, each enhancement is designed to make Staple AI more reliable in real-world, high-volume operations. We’ve also added OAuth2.0 support for enterprise webhook delivery, helping teams meet stricter security requirements without changing existing workflows.

## **Force Unmatch (Manual Removal of Incorrect Matches)**

When fuzzy matching fails, or when no unique match is found based on the business rules due to insufficient data, we may need to use Force Unmatch.

You can now manually **remove incorrect matches**during reconciliation. If the system auto-matches two lines that don’t actually belong together, you can override it with a single action. The new**Force Unmatch** option lets you break a match created by the reconciliation engine.

This is useful when:

* A line was matched to the wrong PO or GRN
* Vendor-provided documents contain inconsistent references
* You want to clean up a match without changing your rules

Once removed, the match is **blocked from appearing again**unless you reconfigure it. Once a match is removed, the system immediately**re-runs reconciliation** for that document, ensuring your view stays consistent.  Reach out to us at [support@staple.io](mailto:support@staple.io) to setup it up for you.

## **Multi-Key Document Matching**

You can now configure document matching using **multiple fields instead of a single key**, allowing far more accurate reconciliation across documents such as invoices, POs, GRNs, and delivery notes.

This update is especially useful when a single identifier isn’t enough to guarantee a correct match. Reach out to us at [support@staple.io](mailto:support@staple.io) to setup it up for you.

![](/_fern-img/c230b2c2887fe75a7e7c1dd4f3fc391a9af335a41a9c96116128838a3f2e49d0.webp)

#####

##### **How do we do it: Support for AND / OR conditions**

You can specify whether the system should match documents only when **all**conditions meet (AND) or**any** of the selected fields match (OR).

This gives you more control over how strict or flexible the matching rules should be.

Eg, in three way matching (Invoice vs multiple purchase orders vs Delivery note)

You can now combine fields such as:

* **PO Number + Vendor ID**
* **Invoice Number + Date + Total Amount**
* **Item Code + SKU + Location**

This reduces mismatches and improves accuracy in reconciliation-heavy workflows. Reach out to us at [support@staple.io](mailto:support@staple.io) to setup it up for you.

## **Scanning List View with Row Count Preference**

You can now choose how many documents you want to see at once in the **Scanning page list view**. Your selection is saved automatically and applied across all your scanning queues.

![](/_fern-img/30bc5e53076ff063f0e665a131bce73427fb244bd2a216438b5e8f83784c89e4.webp)

**Default Setting:**
The list view loads **50 rows** by default.

**To Change the Row Count:**

1. Go to any **Scanning** queue
2. Scroll to the bottom of the list view
3. Open the **Row Count Selector**
4. Choose from: **10, 50, 100, or 200**
5. A confirmation message appears immediately
6. Your preference is saved automatically

**Tips**

**Performance:**
Higher row counts (100–200) may take slightly longer to load, but give a better overview of your queue.

**Consistency:**
Your choice instantly applies to all scanning queues for a uniform experience.

**Confirmation:**
A success message appears each time you update your setting.

## **Expanded Document Counter Categories**

We’ve extended the Document Counter inside Staple Chat to support three additional document statuses: *Failed to Export*, *Rejected*, and *Removed*. These new categories help teams generate complete status-level reporting without disrupting the existing flow.

![](/_fern-img/1fc01081a39c347b71ed3e9a19e7a48b7ef587d2ffc83454a906515b7ddc7813.webp)

**New Status Categories:**

You’ll now see three new options when you use the Document Counter:

* **Documents that failed to export**
* **Documents that were rejected**
* **Documents that were removed**

These appear alongside your existing status options and follow the same selection flow (Queues → Time Range → Report Type).

This works across all queue selections and date ranges, including predefined options like “Last 7 Days” or “This Month.”

## **OAuth2.0 Authentication for Company-Level Webhooks**

We’ve introduced support for **OAuth2.0 Client Credentials** authentication for inbound webhook requests, enabling secure delivery of events to enterprise-grade endpoints.

##### **Why This Matters?**

Organizations with strict security requirements can now ensure that all webhook calls from Staple:

* Originate from authenticated sources
* Carry valid OAuth2.0 tokens
* Meet enterprise security compliance standards

##### **How It Works?**

Once OAuth2.0 is set up for your company:

1. Staple requests an access token from your authentication endpoint
2. The token is generated using the Client Credentials flow
3. Staple attaches the token to all outgoing webhook requests using:
   `Authorization: Bearer {access_token}`
4. Your system validates and processes the event securely

##### **What You Need to Provide?**

Share these details with the Staple AI team:

* Auth validation endpoint URL
* Tenant ID
* Audience
* Client ID
* Client Secret

Reach out to us at [support@staple.io](mailto:support@staple.io) to setup it up for you.

## October '25

This month, we’ve focused on making document handling more visual and intuitive, simplifying complex table workflows, and strengthening audit data security. Below are the new features and enhancements rolled out in October.

## Document Editor: control before processing

Ever opened a single file and found ten different documents inside?

Two invoices, eight purchase orders, a couple of delivery orders… all bundled together like a mystery box.

Every large enterprise faces this challenge: messy, multi-type documents that need to be split, rotated, renamed, and sent to the correct queues before processing can even begin. And, every industry faces them with documents from claims to contracts, from financial documents to KYC docs.

That’s exactly what the **Document Editor** in Staple AI fixes.

With Document Editor, you can:

* **Split** a large file into multiple documents (e.g., invoices, POs, and DOs).
* **Merge** pages across different documents.
* **Rotate, flip, and reorder** pages, all before scanning.
* **Auto-route** each document to the right queue (Invoice, PO, DO, etc.).

It’s like giving your document workflow a pair of hands and a brain. No more manual sorting. No more re-uploading. Just upload once, edit visually, and let AI handle the rest. In short, you control how your documents look before they even reach processing.

## Complex table types, better grouping, faster extraction

Multiple varieties of tables in the same dataset? No problem.

What it does

* **Group tables by type** so all tables of the same kind are listed together.
* **Create / edit categories on the fly** during scanning.
* **Smart fill:** with one click, extract data from tables in new documents using the same type rules.

Why it matters: Saves time when you have mixed table formats and speeds up bulk processing. Less manual mapping, fewer missed rows.

## Product enhancement releases

#### Complex table redirection, see exactly where feedback came from

![](/_fern-img/db23dabb72974ffaea7dc91362cbe04252695353b7db4eb10a0746370fea09f2.webp)

Values in a complex table sometimes change because of feedback from another document. Users saw the change and assumed it was an accuracy bug, but the change was intentional and came from a specific source document. There was no simple way to see which document caused the update.

What we changed

* When you investigate a feedback-driven change in a complex table, you’re now **redirected to the exact source document and page** that provided the feedback.

Why it matters

* Stops false “accuracy issue” tickets.
* Gives users clarity on why a value changed.
* Cuts time spent investigating and reduces unnecessary support overhead.

Success signals we’re tracking

* Fewer complaints about unexplained table changes.
* Faster investigation times.
* Improved user clarity on why values changed.

#### Audit link expiry, shorter, safer access to audit data

Audit download links were valid for 48 hours. That’s more time than we want audit data to remain accessible, and it increases security and compliance risk.

What we changed

* Audit download URLs now **expire after 30 minutes**.
* Emails that contain audit links now explicitly state the 30-minute expiry.

Why it matters

* Reduces the window during which sensitive audit data can be accessed.
* Lowers compliance and security risk for customers who share audit exports.

How it behaves

* When you request an audit export, the generated URL will be valid for 30 minutes only.
* The download email will mention the 30-minute expiry so recipients know the timeframe.

Availability: Live

#### 3. (Misc) Performance and UX tweaks, faster screens, steadier flows

What we changed

* Small but meaningful screen-load optimizations across the app so pages feel snappier.
* UI clarifications in complex table workflows and audit dialogs to reduce confusion.

Why it matters

* Faster page loads = less waiting, higher team throughput, and fewer interruptions during busy workflows.

Need help or want a walkthrough?

If you’d like these features enabled or want a quick demo for your team, contact [**hello@staple.ai**](). We’ll help you get things set up and walk through any changes using your real documents.

## September '25

We’ve rolled out several exciting updates this month to help teams work more efficiently across reconciliation, master data management, and document processing rules.

## **Reconciliation by Staple AI: Identify mismatches while you sleep**

Automate data reconciliation across multiple documents and instantly spot mismatches. Staple AI now supports full-cycle reconciliation for enterprises dealing with complex document workflows. From invoices and purchase orders to delivery orders and financial statements, reconcile any document type.

#### **What’s new?**

* **Multi-document matching:** Automatically match one document to many others using anchor fields such as PO number or item code.
* **Line item reconciliation:** Compare quantities and values across multiple documents based on configurable line-item logic.
* **AI-powered flexibility:** Apply fuzzy logic, thresholds, and force-matching to handle real-world data inconsistencies.
* **End-to-end export:** Push verified data directly into your ERP, RPA, or accounting system for consistent reporting.

#### **Why it matters?**

Say goodbye to manual checks. Automate reconciliations 24/7 and ensure compliance with minimal effort. Would you like to automate reconciliation? reach out to us at [hello@staple.io](https://hello@staple.io).

## **Master Data Mapping by Staple AI**

A next-gen Master Data Management Engine. Map your master data to extracted document fields and export seamlessly to your business systems, all without manual effort.

#### **What’s new?**

* **Multi-sheet support:** Upload and manage up to 10 master data sheets simultaneously.
* **AI-driven matching:** Match records using exact, fuzzy, or semantic logic.
* **Organization-level storage:** Reuse uploaded data across multiple queues.
* **API controls:** Refresh or override mapped fields as needed.
* **Error-free exports:** Automatically sync mapped data with your ERP.

#### Map and review header master data

![Map and review header master data](/_fern-img/0901a02412e099e72a4730c7017663d3a2df140723e3b0c12905f9bf9f111faf.webp)

#### Map and review table master data

![Map and review table master data](/_fern-img/61d1b208814a2a838d5654326324c11f2be1e1d4c123b9924a058b6b8ae2ecfa.webp)

#### Real world use cases - versatile solution for enterprises

![master data mapping](/_fern-img/c95365e8ce5b2095fea4712cd46bdfcc941661ce8682082ffbf5d9e0216e34f2.webp)

#### **Why it matters?**

Simplify vendor, SKU, and cost centre mapping while eliminating redundant uploads. Faster data alignment, fewer mismatches.

## **Label Rules Enhancements**

New ‘Null’ Condition Check: You can now use a **‘null’ option** under label rule conditions to handle blank fields.

For example:*If the PO number field is empty, automatically send the document to "non PO invoice" queue for review.*

![](/_fern-img/cc5aef6b158d072fa919f5928f55877d9a005b89343d1fab3f4aa28255dd9d51.webp)

This enables smarter routing logic and ensures incomplete data is always flagged before processing.

## **Expanded File Format Support: .BMP Image Support**

Staple AI now supports **.bmp (bitmap)** file formats for scanning and processing. Upload bitmap images just like PDFs or JPGs and extract data with the same AI accuracy and speed.

##### **That’s all for this month!**

We’re continuously improving Staple AI to make automation smarter and simpler. If you have feedback or feature requests, reach out at [hello@staple.io]().

## August '25

This month, we’ve rolled out a set of updates to make Staple AI more flexible, secure, and easier to use. From new email integration options to faster screens and improved multilingual support, these enhancements are designed to help your team work more efficiently.

## **Custom Staple Email Integration**

#### Introducing custom inboxes (e.g., *[yourcompany@staple.io](mailto:yourcompany@staple.io)*).

* Now, each customer can configure and verify any email id to send documents to queues in Staple AI
* Previously, only the root accounts (email ids which have login access to Staple AI) were able to send documents to any queue in Staple AI
* Please reach out to us at [support@staple.io](mailto:support@staple.io) to enable custom inboxes in your organisation

This update improves both **flexibility**and**security** when using Staple AI with email.

![](/_fern-img/d1f54dc27fe4a819284a02c1b60baefd353e628c086ddd4f8b3b8b4197424a77.webp)

#### **Root account check**

You can now disable/enable root account check for the customer. (i.e) you can decide whether to receive documents sent from email ids of Staple AI users only or any email id configured using custom inboxes.

![](/_fern-img/3025b19f84c010a4c075609377461a0b0c52ec1107d3ef99b54c731c4f6c1c87.webp)

## **Email Notifications for Document Upload**

Trigger email notifications automatically to respective users upon success document upload

How to enable this feature?

* In the Labels module, choose the lable and go to edit section
* Under "Action" section, either create a new label or edit an existing "Mail a document" action

![](/_fern-img/fc74b3e1a343971f19a56573c977f2622137021d3046e99c1976cbe3e1b5e10e.webp)

Enable "Mail document to the uploader" checkbox

![](/_fern-img/17d77ddd312f38d31f83887fa6d4ec13b6c6673842d5070eebb71aef36903c37.webp)

## Other minor product enhancements

#### **API Font Preference Support**

We've implemented comprehensive multilingual font support for document received via APIs with two predefined font stacks: "default" (Noto Sans) for broad language support including European languages, and "cjk" (Noto Sans CJK) for Chinese, Japanese, and Korean content. This enhancement resolves rendering issues with European character sets that previously displayed missing glyphs

#### **Enhanced Model Description Character Limits**

We've increased character limits for model field descriptions from 512 to 1024 characters in custom model tagging pages, enabling more descriptive and accurate prompts for better model performance

#### Advance Ordering & IMDA Peppol Accreditation

We have extended our Access Point (AP) capabilities to support Advanced Ordering and SG BIS Order Balance documents, bringing our service in line with IMDA’s latest InvoiceNow requirements. This enhancement enables APs to send and receive five key document types—Order, Order Change, Order Cancellation, Order Response Advanced, and Order Balance while ensuring real-time XML validation, network interoperability across Peppol, and compliance with IMDA’s monthly reporting standards.

These updates strengthen Staple’s position as a trusted AP provider by ensuring readiness for IMDA’s September 30, 2025 compliance deadline and accreditation renewal on April 1, 2026. They also expand workflows beyond invoicing to cover purchase orders and balance tracking, improving B2G onboarding and ecosystem interoperability within Singapore’s nationwide digital invoicing initiative

#### Faster screens

Minor optimisations were done so that Staple AI screens load faster, improving your team's efficiency

## November '24

## View number of documents

The digits inside brackets (x) indicate the number of documents in each tab. The number will be immediately updated when the document movement actions are triggered such as moving to different status, moving to another queue, and removing documents.

![](/_fern-img/0e810181465d4c2585b5b4f36de70e902f2431253b9ef6b49691bd459324371c.webp)

## Open a document in a new tab

The system highlights the record that you are about to select in purple. Normally when you click anywhere on the record, the system will display the selected document in the current browser tab.

To open the document in a new browser tab, you can hover your cursor and click the arrow icon “\*Open in a new tab”.\*Once clicked, a new tab of the select document will appear in your browser.

![](/_fern-img/d0ffc30dd7100565cdd4087bb234c9e25d9654ed0c6ec3d4c0b0bfcc7bb93488.webp)

Alternatively, you can hover your cursor over the file name and press Ctrl + Left click. This approach also opens a new tab of the selected document in your browser.

![](/_fern-img/dbc0842839e9665e0eaded5c540070b83f66ecdbbbc9ede2616a5f68d59df107.webp)

**Also,** You can use Ctrl + Left click with several parts on the interface to open a new tab such as

* Queue name
* Received, Completed, Rejected, Failed to Export, Exported
* Match status column with “*Click to view matching*”
* Advance search results listing documents
* Template documents in Model
* Matching tuples

![](/_fern-img/5519da4c897c6793b5289666270b8b35d4cd8836ccf895576c211a9692a57bf6.webp)