---
sourceDocument: Australia Financial Services Operations
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/financial-services-operations

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Document Processor workflows

# Document Processor workflows {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The Financial Services
Document Processor application installs automated workflows for enabling document collection and verification.

## Workflows available with the application {#document-processor-workflows__section_gr5_mlw_vnb}

The following predefined workflows for Document Processor are available with the application.{#document-processor-workflows__section_gr5_mlw_vnb__entry__1}

| Document Processor workflows |
|-|
| Deferred Document Followup |
| Exception Document Approval |
| Generate DocIntel Field |
| Generate DocIntel Document task |
| Generate DocIntel Use case |
[Tabelle : 1. Predefined workflows for Document Processor]

These workflows are built using [Flow Designer](https://www.servicenow.com/docs/access?context=flow-designer&version=australia&pubname=australia-application-development&ft:locale=en-US). The application admin can review and customize these predefined flows that are based on the business needs of an organization.

## General workflow for Document Processor {#document-processor-workflows__section_pwy_vhf_tnb}

Document Processor determines the documents that are required in a workflow in a Financial Services Operations (FSO) application. If
any documents must be verified, a document verification task is automatically generated for a
document agent.  
The following is a typical loan workflow in the Financial Services Loan Operations application.  
Hinweis:  
Depending on the request type, individual workflows might have additional or fewer tasks.

1. The document processor determines the documents that are required. If any documents must be verified, a document verification task is generated for the document collector or agent.
2. The document processor looks up existing documents that have already been verified.
3. A document collector collects the required customer documents and submits the documents for verification, or requests an exception or deferral for specified documents.
4. A document verification task is generated.
5. A document agent manually verifies or rejects the document, or approves or rejects an exception or deferral request.  
   Hinweis:  
   For documents specified to required OCR processing, Document Intelligence can automatically extract data and verify a document if the extracted data attributes are sufficiently provided. For more information, see [Integrating with Document Intelligence](https://servicenow-prod.fluidtopics.net/d8s_8koMqKzcIq8gWQ~6tQ "Integration with Document Intelligence enables machine learning (ML) to assist in quickly automating document processing and accurately extracting information from documents to the ServiceNow AI Platform.").