Explainable Verification

Enterprise finance and risk teams cannot approve a number they cannot defend. When a value is read from a document by a model, the question an examiner asks is not whether the answer looks right, it is how the system arrived at it. Explainable Verification is how Staple answers that question for every field, not just for a sample.

Staple sits in the Trust Layer of the platform and records the reasoning behind each extracted value alongside the value itself, so a reviewer, an internal auditor, or an external examiner can reconstruct the decision months later.

Every Field Carries Its Own Confidence

Staple attaches a per-field confidence score to each value it reads. The default acceptance threshold is 0.9 on a strictly-greater cutoff and is configurable per queue, so a team can hold high-risk fields to a stricter bar than descriptive ones. Confidence is produced during data extraction, not bolted on afterwards.

• Values above the threshold pass through untouched.

• Values below it are routed to a reviewer with the reason attached.

• Inferred fields carry no confidence score, because they were reasoned about rather than read off the page, and QR-code-derived fields score 1.0.

Extracted, Inferred, Mapped, Or Set

Staple separates how each value came to exist, so a judgment is never presented as a fact lifted from the page. A value is labelled extracted (read from the document), inferred (reasoned from context), mapped (matched against master data), or set (a fixed rule value). An auditor can see at a glance which numbers are evidence and which are interpretation.

A Record You Can Reconstruct

Staple keeps a per-field audit trail: every state change in sequence with the source service, the model or rule that produced it, the reviewer, a timestamp, and the before-and-after value. Configurations, extraction models, and validation rules are versioned, so a result is explained against the exact logic in force when it was produced, not against today's settings. This connects directly to AI Contextual Verification and to the business rules and anomaly checks that flag values before they reach an approver.

Explainability is also why Staple carries ISO 42001, the AI management-systems standard, in its Trust Vault alongside SOC 2 Type II and ISO 27001. Certifications are evidence, not decoration.

What Explainable Verification Does Not Do

Staple explains and evidences the extraction and validation of data. It does not make the business decision for you. It will show why an invoice was flagged as anomalous, but a human still approves the payment. It records who approved a value, it does not replace the approver.

Evidence

Global investment bank

A global investment bank running back and middle office processing needed every reconciled figure to be defensible to internal audit across five countries. Staple recorded the source, model version, and reviewer behind each field and eliminated more than 800 document templates while holding accuracy at 99.6 percent.

99.6% field accuracy with a full per-field audit trail

Related Capabilities

• Data Integrity and Tamper Evidence

• Metastructured Data

• Audit Readiness

See Explainable Verification On Your Own Documents

Bring a batch of your own invoices, statements, or claims and we will show you the confidence, the reasoning, and the audit trail behind every field.

Book a demo