> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DocumentProcessing

> Column reference for the DocumentProcessing table, which records an ABBYY FlexiCapture document's processing events per stage, with timing and operator.

## <a id="start" />Purpose

Contains information about document processing events at the given stage.

[Diagram of relationships between Document editing details](/flexi-capture/reporting-service/reporting-db-document-editing)

## List of columns

<table width="100%"><tbody><tr><td><p><strong>Key</strong></p></td><td><p><strong>Name</strong></p></td><td><p><strong>Type</strong></p></td><td><p><strong>Required</strong></p></td><td><p><strong>Description</strong></p></td></tr><tr><td rowspan="2"><p>PK</p></td><td><p>DocumentProcessedDate</p></td><td><p>date</p></td><td><p>yes</p></td><td><p>The date when the document's status changed to "Processed."</p></td></tr><tr><td><p>ID</p></td><td><p>bigint</p></td><td><p>yes</p></td><td><p>Entry identifier.</p></td></tr><tr><td rowspan="12"> </td><td><p>DocumentId</p></td><td><p>bigint</p></td><td><p>yes</p></td><td><p>Document identifier. Corresponds to the entry identifier in the <a href="/flexi-capture/reporting-service/reporting-document">Document</a> table.</p></td></tr><tr><td><p>BeginDate</p></td><td><p>datetime</p></td><td><p>yes</p></td><td><p>The date and time when the document arrived at the given processing stage.</p></td></tr><tr><td><p>EndDate</p></td><td><p>datetime</p></td><td><p>yes</p></td><td><p>The date and time when the document was sent to the next stage.</p></td></tr><tr><td><p>EditingSecondsCount</p></td><td><p>int</p></td><td><p>yes</p></td><td><p>The total time (in seconds) spent on editing the document at the given stage.</p></td></tr><tr><td><p>HasAssemblingErrors</p></td><td><p>bit</p></td><td><p>yes</p></td><td><p>Whether the document has assembly errors.</p></td></tr><tr><td><p>HasFieldsForVerification</p></td><td><p>bit</p></td><td><p>yes</p></td><td><p>Whether the document has fields that require verification.</p></td></tr><tr><td><p>HasRulesErrors</p></td><td><p>bit</p></td><td><p>yes</p></td><td><p>Whether the document has rule errors.</p></td></tr><tr><td><p>Operator</p></td><td><p>nvarchar</p></td><td><p>yes</p></td><td><p>The name of the user.</p></td></tr><tr><td><p>OperatorID</p></td><td><p>int</p></td><td><p>no</p></td><td><p>User identifier.</p></td></tr><tr><td><p>ProcessingOrder</p></td><td><p>smallint</p></td><td><p>yes</p></td><td><p>The sequential number corresponding to the current state of the document (i.e. the state of its fields, its current processing stage, etc.). Each time the document is modified, a new record is created to reflect its "change of state" and the ProcessingOrder counter increments by 1.</p></td></tr><tr><td><p>StageName</p></td><td><p>nvarchar</p></td><td><p>yes</p></td><td><p>The name of the processing stage.</p></td></tr><tr><td><p>StageType</p></td><td><p>int</p></td><td><p>yes</p></td><td><p>The base type of a processing stage. For a predefined processing stage, it is identical to the processing stage type. For a custom processing stage, it corresponds to the predefined stage type that was used as a template to create the custom processing stage.</p></td></tr></tbody></table>