Skip to main content
All CollectionsGetting Started
Getting started with the Trust Score during your Inscribe pilot
Getting started with the Trust Score during your Inscribe pilot

How to manage the trade-off between risk and operational efficiency

Daragh McMeel avatar
Written by Daragh McMeel
Updated over a week ago

Fully automating your document processing introduces a trade-off between operational efficiency and risk. Inscribe's pilot process is designed to help you manage that trade-off, and to understand how best to leverage Inscribe's automation capabilities to achieve your goals.

The Trust Score

The most important input to the decision of whether to automatically accept a document or not is Inscribe's Trust Score. The Trust Score is a numeric indicator of a document's trustworthiness. Documents with scores closer to 0 are more likely to have been tampered with, and documents with scores closer to 100 are less likely to have been tampered with.

Deciding how to interact with the Trust Score for the purposes of automation can depend on your use case and risk appetite. Some Inscribe customers choose to automate all their documents β€” any document with a Trust Score above a certain number is automatically accepted, all other documents are automatically rejected. Other Inscribe customers only choose to auto-accept β€” any document with a Trust Score above a certain number is accepted, all other documents get reviewed. And some customers choose not to automate any of their document volume, instead using Inscribe's fraud signals as an input to their decision process.

Whatever your automation goals are, Inscribe's web app is designed to make it as easy as possible to achieve them during your pilot.

Uploading and reviewing pilot documents

When you create your first Customer within the Inscribe app, you'll see four buckets as in the image below.

When you first start your pilot, all documents you upload will appear within the 'Requires Review' bucket. Clicking on a document will bring up the Document view, and show all evidence of fraud that Inscribe was able to identify during processing. To move a document out of 'Requires Review', simply apply a 'Rejected' or 'Accepted' status to indicate whether you wish to accept or reject the document.

When all documents have been moved from 'Requires Review', you can then set the status for the Customer.

By accepting or rejecting the documents uploaded during your pilot, you'll be able to track the performance of Inscribe's Trust Score in separating out good documents from bad.

Deciding when to auto-accept

Once you have you recorded a decision for each of your uploads, you can export your data in CSV format from the Customers page. For each document, this provides you with the Trust Score Inscribe assigned to the document, as well as the ultimate decision you recorded. This will allow you to identify if there is a suitable Trust Score threshold for auto-accepting your documents.

Depending on your desired outcomes, there are some questions you can consider to help with determining this threshold:

  • Do you have a target reduction in time spent reviewing documents? If you have an existing process in place that you want to make more efficient, you can choose a Trust Score threshold that will achieve those efficiencies. For example, to reduce manual review by 90%, choose a threshold low enough that 90% of documents were scored higher.

  • Do you have a target reduction in fraud? By considering the Trust Scores associated with documents you rejected, you can choose a threshold that keeps the target proportion of fraud out.

Setting your auto-accept criteria

By default, all documents uploaded appear in the manual review filter bucket. To begin auto-accepting documents, you need to create a Check that interacts with a document's Trust Score.

Checks can also be used to validate other properties of a document, such as document type, recency, quality, and more. You can also properties of a document to choose which Checks to apply. For example, you can use Checks to apply a different Trust Score threshold to utility bills and bank statements. If all Checks applied to a document pass, and at least one Check interacts with the document's Trust Score, the document will be auto-accepted. Otherwise, the document will be marked as requiring review.

An example Check is shown above. The document filter is configured so that it only applies to documents classified as bank statements. If this is the only Check present in your workspace, then bank statements will be auto-accepted if they have a Trust Score above 90, and will otherwise be marked for review. All other documents will be marked for review regardless of Trust Score.

Did this answer your question?