Document Analysis statuses

The Document Analysis lifecycle is really simple and consists of the following stages:

Status	Description	Recommended action
`pending`	The Document Analysis has been initiated.	Wait for the `status` to change.
`inconclusive`	The Document Analysis could not be completed, or only partial data were extracted from the Document. If a document doesn't match the expected `document_type`status will always be `failed`.	Check the uploaded file and request a new file to extract data from or manually add the missing data from a manual inspection of the document.
`failed`	At least one check failed or the `document_type` didn't match the expected `type`. For example the expected `first_name`, `last_name` didn't match the extracted value.	Check the document or the input info and request a new Document Analysis.
`done`	The Document Analysis was successful and all data fields were extracted.	Use the extract data to automate your process or reuse the extract data in another verification.

To learn more on how names are matched and better understand a failed status please follow our detailed guide here.

ℹ️
Billing
Unlike done and failed status, an inconclusive Document Analysis does not incur a charge.

Status codes

If the Document Analysis is failedor inconclusive the status codes can help diagnose the issue. A Document Analysis may include multiple reason codes.

STATUS: failed

Code	Type	Description
DA_1001	Check issue	This status code is still emitted alongside more specific check-failure codes (e.g. DA_2001, DA_2002) for backward compatibility. New integrations should rely on the specific codes. At least, the `full_name` or the `income_year` extracted from the document doesn’t match the declared information (ie: the `match_level` between the extracted and expected data was `no_match`). Read the full Name Matching Rules guide.
DA_1002	Document issue	The document is expired. For`company_certificates, business_registration_certificates` we check that the document is at least 3 months old, on `driver_licence` we simply check that the expiration date.
DA_1003	Document issue	The uploaded document didn't match the expected : `document_type`. Check the value in `extracted_from_document.document_type`.
DA_1004	Document issue	We couldn't recognize the type of document.
DA_1100	Provider error	Error on provider side
DA_1201	Document issue	Image quality below minimum threshold
DA_1202	Document issue	PDF document contains annotations
DA_1301	Consistency issue	Holder first name not found in OCR
DA_1302	Consistency issue	Holder last name not found in OCR
DA_1303	Consistency issue	Holder first name initial(s) not found in OCR
DA_1304	Consistency issue	2D-Doc not found in document
DA_1401	Suspicious document	PDF document contains tampering signs
DA_1402	Suspicious document	2D-Doc not signed with trustworthy certificate
DA_2301	Consistency issue (tax notice)	Fiscal number not found in document
DA_1403	Suspicious document	2D-Doc and document type don't match
DA_2302	Consistency issue (tax notice)	Tax notice reference not found in document
DA_2001	Check issue	The `full_name` extracted from the document doesn’t match the declared information (ie: the `match_level` between the extracted and expected data was `no_match`). Read the full Name Matching Rules guide.
DA_2002	Check issue	The `income_year` extracted from the document doesn’t match the declared information (ie: the `match_level` between the extracted and expected data was `no_match`). Read the full Name Matching Rules guide.
DA_2401	Suspicious document (tax notice)	2D-Doc income year does not match
DA_2402	Suspicious document (tax notice)	2D-Doc reference income does not match

STATUS: inconclusive