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.
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:
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 to setup it up for you.
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 to setup it up for you.
.png)
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:
This reduces mismatches and improves accuracy in reconciliation-heavy workflows. Reach out to us at support@staple.io to setup it up for you.
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.
.png)
Default Setting:
The list view loads 50 rows by default.
To Change the Row Count:
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.
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.
.png)
New Status Categories:
You’ll now see three new options when you use the Document Counter:
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.”
We’ve introduced support for OAuth2.0 Client Credentials authentication for inbound webhook requests, enabling secure delivery of events to enterprise-grade endpoints.
Organizations with strict security requirements can now ensure that all webhook calls from Staple:
Once OAuth2.0 is set up for your company:
Authorization: Bearer {access_token}Share these details with the Staple AI team:
Reach out to us at support@staple.io to setup it up for you.
%201.png)