Document Report Instant
Start here
This guide presents a technical overview of Entrust's Document Report Instant solution, available for integration through Workflow Studio and the Entrust IDV SDKs.
Introduction
Document Report Instant is Entrust's next-generation, fully automated identity document verification solution, designed to deliver fast, accurate and reliable results for identity verification and document validation.
The solution's full automation ensures that 95% of Document Report Instant results are returned in under five seconds. At the same time, eliminating human intervention enhances privacy for compliance purposes as identity documents are not manually reviewed.
Document Report Instant also introduces a simplified hierarchy of breakdowns and sub-breakdowns, making report results easier to interpret and ensuring that appropriate actions are clearer based on report results.
The full list of identity documents currently supported by Document Report Instant can be found here.
Document Report Instant breakdowns and sub-breakdowns
The results of a Document Report Instant are generated in the form of breakdowns and sub-breakdowns, with an overall result of clear or consider.
The complexity of the breakdown hierarchy of a Document Report Instant has been significantly reduced when compared to that of the standard Document Report. Certain breakdowns have either been merged, reclassified, replaced or removed to ensure that report results are easier to interpret and act upon. This simplified taxonomy also enables greater flexibility to configure tailored workflows catering for specific verification needs.
Document Report Instant breakdowns are divided into four main categories:
- Media capture: verifying the presence and quality of an identity document
- Document validation: ensuring the identity document is supported and valid
- Fraud analysis: ensuring authenticity, data consistency and format verification
- Applicant validation: verifying the minimum age of an applicant
These Document Report Instant breakdowns and sub-breakdowns are described in the table below:
| Breakdown | Sub-breakdown | Reasons / Properties | Description |
|---|---|---|---|
| Applicant validation | Minimum accepted age | - | The minimum accepted age, configureable at account level. |
| Fraud analysis | Data format | Gender | Asserts whether extracted data matches the expected format. |
| Data format | Date of birth | Asserts whether extracted data matches the expected format. | |
| Data format | Document number | Asserts whether extracted data matches the expected format. | |
| Data format | Expiry number | Asserts whether extracted data matches the expected format. | |
| Data format | MRZ | Asserts whether extracted data matches the expected format. | |
| Data format | Barcode | Flags when the barcode rows and columns don't match the expected structure. | |
| Data consistency | Date of expiry | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Document type | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Nationality | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Issuing country | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Document number | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Gender | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | First name | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Last name | Flags document data that does not match the MRZ/barcode data. | |
| Data consistency | Date of birth | Flags document data that does not match the MRZ/barcode data. | |
| Visual authenticity | - | Flags when the document has been tampered with. | |
| Repeat attempts screening | - | Flags if Entrust has previously seen this document being used in a suspicious way. | |
| NFC authenticity | NFC passive authenticity | Asserts whether the NFC chip has been tampered with. | |
| NFC authenticity | NFC active authenticity | Asserts whether the NFC chip is cloned. | |
| Document validation | Document condition | - | Asserts whether the document has been damaged, preventing data extraction. |
| Expiry date current | - | Asserts whether the document is expired. | |
| Supported document | Entrust supported document | Flags when the document provided is not supported by Entrust. | |
| Supported document | Sanctions screening | Flags that the document's issuing country is subject to sanctions. | |
| Supported document | Configuration supported document | Flags when the document is not supported by the customer's configuration. | |
| Media capture | Media present | Document present | The images provided don't contain a document. |
| Media present | Single document provided | Flags when more than one document has been provided (only a single document can be submitted). | |
| Media present | Front side present | Flags when the front side of the document is missing. | |
| Media present | Back side present | Flags when the back side of the document is missing. | |
| Data visibility | Image quality | Flags when data on the document is obscured by poor image quality. | |
| Data visibility | Document fully visible | Flags if a key data point on the document is obscured. | |
| Data visibility | Portrait present | Flags when a face cannot fully be detected on the document. | |
| Data visibility | Barcode read | Flags when the barcode is not present or successfully read. | |
| Physical document present | - | Asserts whether the document captured is a physical document rather than a digital version. |
Below is an example of the breakdowns and sub-breakdowns of a Document Report Instant, including all supported fields returned in the properties attribute:
1{2 "breakdown": {3 "applicant_validation": {4 "breakdown": {5 "minimum_accepted_age": {6 "result": "clear"7 }8 },9 "result": "clear"10 },11 "document_validation": {12 "breakdown": {13 "document_condition": {14 "result": "clear"15 },16 "expiry_date_current": {17 "result": "clear"18 },19 "supported_document": {20 "properties": {21 "configuration_supported_document": "clear",22 "entrust_supported_document": "clear",23 "sanctions_screening": "clear"24 },25 "result": "clear"26 }27 },28 "result": "clear"29 },30 "fraud_analysis": {31 "breakdown": {32 "data_consistency": {33 "properties": {34 "barcode": null,35 "date_of_birth": null,36 "date_of_expiry": null,37 "document_number": null,38 "document_type": "clear",39 "first_name": null,40 "gender": null,41 "issuing_country": "clear",42 "last_name": null,43 "nationality": null44 },45 "result": "clear"46 },47 "data_format": {48 "properties": {49 "date_of_birth": "clear",50 "date_of_expiry": "consider",51 "document_number": "consider",52 "gender": "clear",53 "mrz": "consider"54 },55 "result": "consider"56 },57 "nfc_authenticity": {58 "properties": {59 "nfc_active_authenticity": null,60 "nfc_passive_authenticity": null61 },62 "result": null63 },64 "repeat_attempts_screening": {65 "result": "clear"66 },67 "visual_authenticity": {68 "result": "clear"69 }70 },71 "result": "consider"72 },73 "media_capture": {74 "breakdown": {75 "data_visibility": {76 "properties": {77 "document_fully_visible": "clear",78 "image_quality": "clear",79 "portrait_present": "clear"80 },81 "result": "clear"82 },83 "media_present": {84 "properties": {85 "back_side_present": "clear",86 "document_present": "clear",87 "front_side_present": "clear",88 "single_document_provided": null89 },90 "result": "clear"91 },92 "physical_document_present": {93 "result": "clear"94 }95 },96 "result": "clear"97 }98 },99 "properties": {100 "first_name": "JOHN",101 "last_name": "DOE",102 "document_number": "123XYZ297",103 "personal_number": "12374AC2",104 "middle_name": "WILLIAM",105 "passport_number": "12398CYB",106 "gender": "Male",107 "driving_licence": "1281293YZA",108 "nationality": "GBR",109 "date_of_expiry": "2028-12-18",110 "place_of_birth": "CONVENTRY",111 "issuing_date": "2010-12-21",112 "date_of_birth": "1990-08-15",113 "issuing_authority": "DVLA",114 "alias_name": "WILLIAM",115 "spouse_name": "SMITH",116 "widow_name": "WASHINGTON",117 "real_id_compliance": false,118 "document_type": "driving_licence",119 "issuing_country": "USA",120 "issuing_state": "AZ"121 },122 "repeat_attempts": {123 "attempts_clear_rate": 0,124 "attempts_count": 1,125 "media_info": [126 {127 "checksum_sha256": "A47qazoDSGe+DgNYHxn2s9S0hEQm11yvITFy77kctx8=",128 "id": "1f9bf798-2f19-4af1-82e0-6037b9dff1a4",129 "type": "document_photo"130 },131 {132 "checksum_sha256": "GXTtyBWjsUvUZNWgcl3e/K+YzaBOnzZnAeDh7TT5NyY=",133 "id": "8270a02c-c0a8-4223-bccf-7987272dd93c",134 "type": "document_photo"135 }136 ],137 "media_uuids": [138 "1f9bf798-2f19-4af1-82e0-6037b9dff1a4",139 "8270a02c-c0a8-4223-bccf-7987272dd93c"140 ],141 "repeat_attempts": [],142 "task_id": "document_check_fully_auto_08e10",143 "unique_mismatches_count": 0,144 "workflow_run_uuid": "8d2503de-ae28-4189-b983-522af20fb62c"145 },146 "result": "consider"147}
For customers migrating from a Document Report integration to Document Report Instant, you will find a complete one-to-one comparison between breakdowns and sub-breakdowns in our migration guide.
Document Report Instant task
To run a Document Report Instant, a Document Report Instant task should be added to a Studio workflow from the Workflow Builder.
When constructing a Studio workflow, a Document Report Instant task must always follow the route of a Document Capture task in order to extract the appropriate input data. Input data for this task can also be received from the workflow input data or an Autofill task. It's important to note that document capture for Document Report Instant is only available through the Entrust IDV SDKs and not direct upload via API.
Below you will find an illustrated example of a Studio workflow running a Document report:

Document Report Instant task results
To obtain the specific outputs from the Document Report Instant task via the Entrust Identity Verification API (for example, the overall report result or breakdown results), you can manage this by configuring the Workflow Output in the Studio Workflow Builder. You can also retrieve all associated output data from a Document Report Instant.
You can refer to our Studio product guide for more information on Workflow Output configuration. Once set up, the output can be consumed by making a Retrieve Workflow Run call to the API. Report results are found in the output property.
Workflow Run results can also be accessed on the results tab of your Studio Dashboard.


