---
sourceDocument: Australia Public Sector
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/government-industry

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Public Sector

ft:clusterId :

    - gvin

bundleId :

    - gvin

workflow :

    - Customer and Industry


---

# Work on a document verification task

# Work on a document verification task {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Document verification tasks are individual tasks for an applicant to upload a single document.

## Antes de Iniciar

Role required: admin, sn_doc_processor.agent​

## Por Que e Quando Desempenhar Esta Tarefa

Each individual DVT component represents one individual document verification task record. "Document verification task" is a table available in the doc processor plugin similar to a case task. The Document verification task
table stores all the document verification tasks in an instance. This table extends the Task \[task\] table.

The task falls upon the applicant to upload a document that matches a specific document category. The category seen above is Proof of identity. Initially, the task state is "not submitted". The category seen above is Proof of
identity. Initially, the task state is "not submitted".

This is what a document verification task looks like within the ServiceNow platform. You can see fields such as the document category and state reflected here. You can navigate to the list of DVTs by going to **Document
Processor \> Document Verification \> All** in the "All" menu in platform. Alternatively, you can search sn_doc_processor_verification_task.list. Also notice the document for field represents the applicant the task is
assigned to.

Again, each individual DVT component represents one of these document verification tasks. Once the applicant uploads a file, the state is changed to submitted and the file is linked to the task. The upload button in the
component turns into a trash can, in which the applicant can delete the attachment if they so choose. They can also click the link to view the attachment.

DVT components are nested within GDVT (Grouped Document Verification Tasks) components. This component groups a set of DVT components by the assigned applicant.

The Upload Documents / Provide Credentials activities are case tasks assigned to the applicant that use the grouped DVT component in the activity UI. They appear next to each other under Intake stage in Workflow Studio.

You can decide which documents show up in these activities. These are determined by document categories (sn_doc_processor_category). Out of box, the Upload Documents activity displays the "Proof of identity" document
category. To edit categories, see [Create and define document categories in Public Sector Digital Services](https://servicenow-prod.fluidtopics.net/tkFKr_pAcWS12MRhGVDg6A "Define document categories to categorize the different document types that can be submitted by applicants using the Government Service Portal across various Public Sector Digital Services applications.").

## Procedimento

1. Navigate to Financial Services OperationsWorkspace.
2. Select the lists icon (![dynamic related records icon.]()).
3. In the Lists tab, under Document verification, open the task list.
   * For your assigned tasks, select Assigned to me.
   * For all document verification tasks, select All.
   {#psds-using-doc-processor-doc-verification-task__choices_xbp_ycm_gmb}
4. In the list, select the document verification task that you want to work on.  
   To work on a verification task that is not assigned to you yet, assign it to yourself by selecting Assign to me.
5. Verify the completeness of all documents that are submitted.  
   If a document has been processed through OCR, you can select Open in DocIntel to review the document and update document field values, or check the Field values tab to review extracted document field values. For more information, see .
6. **Opcional:** From the Notes and Activity tab in the Work notes field, enter any comments.
7. Select one of the following options.

   | Task | Action |
   | Verify | Select Verify if the document details are sufficient. |
   | Reject | You can reject a document verification task if the details are insufficient. 1. From the Rejection reason field, select the reason from the following options. * Information mismatch * Incorrect document * Expired document * Scanning issues * Fraudulent document {#psds-using-doc-processor-doc-verification-task__ul_vwy_dnj_3tb} 2. Select Reject. {#psds-using-doc-processor-doc-verification-task__ol_rts_lw2_rhc} |
   |-|-|

   {#psds-using-doc-processor-doc-verification-task__choicetable_t3f_5r1_wnb}
{#psds-using-doc-processor-doc-verification-task__steps_umb_5vp_shc}