Changelog

Documents waiting in review can now carry a deadline. Set a service-level target per workflow, and Tessera shows the time left on every card, sorts the queue by urgency, and escalates to a named backup reviewer when a document is within 20 percent of its limit.

• New deadline setting on each workflow, in hours or business hours.
• Escalation notifications by email or webhook (document.review_overdue).
• The review queue remembers your filters between sessions.

A score of 0.90 should mean that roughly nine in ten fields at that score are right. We rebuilt how scores are computed so they track that promise on every workflow, and added a calibration chart to each workflow’s settings so you can check it yourself.

• Scores are recalibrated nightly from reviewer corrections on your own workflow.
• Fixed a case where date fields written as 03/04/26 were scored high when the day and month order was ambiguous. They now drop below the default threshold unless your schema sets a locale.

Accounts payable workflows can now compare extracted bank accounts with your vendor master. A mismatch is always held for review, regardless of the confidence score, and the vendor owner is notified.

• Upload the vendor master as a CSV or sync it by API.
• Account numbers are stored hashed for comparison; the master file itself is encrypted at rest.
• New rule condition bank_account.matches_vendor.

POST /v1/batches accepts up to 500 documents in one call and returns a batch id you can poll or subscribe to. Idempotency keys are now supported on every write endpoint so a retried upload never creates a duplicate.

• New batch.completed webhook event.
• Webhook delivery retries now back off for up to 24 hours instead of 6.
• Fixed pagination of GET /v1/documents when two documents shared a timestamp.

Upload your preferred and fallback wording for a clause type, and Tessera classifies each contract’s clause as matching, a known fallback, or different. Differences are held for counsel with both texts side by side and the changed phrases marked.

• Playbooks are versioned. Every classification records the playbook version it used.
• Amendments are read in the context of their parent agreement.

New workspaces choose where their data lives: United States or European Union. Documents, extracted results, review activity and the audit log stay in the chosen region.

• Region is fixed at workspace creation. Moving a workspace is a managed migration; contact us.
• Zero-retention mode is now available on every plan that includes retention settings.

The review lane is now fully keyboard-driven. Confirm a value with Enter, edit with E, skip with S, and move between held fields with the arrow keys. A short tour appears on first use.

• Fixed a bug where the zoomed page region reset after saving a correction.
• Reviewer sessions now time out after 30 minutes of inactivity, configurable per workspace.

Version 2.0 introduces the routing engine. Describe what should happen to a document in conditions and actions: if the total is above 25,000, send to the director queue; if the PO matches, post to the ledger. Rules are evaluated in order, tested against sample documents before they go live, and every decision is written to the audit log.

• Actions: route to queue, post to integration, request a document, hold for review, reject.
• Dry-run mode shows what a rule would have done to the last 500 documents.